-
Notifications
You must be signed in to change notification settings - Fork 29
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
Feature/cam ptype #158
Feature/cam ptype #158
Conversation
feature/CAM_grid2obs_priority is the next branch to merge into the authoritative branch; therefore feature/CAM_plotting needs to stay up to date with changes in feature/CAM_grid2obs_priority
…clude step where pcp_combine output are copied to COMOUT for all models
…p jobs from completing
…s + move MET/METplus loading to prod dirs
…ch with those in stats output files
…ep where pcpcombine output copies to COMOUT
…at definition in child scripts
There was an error in the crontab for hireswarwmem2. Running the prep step again for that model. Perry |
Can you check that you see the hireswarwmen2 prep run? Thanks! Perry |
I see the hireswarwmem2 run and it completed successfully. Thanks! |
Hi, @MarcelCaron-NOAA , For valid date 20230717, I see stat files in /lfs/h2/emc/vpppg/noscrub/perry.shafran/evs/v1.0/stats/cam. I also see prep and stats output files in /lfs/h2/emc/stmp/perry.shafran. Will you take a look at these things and let me know if the stat files and output files are what you would expect? If so, maybe we can finish up this particular PR. Perry |
@PerryShafran-NOAA I looked at the output files for each stats job and found no errors, all seem to have completed cleanly at the end of each cycle. I found intermediate stats files successfully outputted after each cycle, and then final stats files for each model. Each of these final stats files has the PTYPE data that is the motivation for this PR, and otherwise looks good. Overall I'm okay with the prep and stats tests. Another component is the plots job. Were you able to run that as well? That can be run interactively and at any time if pointed to my test archive. |
I have not run plots yet. Let me run that interactively and let you know what I get. Perry |
Hi, Marcel, Your plot job completed on Dogwood. I am transferring the results to Cactus now for you to see. One thing that I noticed is that the tar file wound up in the directory /lfs/h2/emc/vpppg/noscrub/perry.shafran/evs/v1.0/plots/cam rather than /lfs/h2/emc/vpppg/noscrub/perry.shafran/evs/v1.0/plots/cam/atmos.20230718. Also there was another directory written but not used: /lfs/h2/emc/vpppg/noscrub/perry.shafran/evs/v1.0/plots/cam/plots/cam Just to note, we should define the following variables: COMOUT=/lfs/h2/emc/vpppg/noscrub/$USER/evs/v1.0 I think that you defined COMOUT to be /lfs/h2/emc/vpppg/noscrub/${USER}/$NET/$evs_ver/$STEP/$COMPONENT caused some problems down the code. If we could reconfigure these variables, I think we'll be good. Since this is something that is shared by all the cam jobs, we'll all want to define COMOUT and COMOUTplots the same way. Perry |
The .o file is here: /lfs/h2/emc/vpppg/noscrub/perry.shafran/pr158test/EVS/dev/drivers/scripts/cam/plots/jevs_cam_grid2obs_plots.o83809033 The plot file is here: /lfs/h2/emc/ptmp/perry.shafran/evs.plots.cam.atmos.grid2obs.v20230718.tar Perry |
Hi Perry: Yes, Shelley noted the same COMOUT directory problem for the plots step in another PR; thanks for bringing it up as I haven't also made the change here. I'll check the output once it's available on Dogwood and then push some changes based on your feedback about COMOUT, hopefully by around this afternoon. -Marcel |
… tarball write dir to DATA, then copy to COMOUT
…e explicit COMOUTplots def
Hi Perry: Not sure where this /lfs/h2/emc/vpppg/noscrub/perry.shafran/evs/v1.0/plots/cam/plots/cam is being written from yet so I'll have to dig a little bit before I can fix. I did however add a COMOUTplots definition to the J-job and changed the lower level scripts to write to that directory instead of to COMOUT. I didn't add a top level definition in the driver script because it isn't necessary as long as COMOUT is defined there. Otherwise, output log looks good to me, and the output tar file includes the PTYPE graphics that I need and that are the motivation for this PR. I'll update this thread again once I find and fix the part of the code that makes the moot COMOUT directory mentioned above. |
Hi, @MarcelCaron-NOAA , The last time I ran the plots was on Dogwood, so you won't be able to see it unless I run again. But it wound up being right under the /lfs/h2/emc/vpppg/noscrub/perry.shafran/evs/v1.0/plots/cam directory. It's not on Cactus. Machine switches make PRs a bit challenging. ;) I'll need to run with your fixes and then have you confirm. Let me know when I can test. Thanks! Perry |
Perry: Yes I don't envy you all having to deal with PR testing across machine switches! Thanks for the help transferring things over. Strange. I couldn't find where this extra subdirectory is being written, and I couldn't find the directory mentioned in the output log either. I ran the job myself on Cactus and it ran okay for me, no extra subdirectories. Perhaps a recent merge removed the problem? Do you mind running the plots job one more time, on Cactus? -Marcel |
Yes, I can do so. Perry |
I pulled in all your updates; let's see if that helps. Perry |
Is that an old dir that is lingering? Maybe delete it before the re-run and confirm it is (or isn't) created. |
We'll see; I'm running it on Cactus now. But when I ran on Dogwood, it had the time stamp of the time it ran. Marcel made updates; I'm running it now (on his data since it presumably has the ptype in it). Perry |
Hi, @MarcelCaron-NOAA , The file looks to now be in the correct location: /lfs/h2/emc/vpppg/noscrub/perry.shafran/evs/v1.0/plots/cam/atmos.20230720 And here's the plot file: evs.plots.cam.atmos.grid2obs.v20230720.tar Please validate this plot file and then we can approve this PR, pending the code check. Perry |
Hi Perry: I checked the output tar file and it looks good to me. I also didn't notice any extra cam/plots/cam/... subdirectories this time. Thanks for running again. -Marcel |
Excellent. I'm going to do a code review now, and unless I see something else egregious, I'll merge. Thanks! Perry |
I think we are good to merge now. Perry |
Pull Request Testing
All jobs have been running in the cron for months, recent runs have been completing cleanly, and output stats and plots have been approved by the CAM verification team leads.
This feature branch includes PTYPE verification as an addition to the CAM/grid2obs verification set. PTYPE verification occurs over each of the three existing grid2obs steps (prep, stats, plots) and I recommend testing each set of jobs.
Prep and stats jobs are timing-sensitive and should be run in the cron, like this:
Replacing
{USER}
with your WCOSS2 username, and{HOMEevs}
with the location of your EVS PR testing directory. For each driver script ({HOMEevs}/dev/drivers/scripts/cam/...
) set HOMEevs, DATA, and COMOUT to your desired directories. Additionally, in the stats driver script, set COMINmping your prep COMOUT directory.Plots jobs may be run interactively at any time. If you prefer to use the cron, here is how I have my job set up:
0 22 * * * qsub -o /lfs/h2/emc/stmp/{USER}/jevs_cam_grid2obs_plots.out {HOMEevs}/dev/drivers/scripts/cam/plots/jevs_cam_grid2obs_plots.sh >> /lfs/h2/emc/stmp/{USER}/cron.out/test_jevs_cam_grid2obs_plots.out 2>&1
Just be sure to replace
{USER}
and{HOMEevs}
as in the prep/stats cron jobs. Then set HOMEevs, DATA, and COMOUT to your desired directories. Finally, set COMIN to my test directory:export COMIN=/lfs/h2/emc/vpppg/noscrub/marcel.caron/$NET/$evs_ver/stats/$COMPONENT
Has the code been checked to ensure that no errors occur during the execution? [Yes]
Do these updates/additions include sufficient testing updates? [Yes]
Please complete this pull request review by [07/21/2023].
Pull Request Checklist
Review the source issue metadata (required labels, projects, and milestone).
Complete the PR description above.
Ensure the PR title matches the feature branch name.
Check the following:
Instructions provided on how to run
Developer's name is replaced by ${user} where necessary throughout the code
Check that the ecf file has all the proper definitions of variables
Check that the jobs file has all the proper settings of COMIN and COMOUT and other input variables
Check to see that the output directory structure is followed
Be sure that you are not using MET utilities outside the METplus wrapper structure
After submitting the PR, select Development issue with the original issue number.
After the PR is approved, merge your changes. If permissions do not allow this, request that the reviewer do the merge.
Close the linked issue.