Dear Helvi,

I really appreciate your answer.

- About queing systems:

Indeed, queuing systems are used on clusters to manage a large number of

simulations by different users. These are additional programs that are not usually installed on laptops and local desktops, and cannot be controlled by simfactory or the Einstein Toolkit. Therefore, every time you submitted a simulation it started running immediately, i.e., in parallel with those that you started before and presumably caused your laptop to crash

Thanks for clearing that up. I thought that maybe the queuing system was up to Simfactory.

If you want to run multiple simulations simultaneously you will have to do

so on a cluster. On your laptop you should be able to run small test simulations, and typically one at a time.

Actually my intention was to run one simulation at a time, but to submit them all at once with parameter file scripts. Now I understand that I need a cluster anyway.

- About my failure with parameter file scripting, let's take for instance: Cactus/par/arXiv-1111.3344/tov/tov.rpar

Following Simfactory documentation: *"You can use a script in place of a parameter file when invoking SimFactory. When a simulation is run, the script will be executed and the resulting parameter file will be used by Cactus. NB: Remember to use the full path of the original script when determining the output filename, not just the base name."* So I ran:

sim create-run tovs --parfile par/arXiv-1111.3344/tov/tov.rpar --procs 4

And got:

Parameter file: /home/fede/Documents/einstein_toolkit/Cactus/par/arXiv-1111.3344/tov/tov.rpar Skeleton Created Job directory: "/home/fede/simulations/tovs" Executable: "/home/fede/Documents/einstein_toolkit/Cactus/exe/cactus_sim" Option list: "/home/fede/simulations/tovs/SIMFACTORY/cfg/OptionList" Submit script: "/home/fede/simulations/tovs/SIMFACTORY/run/SubmitScript" Run script: "/home/fede/simulations/tovs/SIMFACTORY/run/RunScript" Parameter file: "/home/fede/simulations/tovs/SIMFACTORY/par/tov.rpar" Simulation name: tovs Assigned restart id: 0 Running simulation tovs Error: Parameter file script '/home/fede/simulations/tovs/output-0000/tov.rpar' did not generate a parameter file called '/home/fede/simulations/tovs/output-0000/tov.par' Aborting Simfactory.

It seems that Simfactory is looking for a parameter file with the same name as the script. This can also be seen from the 'log.txt' file, that I attached. On the other hand, all the parameters files designed by 'tov.rpar' are properly created in the current directory, but not taken by Simfactory for running.

Maybe I misunderstood the point of parameter file scripting. I understood they serve for automatically create several parameter files, and automatically run (or submit) the corresponding simulations.

Thanks again! Best,

Federico

On Wed, Jul 18, 2018 at 11:50 AM helvi witek helvi.witek@kcl.ac.uk wrote:

Dear Federico,

...

it seems that I do not have a queuing system. Each time I submit a

simulation, it starts running in parallel with previous ones and my laptop quickly collapses. I configured > simfactory with: Indeed, queuing systems are used on clusters to manage a large number of simulations by different users. These are additional programs that are not usually installed on laptops and local desktops, and cannot be controlled by simfactory or the Einstein Toolkit. Therefore, every time you submitted a simulation it started running immediately, i.e., in parallel with those that you started before and presumably caused your laptop to crash.

If you want to run multiple simulations simultaneously you will have to do so on a cluster. On your laptop you should be able to run small test simulations, and typically one at a time.

...

I've tried some scripting with .rpar files, but failed...

Could you please send us the parameter and logfiles? Otherwise it is difficult to access what goes wrong. I suspect that your runs overwrite each other, since they seem to have the same name and run in parallel. That is probably why only the last submitted simulation actually runs. As an easy check you could submit two small runs with different names.

Best wishes, Helvi

=========================================== Dr. Helvi Witek Royal Society University Research Fellow Theoretical Particle Physics and Cosmology Department of Physics King's College London ===========================================

On Tue, Jul 10, 2018 at 8:24 PM, Federico G Lopez Armengol < fedelopezar@gmail.com> wrote:

...

Hello,

I've been learning how to use the Toolkit for about a year. I've been reading public documentation and running individual simulations on my personal laptop. Now, I need to manage some set of simulations, and found some trouble:

1. it seems that I do not have a queuing system. Each time I submit a

simulation, it starts running in parallel with previous ones and my laptop quickly collapses. I configured simfactory with:

./simfactory/bin/sim setup-silent --optionlist=ubuntu.cfg --runscript

...

debian.sh --submitscript debian.sub --runscript debian.sh

2. I've tried some scripting with .rpar files, but failed. For instance,

if submitting:

./simfactory/bin/sim create-submit tov_multi --parfile par/tov.rpar

no error displays, but the simulation is inmediately finished with no outputs. On the other hand, if running:

./simfactory/bin/sim create-run tov_multi --parfile par/tov.rpar

I get the following error:

Error: Parameter file script

...

'/home/fede/simulations/tov_multi/output-0000/tov.rpar' did not generate a parameter file called '/home/fede/simulations/tov_multi/output-0000/tov.par'

I changed the name of the parameter file created as asked, but just the last simulation of the script runs. I've tried this with every .rpar script that is included on the Toolkit.

I use Linux Mint 18.1 Serena. Thanks in advance!

Federico

---

Users mailing list Users@einsteintoolkit.org

https://emea01.safelinks.protection.outlook.com/?url=http%3A%2F%2Flists.eins...

Dear Ian, thank you very much for your response. I was already thinking on doing it myself, but I wanted to make sure that it hasn't been already implemented.

Thank you very much Helvi and Ian! My issues have been solved.

Best,

Federico

On Wed, Jul 18, 2018 at 5:18 PM ian.hinder@aei.mpg.de wrote:

On 18 Jul 2018, at 18:12, Federico G Lopez Armengol fedelopezar@gmail.com wrote:

Maybe I misunderstood the point of parameter file scripting. I understood they serve for automatically create several parameter files, and automatically run (or submit) the corresponding simulations.

Hi,

Yes, you misunderstood :).

The documentation says

"A parameter file script is a file with a ”.rpar” extension which, when executed, generates a file in the same place but with a ”.par” extension. The resulting file should be a valid SimFactory parameter file."

So you can only generate a single parameter file from the script. You could take a look at the bbh example ( https://bitbucket.org/einsteintoolkit/einsteinexamples/raw/master/par/GW1509...) to see why this sort of thing is needed. Some of what is done in the python header of that script cannot be done directly in the parameter file, or it would be incredibly tedious and error prone to do so.

Having a higher-level mechanism for managing collections of parameter files and simulations would be very useful, but it does not exist at the moment. You will have to implement it yourself, e.g. in a shell script. You should probably use sim create-run rather than sim create-submit so that the simulations don't run in the background at the same time.

-- Ian Hinder https://ianhinder.net