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

Update GSI_BINARY_SOURCE_DIR paths in modulefiles #579

Closed
1 task
KateFriedman-NOAA opened this issue May 22, 2023 · 4 comments · Fixed by #581
Closed
1 task

Update GSI_BINARY_SOURCE_DIR paths in modulefiles #579

KateFriedman-NOAA opened this issue May 22, 2023 · 4 comments · Fixed by #581

Comments

@KateFriedman-NOAA
Copy link
Member

The GSI fix set was recently updated on disk and within global-workflow (see NOAA-EMC/global-workflow#1550). It was later noticed that there is a path in the GSI modulefiles (GSI_BINARY_SOURCE_DIR variable) that needs a matching update (see NOAA-EMC/global-workflow#1550 (comment)).

Example in Hera modulefile: https://github.com/NOAA-EMC/GSI/blob/develop/modulefiles/gsi_hera.intel.lua#L29

The GSI_BINARY_SOURCE_DIR paths in the Hera, Orion, Jet, and WCOSS2 modulefiles need to be updated to use the newer 20230112 fix set.

Also, consider accepting gsi_ver from global-workflow fix.ver file to define the version in the path when run within GFS/global-workflow. See https://github.com/NOAA-EMC/global-workflow/blob/develop/versions/fix.ver#L14.

  • Update the GSI hash in global-workflow develop after update is made (open global-workflow issue to make update).
@RussTreadon-NOAA
Copy link
Contributor

This issue is related to #580. Most of the work requested in this issue is covered by #580.

@RussTreadon-NOAA
Copy link
Contributor

@KateFriedman-NOAA , how do you suggest implementing the idea

accepting gsi_ver from global-workflow fix.ver file to define the version in the path when run within GFS/global-workflow. See https://github.com/NOAA-EMC/global-workflow/blob/develop/versions/fix.ver#L14.

in NOAA-EMC/GSI develop?

@KateFriedman-NOAA
Copy link
Member Author

@KateFriedman-NOAA , how do you suggest implementing the idea accepting gsi_ver from global-workflow fix.ver file to define the version in the path when run within GFS/global-workflow. See https://github.com/NOAA-EMC/global-workflow/blob/develop/versions/fix.ver#L14. in NOAA-EMC/GSI develop?

My initial thought would be similar to how the module versions get set. Something like this:

local gsi_ver=os.getenv("gsi_ver") or "20230112"
pushenv("GSI_BINARY_SOURCE_DIR", pathJoin("/scratch1/NCEPDEV/global/glopara/fix/gsi/" .. os.getenv("gsi_ver")))

^ this would need to be tested, I parsed it together in this comment based on how we're doing similar things in global-workflow with incoming changes to add the initial capability to use version variables like we do in ops, example: https://github.com/KateFriedman-NOAA/global-workflow/blob/feature/version-files/modulefiles/module_base.hera.lua#L35.

The gsi_ver variable in the GSI modulefiles could be gsi_fix_ver here but it's gsi_ver at the workflow level from fix.ver currently so one would need to grab that from the environment (os.getenv) as gsi_ver first.

@RussTreadon-NOAA
Copy link
Contributor

Thank you @KateFriedman-NOAA for outlining what you have in mind. We may need to defer this until you or someone else has time to work on this. We do not have a GSI code manager to make and, more importantly, test the change.

@RussTreadon-NOAA RussTreadon-NOAA linked a pull request May 25, 2023 that will close this issue
4 tasks
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 a pull request may close this issue.

2 participants