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
Jim Edwards suggests creating a timing module (marbl_timing_mod.F90) and using #ifdef wrappers to support GPTL if requested at build time (otherwise we can fall back to walltime or something). This is already done (in a way) in POP & CIME; POP uses CCSMCOUPLED in source/timers.F90 to trigger calls to cime/share/timing/perf_mod.F90 which is just a wrapper for GPTL. My first thought is to cut out the middle man and call GPTL directly if it is available.
This is not currently a high priority, but I would like to finish it sometime this summer... I believe it'll be useful to have #16 finished, because that bugfix will also provide the framework for a stand-alone driver and we'll be able to do some initial testing outside of CESM before trying to tie the MARBL timers in to POP.
The text was updated successfully, but these errors were encountered:
Jim Edwards suggests creating a timing module (marbl_timing_mod.F90) and using
#ifdef
wrappers to support GPTL if requested at build time (otherwise we can fall back to walltime or something). This is already done (in a way) in POP & CIME; POP usesCCSMCOUPLED
insource/timers.F90
to trigger calls tocime/share/timing/perf_mod.F90
which is just a wrapper for GPTL. My first thought is to cut out the middle man and call GPTL directly if it is available.This is not currently a high priority, but I would like to finish it sometime this summer... I believe it'll be useful to have #16 finished, because that bugfix will also provide the framework for a stand-alone driver and we'll be able to do some initial testing outside of CESM before trying to tie the MARBL timers in to POP.
The text was updated successfully, but these errors were encountered: