Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

final tof params object #25

Merged
merged 164 commits into from
Nov 25, 2022
Merged

final tof params object #25

merged 164 commits into from
Nov 25, 2022

Conversation

noferini
Copy link

No description provided.

mfasDa and others added 30 commits November 8, 2022 14:37
* increase factorize lanes to 10

* Increase number of Buffer to 100
Spotted by some syntetic run. The copy was taking 10% of the CPU
utilization.
And per default make the container type the same as the input type.
Useful in case the object send to the aggregator is in itself already
a container as for example a histogram.
…during device compilation"

This reverts commit 73c10d5.
Dmitri Peresunko and others added 29 commits November 22, 2022 10:16
* ITS DCS parser: add always run number to metadata

* clang
Mapping pad channel to position on pad layer
The TriggerOffsetsParam configurableParam got array of custom corrections per detector (0 by default)
which can be applied to triggered detectors IR as an ADDITIVE correction during CTF decoding.
Note that this convention is opposite to that for the LM_L0 convention which is subtracted from the
encoded IR (at the moment only for the TRD if an option --correct-trd-trigger-offset was provided to the
ctf-reader). Therefore, for the TRD, if this option is ON, the effect of the correction is
ir_corrected = ir_decoded - TriggerOffsetsParam::LM_L0 + TriggerOffsetsParam::customOffset[TRD];
while for other EMC,PHS,CPV and HMP (and TRD in absence of --correct-trd-trigger-offset) it is simply
ir_corrected = ir_decoded + TriggerOffsetsParam::customOffset[<det>];

In case the correction moves the IR before the TF 1st orbit, the trigger is discarded.

Extra: ZDC in pbpb2022 was reseting the orbit internally to 1 at the SOR: implemented the shift also for it.
- Calibrated time and calibrated energy were switched which results in
  wrong values energy and time in the AO2D file
This patch allows outputting the full vdrift exb calibration to a file.

Additionally, it adds a previously missed function call to update the
configKeyValues from cli args.

Signed-off-by: Felix Schlepper <[email protected]>
These special triggers can be shifted only orbit-wise but the BC must remain unchanged
Compare data-members explicitly to avoid padding problems in blockwise comparison
* HepMC and Gen status codes handled/entangled via Union as one single
  integer

* some common functionality to en-/decode

* encoding fully implemented for Pythia8, O2Kine and HepMC generators

* be backwards-compatible wrt to HepMC status code

* O2Kine generator now sets the status code correctly

* use ParticleStatus::kToBeDone for TParticle in generators at
  Generator::importParticles to indicate whether to-be-done or not
@njacazio njacazio merged commit 399320f into njacazio:nj-param_container Nov 25, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.