<html><head><meta http-equiv="Content-Type" content="text/html charset=us-ascii"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;"><br><div><div>On 24 Jun 2015, at 12:24, Eloisa Bentivegna <<a href="mailto:bentivegna@cct.lsu.edu">bentivegna@cct.lsu.edu</a>> wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite">On 23/06/15 22:59, Roland Haas wrote:<br><blockquote type="cite">Hello all,<br><br>Present were: Peter, Steve, Christine, Ian, Elo, Matt, Roland<br><br>Tickets:<br>1667 include elliptic solver:<br>* several options present themselves (1) use CactusEllitpic (2) use new<br>arrangement Elliptic (3) use a arrangement collecting the author's<br>thorns (4) postpone the decision<br>* Roland objects to adding the solver to CactusElliptic since it is<br>explicitly tied to Carpet and Carpet is not part of Cactus<br>* a general issue exists in that we either have CactusXXX arrangements<br>or EinsteinXXX arrangements but no neutral XXX arrangement<br></blockquote><br>Thanks Roland for summing up nicely the result of the discussion. It <br>is true that historical reasons are creating a bit of an impasse with <br>arrangements named *Elliptic: the existing CactusElliptic implies more <br>about its thorns than the fact that they apply to elliptic problems; <br>on the other hand, the creation of additional *Elliptic arrangements <br>would make life harder for (and potentially hide tools from) users who <br>are just looking for an elliptic solver.<br></blockquote><div><br></div><div>Putting it in an institution-specific arrangement would do the same. In fact, it could be worse, as the name of the arrangement would not reflect the content, but the origin of the code, making it harder to find "an elliptic solver", if you didn't know where it was originally developed.</div><br><blockquote type="cite">I am now leaning towards a mix of (3) and (4), perhaps under the form <br>of a *Thorns or *Development arrangement (replace * with "Cosmo", or <br>my current institution, or any other meaningful prefix). It seems to <br>me that arrangements named this way have been used as incubators for <br>newborn thorns, which may or may not be moved elsewhere once it's <br>clear where (or whether at all) they belong inside Cactus or the ET.<br><br>For instance, would anyone object to a CataniaThorns arrangement?<br></blockquote><div><br></div><div>I wouldn't object, but it wouldn't be my first choice. The reason is that software authors tend to move between institutions, and code is often developed collaboratively between authors from different institutions. Very little of the code in AEIThorns is now developed by people at AEI, nor that in LSUThorns by people at LSU, and the TAT arrangements have nobody at TAT at all. So my preference would still be to have a place where "community" thorns can be placed. If this shouldn't be in an arrangement with a Cactus prefix, then I think we should create new arrangements.</div><div><br></div><div>$ ls AEIThorns LSUThorns TAT<br>AEIThorns:<br>ADMMass<span class="Apple-tab-span" style="white-space:pre"> </span>PunctureTracker<span class="Apple-tab-span" style="white-space:pre"> </span>Trigger<br>AEILocalInterp<span class="Apple-tab-span" style="white-space:pre"> </span>SystemStatistics<br><br>LSUThorns:<br>PeriodicCarpet<span class="Apple-tab-span" style="white-space:pre"> </span>QuasiLocalMeasures<span class="Apple-tab-span" style="white-space:pre"> </span>SummationByParts<span class="Apple-tab-span" style="white-space:pre"> </span>Vectors<br><br>TAT:<br>TATPETSc<span class="Apple-tab-span" style="white-space:pre"> </span>TATelliptic<br><br></div><div>The non-GR-related thorns would all be covered by a "Numerical" and a "Utils" arrangement. If the Cactus* arrangements are off-limits, and the Einstein* arrangements are not appropriate due to the code not being related to the Einstein equations, then we should have an alternative for this sort of code. Note: I'm not suggesting that we actually move the above thorns (though for AEIThorns and LSUThorns we want to stop using the respective SVN servers, so we may take the opportunity to do so), I'm just illustrating how the thorns would fit into my proposed arrangements.</div><div><br></div><div>If Numerical and Utils are too generic, maybe we could have a prefix, such as Community, User, or something like that. But maybe Numerical and Utils are OK.</div><div><br></div></div><div apple-content-edited="true">
<div style="color: rgb(0, 0, 0); letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px; word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;"><div style="color: rgb(0, 0, 0); letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px; word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;"><div style="color: rgb(0, 0, 0); letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px; word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;"><div style="color: rgb(0, 0, 0); letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px; word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;"><div>-- </div><div>Ian Hinder</div><div><a href="http://members.aei.mpg.de/ianhin">http://members.aei.mpg.de/ianhin</a></div></div></div></div></div>
</div>
<br></body></html>