Gauss merge requestshttps://gitlab.cern.ch:8443/lhcb/Gauss/-/merge_requests2024-03-08T16:43:06+01:00https://gitlab.cern.ch:8443/lhcb/Gauss/-/merge_requests/1033Update sensitive detector mapping for Muon2024-03-08T16:43:06+01:00Erika De LuciaUpdate sensitive detector mapping for MuonUpdate sensitive detector mapping for Muon following new detector description in https://gitlab.cern.ch/lhcb/Detector/-/merge_requests/485Update sensitive detector mapping for Muon following new detector description in https://gitlab.cern.ch/lhcb/Detector/-/merge_requests/485Sim11/2024.03 (Gauss v60r1)Erika De LuciaErika De Luciahttps://gitlab.cern.ch:8443/lhcb/Gauss/-/merge_requests/1044Prepare Gauss v60r02024-02-14T19:52:31+01:00Gloria CortiPrepare Gauss v60r0Gloria CortiGloria Cortihttps://gitlab.cern.ch:8443/lhcb/Gauss/-/merge_requests/1043fix order of options to be compatible with mr 9792024-02-12T09:03:21+01:00Gloria Cortifix order of options to be compatible with mr 979This is needed for the qmtest renamed from Run3 to 2023 to work after applying !979 but it works also before that is applied
cc: @sponceThis is needed for the qmtest renamed from Run3 to 2023 to work after applying !979 but it works also before that is applied
cc: @sponceSim11/2024.03 (Gauss v60r1)Gloria CortiGloria Cortihttps://gitlab.cern.ch:8443/lhcb/Gauss/-/merge_requests/991Change the default value of timing barrier2024-01-31T22:36:28+01:00Michal MazurekChange the default value of timing barrierSim11/2024.02.14 (Gauss v60r0)https://gitlab.cern.ch:8443/lhcb/Gauss/-/merge_requests/973Add simple 2023 DD4hep vs. DetDesc tests2024-01-31T22:28:07+01:00Michal MazurekAdd simple 2023 DD4hep vs. DetDesc testsThis duplicates the tests that we have for 2023 in order to test the geometry description setup with `UT`.This duplicates the tests that we have for 2023 in order to test the geometry description setup with `UT`.Gloria CortiGloria Cortihttps://gitlab.cern.ch:8443/lhcb/Gauss/-/merge_requests/1037Fixes for lcg 1042024-01-29T10:34:57+01:00Marco Clemencicmarco.clemencic@cern.chFixes for lcg 104- fixed stand-alone compilation of public headers (see lhcb/LHCb!4211)
- some headers were fixed and some unused ones removed, in particular those containing syntax errors
- set the maximum C++ standard to 17 for GenEvent, because the ...- fixed stand-alone compilation of public headers (see lhcb/LHCb!4211)
- some headers were fixed and some unused ones removed, in particular those containing syntax errors
- set the maximum C++ standard to 17 for GenEvent, because the version of Pythia8 we use does not work with C++20 (see also Gaussino/Gaussino!158)https://gitlab.cern.ch:8443/lhcb/Gauss/-/merge_requests/984Replace GiGaMessage with Gsino::Message2024-01-18T15:46:50+01:00Michal MazurekReplace GiGaMessage with Gsino::MessageTo be checked with https://gitlab.cern.ch/Gaussino/Gaussino/-/merge_requests/70To be checked with https://gitlab.cern.ch/Gaussino/Gaussino/-/merge_requests/70Sim11/2024.02.14 (Gauss v60r0)https://gitlab.cern.ch:8443/lhcb/Gauss/-/merge_requests/1026Web documentation pointing now to master2023-12-15T11:25:08+01:00Gloria CortiWeb documentation pointing now to masterThe configuration for the default web documentation should no longer refer to `Futurev5` but to `master`.
`Futurev5` can still be selected as version, while the older tag `v60r0` that was pointing to an empty page is removed.The configuration for the default web documentation should no longer refer to `Futurev5` but to `master`.
`Futurev5` can still be selected as version, while the older tag `v60r0` that was pointing to an empty page is removed.https://gitlab.cern.ch:8443/lhcb/Gauss/-/merge_requests/939Enable magnetic field in Sim 11 & correctly access DD4hep conditions2023-12-11T16:39:38+01:00Michal MazurekEnable magnetic field in Sim 11 & correctly access DD4hep conditions@gcorti @kreps @adavis @clemenci
This activates the magnetic field for Sim11 for both DetDesc and DD4hep at initialize time. This has been done be setting `fieldVector` callbacks in magnetic field factories of Gaussino. In DD4hep case,...@gcorti @kreps @adavis @clemenci
This activates the magnetic field for Sim11 for both DetDesc and DD4hep at initialize time. This has been done be setting `fieldVector` callbacks in magnetic field factories of Gaussino. In DD4hep case, the access to `DeMagnet`'s `fieldVector is done by getting an IOV slice with the same run number that is set for ODIN in GenRndINit.
I also had to revisit the way we configure and access DD4hep conditions because DD4hep options are set at the same time in Gauss, LHCbApp and DDDBConf, where the last two depend on the global variable `UseDD4hep`, which no longer works as it is supposed to (in Gauss on the standard platform the choice of DetDesc/DD4hep happens at runtime and is steered from GaussGeometry() configurable).
I prepared a few manual tests using the G4 visuaulization tools in Gaussino. In each test we get just the magnet with a changing polarity. I'm shooting one 1 GeV electron to see if its trajectory is bent inside the magnet. The vector field is also visible. You can see the pictures below.
## Manual Tests
### DD4hep
In this case, we do not have the simulation database yet, so there's no magnetic field for the default `RunNumber=1`. I looked up 2 runs from rundb: one with mag up (`256293`) and one with mag down (`256175`)
#### Mag UP
![Screenshot_from_2023-02-13_11-49-45](/uploads/f822f7295537dd41ba7039f8cf30ebf5/Screenshot_from_2023-02-13_11-49-45.png)
#### Mag DOWN
![Screenshot_from_2023-02-13_11-50-54](/uploads/f3654025e5f3fd4d7aa9a1551edc6a16/Screenshot_from_2023-02-13_11-50-54.png)
### DetDesc
In DetDesc, `RunNumber=1` works, so the polarity can be checked using different versions of SIMCOND database. I used: `sim-20220509-vc-md100` for mag down and `sim-20220509-vc-mu100` for mag up. Btw the difference geometry-wise is that in DetDesc we also have part of BCM.
#### Mag UP
![Screenshot_from_2023-02-13_13-42-06](/uploads/f2522701b6d52dc05eb2fbc9cf2d27e2/Screenshot_from_2023-02-13_13-42-06.png)
#### Mag DOWN
![Screenshot_from_2023-02-13_13-39-08](/uploads/ed46b817ba2f8ea127046709ba8f36d0/Screenshot_from_2023-02-13_13-39-08.png)Sim11/2024.02.14 (Gauss v60r0)Gloria CortiGloria Cortihttps://gitlab.cern.ch:8443/lhcb/Gauss/-/merge_requests/901MuonHitChecker code modernization2023-11-17T11:03:26+01:00Erika De LuciaMuonHitChecker code modernizationhttps://gitlab.cern.ch:8443/lhcb/Gauss/-/merge_requests/1018Remove particles already in G4 10.7.32023-11-16T18:51:21+01:00Gloria CortiRemove particles already in G4 10.7.3XibPlus and XibMinus definition have been added to G4 10.7.3, so it is no longer needed to do so in Gauss and indeed it causes a compilation error.
```
G4WT3 >
-------- EEEE ------- G4Exception-START -------- EEEE -------
*** G4Excepti...XibPlus and XibMinus definition have been added to G4 10.7.3, so it is no longer needed to do so in Gauss and indeed it causes a compilation error.
```
G4WT3 >
-------- EEEE ------- G4Exception-START -------- EEEE -------
*** G4Exception : Run0117
issued by : G4WorkerRunManagerKernel::SetupShadowProcess()
Size of G4ProcessVector is inconsistent between master and worker threads for the particle <anti-xi_b+>.
size of G4ProcessVector for worker thread is 10 while master thread is 6.
*** Fatal Exception *** core dump ***
G4WT3 > **** Track information is not available at this moment
G4WT3 > **** Step information is not available at this moment
G4WT3 >
-------- EEEE -------- G4Exception-END --------- EEEE -------
G4WT3 >
G4WT3 > *** G4Exception: Aborting execution ***
```
This ports by hand the change for `Sim10` in !1003 and replaces the hotfix in !801 that was making the LHCb double definition use the same name as in Geant4.
cc: @mimazure, @veltri, @witoldp, @dpopovremove unused copy of src/GiGaPhysUnknowParticle and fix removal in the one in src/particle that is used
This was initially !1016 that has additional commits to introduce in Sim11 the fucntionality to defined particles on the fly.Sim11/2024.02.14 (Gauss v60r0)Gloria CortiGloria Cortihttps://gitlab.cern.ch:8443/lhcb/Gauss/-/merge_requests/1027Fix 2022_v1.0 and update docs for Future Upgrades run2023-11-16T18:24:09+01:00Emir MuhammadFix 2022_v1.0 and update docs for Future Upgrades run:warning: Needs to go in with Detector!461
These are the tiny changes essential for Future Upgrades.
This merge request changes the `2022` datatype path from `run3/2022_v1.0` to `run3/trunk`. Necessary because Detector!461 deletes `20...:warning: Needs to go in with Detector!461
These are the tiny changes essential for Future Upgrades.
This merge request changes the `2022` datatype path from `run3/2022_v1.0` to `run3/trunk`. Necessary because Detector!461 deletes `2022_v1.0`.
Also updates documentation for future upgrade devs.Emir MuhammadEmir Muhammadhttps://gitlab.cern.ch:8443/lhcb/Gauss/-/merge_requests/981Add generic calohits exporter & merger algorithms2023-11-16T10:14:56+01:00Mateusz KmiecAdd generic calohits exporter & merger algorithmsThis adds 2 algorithms:
- `CaloHitsExporter` that converts generic `Gsino::ExtDet::CaloHits` from Gaussino to `LHCb::MCCaloHits`
- `CaloHitsMerger` that merges multiple TES containers with `LHCb::MCCaloHits` into one.
Both are needed i...This adds 2 algorithms:
- `CaloHitsExporter` that converts generic `Gsino::ExtDet::CaloHits` from Gaussino to `LHCb::MCCaloHits`
- `CaloHitsMerger` that merges multiple TES containers with `LHCb::MCCaloHits` into one.
Both are needed in simulations mixing detailed and fast simulation output from the calorimeters.https://gitlab.cern.ch:8443/lhcb/Gauss/-/merge_requests/1009Fix xml_writer for Detector Refactoring2023-11-01T15:03:08+01:00Emir MuhammadFix xml_writer for Detector Refactoring:warning: Goes in with Detector!428
Fixes `xml_writer.py` to be compatible with the changes introduced in Detector!428.
This is essentially done by adding a new `compVersion` that `xml_writer.py` can track.
(It should be noted that i...:warning: Goes in with Detector!428
Fixes `xml_writer.py` to be compatible with the changes introduced in Detector!428.
This is essentially done by adding a new `compVersion` that `xml_writer.py` can track.
(It should be noted that in the future it would be nice to migrate this towards Detector instead of Gauss :) ).
Things to review:
- [ ] In all_trunk, are we missing any sub-detectors or if we are including ones that aren't needed (eg Gvalve?)
- [ ] Check if these changes work in all use cases. We've only checked using `ci-test` but not much elseMenglin Xumenglin.xu@cern.chEmir MuhammadMenglin Xumenglin.xu@cern.chhttps://gitlab.cern.ch:8443/lhcb/Gauss/-/merge_requests/1023Prepare v56r7 release2023-10-31T20:09:33+01:00Gloria CortiPrepare v56r7 releaseDocumentation and dependencies for Sim10 release to allow for 2024 MC productionsDocumentation and dependencies for Sim10 release to allow for 2024 MC productionsSim10/2023.10.31https://gitlab.cern.ch:8443/lhcb/Gauss/-/merge_requests/1019Add examples for 2023 and 2024 config and change upgrade generic tests to hav...2023-10-31T10:55:39+01:00Gloria CortiAdd examples for 2023 and 2024 config and change upgrade generic tests to have them per yearActualisation and clean up of tests for different configuration for Run3:
- add example steering and db tags for 2023 and 2024
- remove upgrade error files because identical to run1 and run2
- add options to switch off spillover when ot...Actualisation and clean up of tests for different configuration for Run3:
- add example steering and db tags for 2023 and 2024
- remove upgrade error files because identical to run1 and run2
- add options to switch off spillover when otherwise active
- modify tests for run3 removing upgrade from the name and covering all yearsSim10/2023.10.31https://gitlab.cern.ch:8443/lhcb/Gauss/-/merge_requests/864Add pre-commit checks to fix formatting2023-10-27T16:21:39+02:00Marco Clemencicmarco.clemencic@cern.chAdd pre-commit checks to fix formattingSim11/2024.02.14 (Gauss v60r0)https://gitlab.cern.ch:8443/lhcb/Gauss/-/merge_requests/953add of CALO hits for DD4hep2023-10-23T18:11:28+02:00Daniele Manuzziadd of CALO hits for DD4hepThis MR makes Gauss able to save ECAL and HCAL hits in its output file.
Modifications are done on top of [lhcb/Gauss!957](https://gitlab.cern.ch/lhcb/Gauss/-/merge_requests/957) and [lhcb/Gauss!959](https://gitlab.cern.ch/lhcb/Gauss/-/me...This MR makes Gauss able to save ECAL and HCAL hits in its output file.
Modifications are done on top of [lhcb/Gauss!957](https://gitlab.cern.ch/lhcb/Gauss/-/merge_requests/957) and [lhcb/Gauss!959](https://gitlab.cern.ch/lhcb/Gauss/-/merge_requests/959). The news from [lhcb/Detector!337](https://gitlab.cern.ch/lhcb/Detector/-/merge_requests/337) is also assumed.
TODO:
- [ ] compare the output with DetDesc.
Optimization:
- [x] `CellFromDD4hep.h` reports 3 methods for the conversion between the ID of the volumes in `dd4hep` and the `Detector::Calo::CellID` (2 of them are commented now). All of them provide the same result. Todo: local test to choose the fastest one.Sim11/2024.02.14 (Gauss v60r0)Gloria CortiGloria Cortihttps://gitlab.cern.ch:8443/lhcb/Gauss/-/merge_requests/995Turn off the default behavior of Madgraph cuttool.2023-10-18T11:23:12+02:00Nathan Allen Griesernathan.allen.grieser@cern.chTurn off the default behavior of Madgraph cuttool.Decay files should have the option to pass cut tools to the Madgraph configuration, and not have it being forced to none.
We should probably also think about if we want to remove some of these other default settings to avoid this sort o...Decay files should have the option to pass cut tools to the Madgraph configuration, and not have it being forced to none.
We should probably also think about if we want to remove some of these other default settings to avoid this sort of issue in the future where people don't realise their `dkfile` options are being overwritten by the defaults.Gauss/v56r6Nathan Allen Griesernathan.allen.grieser@cern.chNathan Allen Griesernathan.allen.grieser@cern.chhttps://gitlab.cern.ch:8443/lhcb/Gauss/-/merge_requests/968Include supersymmetric (non SM) particles in the treamtment of Geant4 unknown...2023-10-10T20:32:58+02:00Michele VeltriInclude supersymmetric (non SM) particles in the treamtment of Geant4 unknown particlesInclude also supersymmetric (non SM) particles in the treamtment of Geant4 unknown particles.
Addresses issues raised in [presentation](https://indico.cern.ch/event/1265492/contributions/5390343/attachments/2644422/4576940/Sim_Exp.pdf) ...Include also supersymmetric (non SM) particles in the treamtment of Geant4 unknown particles.
Addresses issues raised in [presentation](https://indico.cern.ch/event/1265492/contributions/5390343/attachments/2644422/4576940/Sim_Exp.pdf) by @melashri & @chenders at Simulation Development Meeting on 10 May 2023Gauss/v56r5Michele VeltriMichele Veltri