a-paranjape
commented
3 months ago it makes sense to submit postprocessing only after the tree files are available. the submission script should now forbid submitting a postprocessing job unless the sim/halo/trees flags are switched off. the class and ngenic flags should be irrelevant.
For running post processing, there's an error, the snapshot of which is attached here. Earlier it was not there, as the scales.txt was starting from snapshot 5, for which the .trees file was available. Now, postprocess.py is taking the starting snapshot as 0, for which this file is not available. Also, the postprocessing job starts running only if it is submitted separately after rockstar has run (by setting everything else except postprocess to 0 in the submit script), otherwise it gives an error. The error snapshot is attached here. Although the job is submitted only after the rockstar and consistent trees jobs are completed, its inputs are read before that, which are not available until the completion of rockstar jobs.