CORSIKA 8 general meeting

Thursday Jun 2, 2022, 5:00 PM → 6:30 PM Europe/Berlin

Zoom

Tim Huege (KIT)

Connect to ZOOM meeting room:

https://zoom.us/j/99307684644?pwd=SlFxOXcvWHBCcEM1WVY2TU9DOXJmQT09 

 

5:00 PM → 5:10 PM Some news and infos

Speaker: Tim Huege (KIT)

- we have 30+ participants in the C8 workshop

- please sign up a talk title if you have something to contribute, by June 17th

- please print the poster from the Indico page and post it on blackboards in your institutions

5:10 PM → 5:30 PM Update on "cascade fix"

Speakers: Maximilian Reininghaus (KIT / IAP), Nikos Karastathis (Karlsruhe Institute of Technology)

- Max, Nikos and Jean-Marco have been working on the "Step" interface

- there is some duplicity between Step and Track, in the long run we will want to get rid of Track; Lukas suggests to deprecate it such that developers get compile-time warnings and are encouraged to move away from using Tracks

- we discuss about the logic of applying cuts: the energy cut should be done in the first process of the process list; if the particle falls below the cut threshold, the track end position needs to be updated to reflect the position where the particle is cut and the "absorbed" flag needs to be set

- the absorbed flag should be passed on between modules on the process list; some modules will just ignore "absorbed particles", others will work on them normally (TrackWriter, radio calculation)

- in principle, if we had modules that could increase particle energy (say electric field effects), they could also "unabsorb" particles when they again go above the cut threshold

- this is a minimally invasive change, we have to revisit the overall design soon, likely at the HD workshop

- Max and Nikos found out that there seems to be a fundamental problem with particles being in a different volume than they think they are; it might just happen at volume boundaries - Max and Nikos will investigate

- we still get C8 showers with longitudinal profiles much deeper than in C7, possibly related to the "volume issue", but possibly also an independent problem; Lukas suggests to use "git bisect" to find when things broke

- this illustrates that we need to improve our automatic validation tests!