I had a very strange problem about running CCTM and you can only see the cctm.log which I use the command ‘./nm_27.csh >& cctm.log’ . I haven’t seen any error in cctm.log. But I didn’t sucessfully run it yet.
I can’t upload files because I’m a new user. Here are the last few lines in the log file.
text data bss dec hex filename* 6275173 15665504 102050376 123991053 763f40d /public/home/lzh/HHJ/Build_WRF/CMAQ-5.2/CCTM/scripts/BLD_CCTM_v52_intel/CCTM_v52.exe unlimit limit cputime unlimited filesize unlimited datasize unlimited stacksize unlimited coredumpsize unlimited memoryuse unlimited vmemoryuse unlimited
*descriptors 32768 * memorylocked unlimited
*maxproc 257548 * date Sun Apr 23 23:25:27 CST 2023 mpirun -r ssh -np 36 /public/home/lzh/HHJ/Build_WRF/CMAQ-5.2/CCTM/scripts/BLD_CCTM_v52_intel/CCTM_v52.exe -------------------------------------------------------------------------- mpirun was unable to launch the specified application as it could not find an executable:
Executable: -r Node: compute-0-10.local
while attempting to start process rank 0. -------------------------------------------------------------------------- 96 total processes failed to start 0.016u 0.033s 0:00.15 26.6% 0+0k 0+32io 0pf+0w date Sun Apr 23 23:25:27 CST 2023 if ( ! -e /public/home/lzh/HHJ/Build_WRF/CMAQ-5.2/data/output_CCTM_v52_intel_201001/LOGS ) then mv: No match. setenv NEW_START false set TODAYG = date -ud "${TODAYG}+1days" +%Y-%m-%d date -ud 2020-10-02+1days +%Y-%m-%d set TODAYJ = date -ud "${TODAYG}" +%Y%j date -ud 2020-10-03 +%Y%j end while ( 2020277 < = 2020276 ) exit
My CMAQ version is 5.2. Is there anyone who can help me? THANKS
Hi，lizadams
thanks for your kindly reply
My executable should exist exactly where it shows.
An error occurred when I ran the run script following your advice.
I also want to show the modified script, please help to have a look. Here are the scripts and errors：
# ===================================================================
#> Execution Portion
# ===================================================================
#> Print attributes of the executable
ls -l $BLD/$EXEC; size $BLD/$EXEC
unlimit
limit
date
#> Executable call for single PE, uncomment to invoke
# /usr/bin/time $BLD/$EXEC
#> Executable call for multi PE, configure for your system
set MPI = /public/software/mpi/mpich/intel/3.2/bin
set MPIRUN = $MPI/mpirun
# time mpirun -np 36 $NPROCS $BLD/$EXEC
mpirun -np 36 /public/home/lzh/HHJ/Build_WRF/CMAQ-5.2/CCTM/scripts/BLD_CCTM_v52_intel/CCTM_v52.exe*
date
# ===================================================================
#> Finalize Run for This Day and Loop to Next Day
# ===================================================================
#> Save Log Files and Move on to Next Simulation Day
if (! -e $LOGDIR ) then
mkdir $LOGDIR
endif
mv CTM_LOG_???.${CTM_APPL} $LOGDIR
#> The next simulation day will, by definition, be a restart
setenv NEW_START false
#> Increment both Gregorian and Julian Days
set TODAYG = `date -ud "${TODAYG}+1days" +%Y-%m-%d` #> Add a day for tomorrow
set TODAYJ = `date -ud "${TODAYG}" +%Y%j` #> Convert YYYY-MM-DD to YYYYJJJ
end #Loop to the next Simulation Day
exit
unlimit
limit
cputime unlimited
filesize unlimited
datasize unlimited
stacksize unlimited
coredumpsize unlimited
memoryuse unlimited
vmemoryuse unlimited
descriptors 4096
memorylocked unlimited
maxproc 257509
date
Tue Apr 25 01:06:49 CST 2023
set MPI = /public/software/mpi/mpich/intel/3.2/bin
set MPIRUN = /public/software/mpi/mpich/intel/3.2/bin/mpirun
mpirun -np 36 /public/home/lzh/HHJ/Build_WRF/CMAQ-5.2/CCTM/scripts/BLD_CCTM_v52_intel/CCTM_v52.exe
[cluster.hpc.org:2012] *** An error occurred in MPI_comm_size
[cluster.hpc.org:2012] *** on communicator MPI_COMM_WORLD
[cluster.hpc.org:2012] *** MPI_ERR_COMM: invalid communicator
[cluster.hpc.org:2012] *** MPI_ERRORS_ARE_FATAL: your MPI job will now abort
--------------------------------------------------------------------------
mpirun has exited due to process rank 11 with PID 2022 on
node cluster.hpc.org exiting improperly. There are two reasons this could occur:
1. this process did not call "init" before exiting, but others in
the job did. This can cause a job to hang indefinitely while it waits
for all processes to call "init". By rule, if one process calls "init",
then ALL processes must call "init" prior to termination.
2. this process called "init", but exited without calling "finalize".
By rule, all processes that call "init" MUST call "finalize" prior to
exiting or it will be considered an "abnormal termination"
This may have caused other processes in the application to be
terminated by signals sent by mpirun (as reported here).
--------------------------------------------------------------------------
[cluster.hpc.org:02010] 35 more processes have sent help message help-mpi-errors.txt / mpi_errors_are_fatal
[cluster.hpc.org:02010] Set MCA parameter "orte_base_help_aggregate" to 0 to see all help / error messages
date
Tue Apr 25 01:06:49 CST 2023
if ( ! -e /public/home/lzh/HHJ/Build_WRF/CMAQ-5.2/data/output_CCTM_v52_intel_201001/LOGS ) then
mv: No match.
setenv NEW_START false
set TODAYG = `date -ud "${TODAYG}+1days" +%Y-%m-%d`
date -ud 2020-10-02+1days +%Y-%m-%d
set TODAYJ = `date -ud "${TODAYG}" +%Y%j`
date -ud 2020-10-03 +%Y%j
end
while ( 2020277 < = 2020276 )
exit