DDSim: correct the number of events when running over all events (-1)

[andresailer]

BEGINRELEASENOTES

• DDSim: correct the number of events when running over all events (-1), fixes [ddsim] Get total number of events and time per event right #1257
• GenerationActionInit: declare properties to access number of processed runs (numberOfRuns) and events (numberOfEVents)
• DDG4: decode or eval all properties out of str or cppyy.gbl.string types

ENDRELEASENOTES

[github-actions]

Test Results

   14 files     14 suites   7h 4m 55s ⏱️
  363 tests   363 ✅ 0 💤 0 ❌
2 496 runs  2 496 ✅ 0 💤 0 ❌

Results for commit 991228d.

♻️ This comment has been updated with latest results.

[andresailer]

@MarkusFrankATcernch
Is this the best way to let me read the number of events from the plugin, or is there something else that would be cleaner?

[MarkusFrankATcernch]

@andresailer In principle there is a property
Geant4Kernel::NumEvents, which defines the number of events to be processed.
This property is then passed to Geant4Exec, where the G4 machinery is invoked.
Does this property not work or is this not sufficient to do the computation?

[andresailer]

@andresailer In principle there is a property Geant4Kernel::NumEvents, which defines the number of events to be processed. This property is then passed to Geant4Exec, where the G4 machinery is invoked. Does this property not work or is this not sufficient to do the computation?

But here the number of events to be processed is going to be -1, so I want to check the actual counter of events processed.

[MarkusFrankATcernch]

@andresailer Correct.
Then this approach looks correct.

[andresailer]

Thanks @MarkusFrankATcernch