Pointing frame lambda

[laspsandoval]

Change Summary

Overview

Provides algorithm that mocks Nick Duttons pointing frame (DPS frame) kernel generation. Note that I have TODOs that will be included in the next tickets.

New Files

• pointing_frame_handler.py
  • writes a new C-kernel file containing the averaged pointing data
• changes in the environment: poetry.lock, requirements.txt, pyproject.toml

Testing

• test_pointing_frame_handler.py
  • tests pointing_frame_handler.py
• imap_science_0001.tf
  • pointing frame kernel used for test data
• imap_sclk_0000.tsc
  • spacecraft clock kernel used for test data
• imap_wkcp.tf
  • spacecraft frame kernel used for test data

[greglucas]

I left some initial comments, but want to bring a bigger question up as I might not be up to speed on all of the past decisions. This seems like 2 things going on to me here. 1) how to create the new frame kernel, and 2) how to use that within the infrastructure. Right now those are blended together in this single PR, but I'd like to propose separating them out. (1) could be in imap_processing so that all of our SPICE helper routines etc. are in a single location and we load kernels, and save kernels using the same exact utilities. (2) we can make a lambda/batch/whatever that depends on imap_processing if needed and calls this routine. I personally like the separation of concerns so we don't force infrastructure decisions based on processing, or vice-versa.

I think that decision will impact future reviews, so didn't review everything in-depth.

[laspsandoval]

@greglucas I thought about your question for a while too. Let's talk at Monday's meeting if that is ok. I re-read your comment and probably you are right. It would be easy to move it to imap_processing, but let's discuss.