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

Do we need med_id? #211

Open
rsdunlapiv opened this issue Jul 1, 2021 · 1 comment
Open

Do we need med_id? #211

rsdunlapiv opened this issue Jul 1, 2021 · 1 comment

Comments

@rsdunlapiv
Copy link
Contributor

There is a med_id variable that is set inside of the intenral state:

integer, public :: med_id ! needed currently in med_io_mod and set in esm.F90

The use of component ids seems to be a carryover from before the NUOPC implementation. The med_id is only used in med_io_mod.F90.

#ifdef CESMCOUPLED
    io_subsystem => shr_pio_getiosys(med_id)
    pio_iotype   =  shr_pio_getiotype(med_id)
    pio_ioformat =  shr_pio_getioformat(med_id)
#else

The primary issue is that the med_id has to be set externally by the driver, but it is not clear in general how this should be set from a general NUOPC driver that is using CMEPS (e.g., UFS).

@rsdunlapiv
Copy link
Contributor Author

@DeniseWorthen I opened this here to see if the med_id really needs to be retained.

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

No branches or pull requests

1 participant