No one seems to be using the file-set lists capabilities (requires I/O API 3.2; there were bugs in 3.1’s implementation of file-set lists). For example:
setenv GR_EMIS_001 "E1,E2,E3,E4,E5
setenv E1 <path for first-day emissions file>
setenv E2 <path for second-day emissions file>
setenv E3 <path for third-day emissions file>
setenv E4 <path for fourth-day emissions file>
setenv E5 <path for fifth-day emissions file>
...
[and similarly for other time stepped input files]
time CCTM.exe !! five-day continuous run
set foo = ${status}
if ( ${foo} != 0 ) then
echo "*** ERROR ${foo} in CCTM.exe "
exit ( ${foo} )
endif
[Note that the script checks the error-status for CCTM.exe and exits (with a message and passing that status along as the status of the script) in case of failure…]