v0.3.0

Alright this is a biggie, as you can now use Metis to plan and execute fairly complex manouver and coasting sequences, so expect many bugs.

User Features

• Added: Configurable event triggers (6 types)

Metis has a set of pre-programmed event triggers (see the Wiki for details on these) currently used for manouver and coasting commands in the spacecraft file. The interesting part of this feature is Metis will not waste time or resources checking conditions or calculating variables that the user has not specified as triggers, nor will it check triggers that are not next in the queue. The performance overhead from this feature is incredibly small (at least from my telling) but allows for a huge number of triggers or parameters that can be called or requested in the future, with next-to-no impact on performance. Please request triggers in the discussion page or issues page if you have ideas, as I only have 6 types currently.

• Added: Spacecraft coast command

A simple 'progress until trigger' command has been added to allow for much more complex but flexible mission sequencing. It basically runs the sim until the trigger is met, then moves on to the next event in the sequence

• Added: New example spacecraft files

I've packaged 2 new spacecraft files (lunar_return.cfg and lunar_transfer.cfg) with fully written sequences for returning from, and transfering to, lunar orbit. Be advised that these may need some tweaking if the bodies config file has updated planetary positions, but they should serve as good starting points. To use, either transfer the contents to test_sat.cfg or in SIM_CONFIG.cfg change the name of desired spacecraft file.

• Updated: TIME Trigger type

The TIME event trigger previously executed as 'time since sim start'. Now it executes as 'time since last event'. This is inline with the mission sequencing format I am going for, and links to a change mentioned later on

• Updated: bodies (sun_earth_moon).cfg parameters updated to JPL Horizons values for 16/08/2025
• Updated: Order of events in the spacecraft file now matters

Metis will execute the events stored in the spacecraft file in the order they are written, which is a bit different from my original intended design direction however it made more sense this way.