GeoModel issueshttps://gitlab.cern.ch/GeoModelDev/GeoModel/-/issues2023-02-09T11:16:58+01:00https://gitlab.cern.ch/GeoModelDev/GeoModel/-/issues/68FSL: Hits: HDF5 crashes when low values of particle gun's Pt and/or the magne...2023-02-09T11:16:58+01:00Riccardo Maria Bianchiriccardo.maria.bianchi@cern.chFSL: Hits: HDF5 crashes when low values of particle gun's Pt and/or the magnetic fieldWhen changing the Pt of the particle gun or the magnetic field to low values, the HDF5 writer crashes.
Needs to be investigated, but it could probably be due to no hits being written or something similar.When changing the Pt of the particle gun or the magnetic field to low values, the HDF5 writer crashes.
Needs to be investigated, but it could probably be due to no hits being written or something similar.https://gitlab.cern.ch/GeoModelDev/GeoModel/-/issues/66FSL: HDF5 crashes when running fullsimLight with TrackPlugin enabled2023-02-09T11:18:01+01:00Riccardo Maria Bianchiriccardo.maria.bianchi@cern.chFSL: HDF5 crashes when running fullsimLight with TrackPlugin enabledWhen trying to run fullSimLight through the FSL GUI with the TracksPlugin enabled, it crashes because of HDF5 while trying to save the data file:
```
### CAUGHT SIGNAL: 11 ### address: 0x10, signal = SIGSEGV, value = 11, description...When trying to run fullSimLight through the FSL GUI with the TracksPlugin enabled, it crashes because of HDF5 while trying to save the data file:
```
### CAUGHT SIGNAL: 11 ### address: 0x10, signal = SIGSEGV, value = 11, description = segmentation violation. Invalid permissions for mapped object.
Backtrace:
[PID=11398, TID=4][ 0/25]> 0 libhdf5.200.dylib 0x0000000106bc4748 H5SL_search + 260
[PID=11398, TID=4][ 1/25]> 1 libhdf5.200.dylib 0x0000000106b8029c H5P_close + 508
[PID=11398, TID=4][ 2/25]> 2 libhdf5.200.dylib 0x0000000106b02868 H5I_dec_ref + 136
[PID=11398, TID=4][ 3/25]> 3 libhdf5.200.dylib 0x0000000106a50144 H5D_close + 1564
[PID=11398, TID=4][ 4/25]> 4 libhdf5.200.dylib 0x0000000106c6060c H5VL__native_dataset_close + 12
[PID=11398, TID=4][ 5/25]> 5 libhdf5.200.dylib 0x0000000106c4b718 H5VL__dataset_close + 64
[PID=11398, TID=4][ 6/25]> 6 libhdf5.200.dylib 0x0000000106c4b578 H5VL_dataset_close + 132
[PID=11398, TID=4][ 7/25]> 7 libhdf5.200.dylib 0x0000000106a553d8 H5D__close_cb + 84
[PID=11398, TID=4][ 8/25]> 8 libhdf5.200.dylib 0x0000000106b02868 H5I_dec_ref + 136
[PID=11398, TID=4][ 9/25]> 9 libhdf5.200.dylib 0x0000000106b02978 H5I_dec_app_ref + 84
[PID=11398, TID=4][10/25]> 10 libhdf5.200.dylib 0x0000000106b02a90 H5I_dec_app_ref_always_close + 84
[PID=11398, TID=4][11/25]> 11 libhdf5.200.dylib 0x0000000106a2cf2c H5Dclose + 140
[PID=11398, TID=4][12/25]> 12 libhdf5_cpp.200.dylib 0x0000000106380424 _ZN2H57DataSet5closeEv + 44
[PID=11398, TID=4][13/25]> 13 libhdf5_cpp.200.dylib 0x000000010638053c _ZN2H57DataSetD2Ev + 56
[PID=11398, TID=4][14/25]> 14 libhdf5_cpp.200.dylib 0x00000001063806bc _ZN2H57DataSetD0Ev + 20
[PID=11398, TID=4][15/25]> 15 libGenerateTracksPlugin.1.0.dylib 0x0000000105bbc940 _ZN15TrksEventAction16EndOfEventActionEPK7G4Event + 848
[PID=11398, TID=4][16/25]> 16 libG4event.dylib 0x0000000105355fc8 _ZN14G4EventManager12DoProcessingEP7G4Event + 3428
[PID=11398, TID=4][17/25]> 17 libG4run.dylib 0x00000001055ad93c _ZN18G4WorkerRunManager15ProcessOneEventEi + 52
[PID=11398, TID=4][18/25]> 18 libG4run.dylib 0x00000001055ad8bc _ZN18G4WorkerRunManager11DoEventLoopEiPKci + 172
[PID=11398, TID=4][19/25]> 19 libG4run.dylib 0x00000001055a580c _ZN12G4RunManager6BeamOnEiPKci + 128
[PID=11398, TID=4][20/25]> 20 libG4run.dylib 0x00000001055b0170 _ZN18G4WorkerRunManager6DoWorkEv + 692
[PID=11398, TID=4][21/25]> 21 libG4run.dylib 0x00000001055c370c _ZN20G4MTRunManagerKernel11StartThreadEP14G4WorkerThread + 524
[PID=11398, TID=4][22/25]> 22 libG4run.dylib 0x00000001055ca474 _ZNSt3__1L14__thread_proxyINS_5tupleIJNS_10unique_ptrINS_15__thread_structENS_14default_deleteIS3_EEEEPFvP14G4WorkerThreadES8_EEEEEPvSC_ + 44
[PID=11398, TID=4][23/25]> 23 libsystem_pthread.dylib 0x00000001c36c426c _pthread_start + 148
[PID=11398, TID=4][24/25]> 24 libsystem_pthread.dylib 0x00000001c36bf08c thread_start + 8
ERROR! ==> './fullSimLight' crashed!
```https://gitlab.cern.ch/GeoModelDev/GeoModel/-/issues/65FSL : HDF5 crashes when fullSimLigh is launched twice with Hits plugin2023-02-09T11:18:27+01:00Riccardo Maria Bianchiriccardo.maria.bianchi@cern.chFSL : HDF5 crashes when fullSimLigh is launched twice with Hits pluginWhen launching fullSimLigh through FSL twice, with the Hits plugin enabled, FSL crashes because of errors from the HDF5 library.
The problem seems to be related to HDF5 that tries to write/update the file created from the first run.
We...When launching fullSimLigh through FSL twice, with the Hits plugin enabled, FSL crashes because of errors from the HDF5 library.
The problem seems to be related to HDF5 that tries to write/update the file created from the first run.
We should warn the user and/or delete and recreate the file.https://gitlab.cern.ch/GeoModelDev/GeoModel/-/issues/56Set proper build switches for HepMC and Pythia support2023-01-16T17:51:37+01:00Riccardo Maria Bianchiriccardo.maria.bianchi@cern.chSet proper build switches for HepMC and Pythia supportWe would like to have HepMC and Pythia support optional: OFF by default, but ON on user's request.
At the moment:
* HepMC is ON by default, we should move it to OFF.
* Pythia is OFF by default, but it silently builds Pythia if Pythia ...We would like to have HepMC and Pythia support optional: OFF by default, but ON on user's request.
At the moment:
* HepMC is ON by default, we should move it to OFF.
* Pythia is OFF by default, but it silently builds Pythia if Pythia is found
We should have clear switches to have them ON/OFF, without silent builds/detection.
We should also have the HepMC/Pythia features in FSL greyed out when no support for them is built. In that way, users that haven't enabled their build still can see that support for them is possible/available, if enabled.
----
**Note:**
All this does not apply to distribution kits: at the GeoModel meetings it was agreed that the idea there is to have the full functionality. So, distribution kits should install all functionalities with all needed dependencies.
TODO: remove the optional flag to optionally disable HepMC3 installation in FSL and FullSimLight Homebrew recipes.Riccardo Maria Bianchiriccardo.maria.bianchi@cern.chRiccardo Maria Bianchiriccardo.maria.bianchi@cern.chhttps://gitlab.cern.ch/GeoModelDev/GeoModel/-/issues/55Severe performance degradation when using HEPMC generator and tracking plugin...2023-02-08T00:27:03+01:00Mitch KellySevere performance degradation when using HEPMC generator and tracking plugin, and cannot process files with more than 10 events.When using an input HEPMC file with more than just a few vertices in it and the tracks plugin fullSimLight/FSL effectively hangs. I have had success running a small example file (7 vertices 12 particles), but when running a slightly larg...When using an input HEPMC file with more than just a few vertices in it and the tracks plugin fullSimLight/FSL effectively hangs. I have had success running a small example file (7 vertices 12 particles), but when running a slightly larger file (31 vertices, 42 particles) I experience the problem. I have noticed that when running larger files, if I watch the size of the output .h5 file it will rapidly grow, roughly 40mb per second on my hard drive, until it reaches over ~600mb, at which point the the write speed drops to ~0.1mb per second. Interestingly, I have also noticed that if I turn on the tracking verbosity (any level 1-5), nothing writes to the *.h5 file, but if I pipe the terminal output to a file, this file grows at a rate of around 40mb per second, and I can see in bpytop that my CPU is working much harder. My guess then is that this has something to do with the hdf5 file writing process making some sort of bottleneck as the files are quite large...
Finally, I have tried producing a HEPMC that has each vertex placed in it's own event. In my example there are 78 vertices/events, when I run this file fullSimLight quits after processing 10 of the events/vertices and gives this output (sorry for the formatting I'm not sure how to get it to just display plain text):
```
-----------------------------------------------------------------------------------------------------------------------------------------
GenEvent: #9
Momentum units: GEV Position units: MM
Entries in this event: 1 vertices, 2 particles, 0 weights.
Position offset: 0, 0, 0, 0
GenParticle Legend
ID PDG ID ( px, py, pz, E ) Stat ProdVtx
________________________________________________________________________
Vtx: -1 stat: 0 (X,cT): 1.7e-07 -4.3e-07 2.7e-05 2.7e-05
I: 1 -311 +7.89e-02,-1.97e-01,+1.24e+01,+1.24e+01 2 0
O: 2 130 +7.89e-02,-1.97e-01,+1.24e+01,+1.24e+01 1 -1
________________________________________________________________________
--------------------------------
--------- EVENT CONTENT --------
--------------------------------
Weights (0):
Attributes:
GenParticlePtr (2)
GenParticle: 1 PDGID: -311 (P,E)=+7.89e-02,-1.97e-01,+1.24e+01,+1.24e+01 Stat: 2 PV: 0 EV: -1 Attr: 0
GenParticle: 2 PDGID: 130 (P,E)=+7.89e-02,-1.97e-01,+1.24e+01,+1.24e+01 Stat: 1 PV: -1 EV: 0 Attr: 0
GenVertexPtr (1)
GenVertex: -1 stat: 0 in: 1 out: 1 has_set_position: true (X,cT): 1.7135e-07, -4.28113e-07, 2.69565e-05, 2.69821e-05
-----------------------------
G4Worker_0 > Particle pdgcode: 130
G4Worker_0 > HepMC3PrimaryGeneratorAction::GeneratePrimaries MUTEX unlocked
The file Tracks_data_23.h5 has been created.
=================================================================
Final random number = 0.330781
=================================================================
double free or corruption (fasttop)
### CAUGHT SIGNAL: 6 ### address: 0x3e80000822f, signal = SIGABRT, value = 6, description = abort program (formerly SIGIOT).
malloc_consolidate(): unaligned fastbin chunk detected
Aborted (core dumped)
----------------------------------------------------------------------------------------------------------------------------------------
```
The output .h5 file here has a size of 290mb. I have noticed in the terminal output that after reading the hepmc input file FSL/fullSimLight outputs a formatted table of vertices using the HepMC.read() function however it shows event#0 with 78 vertices, so I guess it takes the 78 vertices and puts them in 1 event, but if I do this myself, I get the stalling behavior I described above.
An aside, I also noticed in FSL if the HEPMC generator is selected multithreading is disabled, or atleast you can't choose more than 1 thread there. I can alter the config file manually and run it with fullSimLight specifying more threads, but can easily freeze my system if I choose 4 cores as it maxes out my system memory (16gb). I wondered if maybe these things are related but I don't experience the problem when using Pythia as the generator.Riccardo Maria Bianchiriccardo.maria.bianchi@cern.chRiccardo Maria Bianchiriccardo.maria.bianchi@cern.chhttps://gitlab.cern.ch/GeoModelDev/GeoModel/-/issues/10Graphics errors on macOS Catalina (and partially on Mojave)2020-11-27T21:22:27+01:00Riccardo Maria Bianchiriccardo.maria.bianchi@cern.chGraphics errors on macOS Catalina (and partially on Mojave)We have two major graphics problems:
1) we get an empty, back screen on macOS Mojave, while using the latest releases from GitHub
2) we get distorted volumes (actually, "flattened") on macOS Catalina
More details, below.We have two major graphics problems:
1) we get an empty, back screen on macOS Mojave, while using the latest releases from GitHub
2) we get distorted volumes (actually, "flattened") on macOS Catalina
More details, below.Riccardo Maria Bianchiriccardo.maria.bianchi@cern.chRiccardo Maria Bianchiriccardo.maria.bianchi@cern.chhttps://gitlab.cern.ch/GeoModelDev/GeoModel/-/issues/9HEAD SoQt on macOS gives empty, black screen2023-01-12T00:57:00+01:00Riccardo Maria Bianchiriccardo.maria.bianchi@cern.chHEAD SoQt on macOS gives empty, black screenBy using a recent version of the SoQt code on macOS >= Mojave makes GeoModelVisualization (`gmex`) show an empty, black screen.
(related to [this VP1 ticket (ATLAS internal)](https://its.cern.ch/jira/browse/ATLASVPONE-504) )By using a recent version of the SoQt code on macOS >= Mojave makes GeoModelVisualization (`gmex`) show an empty, black screen.
(related to [this VP1 ticket (ATLAS internal)](https://its.cern.ch/jira/browse/ATLASVPONE-504) )Riccardo Maria Bianchiriccardo.maria.bianchi@cern.chRiccardo Maria Bianchiriccardo.maria.bianchi@cern.chhttps://gitlab.cern.ch/GeoModelDev/GeoModel/-/issues/7Builtin Coin: CMake error with CMake 3.19 on macOS2020-11-24T17:32:02+01:00Riccardo Maria Bianchiriccardo.maria.bianchi@cern.chBuiltin Coin: CMake error with CMake 3.19 on macOS
While testing the latest release from GitHub:
```
https://github.com/coin3d/coin/releases/download/Coin-4.0.0/coin-4.0.0-src.tar.gz
```
I get:
```
CMake Error: install(EXPORT "Coin" ...) includes target "Coin" more than once in the e...
While testing the latest release from GitHub:
```
https://github.com/coin3d/coin/releases/download/Coin-4.0.0/coin-4.0.0-src.tar.gz
```
I get:
```
CMake Error: install(EXPORT "Coin" ...) includes target "Coin" more than once in the export set.
```
**NOTE:** No error seen on macOS with CMake 3.18.4.Riccardo Maria Bianchiriccardo.maria.bianchi@cern.chRiccardo Maria Bianchiriccardo.maria.bianchi@cern.ch