This is the high level ticket covering all the work needed to produce the Lo pivot platform CK.
Things that are needed:
- Decide on how the time coverage of the kernel will be handled. Should it build, appending new coverage, for some duration then reset similar (or exactly?) to how the attitude history and pointing attitude kernels work? Further thinking about how this could work: Could it use the same partition as the pointing attitude job? That may be the way to match up the time coverage between the two.
- Figure out details about when the Lo pivot is moved. Can we just have a gap in coverage in the kernel for this time? Is any science being taken when it is moved?
- Implement the code to take in Lo L1B (TBR) housekeeping products and generate the C kernel. Do we append to the previous Lo pivot kernel?
- Need to determine naming convention for this kernel.
- Add the kernel job to Dagster
This is the high level ticket covering all the work needed to produce the Lo pivot platform CK.
Things that are needed: