input file and pdb as part of the final download link
RudoRoemer opened this issue · comments
The final download link should always contain
[1] the input file of the submission parameters,
[2] the original .pdb file
[3] the .py file, if there was one submitted.
This would then mean that users have a fully self-contained output link, i.e. such that all the information needed to check the output (and redo) is contained in that single download.
Added functionality, CSC is very slow at the moment, when my request begins processing and completes, I will clarify that this has definitely been resolved.
the compressed file I received contained the input files. I will add functionality to contain a .txt file that has the given params.
txt file created and added to compression in both .zip and .tar.gz functions. Will be added in the next pull request.
It would also be good to make the .py file available (if present) in the DL link just like the other input files.
This has been added and successfully works on the production and test servers