-
Notifications
You must be signed in to change notification settings - Fork 7
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
package fit2obs and install it #12
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@aerorahul @KateFriedman-NOAA I see where you're going with this and definitely approve. There's a couple loose ends which I listed some thoughts on below.
- runfits has been the entry point for running the fits software. I would promote it to scripts/runfits.sh, and keep its function the same, including propagating the fit2obs module paths into the subsequent scripts as is done now.
- keep the batrun directory to contain subfits files for various machines as examples of how jobs would be submitted on each. They would be stand-alone in the sense that users would fill in various parameters in a subfits file, and then run a batch job by invoking the modified subfits script with a date argument.
- probably remove the runs directory from the repo since the new subfits files will not need drivers to function.
I/we could make changes in this branch before merging it to develop, or I could go ahead and approve merging as is, and raise another issue and make another PR to tie up the loose ends. Let me know your feedback on this question. Thanks!
@jack-woollen
There is use of There is also a lot of repetition in the various I would wait for @KateFriedman-NOAA to approve and confirm this branch works as her expectations in the global-workflow. Thoughts? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@aerorahul in ush/CMakeLists.txt it should have runfits.sh (maybe cfs_runfits.sh) but maybe not run_fits.sh. Consistent with the runfits script name in the ush directory in any case.
apologies @jack-woollen That was a typo on my part. I have fixed the name of the script to be consistent w/ what is in ush. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Changes look good. I will build this branch and run it via global-workflow on Orion (likely tomorrow) to confirm it works for us. Stay tuned.
I made the needed updates on the global-workflow side to use this Fit2Obs PR branch and installed a copy of Log: /work/noaa/stmp/kfriedma/comrot/testfit2obs/logs/2022011000/gdasfit2obs.log Here are the few changes I had to make on the workflow side:
Note, I set Based on this successful testing this PR is good to merge and then tag. |
Thanks for testing @KateFriedman-NOAA Please use the version in your tag e.g. |
Gentle reminder @jack-woollen |
If no objections The tag will be wflow.v1.0.0 |
@jack-woollen |
Tagged and pushed. Will do on the update procedure. |
Thanks @jack-woollen and @aerorahul ! |
This PR:
HOMEfit2obs
, USHfit2obsetc. See the
modulefiles/fit2obs.lua.tmpl` for details.excfs.....sh
andglobal_hyblevs.l65.txt
toscripts/
andfix/
directories to conform w/ NCO EE2 standardsREADME.md
that describes installation instructions for the package. This may need update from @jack-woollen to accurately describe what this repository does.VERSION
file. The version number in here should be incremented with every release. This is for managing releases of this project.BUILD_LEGACY=YES
for building and installing executables in the project cloned space.batrun
toush
.batrun/runfits
is moved toush/runfits.sh
runs
following suggestions from @jack-woollenbatrun/subfits_dell_nems
as the WCOSS Dell machine has been decomissionedResolves #10