EIC issueshttps://eicweb.phy.anl.gov/groups/EIC/-/issues2022-08-12T22:39:21Zhttps://eicweb.phy.anl.gov/EIC/juggler/-/issues/73add RICH IRT algorithm2022-08-12T22:39:21ZChristopher Dilksadd RICH IRT algorithmChristopher DilksChristopher Dilkshttps://eicweb.phy.anl.gov/EIC/benchmarks/reconstruction_benchmarks/-/issues/81RICH benchmarks2021-11-05T18:15:49ZChristopher DilksRICH benchmarksChristopher DilksChristopher Dilkshttps://eicweb.phy.anl.gov/EIC/detectors/athena/-/issues/134make new 3d views of FF region and detectors2021-11-05T17:18:58ZAlex Jentschmake new 3d views of FF region and detectorsAlex JentschAlex Jentschhttps://eicweb.phy.anl.gov/EIC/benchmarks/reconstruction_benchmarks/-/issues/80Add BTOF Benchmark2021-11-04T22:35:05ZZhenyu YeAdd BTOF Benchmarkhttps://eicweb.phy.anl.gov/EIC/benchmarks/detector_benchmarks/-/issues/59Add BTOF benchmarks2021-11-03T03:43:48ZZhenyu YeAdd BTOF benchmarkshttps://eicweb.phy.anl.gov/EIC/benchmarks/physics_benchmarks/-/issues/37Job Failed #427685: Recurring segfault in 10x100 DIS2021-11-05T04:40:12ZWouter DeconinckJob Failed #427685: Recurring segfault in 10x100 DISJob [#427685](https://eicweb.phy.anl.gov/EIC/benchmarks/physics_benchmarks/-/jobs/427685) failed for 4398ec62d712ac34dc9f41d8a86bb1e9cac5382b:
```
*** Break *** segmentation violation
====================================================...Job [#427685](https://eicweb.phy.anl.gov/EIC/benchmarks/physics_benchmarks/-/jobs/427685) failed for 4398ec62d712ac34dc9f41d8a86bb1e9cac5382b:
```
*** Break *** segmentation violation
===========================================================
There was a crash.
This is the entire stack trace of all threads:
===========================================================
#0 0x00007ff96843ac46 in __GI___wait4 (pid=308, stat_loc=stat_loc
entry=0x7fff5ef39408, options=options
entry=0, usage=usage
entry=0x0) at ../sysdeps/unix/sysv/linux/wait4.c:30
#1 0x00007ff96843ac07 in __GI___waitpid (pid=<optimized out>, stat_loc=stat_loc
entry=0x7fff5ef39408, options=options
entry=0) at waitpid.c:38
#2 0x00007ff9683b9a73 in do_system (line=<optimized out>) at ../sysdeps/posix/system.c:172
#3 0x00007ff96754980b in TUnixSystem::StackTrace() () from /opt/software/linux-debian-x86_64/gcc-10.3.0/root-6.24.06-pgd4i7gxclnyg4ysoebhpu4btbrbrh27/lib/libCore.so.6.24
#4 0x00007ff9676f5cd2 in ?? () from /opt/software/linux-debian-x86_64/gcc-10.3.0/root-6.24.06-pgd4i7gxclnyg4ysoebhpu4btbrbrh27/lib/libcppyy_backend3_9.so.6.24
#5 0x00007ff967546c21 in TUnixSystem::DispatchSignals(ESignals) () from /opt/software/linux-debian-x86_64/gcc-10.3.0/root-6.24.06-pgd4i7gxclnyg4ysoebhpu4btbrbrh27/lib/libCore.so.6.24
#6 <signal handler called>
#7 0x00007ff9549fa8ce in dd4hep::sim::Geant4Particle::release() () from /opt/software/linux-debian-x86_64/gcc-10.3.0/dd4hep-1.18-rubohuy3jsc7u4vqoh77kbw6vqozds35/lib/libDDG4.so.1.18
#8 0x00007ff954a0fe7e in dd4hep::sim::Geant4PrimaryInteraction::~Geant4PrimaryInteraction() () from /opt/software/linux-debian-x86_64/gcc-10.3.0/dd4hep-1.18-rubohuy3jsc7u4vqoh77kbw6vqozds35/lib/libDDG4.so.1.18
#9 0x00007ff9549f7df6 in ?? () from /opt/software/linux-debian-x86_64/gcc-10.3.0/dd4hep-1.18-rubohuy3jsc7u4vqoh77kbw6vqozds35/lib/libDDG4.so.1.18
#10 0x00007ff955840302 in dd4hep::ObjectExtensions::clear(bool) () from /opt/software/linux-debian-x86_64/gcc-10.3.0/dd4hep-1.18-rubohuy3jsc7u4vqoh77kbw6vqozds35/lib/libDDCore.so.1.18
#11 0x00007ff95584034c in dd4hep::ObjectExtensions::~ObjectExtensions() () from /opt/software/linux-debian-x86_64/gcc-10.3.0/dd4hep-1.18-rubohuy3jsc7u4vqoh77kbw6vqozds35/lib/libDDCore.so.1.18
#12 0x00007ff9549df30e in dd4hep::sim::Geant4UserEventAction::EndOfEventAction(G4Event const*) () from /opt/software/linux-debian-x86_64/gcc-10.3.0/dd4hep-1.18-rubohuy3jsc7u4vqoh77kbw6vqozds35/lib/libDDG4.so.1.18
#13 0x00007ff9540ebb43 in G4EventManager::DoProcessing(G4Event*) () from /opt/software/linux-debian-x86_64/gcc-10.3.0/geant4-10.7.1-wfvgumef3sbbgrh2gopyldz7rphwudgo/lib/libG4event.so
#14 0x00007ff95418e117 in G4RunManager::ProcessOneEvent(int) () from /opt/software/linux-debian-x86_64/gcc-10.3.0/geant4-10.7.1-wfvgumef3sbbgrh2gopyldz7rphwudgo/lib/libG4run.so
#15 0x00007ff95418dfbb in G4RunManager::DoEventLoop(int, char const*, int) () from /opt/software/linux-debian-x86_64/gcc-10.3.0/geant4-10.7.1-wfvgumef3sbbgrh2gopyldz7rphwudgo/lib/libG4run.so
#16 0x00007ff95418c07e in G4RunManager::BeamOn(int, char const*, int) () from /opt/software/linux-debian-x86_64/gcc-10.3.0/geant4-10.7.1-wfvgumef3sbbgrh2gopyldz7rphwudgo/lib/libG4run.so
#17 0x00007ff954a1b323 in dd4hep::sim::Geant4UIManager::start() () from /opt/software/linux-debian-x86_64/gcc-10.3.0/dd4hep-1.18-rubohuy3jsc7u4vqoh77kbw6vqozds35/lib/libDDG4.so.1.18
#18 0x00007ff9549e0676 in dd4hep::sim::Geant4Exec::run(dd4hep::sim::Geant4Kernel&) () from /opt/software/linux-debian-x86_64/gcc-10.3.0/dd4hep-1.18-rubohuy3jsc7u4vqoh77kbw6vqozds35/lib/libDDG4.so.1.18
#19 0x00007ff9549fcfda in dd4hep::sim::Geant4Kernel::run() () from /opt/software/linux-debian-x86_64/gcc-10.3.0/dd4hep-1.18-rubohuy3jsc7u4vqoh77kbw6vqozds35/lib/libDDG4.so.1.18
```Wouter DeconinckWouter Deconinckhttps://eicweb.phy.anl.gov/EIC/benchmarks/physics_benchmarks/-/issues/34Job Failed #416935: cycles of `malloc(): unsorted double linked list corrupte...2021-10-27T21:24:21ZWouter DeconinckJob Failed #416935: cycles of `malloc(): unsorted double linked list corrupted *** Break *** abort`Job [#416935](https://eicweb.phy.anl.gov/EIC/benchmarks/physics_benchmarks/-/jobs/416935) failed for f029424083a9ef610146fbc2003084ad030c56f8:
While running npsim, lots of repeated
```
malloc(): unsorted double linked list corrupted
**...Job [#416935](https://eicweb.phy.anl.gov/EIC/benchmarks/physics_benchmarks/-/jobs/416935) failed for f029424083a9ef610146fbc2003084ad030c56f8:
While running npsim, lots of repeated
```
malloc(): unsorted double linked list corrupted
*** Break *** abort
```
Could be a transient, but seen this several times in last week so it may be triggered by something recent.Wouter DeconinckWouter Deconinckhttps://eicweb.phy.anl.gov/EIC/benchmarks/detector_benchmarks/-/issues/58Material scan for ecal2021-10-27T04:06:59ZWouter DeconinckMaterial scan for ecalThe material scan behind the ECAL looks like it has way too much material in the ECAL barrel region, with 1e2 X0.
https://eicweb.phy.anl.gov/EIC/benchmarks/detector_benchmarks/-/jobs/411758/artifacts/file/results/images/materialScanEcal...The material scan behind the ECAL looks like it has way too much material in the ECAL barrel region, with 1e2 X0.
https://eicweb.phy.anl.gov/EIC/benchmarks/detector_benchmarks/-/jobs/411758/artifacts/file/results/images/materialScanEcal.png
We should figure out why that is the case, and if other parts of the material scans are similarly affected.
While on the topic:
- add missing materials to the table of known materials (or figure out an automatic numbering scheme)
- add a legend
- use actual regions in compact xml and material scan instead of mathematical cylindersWouter DeconinckWouter Deconinckhttps://eicweb.phy.anl.gov/EIC/detectors/athena/-/issues/130Excessive output for convert_to_gdml2021-10-27T04:02:34ZWouter DeconinckExcessive output for convert_to_gdmlhttps://eicweb.phy.anl.gov/EIC/detectors/athena/-/jobs/412116
Lots of segments with
```
-------- WWWW ------- G4Exception-START -------- WWWW -------
*** G4Exception : CUTS0100
issued by : G4ProductionCutsTable::ConvertRangeToEne...https://eicweb.phy.anl.gov/EIC/detectors/athena/-/jobs/412116
Lots of segments with
```
-------- WWWW ------- G4Exception-START -------- WWWW -------
*** G4Exception : CUTS0100
issued by : G4ProductionCutsTable::ConvertRangeToEnergy()
Invoked prematurely before it is fully initialized.
*** This is just a warning message. ***
-------- WWWW -------- G4Exception-END --------- WWWW -------
```
These should be grepped out in the convert_to_gdml script so the log files can be used for finding other issues (validation).Wouter DeconinckWouter Deconinckhttps://eicweb.phy.anl.gov/EIC/eicd/-/issues/21add IRT output data structures2022-02-11T16:12:10ZChristopher Dilksadd IRT output data structuresChristopher DilksChristopher Dilkshttps://eicweb.phy.anl.gov/EIC/detectors/athena/-/issues/128material map for Acadia (cbor)2021-10-24T23:17:39ZWouter Deconinckmaterial map for Acadia (cbor)[material-maps.cbor](/uploads/458fee1b8c95bf408159fe70d654b8c0/material-maps.cbor)[material-maps.cbor](/uploads/458fee1b8c95bf408159fe70d654b8c0/material-maps.cbor)Wouter DeconinckWouter Deconinckhttps://eicweb.phy.anl.gov/EIC/juggler/-/issues/68Issue with nucleus PDG code2021-10-22T19:14:00ZZhoudunming TuIssue with nucleus PDG codeThe current sim step does not take 10-digit nucleus PDG code, SEE screenshot,
https://files.slack.com/files-pri/T01RLU7AFNY-F02HMJCGGRK/screen_shot_2021-10-13_at_7.58.12_pm.png
This will be an issue for every eA event generator.
The ve...The current sim step does not take 10-digit nucleus PDG code, SEE screenshot,
https://files.slack.com/files-pri/T01RLU7AFNY-F02HMJCGGRK/screen_shot_2021-10-13_at_7.58.12_pm.png
This will be an issue for every eA event generator.
The version of the code can be found here,
https://eicweb.phy.anl.gov/EIC/benchmarks/physics_benchmarks/-/tree/diffractive-phi-benchmarks/benchmarks/diffractive_phi
also,
the test file is
S3/eictest/ATHENA/EVGEN/TEST/Output_input_temp_189.hepmc
or any eA hepmc files.https://eicweb.phy.anl.gov/EIC/juggler/-/issues/67Issues related to DVCS photon and proton reco2021-10-22T19:08:48ZZhoudunming TuIssues related to DVCS photon and proton recoDVCS ep events (with crossing angle after-burner applied) has been passed thru full ATHENA simulations.
Two observations:
1. DVCS real photon reconstruction is missing eta>0, comparing to MC distribution.
2. DVCS scattered proton, REC ...DVCS ep events (with crossing angle after-burner applied) has been passed thru full ATHENA simulations.
Two observations:
1. DVCS real photon reconstruction is missing eta>0, comparing to MC distribution.
2. DVCS scattered proton, REC eta distribution shifts to high eta comparing to MC distribution
[photon.pdf](/uploads/c4070f027f853b456c298ec2441ac4d1/photon.pdf)
[photon_eta.pdf](/uploads/f2dbe9123b59aa511495da788609fe1b/photon_eta.pdf)
[proton_eta.pdf](/uploads/4b9e7694573396ae09f024c157fa37a2/proton_eta.pdf)
Instruction to reproduce these plots, see the following gitlab link:
https://eicweb.phy.anl.gov/EIC/benchmarks/physics_benchmarks/-/tree/diffractive-phi-benchmarks/benchmarks/dvcs-d
run
`dvcs-d.sh`
will run the full chain of reco and analysis.https://eicweb.phy.anl.gov/EIC/detectors/athena/-/issues/125TGeo overlap check now slower than GEANT4 check2021-10-21T20:04:19ZSylvester JoostenTGeo overlap check now slower than GEANT4 checkNeed to figure out what is going on, and if there are no issues trigger the downstream pipelines off the GEANT4 check instead.Need to figure out what is going on, and if there are no issues trigger the downstream pipelines off the GEANT4 check instead.https://eicweb.phy.anl.gov/EIC/juggler/-/issues/64CKFTracking: reduce verbosity on failed tracks found2021-10-13T16:09:37ZWouter DeconinckCKFTracking: reduce verbosity on failed tracks foundFilling up logs at GB-level quantities...Filling up logs at GB-level quantities...Wouter DeconinckWouter Deconinckhttps://eicweb.phy.anl.gov/EIC/eicd/-/issues/20VectorXYZT operator+ and operator-2021-10-12T00:15:01ZWouter DeconinckVectorXYZT operator+ and operator-Currently not operators are defined on the four vectors.Currently not operators are defined on the four vectors.https://eicweb.phy.anl.gov/EIC/eicd/-/issues/19VectorXYZT::mag() may be confusing since not four-vector magnitude2022-02-24T02:43:09ZWouter DeconinckVectorXYZT::mag() may be confusing since not four-vector magnitude`mag()` is defined as
```code
double mag() const {return std::hypot(x, y, z);}
```
but the magnitude of a fourvector is traditionally defined as `mass()` (maybe up to a sign)
```code
double mass() const {return sqrt(t*t - x*x - y*y - z*z...`mag()` is defined as
```code
double mag() const {return std::hypot(x, y, z);}
```
but the magnitude of a fourvector is traditionally defined as `mass()` (maybe up to a sign)
```code
double mass() const {return sqrt(t*t - x*x - y*y - z*z);}
```
This might lead to confusion when people start to use this in things like `q2 = (ef-ei).mag()`.https://eicweb.phy.anl.gov/EIC/eicd/-/issues/18Provide constructor for eic::VectorXYZT from dd4pod::VectorXYZ and double2021-10-13T02:28:09ZWouter DeconinckProvide constructor for eic::VectorXYZT from dd4pod::VectorXYZ and doubleCreating an eic::VectorXYZT fourvector from a dd4pod mcparticles entry requires individual x,y,z setters. Ideally, we'd have
```code
for (const auto& p : mcparts) {
if (p.genStatus() == 4 && p.pdgID() == 11) {
// Incomi...Creating an eic::VectorXYZT fourvector from a dd4pod mcparticles entry requires individual x,y,z setters. Ideally, we'd have
```code
for (const auto& p : mcparts) {
if (p.genStatus() == 4 && p.pdgID() == 11) {
// Incoming electron
eic::VectorXYZT ei(p.ps(), p.E());
break;
}
}
```https://eicweb.phy.anl.gov/EIC/eicd/-/issues/17Use consistent namespaces and include directories2021-10-11T19:48:33ZWouter DeconinckUse consistent namespaces and include directoriesRight now we are using a mixture of
- header files in `eicd/`
- namespace `eic::` for data structures in CamelCase
- namespace `eicd::helpers::` for helper functions in lowercase
This causes confusion when
```code
#include "eicd/Reconst...Right now we are using a mixture of
- header files in `eicd/`
- namespace `eic::` for data structures in CamelCase
- namespace `eicd::helpers::` for helper functions in lowercase
This causes confusion when
```code
#include "eicd/ReconstructedParticleCollection.h"
```
provides `eic::ReconstructedParticleCollection`, but
```code
#include "eicd/helpers.h"
```
provides `eicd::helpers::momenta_from_tracking`.
Proposal:
- keep namespaces as `eic::`,
- change install paths to `eic/`,
- remove `eic::helpers::` as an intermediate namespace in favor of e.g. `eic::KinematicsHelpers::`,
- provide headers for helpers in the same structure are the intermediate namespaces, e.g.
```code
#include "eic/KinematicsHelpers.h"
```https://eicweb.phy.anl.gov/EIC/eicd/-/issues/16Provide single header to include for all collection types2021-10-11T19:05:15ZWouter DeconinckProvide single header to include for all collection typesDownstream analysis codes now require
```code
#include "eicd/InclusiveKinematicsCollection.h"
#include "eicd/ReconstructedParticleCollection.h"
```
while it may be easier and more transparent for users to use a single overall header
```c...Downstream analysis codes now require
```code
#include "eicd/InclusiveKinematicsCollection.h"
#include "eicd/ReconstructedParticleCollection.h"
```
while it may be easier and more transparent for users to use a single overall header
```code
#include "eicd.h"
```
or mabye
```code
#include "eicd/DataModel.h"
```