-
Related to #237
Provided cleaning levels are set to 0 in order to keep all the events, it does not make sense to calculate Hillas parameters. Thus DL1 output file should contain only images and pu…
-
From looking through the code the default (only) way to calculate the Hillas parameters seems to be in the camera frame. Probably the default behaviour of this of this code should be to calculate the …
-
In the framework of the [comparison](https://forge.in2p3.fr/projects/benchmarks-reference-analysis/wiki/Comparisons_between_pipelines) between _protopipe_ and _CTA-MARS_, and in particular looking at …
-
It would be useful to access directly the "alpha" image parameter instead of calculating it in a separate step.
-
Hello Everyone.
I'm having trouble reconstructing the direction on diffuse gammas.
Here is the code I use. I basically took it from the example scripts. The code below is executed for each event.…
-
I need to calculate the hillas parameters in a experimental analysis framework as part of a masters thesis. The routines in ctapipe would be very handy, since they allow arbitrary camera geometries an…
-
@kosack and I discovered that there seems to be an inconsistency between the direction of the axis against which the psi angle is defined.
Function 1 does not agree with at least function 2 and 4.
T…
-
Currently the default behaviour of the CameraGeometry class is to return the position of the camera pixels de-rotated by the camera rotation angle defined in sim_telarray. But I'm not really sure this…
-
Hi
These are two related issues (discovered them at the same time) that actually compensate each other.
1. The altitude info is not correctly set in the MC production for point source gammas. I …
-
This is just a reminder to look into why slicing is now causing a large overhead in calculating hillas params (it's probably something simple). Note that in this case, the mask and therefore sliced d…