Grading of lab3?

[Gregor Ulm]

My lab partner and me finished lab 3 on Tuesday, during the exercise sessions, and submitted our code. However, afterwards some more files were added to the test suite.

To me it seems that this late change does disadvantage groups that submitted their work early. Our lab passes all good*.cc cases, but as we've just noticed there might be some issues with the newly-added core*.cc files. Because we did submit our work before those files were added to the test suite, we couldn't take those into account. As a result, we might now have wasted one of our submission attempts. This would not have happened had the core*.cc files been released earlier.

To avoid that groups who submitted early are treated unfairly in the grading process, I was therefore wondering whether you might want to consider any of those two options:

1) Make correctly processing the core*.cc files optional.

2) Give groups who submitted before the core*.cc files were posted an additional chance to submit lab3, so that they can correct any mistakes.

Thank you!

[Mattias Appelgren]

Well, it says on five places in the lab PM that only the "good" files are required to pass. Aarne did mention it a few times in the lectures too.

[Aarne Ranta]

Hello,

As I also said, the testsuites don't decide whether you pass, but whether you can submit your lab. If you submit a lab that doesn't pass, rejection is automatic. If it does pass, we still run some more tests and can reject your lab. I'm sure many of you have experienced it.

Therefore extending the test set is not to make your life more difficult, but to help you solve more possible cases before you submit. 

The definition of the task is the lab PM, nothing else. So if you get a rejection on whatever grounds, just check what the lab PM says.

Regards

  Aarne.

e

[Robert Edström]

Then again, my submission was rejected because 'For the testsuite to work, your compiler should create the .class file in the same directory as the original .cc file. Its class name should not contain any dots or slashes, e.g. just "good001".'

Nothing about that in the lab PM - it just states that it should produce a .class file. Since this is a requirement for passing, it really should be included in the lab PM.

[Aarne Ranta]

The lab PM says as follows:

Running the compiler

    % lab3 good.cc
    # produces good.class
  
    % echo 3 | java good.class
    3
    3
    4
    5
    5  

which implies that the file name prefix before .cc is the same as before .class. Which does imply that the source and the the class must be in the same directory.

But I admit that this is not said in words, but only shown in the example. Therefore we are now discussing how to treat these cases.

  Aarne.