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

Mapping scripts re-worked for "new" geyser and caldera? #2469

Closed
mnlevy1981 opened this issue Apr 13, 2018 · 7 comments
Closed

Mapping scripts re-worked for "new" geyser and caldera? #2469

mnlevy1981 opened this issue Apr 13, 2018 · 7 comments
Labels
Responsibility: CESM Responsibility to manage and accomplish this issue is through CESM tp: tools ty: Bug
Milestone

Comments

@mnlevy1981
Copy link
Contributor

A grad student from Michigan contacted me because she was having trouble running [very old versions of] gen_cesm_maps.sh and create_esmf_map.sh on geyser. The current version of the script won't fair any better:

./gen_ESMF_mapping_file/create_ESMF_map.sh: line 108: mpirun.lsf: command not found
Error status returned from create_ESMF_map script

Also, gen_cesm_maps.sh should abort if create_esmf_map.sh returns an error rather than continuing on to the next file.

@mnlevy1981 mnlevy1981 added ty: Bug Responsibility: CESM Responsibility to manage and accomplish this issue is through CESM tp: tools labels Apr 13, 2018
@billsacks
Copy link
Member

Does this need to be fixed for cesm2? If so, can you please add it to the cesm2 milestone?

@jedwards4b
Copy link
Contributor

There was some talk of De coupling this from cime, is this still a possibility?

@ekluzek ekluzek added this to the CESM2.0 milestone May 2, 2018
@ekluzek
Copy link
Contributor

ekluzek commented May 2, 2018

@mnlevy1981 it seems to me this should be done for CESM2.0, so I added it to that milestone. @jedwards4b I bet it's too late to de couple these now. These tools are required for making datasets needed to run CESM and so are required.

@billsacks
Copy link
Member

Is the plan for this to be fixed for cesm2.0?

@mnlevy1981
Copy link
Contributor Author

It should be in cesm2.0, and I'll work on it this afternoon / Monday

@mnlevy1981
Copy link
Contributor Author

mnlevy1981 commented May 11, 2018

Okay, I have a branch where we can run all the mapping tools in serial on all the CISL machines (cheyenne, geyser, caldera, pronghorn). I have also submitted a ticket to CISL for guidance on how to run these tools in parallel, because I get different errors from different versions of mpiexec (mpich, openmpi, mpt) but nothing that actually runs.

I'll submit a PR on Monday, whether the parallel tools work or not (working serial / broken parallel seems better than everything being broken, and my current branch defaults to using the serial tools even if you're on geyser)

(edit: Monday, not tomorrow)

@mnlevy1981
Copy link
Contributor Author

I'm not confident in CISL's ability to get the parallel ESMF tools running so I guess we'll only provide serial tools for the release.

jedwards4b added a commit that referenced this issue May 14, 2018
Mlevy/mapping on geyser
Updated the wrappers for the ESMF mapping tools to work on NCAR machines. Note that currently only the serial modules are working - I have an issue ticket in with CISL to get the ESMF tools running in parallel, at which point I'll submit another pull request.

I also removed all reference to yellowstone and jaguar from the mapping tools.

Test suite: None
Test baseline: N/A
Test namelist changes: N/A
Test status: I verified that I could use my scripts to generate mapping files on cheyenne (both login node and compute node), geyser, caldera, and pronghorn.

Fixes #2469

User interface changes?: None

Update gh-pages html (Y/N)?: N

Code review: jedwards
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Responsibility: CESM Responsibility to manage and accomplish this issue is through CESM tp: tools ty: Bug
Projects
None yet
Development

No branches or pull requests

4 participants