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

FIX: Handle updating options without changing other variables #60

Merged
merged 1 commit into from
Nov 15, 2024

Conversation

greglucas
Copy link
Member

There was an issue in MSIS2 where some steps are cached in the Fortran code if the input values (lat, lon, ...) are unchanged between subsequent runs. This causes issues if one wants to compare what the differences are between the options switches. (MSIS00 didn't have this same cache)

Additionally, add a check to the Python side to only call the init() function when options have changed, not every time we enter the run() call.

closes #59

There was an issue in MSIS2 where some steps are cached in the
Fortran code if the input values (lat, lon, ...) are unchanged
between subsequent runs. This causes issues if one wants to compare
what the differences are between the options switches. (MSIS00 didn't
have this same cache)

Additionally, add a check to the Python side to only call the init()
function when options have changed, not every time we enter the run()
call.
@greglucas greglucas merged commit be2cb86 into SWxTREC:main Nov 15, 2024
22 checks passed
@greglucas greglucas deleted the fix-options branch November 15, 2024 05:00
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

MSIS2 options updates don't work on iterative calls
1 participant