Crab submission of step1+2 is now via multicrab framework (thanks @d-salerno). This also allows to specify different configuration files. The multicrab code allows one to submit different workflows (e.g. leptonic tt-decay, hadronic, testing jobs), it should not be necessary to comment things in or out in the code.
The crab job will also print out the git hashes of the code when it is executing, allowing it later to be understood what version of the code was used to produce some files.
Crab submission of step1+2 is now via multicrab framework (thanks @d-salerno). This also allows to specify different configuration files. The multicrab code allows one to submit different workflows (e.g. leptonic tt-decay, hadronic, testing jobs), it should not be necessary to comment things in or out in the code. The crab job will also print out the git hashes of the code when it is executing, allowing it later to be understood what version of the code was used to produce some files.