HTCondor job run directory #343
Open
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Hello
FCCAnalysesexperts - I found that when submitting many jobs to HTCondor due to running over many processes and chunks, this would create a ton of directories, each used to run for a given job.While I suppose one can create a
rundirectory and simply submit jobs from there (actually, not sure if that would work since the condor script looks forsetup.shin yourlocal_dir), which would populate that separated directory with lots of extra directories, I wanted to make things more organized and not dependent on the local directory you run from, so I propose with these changes to have each job's working directory be located inside thelog_dir.I'm not sure what other users prefer, but I wanted to share this code in case it's desirable/useful for the repo.
Files edited:
python/run_analysis.py:log_diroutside ofsend_to_batchto ensure it can be used bycreate_condor_configso that in the condor script, job's are directed to thelog_dirbefore creating a working directory.