<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div><br></div><div>Conference paper citation, but not very many details of the unstructured code</div><div><br></div><div><font class="Apple-style-span" color="#333333" face="Arial, sans-serif"><span class="Apple-style-span" style="font-size: 13px; line-height: 14px;"><a href="http://dl.acm.org/citation.cfm?id=1560766">http://dl.acm.org/citation.cfm?id=1560766</a></span></font></div><div><font class="Apple-style-span" color="#333333" face="Arial, sans-serif"><span class="Apple-style-span" style="font-size: 13px; line-height: 14px;"><br></span></font></div><div><span class="Apple-style-span" style="font-family: Verdana, Arial, Helvetica, sans-serif; font-size: 16px; ">Claes Eskilsson, Yaakoub El-Khamra, David Rideout, Gabrielle Allen, Q. Jim Chen, and Mayank Tyagi. 2009. A Parallel High-Order Discontinuous Galerkin Shallow Water Model. In <em>Proceedings of the 9th International Conference on Computational Science: Part I</em> (ICCS '09), Gabrielle Allen, Jaros\&\#322;aw Nabrzyski, Edward Seidel, Geert Dick Albada, Jack Dongarra, and Peter M. Sloot (Eds.). Springer-Verlag, Berlin, Heidelberg, 63-72. DOI=10.1007/978-3-642-01970-8_7 <a href="http://dx.doi.org/10.1007/978-3-642-01970-8_7">http://dx.doi.org/10.1007/978-3-642-01970-8_7</a></span></div><div><span class="Apple-style-span" style="font-family: Verdana, Arial, Helvetica, sans-serif; font-size: 16px; "><br></span></div><div><span class="Apple-style-span" style="font-family: Verdana, Arial, Helvetica, sans-serif; font-size: 16px; "><br></span></div><div><font class="Apple-style-span" color="#333333" face="Arial, sans-serif"><span class="Apple-style-span" style="font-size: 13px; line-height: 14px;"><br></span></font></div><div apple-content-edited="true">
<span class="Apple-style-span" style="font-size: 12px; "><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div>--</div><div>Gabrielle Allen</div><div>Associate Professor</div><div>Department of Computer Science</div><div>Louisiana State University</div><div><a href="mailto:gallen@cct.lsu.edu">gallen@cct.lsu.edu</a></div><div><br class="khtml-block-placeholder"></div></div><br class="Apple-interchange-newline"></span><br class="Apple-interchange-newline">
</div>
<br><div><div>On Apr 24, 2012, at 8:10 PM, Steven R. Brandt wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><div>Not sure what we want to capture with "Thorns we know of" but what about <br>the unstructured mesh code that David used to solve the shallow water <br>equations? Incidentally, does anyone know of a journal citation for the <br>unstructured mesh code?<br><br>Cheers,<br>Steve<br><br>On 04/24/2012 07:47 AM, Erik Schnetter wrote:<br><blockquote type="cite">On Tue, Apr 24, 2012 at 1:32 AM, Roland Haas<br></blockquote><blockquote type="cite"><<a href="mailto:roland.haas@physics.gatech.edu">roland.haas@physics.gatech.edu</a>> wrote:<br></blockquote><blockquote type="cite"><blockquote type="cite">Hello all,<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite">ET release:<br></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">Following (but independent and not speaking for the maintainers) the<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">discussion about which thorns to include and what requirements there are<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">for thorns to be included, I added a page to the wiki<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><a href="https://docs.einsteintoolkit.org/et-docs/Thorns_we_know_of">https://docs.einsteintoolkit.org/et-docs/Thorns_we_know_of</a><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">with the intention of collecting thorns known to users that might be of<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">interest to the general public. This would serve as a way to advertise<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">the thorns presence and allow the maintainers to judge the amount of<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">interest and use a given thorn sees without including the thorn in ET<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">and "blessing" it.<br></blockquote></blockquote><blockquote type="cite">On a slightly related note I would like to add that the Cactus team<br></blockquote><blockquote type="cite">offers hosting svn repositories for thorns for various projects,<br></blockquote><blockquote type="cite">groups, or people. This may be interesting if you don't want to set up<br></blockquote><blockquote type="cite">an svn server of your own. Using such a repository does not mean that<br></blockquote><blockquote type="cite">the thorn is "part of" Cactus, does not require any particular<br></blockquote><blockquote type="cite">licence, and does not require following any particular standard.<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">Such thorns or arrangements are typically located under<br></blockquote><blockquote type="cite"><<a href="http://svn.cactuscode.org/projects">svn.cactuscode.org/projects</a>>.<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">-erik<br></blockquote><blockquote type="cite"><br></blockquote><br>_______________________________________________<br>Users mailing list<br><a href="mailto:Users@einsteintoolkit.org">Users@einsteintoolkit.org</a><br>http://lists.einsteintoolkit.org/mailman/listinfo/users<br></div></blockquote></div><br></body></html>