add LPM effect as neumann rejection sampling

See merge request !530

corsika.cpp prints out the seed independently of logging level

See merge request !517

Fix extra star

See merge request !526

fixed target directory

See merge request !524

conan-install into specified directory

See merge request !523

Resolve "Wrong indexing for nested ProcessSequences?"

Closes #586

See merge request !520

update proposal in conanfile to version 7.5.1

See merge request !501

Resolve "Reduce number of unnecessarily linked boost libraries"

Closes #571

See merge request !506

Resolve "particles with lifetime zero get stuck in infinite loop"

Closes #598

See merge request !515

Adapt condition in `SwitchProcessSequence` similar to !507

See merge request !514

Merge branch '584-cascade-inl-calls-interactions-with-cross-sections-that-are-zero-causing-warnings' into 'master'

Add two tests dealing with 0_mb cross sections in Cascade and ProcessSequence

Closes #584

See merge request !507

Jean-Marco Alameddine authored 1 year ago and Maximilian Reininghaus committed 1 year ago

Add same treatment to selectDecay as in selectInteraction (see commit a9620174)

Jean-Marco Alameddine authored 1 year ago and Maximilian Reininghaus committed 1 year ago

Adapt `ProcessSequence` so that if cx_select and cx_sum are zero, we don't select any interaction instead of the first one.

Adapt `Cascade`. In case a discrete interaction has been selected, it will only delete the initial particle from the stack
if `interaction` or `decay` have actually returned that they have called an interaction process or a decay process.
If this is not the case, which means we did not call `doInteract` or `doDecay`, we will keep the particle on the stack.

Jean-Marco Alameddine authored 1 year ago and Maximilian Reininghaus committed 1 year ago

This commit adds tests to testProcessSequence and testCascade.
In the first test, we create a sequence with only one InteractionProcess with a cross section that is 0.
We check that calling `selectInteraction` does not call the `doInteraction` method of the process.

In the second test, we create a `Cascade` object, based on a sequence including an InteractionProcess with a cross section that is zero.
Again, we check that the `doInteraction` is not called. Furthermore, we check that `Cascade` does not delete the initial particle from the
stack (it should not be deleted since it did not interact!)