Present were: Frank, Roland, Peter, Tanja, Yosef, Erik, Ian, Steve
* connectivity issues with LSU svn server - should be gone by now (was a LDAP server migration) - please report in a trac ticket (and amend the ticket) whenever that happens (again) - currently svn.einsteintoolkit.org and svn.lsu.edu are two different machines (for historical reasons). Since only svn.lsu.edu seems to cause problems, there is the suggestion to migrate LSUThorn and simfactory from svn.lsu.edu to svn.einsteintoolkit.org
ET release: * ADMMass - used by Frank, Luca (that we know of) - please speak up if you use this thorn and (even better) you would have a test suite and or documentation for it - want test suite and/or docs for inclusion in the toolkit - do not include if neither one is provided * SphericalSlice - no test suites or docs - do not include without since it is a rather complicated thorn - all agree that it is very useful - Erik might have time to write some docs but not soon - see discussion on generic Cactus output routines in ticket #822 * Outflow - no (sustained) objection to inclusion voiced - clearly indicate that output format will change as soon as we have the generic Cactus output routines in place and or that we might use SphericalSlice - make current output routines more Cactus compliant if there are not yet - used by: Tanja, Roland (who are authors), all of GT, interest by Frank, Bruno Giacomazzo * OpenCLRuntime: - needs test case or example, do not include otherwise - deemed useful by Frank and Erik (who is author) * ML_NSSN_O2: - remove from toolkit * ML_NSSN_MP: - propose to remove or remove if already proposed * ADM: - remove only if tests are rewritten to no longer use it * BSSNL_MoL: - remove/convert/regenerate all testsuites using it (assigned to Roland)
Yours, Roland
Hello all,
ET release:
Following (but independent and not speaking for the maintainers) the discussion about which thorns to include and what requirements there are for thorns to be included, I added a page to the wiki
https://docs.einsteintoolkit.org/et-docs/Thorns_we_know_of
with the intention of collecting thorns known to users that might be of interest to the general public. This would serve as a way to advertise the thorns presence and allow the maintainers to judge the amount of interest and use a given thorn sees without including the thorn in ET and "blessing" it.
Yours, Roland
On Tue, Apr 24, 2012 at 1:32 AM, Roland Haas roland.haas@physics.gatech.edu wrote:
Hello all,
ET release:
Following (but independent and not speaking for the maintainers) the discussion about which thorns to include and what requirements there are for thorns to be included, I added a page to the wiki
https://docs.einsteintoolkit.org/et-docs/Thorns_we_know_of
with the intention of collecting thorns known to users that might be of interest to the general public. This would serve as a way to advertise the thorns presence and allow the maintainers to judge the amount of interest and use a given thorn sees without including the thorn in ET and "blessing" it.
On a slightly related note I would like to add that the Cactus team offers hosting svn repositories for thorns for various projects, groups, or people. This may be interesting if you don't want to set up an svn server of your own. Using such a repository does not mean that the thorn is "part of" Cactus, does not require any particular licence, and does not require following any particular standard.
Such thorns or arrangements are typically located under <svn.cactuscode.org/projects>.
-erik
Not sure what we want to capture with "Thorns we know of" but what about the unstructured mesh code that David used to solve the shallow water equations? Incidentally, does anyone know of a journal citation for the unstructured mesh code?
Cheers, Steve
On 04/24/2012 07:47 AM, Erik Schnetter wrote:
On Tue, Apr 24, 2012 at 1:32 AM, Roland Haas roland.haas@physics.gatech.edu wrote:
Hello all,
ET release:
Following (but independent and not speaking for the maintainers) the discussion about which thorns to include and what requirements there are for thorns to be included, I added a page to the wiki
https://docs.einsteintoolkit.org/et-docs/Thorns_we_know_of
with the intention of collecting thorns known to users that might be of interest to the general public. This would serve as a way to advertise the thorns presence and allow the maintainers to judge the amount of interest and use a given thorn sees without including the thorn in ET and "blessing" it.
On a slightly related note I would like to add that the Cactus team offers hosting svn repositories for thorns for various projects, groups, or people. This may be interesting if you don't want to set up an svn server of your own. Using such a repository does not mean that the thorn is "part of" Cactus, does not require any particular licence, and does not require following any particular standard.
Such thorns or arrangements are typically located under <svn.cactuscode.org/projects>.
-erik
Conference paper citation, but not very many details of the unstructured code
http://dl.acm.org/citation.cfm?id=1560766
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 Proceedings of the 9th International Conference on Computational Science: Part I (ICCS '09), Gabrielle Allen, Jarosł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 http://dx.doi.org/10.1007/978-3-642-01970-8_7
-- Gabrielle Allen Associate Professor Department of Computer Science Louisiana State University gallen@cct.lsu.edu
On Apr 24, 2012, at 8:10 PM, Steven R. Brandt wrote:
Not sure what we want to capture with "Thorns we know of" but what about the unstructured mesh code that David used to solve the shallow water equations? Incidentally, does anyone know of a journal citation for the unstructured mesh code?
Cheers, Steve
On 04/24/2012 07:47 AM, Erik Schnetter wrote:
On Tue, Apr 24, 2012 at 1:32 AM, Roland Haas roland.haas@physics.gatech.edu wrote:
Hello all,
ET release:
Following (but independent and not speaking for the maintainers) the discussion about which thorns to include and what requirements there are for thorns to be included, I added a page to the wiki
https://docs.einsteintoolkit.org/et-docs/Thorns_we_know_of
with the intention of collecting thorns known to users that might be of interest to the general public. This would serve as a way to advertise the thorns presence and allow the maintainers to judge the amount of interest and use a given thorn sees without including the thorn in ET and "blessing" it.
On a slightly related note I would like to add that the Cactus team offers hosting svn repositories for thorns for various projects, groups, or people. This may be interesting if you don't want to set up an svn server of your own. Using such a repository does not mean that the thorn is "part of" Cactus, does not require any particular licence, and does not require following any particular standard.
Such thorns or arrangements are typically located under <svn.cactuscode.org/projects>.
-erik
Users mailing list Users@einsteintoolkit.org http://lists.einsteintoolkit.org/mailman/listinfo/users
users@lists.einsteintoolkit.org
-
Allen Gabrielle -
Erik Schnetter -
Roland Haas -
Steven R. Brandt