Assignment created with .ipynb extension, which adds to directory of source, prevents release and collection of data files other than .ipynb #1758
Unanswered
RDProboticsLLC
asked this question in
Q&A
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hello All, I have already searched some solutions but it looks like a manual creation of a new assignment might be what I have to do. However if there is another option to keep students from having to resubmit their assignments that is superior. The problem is when creating the assignment, a combination of a time issue and an ambiguity of the documentation led to an error in creating the assignment in formgrader. I created one, let's say "Assignment1.ipynb" but used .ipynb in the assignment name. What happens is, even though there are datafiles in the source directory other than a jupyter notebook, only the notebook is copied to release and will be released/collected. I didn't catch the fact that this would be a problem for autograding until later. Basically when collecting files those files (small CSV files) get stripped out. One cannot add them later as during the autograding process the data files are stripped out during sanitization of the assignment. I looked to see if I could copy those files in, add in an option to the setup file, or write a script to put the data files in place but this isn't how nbgrader is written and in all cases it appears to remove the new files. Is there any option I have not considered to solve this without basically creating a new assignment, releasing it (named properly) and asking the students to copy over their files then resubmit? It is finals week and some students of the ~500 student course won't do this, so it's not ideal. I'm new to nbgrader this quarter and there were various variables leading to this. I also suggest adding some error checking for this kind of naming error or something in the documentation somewhere warning of this. This probably seems obvious and in retrospect it is but since it can be done and causes serious issues there could be a very easily implemented check for this confirming that this is what the user really wants to do. Any help would be appreciated, though I need to make a decision this afternoon asap.
Beta Was this translation helpful? Give feedback.
All reactions