Wrap Up

• [ ] create a notion page summarize findings on the number of imaging passes
• [ ] write up on the trade case done for selecting target tracking for the image pass (@Connor Wilson)

Timeline:

• Compile a video of all the imaging passes based on the two possible positions (x, y) - (1)
  • STK - Basically figure out pointing vector during target tracking and record valid passes
• Quantitative data:
  • First step is to determine all imaging passes given constraints (e.g. determine a set of time arrays) [ [0.0000, 1.0000, 2.0000], [12.0000, 13.0000, 14.0000] … ]
  • Number of imaging passes per year → direct result of step 1
  • Slew rate → Plots of best case slew rate overtime
    • From this, plot of estimated attitude error overtime
  • imaging time

Present at systems (MID-LATE JAN)

Once star tracker placement decision has been made…

• Meet with arcsec once a position is selected and get their opinion
• Figure out the maneuver to use (STK)
  • Figure out minimum skew due to albedo
    • Is this possible to do in the automatic target tracking
• Figure out the operations and data to and from the module during nominal scenarios
• Figure out what the pipeline looks like for ADCS (best way to actually perform image passes)
  • assumptions: we’ve selected a star tracker position and have the data from tensor tech
  • Turn what we get from tensor tech to convert it to a more accurate simulations to get gains, star tracker error, slew rate
  • Once we know all the imaging passes in theory, figure out how we want to send data to module (Which coordinates and when, how often)
  • Quantify the size of this information, explore “compression” methods if necessary

Check results with tensor tech (~MARCH)

Create protocol documentation and standardize the process (integrate with ops?)

END OF WINTER SEM