Announcements (Search)

Ratings reset

by bbi5291 on Jun 25, 2013 - 7:31:04 am UTC
  • (1/0)
I dropped all the ratings from old "contests" that were really just PEG exercises or imported contests. Ratings were recalculated based on the two public contests held on the Judge so far (one mock DWITE and one mock CCC). For most previously rated users this probably means you're no longer rated; in other cases your rating may have changed.

I hope to hold more contests on the Judge in the future.

Improved code editor

by bbi5291 on Jun 17, 2013 - 4:01:02 am UTC
  • (0/0)
Thanks to Robin Cheng (javic), the textarea on the submit page now supports tabs (if you have scripts enabled).

C++11 support

by bbi5291 on Jun 08, 2013 - 12:19:28 am UTC
  • (4/0)
gcc 4.8.1, released today, is the first major C++ compiler to support all C++11 language features. The PEG Judge now supports C++11 using gcc 4.8.1. To submit in C++11, just select the option at the bottom of the dropdown. C++11 has been enabled for all problems that support C++ (that is, all of them). Submissions tagged "C++" will continue to use the old compiler, gcc 4.1.3.

Top submitters

by bbi5291 on May 23, 2013 - 7:07:45 am UTC
  • (1/0)
Fun stats:
 
+-------------------------+------+
| username | cnt |
+-------------------------+------+
| Daniel | 8632 |
| SourSpinach | 4344 |
| Alex | 3455 |
| zhxl0903 | 3453 |
| Bob | 2698 |
| bleung91 | 2118 |
| dAedaL | 2045 |
| Logical1111 | 1707 |
| bbi5291 | 1451 |
| fyyaz | 1450 |
...

Note about logging in

by SourSpinach on May 12, 2013 - 11:33:07 am UTC
  • (1/0)
Before your first login with the PEG Judge hosted on its new server, you may need to clear your cache.

PEG Judge basic functionality now in place

by bbi5291 on May 12, 2013 - 5:16:34 am UTC
  • (1/1)
We've just migrated over from the previous server. Unfortunately, the last 6 months or so of submissions were lost. This is entirely my fault, so downvote away.

As usual, reply to this comment if you notice anything broken.

EDIT: Stop replying to this comment whenever you find a new bug. This was only supposed to be for bugs related to the migration. If you're just discovering them now, they're probably not in that category.

Report bugs

by bbi5291 on Jul 07, 2012 - 6:26:05 am UTC
  • (1/1)
I've decided to have PEG Judge bugs tracked on Launchpad (just so they'll all be in one place, as there are so many bugs that I can't remember them all).

If you've reported an issue in the past and it hasn't been fixed, report it here.

ACSL shortest code problems abolished

by bbi5291 on Feb 24, 2012 - 5:39:39 am UTC
  • (0/0)
for technical reasons. Any correct solution will now earn full points.

Problem description sidebar

by bbi5291 on Jan 13, 2012 - 3:52:30 am UTC
  • (2/0)
The div on the right-hand side of each problem description page has changed slightly. Now all the links are at the top and the info is at the bottom. Also, it shows you a list of languages that are allowed (because I wouldn't want anyone to write a solution and then try to submit it and find to their dismay that their effort was wasted because the language isn't allowed).

Rules on asking questions

by admin on Nov 15, 2011 - 1:47:11 pm UTC
  • (5/2)
Before you ask a question, please do the following:
  • Read this.
  • Java users: make sure you name your class the same thing as the problem code.
  • Be wary of carriage returns '\r' in test data. C/C++ users check for a trailing '\r' in strings you read with gets()/getline(), Python users use raw_input().strip() instead of input(), etc.
  • The status page will only let you preview a snippet of your output. "Your Output (clipped)" simply means that the preview was truncated.
  • Make sure your program works correctly on the sample input(s). It must match exactly!
  • Indent your code and use logical variable names if you want help.
  • Think about large or tricky test cases, and ensure your program can handle them properly.
  • Java users: if the answer to your question is xyzException, that means we deem the bug sufficiently trivial so that just knowing what the exception is should allow you to fix it.
  • Try to fix the problem yourself for at least 15 minutes before giving up and asking for help.
  • If you think the test data are incorrect, please take a moment and consult the Best Solutions page to see how many people have gotten the problem Accepted, and then ask yourself whether it would not be arrogant to conclude that your program is correct and everyone else's programs are wrong. (Of course, problem setters do screw up sometimes, by adding trailing space, or something like that; this may bite you if you're using a different programming language than everyone else. If you suspect that this may be the case, don't hesitate to speak up. However, be forewarned that this is almost always not the case whenever the input consists entirely of numbers.)

On asking questions: post on a problem page if and only if your question is of relevance to everybody (for instance, a clarification question). If your question pertains only to you (such as if your program doesn't work, or if there's something you don't understand about your programming language), please don't clutter up the comments page with it. Instead, consider posting on the forums or just asking a friend to look your program over.

PEG Members: Please do not post for help here. Instead, use the in-class resources and email your leaders for assistance.
If at any time you post a question asking for help in the comments section of a problem, we will delete and ignore it.

Also note: programs may behave differently on the judge and on your computer, but this almost always happens only because you have done Something Bad. Please review this checklist before assuming there is a grader bug and posting a comment about it.

Thank you for your cooperation.