Hello Chris,
Unfortunately, when I attempted to run it, I received the following error:
WARNING level 0 in thorn Cactus processor 0 host qb563 (line 93 of /home/ettest34/Cactus/src/main/SetParams.c): -> CCTKi_SetParameter: Error at line 77 in parameter file /scratch/ettest34/simulations/tov_collapse/output-0000/tov_collapse_vc_l3.par while activating thorns WARNING level 0 in thorn Cactus processor 1 host qb562 (line 93 of /home/ettest34/Cactus/src/main/SetParams.c): -> CCTKi_SetParameter: Error at line 77 in parameter file /scratch/ettest34/simulations/tov_collapse/output-0000/tov_collapse_vc_l3.par while activating thorns WARNING level 0 in thorn Cactus processor 2 host qb532 (line 93 of /home/ettest34/Cactus/src/main/SetParams.c): -> CCTKi_SetParameter: Error at line 77 in parameter file /scratch/ettest34/simulations/tov_collapse/output-0000/tov_collapse_vc_l3.par while activating thorns WARNING level 0 in thorn Cactus processor 3 host qb027 (line 93 of /home/ettest34/Cactus/src/main/SetParams.c): -> CCTKi_SetParameter: Error at line 77 in parameter file /scratch/ettest34/simulations/tov_collapse/output-0000/tov_collapse_vc_l3.par while activating thorns application called MPI_Abort(MPI_COMM_WORLD, 0) - process 2application called MPI_Abort(MPI_COMM_WORLD, 0) - process 0application called MPI_Abort(MPI_COMM_WORLD, 0) - process 1application called MPI_Abort(MPI_COMM_WORLD, 0) - process 3handle_mt_peer: fail to read...: Success
It appears to be referring to the empty line between where Trigger is declared an active thorn and the user_random_restart_hill_climbing property is set. Do you know what could be causing this?
That does not actually seem to tell me what thorn caused the abort, but it looks as if a thorn was not found. Unfortunately these error messages tend to be a jumble due to output from stderr and stdout being mixed. Would you mind checking near the top of the output file if there is an more detailed error (or attach the full file).
Since you say that the error line is just after the ActiveThorns line for Trigger, it might be that the executable used does not have the proper thorn compiled in.
To check you can run "/scratch/ettest34/simulations/tov_collapse/SIMFACTORY/exe/cactus_sim -T" which will output a list of the compiled in thorns. You can also run "/scratch/ettest34/simulations/tov_collapse/SIMFACTORY/exe/cactus_sim -S /scratch/ettest34/simulations/tov_collapse/output-0000/tov_collapse_vc_l3.par" to check if the parameter file parses correctly and all required thorns are present (both do not require MPI so you can run them on the head node of the cluster).
When you added the Trigger thorn to your thornlist, did you recompile? One way of achieving this should be:
cd Cactus # add AEIThorns/Trigger to AEIThorns section vim thornlists/einsteintoolkit.th simfactory/bin/sim build --reconfig --thornlist=thornlists/einsteintoolkit.th simfactory/bin/sim purge tov_collapse simfactory/bin/sim create-submit tov_collapse --parfile par/tov_collapse.par
Yours, Roland