jcrodriguez-dis
commented
4 years ago Hi, each evaluation is linked to its submission. The evaluation of the last submission goes to the grade book. I think that the submission related to grade at the grade book must not be lost.
If "experiment" with its code means running the program it can be resolved by adding a read-only option for each activity. If you want that the student experiment changing the code I think it will be better to duplicate the VPL activity and remove the grade options and due date. The students can easily download the code and drop it in the new VPL activity to experiment and test it.
Best regards, Juan Carlos.
We have this scenario: The VPL activity has a due date. We allow students to run the code, but not to evaluate it. After the due date the manager allows evaluation, evaluates all submissions. After all that is done it would be nice if the students could still experiment with their code, i.e. make changes and run it, but without actually making new submissions. Just to see if they can improve their code.
I've tested if this is possible by evaluating the student submission after the due date, then disabling evaluation again and disabling the due date. This should ensure that we have evaluated the final submission before the due date and everything after that isn't evaluated so doesn't count. But that does not work. If a student edits his submission afterwards the grade is deleted and it's listed as "No grade" in the submission list. The grade comment of the previous submission and the evaluation output with proposed grade etc. is still there. But unfortunately since the grade itself is deleted we can't do it this way.
Maybe we could implement it so students can just make private copies of their submissions after the due date? That would work in our case.