-
a folder containing an example is at /osgpool/halld/tbritton/37030_0/
set your calib context to "variation=mc" and run the command in bold below. You can see it produces a number of errors, writes…
-
From Ashley:
I was trying to test the reaction filter with the reactions below. From what I found, the analysis library crashes when adding a pi0 or gamma to a reaction containing particle index 2…
-
Several monitoring plugins crash hd_root:
ST_Tresolution,ST_online_tracking,ST_online_efficiency,HLDetectorTiming
The faults are not fully reproducible, but all 4 plugins together result in a fa…
aaust updated
5 years ago
-
HDGeant4 reads the run number from control.in as RUNG and again from the command line -r parameter. The command line param supersedes control.in
I don't see the value of setting it in the command…
-
Looking at the raw output of HDGeant4, it looks like the overall distribution of TOF truth hits has a different shape compared to that generated by HDGeant. It looks like in HDGeant4, the central Gau…
-
Looking at the raw output of HDGeant4, it looks like the integrated charge determined for CDC hits is systematically shifted to higher values compared to HDGeant.
Example MC data files and the in…
-
One issue I've run into seems to come from the inclusion of RFtime information in the output of HDGeant4. This data was not generated in HDGeant.
I believe that the values stored come from GlueXPh…
-
Justin, Dave, and I were looking at a comparison between HDGeant3 and 4. We simulated a signal MC data set with Simon's genEtaRegge generator (eta -> 2g).
We ran it with the same control.in file (…
-
When running over events generated with an external generator (e.g. bggen), the run number set for those events is not propagated into HDGeant4. Unless I missed some change, I believe the policy was …
-
I am attempting to validate some changes I made to the geometry by using a particle gun. After commenting out all my detector changes and trying to run the attached control.in (I had to rename it for…