Open gabemery opened 1 year ago
The same applied to a subrun works correctly. It happens with both the available (v0.9) merged run (13396) and a merging I produced with 10 subruns and lstchain 0.9.6.
Just to be sure: did you merge 0.9 files using lstchain 0.9? or did you try merging files written with 0.9 using lstchain 0.10?
Looking at the code, it just iterates over all tables in the file and doesn't make any difference between things that should stay the same (e.g. instrument tables) and things that need to be concatenated.
I wonder why this ever worked....
Ok, short answer is: "this never worked"
The OSA merged files have this issue. It seems this only worked because the camera geometry wasn't used after dl1.
Just to be sure: did you merge 0.9 files using lstchain 0.9? or did you try merging files written with 0.9 using lstchain 0.10?
I merged v0.9 (OSA) files using lstchain 0.9.6 and also got the same error on already merged files with v0.9 (OSA) .
It seems this only worked because the camera geometry wasn't used after dl1.
Probably, i only got this issue because I was using the merged file in magic-cta-pipe. When initiating HillasReconstructor(subarray)
before adding stereo parameters.
I am trying to use merged dl1 files from LST data and the following method fails :
subarray.camera_types[0].geometry.neighbor_matrix_sparse
wheresubarray = SubarrayDescription.from_hdf(input_file)
The same applied to a subrun works correctly. It happens with both the available (v0.9) merged run (13396) and a merging I produced with 10 subruns and lstchain 0.9.6.
Here is the error message :
I also see in the hdf5 file the LST geometry (in configuration/instrument/subarray/telescope/camera/geometry_0) contains 18550 elements instead of 1855. So it looks like the pix_id, pix_x, pix_y and pix_area are stacked for each subrun.