TableLoader has uniqueness pre-conditions when merging the different tables,
mainly on sb_id in the scheduling blocks, obs_id in the observation_blocks and the event primary keys in the event tables.
We don't check if these pre-conditions are met and astropy table joining explodes the rows in case of non-unique rows.
To Reproduce
Merge the same file twice using ctapipe-merge, read it with table loader.
Describe the bug
TableLoaderhas uniqueness pre-conditions when merging the different tables, mainly on sb_id in the scheduling blocks, obs_id in the observation_blocks and the event primary keys in the event tables.We don't check if these pre-conditions are met and astropy table joining explodes the rows in case of non-unique rows.
To Reproduce
Merge the same file twice using ctapipe-merge, read it with table loader.
Expected behavior
Some kind of user-friendly error