Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Figure out how to display inter-satellite links based on conditions in VTS #26

Open
Nosudrum opened this issue May 25, 2023 · 2 comments
Assignees
Labels
feature New feature or request

Comments

@Nosudrum
Copy link
Member

No description provided.

@Nosudrum Nosudrum added the feature New feature or request label May 25, 2023
@Nosudrum
Copy link
Member Author

Nosudrum commented Jun 8, 2023

Turns out variable (on/off based on an MEM file) inter-satellite links isn't really doable, but this is the way to do it : two sensors on the satellite (2 IRIDIUM antennas or 2 GNSS antennas, depending on the simulation) with their own specs (angle, frame). Also have mission events in VTS linked to the respective IRIDIUM and GNSS satellites that say AOS_1 and LOS_1 (1 or 2 depending on the sensor) when there is a visibility window with TOLOSAT as computed by the Python code.

@Nosudrum
Copy link
Member Author

Nosudrum commented Jun 8, 2023

What needs to be automated :

  • Adding the two sensors to TOLOSAT (IRIDIUM or GPS based on an input setting)
  • Adding the nadir sensor to all IRIDIUM or GPS satellites. Use hard coded specs for now
  • Switch sensors to use specs in new text file in input_data, structure to be defined
  • Export individual per-satellite windows from the doppler processing script
  • Compute MEM files from the windows files to be used as AOS/LOS mission events in VTS
  • Automate the creation of AOS/LOS mission events for all the satellites

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature New feature or request
Projects
None yet
Development

No branches or pull requests

4 participants