Hello Justin,
those were some thorns that were private at the time.
CoreCollapseControl has been proposed for inclusion in this ticket:
https://bitbucket.org/einsteintoolkit/tickets/issues/1358/import-corecollaps...
and you can obtain a copy using svn:
svn checkout https://svn.einsteintoolkit.org/incoming/CoreCollapseControl/
CartesianCoordinates is part of Llama and in the llama repository that has since become part of the Toolkit.
So you can use it by adding a line like this:
Llama/CartesianCoordinates
to your ThornList. You may have to create the appropriate symbolic link first via (something like):
cd arrangements/Llama ln -s ../../repos/llama/CartesianCoordinates CartesianCoordinates
TriggerTerminationManual has been superseeded my the TerminationTrigger thorn (in CactusUtils) in the toolkit, though you can also just comment it out since it does not affect physics.
Even with all those in place, the TOV collapse is "temperamental" and sometimes does not work well.
Please see here:
http://lists.einsteintoolkit.org/pipermail/users/2019-March/006802.html
for someone else's experience.
Basically Tony had to increase resolution by a factor of 2 (to 1.6 from 3.2) to avoid failures.
Yours, Roland
Hi everyone,
I'm a new user to the toolkit and have been trying to run the TOV collapse example from arXiv-1111.3344 on my home system with 4 cores. I keep getting the following errors before the job crashes:
=============================================== Error: Thorn CartesianCoordinates not found Error: Thorn corecollapsecontrol not found Error: Thorn TriggerTerminationManual not found Activation failed - 3 errors in activation sequence WARNING level 0 from host euler process 0 in thorn Cactus, file /home/verde029/ETK/Cactus/configs/sim/build/Cactus/main/SetParams.c:93: -> CCTKi_SetParameter: Error at line 66 in parameter file /home/verde029/simulations/collapse_crash_test/output-0000/tov_collapse_vc_l3.par while activating thorns
MPI_ABORT was invoked on rank 0 in communicator MPI_COMM_WORLD with errorcode 1.
NOTE: invoking MPI_ABORT causes Open MPI to kill all MPI processes. You may or may not see output from other processes, depending on exactly when Open MPI kills them.
============================================
I can't find anything on these thorns through the thorn documentation guide. Have the thorns or par file been updated, or is there a quick workaround to update the file?
I appreciate any help!