Posts Tagged ‘admin’

Current Problems

October 25, 2009

To date, there has been a widget in the right-hand column with the “current problems”. The original intention here was to have two per week. Of course, the original intention also involved some other authors.

I’m going to remove the “current problems” widget. I’ll still hope to do at least one problem per week.

Advertisements

Moving On

May 22, 2009

So, I was updating the sidebar links for next week’s problems, and looked ahead at the two after that as well, and thought, “We could easily do all of those in a week”. In my mind, one of them is trivial (lcm), and one is… extensive (factoring). That leaves two that seem pretty reasonable for a week (and, I hope, neither particularly difficult).

So let’s shoot for problems 3-6 next week. If I misjudged interest in these problems, we can always leave some on the bill for the following week as well.

Also, if you want to see messages like this in the future, about when the assignment gets updated, leave a comment below. Unless there’s some noteworthy change to the schedule, I’ll just keep updating the sidebar every Friday afternoon/evening (Saturday if it works out that way) without any more word on it.

Still on Problems 1 and 2

May 19, 2009

Yes, I know that I’ve been saying 2 problems per week, and we started early last week on problems 1 and 2. However, I thought some extra time on the first two problems would give everybody some time to get going. So I set the “Current Problems” to be problems 1 and 2, due this coming Friday (May 22). I, at least, still have things to say about problem 2 :). There’s a little widget in the right-hand sidebar of the blog with the “Current Problems”. I’ll change them after this Friday.

Please leave comments below answering the following question: Do you want me to write a post each time I change the “Current Problems”, or are you happy to just move to the next problems after the “Current Problems” “due date” as passed?

If you’re already done with the “Current Problems” any given week, feel free to go on ahead working on whatever. But if you do so, please refrain from posting solutions. Let’s try to stay, online anyway, at least a little bit together. If you’re ahead, I’d say it’s a good time to spend reading some documentation or something, like the various tutorials or whatever other references you find. If you find any nice references, please share. This reading might show you other ways to approach a problem you’ve already done, which would be helpful to see.

In the same spirit, though, after we get going, if you have something new to say about a previously “Current Problem”, feel free to write a post.

If you seriously disagree with this (or any other) “policy”, let’s talk it out in the comments below.

Hello, World

May 13, 2009

This blog is intended to contain the work of a collection of math graduate students at the University of Virginia as we learn Python (and/or Sage) by using projecteuler.net as a problem library. For those of us that need tutorials, the Python one is here, and Sage here. Surely lots of other documentation will be found and used (and linked to) in this process.

We will (at least, at the start) set two problems each week as our goal, the link in the sidebar giving which problems, and the “due date.” All of us are encouraged to post whatever we come up with as far as solutions, even if it is similar to an already posted solution. We should also feel free to post programming questions here, and any math questions or facts that we encounter while working on these problems. We should link to any pages we find helpful (programming resources, or math resources), and leave comments on each others posts whenever we are inspired to do so.

I encourage each author to tag each of their posts with their initials, so we can track authors. Presumably wordpress will also handle that for us, so we might drop this habit when we see how it all works. Also tag posts with the problem number, for example: use the tag “prob1” and “prob2”. Then all of the content for each problem can be quickly accessed. You might also consider giving your posts titles that indicate the author and the problem. Maybe also use the tag “math” if you talk about the math of a solution, “question” for questions you post, “misc” for other things? These are just ideas – do whatever makes sense to you at the time, and we’ll work it out.

If you are beaten to a solution, you may try gathering up some of the other contributor’s solutions to compare them, e.g. based on speed or generality or… It will also be fun to see what happens when different solutions claim different answers. If you modify a solution that you have already posted, e.g. to fix an error or something, start a new post (with links back), or add to your old post – do not remove content from your old posts. It’s instructive to see errors.

Let’s put all of our code in

# Preformatted Text
print "Hello, World!"

to distinguish it from other text. For authors new to wordpress, the button at the far right, at the top of the editor when you make a new post, gives more formatting options. This is where you will be able to set code as preformatted (and indented, if you chose to use it).

If any of the authors would like to mess around with more settings for this blog, they are welcome to email me, and I will change their status to administrator. Additionally, if authors have ideas about how to change how things are set up or run, they are welcome to just make a post so that everybody can see it (tag it “misc” or “admin” perhaps?). While I may have been the one to start this thing, I really want it to be a group project.

Well, that’s all I can think of for now. Happy hacking!