Hi<br><br>Could we, for the development version, enable them for all machines and see what breaks? Maybe we can fix them such that we can unconditionally include them.<br><br>Frank<br><br>Erik Schnetter <schnetter@cct.lsu.edu> schrieb:<br><br><div dir="ltr">The situation is similar to the OpenCL thorns: They are part of the Einstein Toolkit, part of the release, should be tested (where possible), and should be disabled by default in the thorn list since we assume most people won't be using them. That is inconvenient for testing, but convenient for the end users.<div>
<br></div><div style>What we really need is a mechanism to easily select a subset of the thorns in the manifest. Simfactory has a mechanism for that, but that is per-machine and may not do what people want. I enable these thorns in my defs.local.ini where they make sense.</div>
<div><br></div><div style>-erik</div><div style><br></div></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Sun, May 12, 2013 at 4:48 AM, Ian Hinder <span dir="ltr"><<a href="mailto:ian.hinder@aei.mpg.de" target="_blank">ian.hinder@aei.mpg.de</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div style="word-wrap:break-word"><br><div><div class="im"><div>On 11 May 2013, at 21:48, Erik Schnetter <<a href="mailto:schnetter@cct.lsu.edu" target="_blank">schnetter@cct.lsu.edu</a>> wrote:</div>
<br><blockquote type="cite"><div dir="ltr">I test them regularly. They build fine on many systems (but not all).<div><br></div><div>The reason we commented them out was that they take a long time to build, while no standard ET thorn uses them. Please include them in the release.</div>
</div></blockquote><div><br></div></div><div>Hi Erik,</div><div><br></div><div>Do you mean to included them in the release, but commented-out in the thornlist, or to uncomment them in the thornlist?</div><div><br></div><div>
If they are in the release, we need to test them as part of the usual process. This will be awkward if they are commented out. Everyone will have to remember to uncomment them before running the tests. The automated test system also doesn't know that they should be tested.</div>
<br><blockquote type="cite"><div class="im"><div dir="ltr">
<div><br></div><div>-erik</div></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Sat, May 11, 2013 at 3:21 PM, Frank Loeffler <span dir="ltr"><<a href="mailto:knarf@cct.lsu.edu" target="_blank">knarf@cct.lsu.edu</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">On Sat, May 11, 2013 at 01:49:34PM -0400, Erik Schnetter wrote:<br>
> CactusElliptic/EllPETSc<br>
> CactusTest/TestAllTypes<br>
> ExternalLibraries/PETSc<br>
> TAT/TATPETSc<br>
<br>
Right. That's because they are commented out in the standard thornlist.<br>
Is this so because they don't build in a lot of places? With them being<br>
commented out they very likely don't receive much testing...<br>
<span><font color="#888888"><br>
Frank<br>
<br>
</font></span></blockquote></div><br><br clear="all"><div><br></div>-- <br>Erik Schnetter <<a href="mailto:schnetter@cct.lsu.edu" target="_blank">schnetter@cct.lsu.edu</a>><br><a href="http://www.perimeterinstitute.ca/personal/eschnetter/" target="_blank">http://www.perimeterinstitute.ca/personal/eschnetter/</a>
</div></div>
_______________________________________________<br>Users mailing list<br><a href="mailto:Users@einsteintoolkit.org" target="_blank">Users@einsteintoolkit.org</a><br><a href="http://lists.einsteintoolkit.org/mailman/listinfo/users" target="_blank">http://lists.einsteintoolkit.org/mailman/listinfo/users</a><span class="HOEnZb"><font color="#888888"><br>
</font></span></blockquote></div><span class="HOEnZb"><font color="#888888"><br><div>
<span style="text-indent:0px;letter-spacing:normal;font-variant:normal;text-align:-webkit-auto;font-style:normal;font-weight:normal;line-height:normal;border-collapse:separate;text-transform:none;font-size:medium;white-space:normal;font-family:Helvetica;word-spacing:0px"><span style="text-indent:0px;letter-spacing:normal;font-variant:normal;font-style:normal;font-weight:normal;line-height:normal;border-collapse:separate;text-transform:none;font-size:12px;white-space:normal;font-family:Helvetica;word-spacing:0px"><div style="word-wrap:break-word">
<span style="text-indent:0px;letter-spacing:normal;font-variant:normal;font-style:normal;font-weight:normal;line-height:normal;border-collapse:separate;text-transform:none;font-size:12px;white-space:normal;font-family:Helvetica;word-spacing:0px"><div style="word-wrap:break-word">
<span style="text-indent:0px;letter-spacing:normal;font-variant:normal;font-style:normal;font-weight:normal;line-height:normal;border-collapse:separate;text-transform:none;font-size:12px;white-space:normal;font-family:Helvetica;word-spacing:0px"><div style="word-wrap:break-word">
<div>-- </div><div>Ian Hinder</div><div><a href="http://numrel.aei.mpg.de/people/hinder" target="_blank">http://numrel.aei.mpg.de/people/hinder</a></div></div></span></div></span></div></span></span>
</div>
<br></font></span></div></blockquote></div><br><br clear="all"><div><br></div>-- <br>Erik Schnetter <<a href="mailto:schnetter@cct.lsu.edu" target="_blank">schnetter@cct.lsu.edu</a>><br><a href="http://www.perimeterinstitute.ca/personal/eschnetter/" target="_blank">http://www.perimeterinstitute.ca/personal/eschnetter/</a>
</div>