-
Notifications
You must be signed in to change notification settings - Fork 0
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
Hard-coded discover paths #1
Comments
Eventually, we'll probably want this accessed via ExtData somehow. Need to work out the scripting, etc. |
First, regarding the XGBoostFile - I will handle that once there are a full set of 12 monthly files from Dan Anderson. (Previously I have worked with Mark Solomon to move many GMI files to GMAO project space, so I know the process). Note that the Boost files are not gridded, so ExtData does not apply. More generally, there are a number of lines in OH_GridComp_ExtData.rc which reference daily output files from "MERRA2/GMI", Luke Oman's full chemistry replay run. I will check with Luke to see if there has been much demand for accessing these at NAS. Copying all of the output to mirrored GMAO space would be prohibitive. |
Ohhh. It's only a month? I didn't know that. I thought these were "universal". I suppose it makes sense it's not. I'm learning about ML! :) So these are like monthly climatologies (which isn't the right word, but...) where we expect all Januarys to look like model January? And I only meant "ExtData" in the sense that that is our "generic model boundary condition" sort of space. If not there, then we probably need some sort of scripting to edit for NAS like we do for MERRA2 Replay. And, yeah, if you think these runs would only ever be run at NCCS, then I suppose it doesn't matter. 😄 |
As I understand it, Dan trains the model for a given month, so yes- like a climatology. He recently trained January using XGBoost 1.6, and now that things are working in GEOS, I will ask him to complete Feb - Dec. Regarding ExtData, I was confused between the directory (which sits under scratch/) and the software for reading/interpolating gridded input. Yes, you are correct, it should be re-located under ExtData/ |
Or maybe somewhere new? I mean, we use ExtData as a catchall, but there is no requirement we use that. Then again, these are chemistry files and I'm sure Arlindo would say |
One issue that will eventually need to be fixed (once NAS runs of GEOS are working again) is that this repo currently has hard-coded discover paths in
OH_GridComp/OH_instance_OH.rc
:QuickChem/OH_GridComp/OH_instance_OH.rc
Lines 17 to 20 in 33728f6
And pretty much everywhere in
OH_GridComp/OH_GridComp_ExtData.rc
The text was updated successfully, but these errors were encountered: