Open mt82 opened 3 weeks ago
The icaruscode version is not working. Now the icaruscode is identified. But @PromitaRoy wonder if all the 8 datastreams should be run. @PetrilloAtWork what is your opinion?
My opinion: wait until the release and workflow for #17 are decided, and then process the whole run again with that version. The effort will then be credited back when the full Run3 is to be processed again.
expectation: completed for 27th of June
6 datastreams completed, rest 2 are running
Destination paths: bnbmajority, bnbminbias, numimajority, numiminbias, offbeambnbmajority, offbeamnumimajority
/pnfs/sbn/data_add/sbn_fd/poms_production/data/Data_OpRecoWG_Run3_11816_datastream/reconstructed/icaruscode_v09_90_00/Icaruspro_2024_Run3_11816_OpRecWG_datastream/datastream/stages/
Destination paths: offbeambnbminbias, offbeamnumiminbias
/pnfs/sbn/data_add/sbn_fd/poms_production/data/Data_OpRecoWG_Run3_11816_datastream/reconstructed/icaruscode_v09_90_00/Icaruspro_2024_Run3_11816_datastream/datastream/stages/
Please note the two slightly different dest paths. Also, kindly replace the "datastream" in the destination path with whichever datastream you want to work with as well as replace the "stages" with whatever stage you want to analyze, for instance: stage1, calibtuples, caf_blind, caf_unblind, caf_prescaled etc.
Icarus code version and fhicls same as request #14
Similar to request #14, a few jobs are held for 1-2 datastreams, for them I need to launch recovery. But there is some issue with gpvm migration, looking at it with help from Vito. Also a ticket has been raised by Vito.
name/tag: ICARUSrun11816full size: 110k output: stage1, caf