[Commits] [svn:einsteintoolkit] www/toolkit/ (Rev. 302)
schnetter at cct.lsu.edu
schnetter at cct.lsu.edu
Wed Jun 23 07:39:12 CDT 2010
User: eschnett
Date: 2010/06/23 07:39 AM
Modified:
/toolkit/
index.php
Log:
Correct broken links
File Changes:
Directory: /toolkit/
====================
File [modified]: index.php
Delta lines: +78 -18
===================================================================
--- toolkit/index.php 2010-06-22 02:39:23 UTC (rev 301)
+++ toolkit/index.php 2010-06-23 12:39:12 UTC (rev 302)
@@ -3,31 +3,69 @@
-<p>The Einstein Toolkit currently consists of an open set of over 100 <a href="http://www.cactuscode.org">Cactus</a> thorns for computational relativity along with associated tools for simulation management and visualization. The toolkit
- includes a vacuum spacetime solver (McLachlan), a relativistic hydrodynamics solver (formerly the public version of the <a href="http://www.whiskycode.org/">Whisky code</a>), along with thorns for initial data, analysis and computational infrastructure. These thorns have been developed and improved over many years by <a href="../credits">many different researchers</a>.
-</p>
+<p>The Einstein Toolkit currently consists of an open set of over
+ 100 <a href="http://www.cactuscode.org">Cactus</a> thorns for
+ computational relativity along with associated tools for simulation
+ management and visualization. The toolkit includes a vacuum
+ spacetime solver (McLachlan), a relativistic hydrodynamics solver
+ (formerly the public version of
+ the <a href="http://www.whiskycode.org/">Whisky code</a>), along
+ with thorns for initial data, analysis and computational
+ infrastructure. These thorns have been developed and improved over
+ many years by <a href="../credits">many different
+ researchers</a>.</p>
- <p>The Einstein Toolkit can be used with your own thorns for initial data, evolution, equation of state or analysis. Writing your own thorns to work with the Einstein Toolkit requires following the conventions specified in the ADMBase and HydroBase thorns which define the basic fields (e.g. 3-metric, extrinsic curvature, lapse, shift vector, density, etc).</p>
+<p>The Einstein Toolkit can be used with your own thorns for initial
+ data, evolution, equation of state or analysis. Writing your own
+ thorns to work with the Einstein Toolkit requires following the
+ conventions specified in the ADMBase and HydroBase thorns which
+ define the basic fields (e.g. 3-metric, extrinsic curvature, lapse,
+ shift vector, density, etc).</p>
- <p>The Einstein Toolkit is supported by a distributed model, combining core support of software, tools, and documentation in its <a href="https://svn.einsteintoolkit.org">SVN repository</a> with partnerships with other developers who contribute open software and coordinate together on development. </p>
+<p>The Einstein Toolkit is supported by a distributed model, combining
+ core support of software, tools, and documentation in
+ its <a href="https://svn.einsteintoolkit.org">SVN repository</a>
+ with partnerships with other developers who contribute open software
+ and coordinate together on development.</p>
-<!-- <p>The thorns comprising the Einstein Toolkit are provided in a standard Cactus thornlist: <a href="https://svn.einsteintoolkit.org/cactus/thornlists/einsteintoolkit.th">Einstein Toolkit Thornlist</a>. A <a href="../info/documentation/">worked example</a> describes how to download, compile and run the toolkit.</p>-->
+<!--
+<p>The thorns comprising the Einstein Toolkit are provided in a
+ standard Cactus
+ thornlist: <a href="https://svn.einsteintoolkit.org/manifest/branches/ET_2010_06/einsteintoolkit.th">Einstein
+ Toolkit Thornlist</a>. A <a href="../info/documentation/">worked
+ example</a> describes how to download, compile and run the
+ toolkit.</p> -->
- <p>The components of the Einstein Toolkit include:</p>
+<p>The components of the Einstein Toolkit include:</p>
<table border="1">
<tr>
<td valign="top"><i>Cactus Framework</i></td>
- <td><p>The <a href="http://www.cactuscode.org" class="nostyle">Cactus Framework and Computational Toolkit</a> provides an parallel, collaborative, component framework for the Einstein Toolkit. Cactus was developed by the numerical relativity community but now supports scientific applications in different disciplines. The Cactus Computational Toolkit is a set of thorns that provide general capabilities used by the Einstein Toolkit such as I/O, coordinates and boundary conditions.</p><p>Distribution: The Cactus Framework is distributed under an open source license from the Cactus web site <a href="http://www.cactuscode.org">http://www.cactuscode.org</a></p></td>
+ <td><p>The <a href="http://www.cactuscode.org"
+ class="nostyle">Cactus Framework and Computational Toolkit</a>
+ provides an parallel, collaborative, component framework for the
+ Einstein Toolkit. Cactus was developed by the numerical relativity
+ community but now supports scientific applications in different
+ disciplines. The Cactus Computational Toolkit is a set of thorns
+ that provide general capabilities used by the Einstein Toolkit such
+ as I/O, coordinates and boundary conditions.</p><p>Distribution: The
+ Cactus Framework is distributed under an open source license from
+ the Cactus web
+ site <a href="http://www.cactuscode.org">http://www.cactuscode.org</a></p></td>
</tr>
<tr>
<td valign="top"><i>Component Lists and GetComponents</i></td>
- <td><p>The Einstein Toolkit component list contains the locations of the source code and associated tools for simulations, including Cactus thorns. The component list is written using the Component Retrieval Language and can be checked out using the <a href="http://www.cactuscode.org/download/GetComponents" class="nostyle">GetComponents</a> tools.</p>
- <p>Distribution: <a href="https://svn.einsteintoolkit.org/manifest/einsteintoolkit.th">https://svn.einsteintoolkit.org/manifest/einsteintoolkit.th</a> <br>
-<a href="http://www.cactuscode.org/download/GetComponents">http://www.cactuscode.org/download/GetComponents</a>
+<td><p>The Einstein Toolkit component list contains the locations of
+ the source code and associated tools for simulations, including
+ Cactus thorns. The component list is written using the Component
+ Retrieval Language and can be checked out using
+ the <a href="https://svn.cactuscode.org/Utilities/branches/ET_2010_06/Scripts/GetComponents"
+ class="nostyle">GetComponents</a> tools.</p>
+<p>Distribution: <a href="https://svn.einsteintoolkit.org/manifest/branches/ET_2010_06/einsteintoolkit.th">https://svn.einsteintoolkit.org/manifest/einsteintoolkit.th</a> <br>
+<a href="https://svn.cactuscode.org/Utilities/branches/ET_2010_06/Scripts/GetComponents">https://svn.cactuscode.org/Utilities/branches/ET_2010_06/Scripts/GetComponents</a>
</p>
</td>
@@ -35,29 +73,51 @@
<tr>
<td valign="top"><i>Simulation Factory</i></td>
- <td><p>The <a href="http://www.cct.lsu.edu/~eschnett/SimFactory/" class="nostyle">simulation factory</a> includes configuration and batch script files for compiling and running simulations using the Cactus code on many different architectures. Additional capabilities provide for management of simulations, simplifying checkpoint & restart, and remote use of machines. The Einstein Consortium have selected the simulation factory as the default mechanism for supporting the easy use of Cactus on heterogeneous resources.</p>
+ <td><p>The <a href="http://www.cct.lsu.edu/~eschnett/SimFactory/"
+ class="nostyle">simulation factory</a> includes configuration and
+ batch script files for compiling and running simulations using the
+ Cactus code on many different architectures. Additional
+ capabilities provide for management of simulations, simplifying
+ checkpoint & restart, and remote use of machines. The Einstein
+ Consortium have selected the simulation factory as the default
+ mechanism for supporting the easy use of Cactus on heterogeneous
+ resources.</p>
- <p>Distribution: CCT SVN repository: <a href="https://svn.cct.lsu.edu/repos/numrel/simfactory">https://svn.cct.lsu.edu/repos/numrel/simfactory</a></p></td>
+<p>Distribution: CCT SVN
+repository: <a href="https://svn.cct.lsu.edu/repos/numrel/simfactory">https://svn.cct.lsu.edu/repos/numrel/simfactory</a></p></td>
</tr>
<tr>
<td valign="top"><i>Cactus Thorns</i></td>
- <td><p>Code for the centrally supported Cactus thorns in the Einstein Toolkit. Additional thorns are maintained in external repositories with open access.</p>
- <p>Distribution: Einstein Toolkit SVN <br><a href="https://svn.einsteintoolkit.org/cactus">https://svn.einsteintoolkit.org/cactus/</a></p>
+<td><p>Code for the centrally supported Cactus thorns in the Einstein
+Toolkit. Additional thorns are maintained in external repositories
+with open access.</p>
+<p>Distribution: Einstein Toolkit
+SVN <br><a href="https://svn.einsteintoolkit.org/cactus">https://svn.einsteintoolkit.org/cactus/</a></p>
</td>
</tr>
<tr>
<td valign="top"><i>Parameter Files</i></td>
- <td><p>Example Cactus code parameter files for Einstein Toolkit beginners. Simple examples are provided for a Kerr-Schild black hole, a binary black hole coalescence, and a static TOV star. See the documentation for information on how to run these on the QueenBee machine.</p>
+ <td><p>Example Cactus code parameter files for Einstein Toolkit
+ beginners. Simple examples are provided for a Kerr-Schild black
+ hole, a binary black hole coalescence, and a static TOV star. See
+ the documentation for information on how to run these on the
+ QueenBee machine.</p>
- <p>Distribution: <a href="https://svn.einsteintoolkit.org/cactus/EinsteinExamples/par">https://svn.einsteintoolkit.org/cactus/EinsteinExamples/par</a></p>
+<p>Distribution: <a href="https://svn.einsteintoolkit.org/cactus/EinsteinExamples/par">https://svn.einsteintoolkit.org/cactus/EinsteinExamples/par</a></p>
</td>
</tr>
</table>
<h2>Thorns moving</h2>
-<p>A lot of components moved from one place to another in the recent past. The following table gives an overview of the moved components. Please note that only components are mentioned here which either moved to the Einstein Toolkit or into Cactus. Many other Cactus repositories moved from CVS to Subversion as well, but stayed within Cactus itself. Those are not mentioned here.</p>
+<p>A lot of components moved from one place to another in the recent
+ past. The following table gives an overview of the moved
+ components. Please note that only components are mentioned here
+ which either moved to the Einstein Toolkit or into Cactus. Many
+ other Cactus repositories moved from CVS to Subversion as well, but
+ stayed within Cactus itself. Those are not mentioned here.</p>
+
<h3>Cactus thorns</h3>
<table border="0">
<tr><th>Old arrangement</th><th>Old thorn name </th><th>New arrangement </th><th>New name (if changed)</th></tr>
More information about the Commits
mailing list