<html><head><meta http-equiv="Content-Type" content="text/html charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">Hi Ian,<div class=""><br class=""></div><div class="">Thanks for your reply- please see below.</div><div class=""><br class=""><div><blockquote type="cite" class=""><div class="">On 3 Feb. 2017, at 3:05 am, Ian Hinder <<a href="mailto:ian.hinder@aei.mpg.de" class="">ian.hinder@aei.mpg.de</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div class=""><br class="">On 2 Feb 2017, at 12:53, Guy <<a href="mailto:guy.pitman@bigpond.com" class="">guy.pitman@bigpond.com</a>> wrote:<br class=""><br class=""><blockquote type="cite" class="">Hi Ian,<br class=""><br class="">Thanks for you reply-one more question:<br class=""><br class="">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.<br class=""></blockquote><br class="">Hi Guy,<br class=""><br class="">Yes, the thornlist is simply the list of thorns that are compiled into the configuration. By adding a new thorn to the thornlist, it will be included in the final executable built from that thornlist.<br class=""><br class=""></div></div></blockquote><blockquote type="cite" class=""><div class=""><div class=""><blockquote type="cite" class="">The simfactory thornlist (<a href="http://einsteintoolkit.th" class="">einsteintoolkit.th</a>) doesn’t have a pointer at the end, so I assume that all of the thorns are combined in the simulation.<br class=""></blockquote><br class="">I'm not sure I understand what you mean by "pointer". The thornlist is just the list of thorns that are included. <br class=""><br class=""></div></div></blockquote><div>By pointer I meant the path to the KrancExample SimpleWave was added at the end of the Thornlist</div><div><br class=""></div><pre style="padding: 6pt 6pt 6pt 12pt; background-color: rgb(255, 245, 230); white-space: pre-wrap; word-wrap: break-word; font-size: 13.3333px; font-variant-ligatures: normal; orphans: 2; widows: 2;" class="">echo 'KrancNumericalTools/GenericFD
KrancExamples/SimpleWave' >> <a href="http://kranc.th" class="">kranc.th</a></pre><div class="">I can understand that this compiles this Example , together with some required thorns.</div><div class=""><br class=""></div><blockquote type="cite" class=""><div class=""><div class=""><blockquote type="cite" class=""> Without knowing what all of the individual thorns are doing, is there a risk that<br class="">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? </blockquote></div></div></blockquote><blockquote type="cite" class=""><div class=""><div class="">I think I'm not following. What are you trying to achieve? If you want to follow along the Kranc tutorial, then you only need the thornlist in that tutorial; you shouldn't need any extra thorns. Since Cactus doesn't compile out-of-the-box on Mac OS, the only change you should need to make is to compile with simfactory instead of with make. This doesn't mean using the <a href="http://einsteintoolkit.th" class="">einsteintoolkit.th</a> thornlist; you would still use the thornlist from the tutorial. For example, you could replace<br class=""><br class="">make kranc-config THORNLIST=<a href="http://kranc.th" class="">kranc.th</a> PROMPT=no<br class=""><br class="">with<br class=""><br class="">sim build kranc --thornlist <a href="http://kranc.th" class="">kranc.th</a><br class=""><br class=""></div></div></blockquote><div>I guess I am trying to understand the relationship between Kranc thorns as in the examples and other thorns - now that I know where to look for the latter I will probably be able to work it out - presumably it only makes sense to combine certain combinations of thorns , and the example Kranc thorns require specific thorns to be present, but if you add others in to the Thornlist this may change behaviour. I am trying to understand how one would go about building a new simulation combining existing thorns and new Kranc thorns that would work together. For example would it make sense to combine more than one Kranc thorn in the thornlist?</div><br class=""><blockquote type="cite" class=""><div class=""><div class=""><blockquote type="cite" class="">Is there a document that explains what all the thorns do and how they can be combined? <br class=""></blockquote><br class="">I think you don't need this, but if you want to know what a given thorn does, your best bet is the documentation, which you can find at<br class=""><br class=""><a href="https://einsteintoolkit.org/documentation/ThornDoc/" class="">https://einsteintoolkit.org/documentation/ThornDoc/</a><br class=""><br class="">-- <br class="">Ian Hinder<br class="">http://members.aei.mpg.de/ianhin<br class=""><br class=""></div></div></blockquote></div>Regards</div><div class=""><br class=""></div><div class="">Guy</div></body></html>