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
Testing scripts on Titan sometime still pickups the default configuration information (such as Project and Baseline) when user has explicitly defined his options.
Added log kind flag to ESMF_Initialize call to allow control over ESMF PET log files when the ESMF library is used. The flag determines what ESMF log files (if any) are generated when USE_ESMF_LIB is TRUE.
ESMF_LOGKIND_SINGLE: Use a single log file, combining messages from all of the PETs. Not supported on some platforms.
ESMF_LOGKIND_MULTI: Use multiple log files -- one per PET.
ESMF_LOGKIND_NONE: Do not issue messages to a log file.
By default, no ESMF log files are generated.
Test suite: ./scripts_regression_test.py + hand testing:
./create_newcase --case /glade/scratch/goldy/esmfTest --compset A --res ne16_ne16 --run-unsupported
./xmlchange USE_ESMF_LIB=TRUE,DOUT_S=FALSE,STOP_OPTION=nsteps,STOP_N=3
Run test with each ESMF log kind option
Test baseline: NA
Test namelist changes: New driver namelist variable: esmf_logging
Test status: bit for bit
Fixes#1245
User interface changes?: New run time XML variable: ESMF_LOGFILE_KIND
Code review:
Testing scripts on Titan sometime still pickups the default configuration information (such as Project and Baseline) when user has explicitly defined his options.
For example:
./create_test --baseline-root /lustre/atlas/proj-shared/cli112/wangd/ --compiler pgi --project cli112 -o acme_developer –g
The text was updated successfully, but these errors were encountered: