-
Notifications
You must be signed in to change notification settings - Fork 0
Description
I just added some code that decoms header 3, but it is not complete yet (6d7ee5f600e...)
The function I added can clearly be compared to table 11-1 in the Users Guide.
There is a class to decom header 3 which works like an accumulator. While decommuting frames, the corresponding header packets are passed to the call method one by one. The class then keeps track of the most recent header 3 sub-packets. It is relatively easy to then assemble them and set the proper values, after one knows which sub-packets are there (the class knows that).
The questions are:
- When to request the header 3 (at a given time when everything is set? at every frame with incomplete data?).
- When to clear header 3 sub-packets (when image type is not 6 or 7? when it is 0, 1, or 2?). The class currently clears the header 3 packets when the image type changes, but maybe one does not want that.
This matters because images can come completely out of phase. The records for DSN_RecordCount and PixelOffset_32bit_C cross sub-packet boundaries, so are sensitive to this. CCD_Temperature is split, but each part is complete (just in different units).
I hope this makes sense thus far. I can edit it if it is not clear.