Fnal - Githubissues

elaird commented 11 years ago

Hello,

This branch restores the ability to run on the FNAL batch. supy's output behavior is documented in docs/output.txt. The changes w.r.t. the previous behavior are:

at FNAL, condor is used to move the output files instead of supy
condor moves output files to the submission directory, so job submission is now done from the global output directory
.../TTbar_2_1/... is used instead of .../TTbar/tmpBLaBlA/..., so that the directory name can be written to the .condor file before submission and also used during looping
an rm of .../TTbar_2_1 is used to guarantee a fresh start (which was the motivation for the tmp directory)
a max-replace of 1 enables the sample name "Data" to be used
(if supy is moving the files), mv is used rather than rsync: it works with dcache and has less overhead

Burt, if you have a work-flow at IC with known results, could you do a clean run with this branch to check that it isn't broken?

Ted

betchart commented 11 years ago

It works fine at IC. I am having trouble logging in to FNAL LPC, and did not test there.

elaird commented 11 years ago

I tested it at FNAL and compared with the results of an interactive run; they matched.

betchart commented 11 years ago

Thanks very much for this Ted.

elaird / supy

Fnal #171