search

DUNE / rock_propagation

Code to propagate GENIE reaction products in GEANT and then stuff them back into a GENIE record when they cross a particular boundary. This code is useful for simulating rock events in DUNE.
0 stars 1 forks source link

Error in <TBranchObject::TBranch::WriteBasketImpl>: basket's WriteBuffer failed. #4

Open quantatanu opened 4 years ago

quantatanu commented 4 years ago

Hi,

I was running rock propagation on this file for example:

/pnfs/dune/persistent/users/mylab/stt/geniejob/nov042019/stt_fhc/STT_FHC_173_gsim175_5e17.192819.ghep.root

Genie is printing everything normally but I am also getting the following error:

Error in <TBranchObject::TBranch::WriteBasketImpl>: basket's WriteBuffer failed.
Error in <TBranchObject::TBranch::Fill>: Failed to write out basket.
Error in <TTree::Fill>: Failed filling branch:gtree.gmcrec, nbytes=-1, entry=911
 This error is symptomatic of a Tree created as a memory-resident Tree
 Instead of doing:
    TTree *T = new TTree(...)
    TFile *f = new TFile(...)
 you should do:
    TFile *f = new TFile(...)
    TTree *T = new TTree(...)

image

I have checked the source files and couldn't find any TTree definition before TFile, then why am I getting this error, this is then resulting in empty/corrupted output root files. But this is not always the case, sometimes the output files are of the right size and I can analyze them. Can you please help me find the source of this issue?

Another error message at the end of the jobs is:

Error in <TFile::TFile>: file local_file/gsimple_DUNE_ND_NEAR_FID1_g4lbne_v3r5p4_QGSP_BERT_OptimizedEngineeredNov2017_antineutrino_00249_00247.root does not exist

but this seems harmless.

Thanks

additional info: job run from location: /dune/app/users/anath/ and I load the following before starting running the rock_propagation:

source /cvmfs/dune.opensciencegrid.org/products/dune/setup_dune.sh
setup genie v2_12_10d -q e17:prof
setup geant4 v4_10_3_p03d -q e17:prof
setup cmake v3_14_3 -q Linux64bit+3.10-2.17
setup root v6_16_00 -q e17:prof

and then

export ROCKPROP_DIR="$( cd "$( dirname "${BASH_SOURCE[0]}" )" >/dev/null 2>&1 && pwd )"
export ROCKPROP_BUILD_DIR=${ROCKPROP_DIR}/build
mkdir -p $ROCKPROP_BUILD_DIR
export PATH=$ROCKPROP_BUILD_DIR/bin:$PATH
echo "Top RockProp directory: $ROCKPROP_DIR"
quantatanu commented 4 years ago

I am not sure if you are subscribed so tagging you just to make sure that you get this message.. but I am new to GitHub, so not sure if this is how it works! @kordosky

kordosky commented 4 years ago

Can you ask me about this on slack? I am not sure what you are trying to do and who you are working with. This may not be part of the problem but it looks like you might be trying to run rock propagation on events created in the STT. That seems like an odd thing to do.

On Sun, Jun 21, 2020 at 7:13 PM atanu notifications@github.com wrote:

I am not sure if you are subscribed so tagging you just to make sure that you get this message.. but I am new to GitHub, so not sure if this is how it works! @kordosky https://github.com/kordosky

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/DUNE/rock_propagation/issues/4#issuecomment-647193903, or unsubscribe https://github.com/notifications/unsubscribe-auth/AHFVH4TGKK3AZGDVR7GBQLDRX2H2RANCNFSM4OECFP7Q .

-- Professor of Physics Small Hall 335B William & Mary makordosky@wm.edu Phone: +1 (757) 221 5522 FAX: +1 (757) 221 3540

quantatanu commented 4 years ago

Hi.

thanks a lot for replying. Can you please give me the slack channel link.

And,

it looks like you might be trying to run rock propagation on events created in the STT

Yes, the original files were generated by KLOE (SAND) with STTs, I moved the rock_prop boundary from volDetEnclosure to KLOEYokeBarrel_volume and many other boundaries actually... like the Solenoid etc and then looking at what passes through those boundaries. Basically, events have been analyzed till the ECAL, I am trying to see what escaped after that.. especially how many muons leave the yoke etc. So I put a scintillator outside the Yoke and using rock propagation with the Yoke boundary.

Why can't I do that?

quantatanu commented 4 years ago

@kordosky

Using multiple boundaries and plotting the boundary coordinates (particles entering cavern coords), I got this...

image

I was hoping, rock_propagation can be useful in such situations instead of starting from the neutrino beams.

kordosky commented 4 years ago

Just DM me on the DUNE slack workspace.

On Mon, Jun 22, 2020 at 11:03 AM atanu notifications@github.com wrote:

Hi.

thanks a lot for replying. Can you please give me the slack channel link.

And,

it looks like you might be trying to run rock propagation on events created in the STT

Yes, the original files were generated by KLOE (SAND) with STTs, I moved the rock_prop boundary from volDetEnclosure to KLOEYokeBarrel_volume and many other boundaries actually... like the Solenoid etc and then looking at what passes through those boundaries. Basically, events have been analyzed till the ECAL, I am trying to see what escaped after that.. especially how many muons leave the yoke etc. So I put a scintillator outside the Yoke and using rock propagation with the Yoke boundary.

Why can't I do that?

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/DUNE/rock_propagation/issues/4#issuecomment-647575244, or unsubscribe https://github.com/notifications/unsubscribe-auth/AHFVH4RKSOGTN7G3CQHTJBDRX5XEDANCNFSM4OECFP7Q .

-- Professor of Physics Small Hall 335B William & Mary makordosky@wm.edu Phone: +1 (757) 221 5522 FAX: +1 (757) 221 3540