Design choice: mcps

[martin-rdz]

Switch from a mixture of photon counts and mcps to mcps consistently in the code.

ToDo @HolgerPollyNet : clarify if the factor should be 50 or 150

[martin-rdz]

It's c/2 = 150 m/μs (travel time of light back and forth).
Divided by 7.5m range resolution, thats 20 μs^{-1}, which is equivalent to 50ns sampling duration per height bin.

So the equation should be

$$ \text{PCR} = \frac{\text{signal}}{\text{mshots} \, \cdot \, \text{sample\_duration\_per\_height\_bin }} = \frac{\text{signal}}{\text{mshots}} \, \frac{c}{2} \, \frac{1}{\text{hRes}} $$

Implicitly the 1e-6 in μs seems to be omitted to directly give the megacounts.

[ulysses78]

$$ \text{sample\_duration\_per\_height\_bin } = \frac{2 \cdot \text{h}_\text{res}}{\text{c}} = \frac{2 \cdot \text{7.5m}}{\text{300000000 m/s}} = \text{50} ns $$

[ulysses78]

Nice to have it in such clear and understandable formula :-)

[HavardStridBuholdt]

Similarly to the MCPS/PCR and photon count mixture, we also should be more consistent on the RCS usage in the future. In the current version we calculate the RCS from the PCR signal in the prepossessing and save it as an output. However this is never used later in the code and the RCS is instead recalculated from the photon count (BG corrected) signal whenever it is needed.

Additionally, at the moment we also aggregate the signals differently. The RCS is averaged while everything else is summed. We should find a more consistent way of doing this. Either sum everything or averaged everything.