Hi Ian,
Thanks for you reply-one more question:
The Kranccode example seems to imply that by adding a pointer at the bottom of the Thornlist which refers to the Kranc thorn Example, that the compilation will include that code in the simulation.
The simfactory thornlist (
einsteintoolkit.th) doesn’t have a pointer at the end, so I assume that all of the thorns are combined in the simulation. Without knowing what all of the individual thorns are doing, is there a risk that
the thornlist that I made up for my Kranccode example (which I did by gradually adding groups of thorns based on error messages) could be incompatible? Is there a document that explains what all the thorns do and how they can be combined?
Thanks and regards
Guy
Hi Ian,
I was following the method used in the
Kranccode.org tutorial - I didn’t realise that you could just replace the Thornlist file in the command
./simfactory/bin/sim build --mdbkey make 'make -j2' --thornlist=kranc.th
- that seems to work! Thank you very much.
I should add a comment to the tutorial suggesting that you can use simfactory if you are familiar with it. For the simple kranc example, which doesn't need fortran etc or any complicated thorns, it is close to working out of the box with just plain "make" on some systems, which is why I didn't want to introduce the additional layer of complexity that is simfactory.