Check SpEC version when importing

[nilsvu]

Proposed changes

Check the SpEC version when import Python modules to make sure it's compatible (of course the real solution is to port SpEC modules into SpECTRE when we need them or factor the code into a separate repository, but that requires some work and comes with a maintenance burden keeping the two codes in sync).

Upgrade instructions

To use eccentricity control, make sure you're pointing to a recent enough SpEC version (Aug 2024) and update your Python environment with pip install -r Support/Python/requirements.txt to pick up the new git dependency (if running on CaltechHPC you don't have to do anything).

Code review checklist

• The code is documented and the documentation renders correctly. Run
  make doc to generate the documentation locally into BUILD_DIR/docs/html.
  Then open index.html.
• The code follows the stylistic and code quality guidelines listed in the
  code review guide.
• The PR lists upgrade instructions and is labeled bugfix or
  new feature if appropriate.

Further comments

[knelli2]

Will this be superceded by #6471? @nilsvu @nilsdeppe

[nilsvu]

no I don't think so. rebased.

[knelli2]

CI very unhappy

[knelli2]

@nilsdeppe Did you want to take a look at this? Check that it works on mbot?

[nilsdeppe]

Yes, please don't merge this because it'll break mbot and I don't have time to upgrade spec right now.

…

On Tue, Feb 11, 2025, 14:09 Kyle Nelli ***@***.***> wrote: @nilsdeppe <https://github.com/nilsdeppe> Did you want to take a look at this? Check that it works on mbot? — Reply to this email directly, view it on GitHub <#6467 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ADHHPFWE2F4PO5XX5EYQRHL2PJDF3AVCNFSM6AAAAABWI72TAGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDMNJRHAZDGMRWGA> . You are receiving this because you were mentioned.Message ID: ***@***.***>

[nilsvu]

It shouldn't break mbot, only the unit tests that try to import spec will fail (ecc control and initial orbital params).