sync#315
Closed
GiuliaPaggi wants to merge 99 commits into
Closed
Conversation
We have new geofiles for all configurations, testbeam and TI18, with the new Scifi model and adding the 2023 emulsion target run 5 geo calibration.
This actually makes life easier as now all filenames are consistent and we removed the versions featuring date/month/year.
Use input data to adjust the scoring plane (flux window in Genie)! Ran Clang-formatting on the file.
Includes a brief description of the software versioning convention to be followed. We start off with the first release and list of additions/changes/fixes.
The here-fixed time_lower_range unit was correctly set everywhere else in the SciFi tools
* 2dED: Add option to filter SciFi hits by time It is basically using one of the existing SciFi analysis tools. Added informative control and helper messages to quide the user how to use the option FilterScifiHits with the loopEvents() function.
--no-extra-info to suppresses printing the detailed event time/QDC information
--extension allows for choosing the format of the saved file. E.g., png, pdf , root, etc.
--rootbatch runs in ROOT batch mode
--collision-axis draws the collision axis as a dotted red line in (x, y) = (0, 0)
---------
Co-authored-by: Cristovao Vilela <cvilela@lxplus910.cern.ch>
Co-authored-by: Oliver Lantwin <oliver.lantwin@cern.ch>
includes also configuration settings for analyses of TI18(2022-2023 and 2024-), and 2023 and 2024 testbeams
… with static_cast
…in hitPositionVectorsPerStation()
Adding MC Event Builder Task and its run manager. Noise filter parameters are stored in a namespace, together with other used constants. Beware: One has to free memory of the TClonesArray to avoid point/track leaking to following event chunks. Some specifics of the task are: - An event's header is copied to all its chunked events. - The mother track is only copied in the first event, unless it has MC points in the following ones. - To keep track of track indices, one has to create MCTrack array of the same size for each event chunk. Originally each such array is filled with dummy tracks using the ShipMCTrack standard ctor (PdgCode = 0). Only tracks having MC points in a given chunk are overwritten with their true values. --------- Co-authored-by: Oliver Lantwin <oliver.lantwin@cern.ch> Co-authored-by: siilieva <simona.ilieva.ilieva@cern.ch>
Move from TClonesArray to std::vector in the plane class functions!
…5nsOnly Spotted by @olantwin
This gives a hande to tag NC nu events in analysis.
Before July 2022 the Scifi signal speed was not determined, thus missing from the geofiles. At that time it was not a problem for digitization cause light propagation in the fibers was not simulated. The latter effect was added in Nov 2023. Ever since, if one re-digitizes old MC, it is essential to have that parameter set.
0.5**u.mrad translates to ~1 rad which is correct given ** is python's power operator Of course, it is catastrophic for positions. Fixed the only two occurrences, but one of them is 0**mrad so the corresponding run_258 was not affected.
For the cases of passing muon, DIS and Genie events.
Once again need to bypass FairROOT branch management.
This is the list advised by G4 manual, also recently employed in FairShip.
The correct spell was found in deprecated documentation https://root.cern/d/special-cuts-and-regions.html Also adding a few more useful commands for future debugging.
…and line This is not a production cut, but a storage one. If a particle's Ekin drops below the cut value, its MC track is not saved to the MC track stack. However that particle is still tracked and energy loss is generated thus MC points are created and stored. These MC points have fTrackID=-2. The default value for the Ekin storage cut is the usual 100 MeV.
Using 2022-2025 datasets these parameters were revised. The atten. length is much dependent on the bar. Precise simulation of the response will have to feature per-bar fluctuations as these are large 130-330cm for US and Veto! For now using a single value. Perhaps it is enough given the bars are only 42cm(Veto) and 82cm(US) long. Note these parameters are also slightly dependent on the daq calibration. So a meticulous model will have to take this into account.
Urge the user to regenerate the MC production, not only re-digitize, shall they use outdated sim files. This state is easily detectable through the digi parameters as the update of the latter coincides with the *major* update of Geant4 production cut and physics list!
MuFilter spatial alignment consts are very similar to the 2025 ones, as should be given the detectors were not moved. Anyways, since we moved to a geofile per year, better recalibrate and use new values.
Another task will handle mini DT data.
…uding white SND@LHC logo.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
9 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
sync to prepare for future merge