-
Notifications
You must be signed in to change notification settings - Fork 31
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
[DISCUSSION] HCOIO_Read_Std_Mod #19
Comments
I am going to tackle this starting this week. If there is other information related to it that you added to other github issues in this or other repos let me know. |
The only thing I added was #31, which is a quick bug fix for the dry-run. I don't intend on touching anything else in HEMCO in the near future. |
Sorry, that question was aimed at @jimmielin. But thanks for the update on that since it does touch this file! |
Hi @lizziel, I don't have any new updates on this. I will be looking into other parts of the HEMCO code to implement an intermediate grid functionality and ask for everyone's feedback during MDS. Thanks for helping with this! |
This update is complete in commit b902b23. Additional work to clean up subroutine calls will be ongoing. |
Overview
There seems to be a lot of extra routines in
HCOIO_Read_Std_Mod
compared to the ESMF version.HCOIO_Read_Std_Mod:
HCOIO_Read_ESMF_Mod
Could any of the STD mod routines be moved to somewhere else? Some of these are basically managing IO stuff that is handled by MAPL in GCHP, but they may also be useful for the CESM implementation. Moving them to a more generic component (HCOIO helpers?) would allow less duplication of code as I think the CESM Parallel IO-based interface will be based upon the standard HCOIO interface quite a bit, and 4.7k lines of code is quite a lot of stuff to duplicate.
References
The only public entry points to the HCOIO_Read_* routines in HEMCO are the following:
So shuffling the internal routines around should be OK for compatibility.
After #11 which aims to unify the subroutine calls, maybe it would be nice to clean up all the calls to
ReadOther
CloseAll
etc., maybe adding a cleanup routine to each IO component so they can free up the file handles (standard) or do nothing (MAPL).The text was updated successfully, but these errors were encountered: