You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
TimestampPackets only have a chip_key attribute (not an io_group field), so this is skipped when converting the packets to array data within the LArPix hdf5 format. This is a bug - we should be tracking the io_group data for all packet types.
The text was updated successfully, but these errors were encountered:
@peter-madigan I've recently noticed this issue in larnd-sim when it simulates timestamp packets, since it uses larpix-control. Are there any plans to address this bug? Do you have a vision of how this bug could be addressed? Is it as "simple" as modifying packet/timestamp_packet.py?
No plans as far as I know, but this should be fixed.
I think it should be a simple fix of adding a property to the timestamp packet so that it will parse the io group out of the chip key if it is available. Something like:
@property
def io_group(self):
if self.chip_key is not None:
return None
else:
return self.chip_key.io_group
You'd also need to modify the method that creates the timestamp packets from the pacman messages:
TimestampPacket
s only have achip_key
attribute (not anio_group
field), so this is skipped when converting the packets to array data within the LArPix hdf5 format. This is a bug - we should be tracking theio_group
data for all packet types.The text was updated successfully, but these errors were encountered: