-
Pretty self explanatory. This would be nice so that users don't have to soft link the detector description if they are using a standard one that is installed with ldmx-sw.
-
This task is pretty simple, but will take some time to make sure that they are working after translation.
Since we moved from using steering macros (in the Geant4 style), we have started using our …
-
Currently the state of the biasing system is managed via static variables, especially in BiasingMessenger. This is problematic because it will prevent the sim code from eventually being MT compatible…
-
The `useRootSeed_` flag does not need to be static. It could instead be accessed as a data member via PrimaryGenerationAction which is available from the RunManager.
-
This will help when the process method `printMe` is called for people to see what parameters they are passing to the process and to the UserAction method.
-
Now that unit testing is incorporated into ldmx-sw, we can go back and write more tests for all of the abilities of ldmx-sw. We need both functional tests and physics tests in all modules.
The over…
-
I have run into this issue while playing with the custom iso I've been creating.
I'm not sure if this actually has anything to do with the OS that I am working on or not, but I'm trying to figure o…
-
This would be nice so that we can keep Framework and Simulation separate.
In the long run, there could even be a "geant4-less" build where a user can have everything except the simulation.
-
This is a feature that could be helpful and would (hopefully) make the python configuration approach a little more unified.
This would need to include macros and managers and stuff that we can copy…
-
Currently, a lot of different parts of the geometry description are hard-coded in various producers/analyzers/classes. Isolating the geometry description to one class in the DetDescr module would allo…