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
To run E3SM tests with ADIOS type, there are a few issues to be resolved.
Issue 1
Is it possible to directly specify ADIOS type with a single "create_test XXXX" command?
For now, a workaround is to use "create_test XXXX --no-build" and then manually build and submit the case:
Issue 2
case_test might complain about copying an ADIOS format output file foo.nc.bp, even when there is a symbolic link foo.nc created for it. For a simple test SMS.ne30_f19_g16_rx1.A run with ADIOS type on ANL GCE nodes, case_test has an exception like below:
...
CASE.RUN HAS FINISHED
Exception from case_test: can't copy '/scratch/wuda/e3sm/scratch/SMS.ne30_f19_g16_rx1.A.anlgce_gnu.20240308_135932_80asj0/run/SMS.ne30_f19_g16_rx1.A.anlgce_gnu.20240308_135932_80asj0.cpl.hi.0001-01-06-00000.nc': doesn't exist or not a regular file
Note that a symbolic link cpl.hi.0001-01-06-00000.nc has already been created for cpl.hi.0001-01-06-00000.nc.bp:
86 Mar 8 14:02 SMS.ne30_f19_g16_rx1.A.anlgce_gnu.20240308_135932_80asj0.cpl.hi.0001-01-06-00000.nc -> SMS.ne30_f19_g16_rx1.A.anlgce_gnu.20240308_135932_80asj0.cpl.hi.0001-01-06-00000.nc.bp
4096 Mar 8 14:02 SMS.ne30_f19_g16_rx1.A.anlgce_gnu.20240308_135932_80asj0.cpl.hi.0001-01-06-00000.nc.bp
The text was updated successfully, but these errors were encountered:
To run E3SM tests with ADIOS type, there are a few issues to be resolved.
Issue 1
Is it possible to directly specify ADIOS type with a single "create_test XXXX" command?
For now, a workaround is to use "create_test XXXX --no-build" and then manually build and submit the case:
Issue 2
case_test might complain about copying an ADIOS format output file foo.nc.bp, even when there is a symbolic link foo.nc created for it. For a simple test SMS.ne30_f19_g16_rx1.A run with ADIOS type on ANL GCE nodes, case_test has an exception like below:
Note that a symbolic link cpl.hi.0001-01-06-00000.nc has already been created for cpl.hi.0001-01-06-00000.nc.bp:
The text was updated successfully, but these errors were encountered: