Thanks Ian,

I did a sim purge static_tov and tried rebuilding with ./simfactory/bin/sim build --mdbkey make 'make -j2' --thornlist=kranc.th (I needed to add a couple more thorns into kranc.th after submitting and getting error messages) but now I get an error

Formaline: Pushing to master git repository...
Formaline: ERROR during: Pushing to master git repository
Pushing to /Users/Guy/Documents/EinsteinToolkit/Cactus/cactusjar.git
Total 0 (delta 0), reused 0 (delta 0)
remote: error: cannot lock ref 'refs/heads/config-sim-Guy-Pitman.local-Users-Guy-Documents-EinsteinToolkit-Cactus': is at ca3fd643c45d8b1a29e9cbace4d149036b6534a3 but expected 883ab226b3bd16363cdf557c0752a9d97ccfb396
To /Users/Guy/Documents/EinsteinToolkit/Cactus/cactusjar.git
 = [up to date]      master -> master
 ! [remote rejected] config-sim-Guy-Pitman.local-Users-Guy-Documents-EinsteinToolkit-Cactus -> config-sim-Guy-Pitman.local-Users-Guy-Documents-EinsteinToolkit-Cactus (failed to update ref)
error: failed to push some refs to '/Users/Guy/Documents/EinsteinToolkit/Cactus/cactusjar.git'


I have googled the git errors, but nothing seems to help- can I reinitialise the repositories some how to get over this error?

Thanks and regards

Guy



On 6 Feb 2017, at 7:12 pm, Ian Hinder <ian.hinder@aei.mpg.de> wrote:


On 6 Feb 2017, at 02:08, Guy Pitman <guy.pitman@bigpond.com> wrote:

Hi Ian,

I ran the following command ./simfactory/bin/sim build --mdbkey make 'make -j2' --thornlist=kranc.th  with the attached Thornlist, which included the CT_Dust Kranc thorn, and then ran 
./simfactory/bin/sim submit static_tov --parfile=par/static_tov_small.par --procs=1 --walltime=8:0:0  with the attached parameter file, which also includes CT_Dust , but when I look at the output in ~/simulations/static_tov/output-0003, the  static_tov_small.par which I assume has been copied from the par directory has CT_Dust removed?  The static_tov.out file also has no reference to CT_Dust.  Can you see what I am doing wrong?


Hi,

sim submit not only creates a new simulation, but also continues existing simulations.  The fact that you have an output-0003 means this is the 4th time you have submitted the same simulation.  In that case, I don't know whether simfactory tries to update the parameter file.  It really shouldn't accept the option without an error if it's just going to ignore it, but I wouldn't be surprised if it did.  I suggest to delete the whole simulation and try again.  You can also use

sim purge static_tov

which will do the deletion.