You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi. I would like to suggest the usage of the tool's name instead of common namelist.input. I see that under Mesh Tools, each grid_rotate, periodic_quad, and periodic_hex use namelist.input as the namelist file. I'm suggesting for them to use namelist.grid_rotate, namelist.periodic_quad, and namelist.periodic_hex instead.
For example, in a workflow, that may call for at least periodic_hex and periodic_quad, currently both would refer to namelist.input. While this can be deal with the use of 'ln -sf' each time for each tool, it can be better if both of them would read their own namelist.periodic_hex and namelist.periodic quad.
There will be less confusion and less human error in using the tools.
The text was updated successfully, but these errors were encountered:
zemega
changed the title
Suggestion. Use tools name instead of namelist.input.
Suggestion. Use namelist.tools_name instead of namelist.input.
Feb 15, 2021
@mgduda, I think you and the MPAS-Atmosphere team may be the only MPAS developers still using these tools, is that correct?
@zemega, I think most of the MPAS developers are using the python-based tools, which do not have namelist files. However, we have not created python version of periodic quad or grid_rotate, since our workflows don't involve these tools, so it sounds like you would be best off sticking with the Fortran tools.
@zemega, thanks for the context. It does sound like you're using the right tools, then. I'll let @mgduda respond if there are plans to enhance or modify the tools as you suggest.
Hi. I would like to suggest the usage of the tool's name instead of common namelist.input. I see that under Mesh Tools, each grid_rotate, periodic_quad, and periodic_hex use namelist.input as the namelist file. I'm suggesting for them to use namelist.grid_rotate, namelist.periodic_quad, and namelist.periodic_hex instead.
For example, in a workflow, that may call for at least periodic_hex and periodic_quad, currently both would refer to namelist.input. While this can be deal with the use of 'ln -sf' each time for each tool, it can be better if both of them would read their own namelist.periodic_hex and namelist.periodic quad.
There will be less confusion and less human error in using the tools.
The text was updated successfully, but these errors were encountered: