update directory paths for scrip files in gen_mapping template
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 48/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Stale
- Domain
- tooling
Research direction
Start in the gen_mapping directory and search for every occurrence of "cseg" in the templates and scripts. Update the outdated mapping paths, including the ww3 mapping root and the ocnGridName path, so they use the cesmdata locations; done means no stale /glade/p/cesm/cseg/mapping/grids/ references remain.
Written by the indexing model from the issue text.
Description
Turns out the software engineers moved the ww3 mapping file into the cesmdata server.
replace the root directory for the ww3 mapping file "/glade/p/cesm/cseg/mapping/grids/" with "/glade/p/cesmdata/inputdata/share/scripgrids/"
Quick look at the gen_mapping directory, it looks like we'll run into this with the ocean grid as well: ocnGridName="/glade/p/cesmdata/cseg/mapping/grids/gx1v7_151008.nc"
probably another one somewhere in that directory -- just search for "cseg" and that should find the outdated paths
Adam
On Fri, Jul 29, 2022 at 4:35 PM Robert Jnglin Wills <rcwills@uw.edu> wrote:
Hi Adam,
I am finally getting back to this, and I'm running into errors relating to the non-existence of '/glade/p/cesm/cseg/mapping/grids/ww3a_120222.nc'. Is this because this grid is no longer used? Is there an updated version of VRM_tools that corresponds to any updates in '/glade/p/cesm/cseg/mapping/grids/'?
If you need more info about the errors, the log files are here: /glade/u/home/rwills/Community_Mesh_Generation_Toolkit/VRM_tools/gen_mapping/ne0np4.NATL.ne30x4/
Thanks,
Robb
- Dominant language
- C
- Stars
- 11
- Forks
- 11
- PR merge metrics
- No merged PRs in 30d
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from ESMCI/Community_Mesh_Generation_Toolkit
-
Difficulty 4/5 3-5 days Newbie friendliness 25/100
-
Difficulty 4/5 3-5 days Newbie friendliness 25/100
-
Create_VRMgrid error Open
Difficulty 1/5 Under an hour Newbie friendliness 55/100
All issues in ESMCI/Community_Mesh_Generation_Toolkit
Similar issues
-
level/task module/gcp type/bug
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
-
Difficulty 1/5 Under an hour Newbie friendliness 86/100
hapostgres/pg_auto_failover#1190 ·
-
docs
Difficulty 1/5 Under an hour Newbie friendliness 85/100
-
P3 sonic-vpp
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
sonic-net/sonic-buildimage#29662 ·
-
Difficulty 1/5 Under an hour Newbie friendliness 94/100
spack/spack-packages#6586 ·