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

gen_domain uses non-standard fortran extensions that don't work with all compilers #4455

Closed
billsacks opened this issue Jul 7, 2023 · 2 comments · Fixed by #4457
Closed

Comments

@billsacks
Copy link
Member

A user ran into trouble compiling gen_domain with some version of gfortran because of the use of iargc, which is a non-standard Fortran extension. It worked when the user changed iargc to command_argument_count, which is the newer Fortran standard method. I also suggested replacing the uses of getarg with get_command_argument, but I don't think that turned out to be needed for that user.

I started to make these changes and test them, but ran into trouble building gen_domain on my local machine. Before we spend time patching this, I first wanted to check whether this is something that is still being used by either CESM (@jedwards4b , @ekluzek do either of you know?) or E3SM (@rljacob @jgfouca @jasonb5 do any of you know?).

@ekluzek
Copy link
Contributor

ekluzek commented Jul 7, 2023

gen_domain is largely deprecated, in CESM because you don't need domain files anymore with NUOPC. It would only be required for MCT, which is now deprecated.

I think it's possible there might be really limited applications where gen_domain could be useful. The only thing that comes to mind is that we are using domain files in CTSM to create mesh files for subset_data. But, that's only used for a standard grid, so there's no reason to use gen_domain on a new grid.

So although gen_domain was a workhorse application in the past, it's not required anymore and as such doesn't make sense to put a lot of effort into it.

@billsacks
Copy link
Member Author

Thanks @ekluzek . Based on your input, I'm doing the quick fix that I had already determined, testing it on cheyenne, but I'm not tackling the more open-ended issue of getting the gen_domain build to be more robust.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants