Ops update

[aburrell]

Description

Cycles Python support for updated operational environment.

Type of change

Please delete options that are not relevant.

• New feature (non-breaking change which adds functionality)
• This change requires a documentation update

How Has This Been Tested?

Verified ops configuration.

Test Configuration

• Operating system: Red Hat
• Version number: Python 3.9
• Any details about your local setup that are relevant

Checklist:

• Make sure you are merging into the develop (not main) branch
• My code follows the style guidelines of this project
• I have performed a self-review of my own code
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• My changes generate no new warnings
• I have added tests that prove my fix is effective or that my feature works
• New and existing unit tests pass locally with my changes
• Any dependent changes have been merged and published in downstream modules
• Add a note to CHANGELOG.md, summarizing the changes

If this is a release PR, replace the first item of the above checklist with the
release checklist on the pysat wiki:
https://github.com/pysat/pysat/wiki/Checklist-for-Release

[jklenzing]

Are there specific versions of the other scientific python codes (pandas, scipy, xarray) that the new ops environment is running? We may want to use those in addition to numpy.

[aburrell]

I asked, and these were the specs I got :/ I think numpy is the limiting factor for the rest of them. From: Jeff Klenzing ***@***.***> Reply-To: pysat/pysatSpaceWeather ***@***.***> Date: Tuesday, September 17, 2024 at 13:59 To: pysat/pysatSpaceWeather ***@***.***> Cc: "angeline.burrell" ***@***.***>, Author ***@***.***> Subject: Re: [pysat/pysatSpaceWeather] Ops update (PR #152) Are there specific versions of the other scientific python codes (pandas, scipy, xarray) that the new ops environment is running? We may want to use those in addition to numpy. — Reply to this email directly, view it on GitHub<#152 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/ABVYF7XED2KQUIPZNJMIOOLZXBUXVAVCNFSM6AAAAABOLVXCW6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGNJWGU3DSMZQGE>. You are receiving this because you authored the thread.Message ID: ***@***.***>

[jklenzing]

Can't comment directly on the code, but the Install Operational dependencies job in the workflow should be rewritten to look like the NEP29 job:

      run: |
        pip install numpy==${{ matrix.numpy_ver }}
        pip install --upgrade-strategy only-if-needed .[test]

This should fix the install issue that motivated the switch to pyprojecct.