... | ... | @@ -71,5 +71,3 @@ Notes from HD: |
|
|
- HD to RU: The Stack should hold on to allocated memory and not give it back, to minimize the very costly allocations and deallocations. Ideally, the Stack would be placed on the stack (I am talking about what people normally call stack in C++, the non-dynamically allocated memory used by a program), by implementing it based on std::array or similar. The particles placed on the Stack should be trivially constructible types, so that copying a particle is a matter of copying bits around. Under these conditions, using the Stack could be fast enough. If the photons have to be stored somewhere anyway, they should be put on the stack.
|
|
|
|
|
|
- DB: Cherenkov photons are in physics terms a ```ContinuousProcess``` even if they there contribution is rather small. For most implementations the exact track must be known (similar to Radio). Cherenkov Photons do require some sort of storage/stack... (see [Requirement DynamicStack](Requirement-list-for-the-Dynamic-Stack)) |
|
|
|
|
|
- RU: try to resolve this here: Cherenkov process is a ContinuousProcess. Cherenkov photons need to be stored, and this should happen on "a" stack. This Stack does not need to be the identical one used for real particles, but this could be arranged with a "stack decorator". |
|
|
\ No newline at end of file |