<?xml version="1.0"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
	<id>https://docs.einsteintoolkit.org/et-docs/api.php?action=feedcontributions&amp;feedformat=atom&amp;user=Bmundim</id>
	<title>Einstein Toolkit Documentation - User contributions [en]</title>
	<link rel="self" type="application/atom+xml" href="https://docs.einsteintoolkit.org/et-docs/api.php?action=feedcontributions&amp;feedformat=atom&amp;user=Bmundim"/>
	<link rel="alternate" type="text/html" href="https://docs.einsteintoolkit.org/et-docs/Special:Contributions/Bmundim"/>
	<updated>2026-05-21T23:14:51Z</updated>
	<subtitle>User contributions</subtitle>
	<generator>MediaWiki 1.31.0</generator>
	<entry>
		<id>https://docs.einsteintoolkit.org/et-docs/index.php?title=Improving_the_treatment_of_external_libraries&amp;diff=4065</id>
		<title>Improving the treatment of external libraries</title>
		<link rel="alternate" type="text/html" href="https://docs.einsteintoolkit.org/et-docs/index.php?title=Improving_the_treatment_of_external_libraries&amp;diff=4065"/>
		<updated>2015-10-21T14:30:23Z</updated>

		<summary type="html">&lt;p&gt;Bmundim: /* Additional Issues */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;==Background==&lt;br /&gt;
&lt;br /&gt;
Sometimes Cactus code needs to call code in libraries external to Cactus. In order to ensure that these libraries are available to Cactus, each is represented by a Cactus thorn.  These thorns perform the following functions:&lt;br /&gt;
&lt;br /&gt;
# Provide configuration variables for the user to use in their option lists to specify the location of the library on the machine.  Sometimes this is as simple as &amp;lt;lib&amp;gt;_DIR = /path/to/lib, but sometimes additional options need to be set, for example if the lib and include directories are in nonstandard locations in relation to the base library path.  The external library thorn translates the user&amp;#039;s settings for these variables into compiler and linker options which are then used by Cactus when compiling and linking.&lt;br /&gt;
# In the case that the user doesn&amp;#039;t specify the location of the library, the thorn attempts to locate the library in some standard locations.&lt;br /&gt;
# As a last resort, or if requested by the user, the thorn will build a version of the library and install it in the configuration directory.  For this reason, the thorn usually contains a distribution tarball of the library which is extracted and compiled during the Cactus configuration (CST) stage.  Sometimes there is also a patch which is applied to the source of the library. Having the libraries built as part of the configuration ensures that all the libraries needed are always available even if they have not been installed on the machine, but adds a significant overhead to compilation time.&lt;br /&gt;
&lt;br /&gt;
==Problems with the existing mechanism==&lt;br /&gt;
&lt;br /&gt;
At present, the logic for performing all of the above is implemented in configure.sh scripts in each library thorn.  This logic can be quite subtle and involved, and it is desirable for this to be implemented in a central location in a careful and correct way, rather than being duplicated for each library thorn.&lt;br /&gt;
&lt;br /&gt;
==Requirements==&lt;br /&gt;
&lt;br /&gt;
Collecting together the behaviour required by library thorns, such a mechanism needs to make it straightforward to do the following:&lt;br /&gt;
&lt;br /&gt;
* Provide a variable, &amp;lt;lib&amp;gt;_DIR which either:&lt;br /&gt;
** points to the library installation, in which case the thorn checks that the library in this location is usable and uses it if this is the case, otherwise compilation is aborted;&lt;br /&gt;
** is BUILD (caseless), in which case the thorn builds the library and uses that version;&lt;br /&gt;
** is NO_BUILD (causeless), in which case the thorn searches for a version on the system and uses that, unless it cannot be found, in which case the compilation is aborted;&lt;br /&gt;
** is unset, or is the empty string, in which case the library is first searched for, and if not found, is built (we could have a synonym AUTO (caseless) for this, to make it explicit)&lt;br /&gt;
* Provide variables which point to the include and library directories, but by default set these variables to &amp;lt;lib&amp;gt;/include and &amp;lt;lib&amp;gt;/lib.&lt;br /&gt;
* Search some standard locations for the library.&lt;br /&gt;
* Test that a given setting of the configuration variables works correctly; i.e. that a working version of the library is actually found at a given location&lt;br /&gt;
&lt;br /&gt;
Current configuration scripts search through some &amp;quot;standard&amp;quot; directories such as /usr and /usr/local and then look in standard subdirectories such as &amp;quot;lib&amp;quot; and &amp;quot;lib64&amp;quot; for libraries with standard extensions such as &amp;quot;.a&amp;quot;, &amp;quot;.so&amp;quot; and &amp;quot;.dylib&amp;quot; (for Mac OS).  This search logic is very low-level, and should probably be replaced by something higher level. For example, we shouldn&amp;#039;t make assumptions about the possible library extensions (.so etc), but instead should leave that to the linker.  Similarly, many standard installations of libraries will be in locations which the linker searches automatically, so in those cases, if the linker can find the library without assistance, we should not try to second-guess it.&lt;br /&gt;
&lt;br /&gt;
==Proposal==&lt;br /&gt;
&lt;br /&gt;
===Building===&lt;br /&gt;
&lt;br /&gt;
The thorn can provide a build.sh script which is responsible for building and installing the library in the configuration directory.  Separating this into a separate script makes the system more modular, and separates the logic for whether to build from the code that builds.&lt;br /&gt;
&lt;br /&gt;
===Testing===&lt;br /&gt;
&lt;br /&gt;
The thorn can provide a source file conftest.cc which, if successfully compiled, linked and run, indicates that the options used to compile and link it are sufficient to find the library.  When the user sets &amp;lt;lib&amp;gt;_DIR = /path/to/lib, &amp;lt;lib&amp;gt;_INC_DIRS and/or &amp;lt;lib&amp;gt;_LIB_DIRS, or sets &amp;lt;lib&amp;gt;_DIR = NO_BUILD, these are used to compile and link this program in order to test that this is possible.  This testing ensures that a missing library is detected early during the configuration stage, rather than when the first source file tries to include the missing header file.&lt;br /&gt;
&lt;br /&gt;
===Searching===&lt;br /&gt;
&lt;br /&gt;
When the library location has not been specified, the system needs to search for the library.  It will first attempt to compile, link and run the test program with no additional options.  This may be successful if the library is installed in a location which is on the standard compiler include/linker paths. If this fails, a sequence of include and library directories can be tried, and the first combination which works can then be used.  It may turn out that this is unnecessary, because any &amp;quot;standard&amp;quot; paths that the thorn might know about would probably be tried by the system anyway.  A possible exception would be a MacPorts installation in /opt/local which is not searched for by default by the compiler. Note that this is related to the problem that if we add, e.g. /opt/local/lib to the linker path for, say, HDF5, then this might cause something else like MPICH to be found from there, even if the user has specified MPI_DIR to be something else.  We don&amp;#039;t have a solution to this problem.&lt;br /&gt;
&lt;br /&gt;
===Factoring out common code===&lt;br /&gt;
&lt;br /&gt;
Each library thorn&amp;#039;s configure.sh script can call a bash function (or maybe a script) which we provide in the flesh: configure_library:&lt;br /&gt;
&lt;br /&gt;
  configure_library &amp;lt;lib&amp;gt; &amp;lt;dist&amp;gt; &amp;lt;patch&amp;gt;...&lt;br /&gt;
&lt;br /&gt;
* &amp;lt;lib&amp;gt;: A capitalised name of the library, e.g. HDF5, HWLOC, MPI suitable for use in environment variable names.&lt;br /&gt;
* &amp;lt;dist&amp;gt;: A path to the source distribution tarball relative to the thorn, e.g. dist/zlib-1.2.7.tar.gz&lt;br /&gt;
* &amp;lt;patch&amp;gt;: A path to any patch that needs to be applied&lt;br /&gt;
  &lt;br /&gt;
configure_library does the following:&lt;br /&gt;
* Enable verbose output if requested&lt;br /&gt;
* Look at the variables set by the user and choose which of the following to do, and do it:&lt;br /&gt;
** Build the library&lt;br /&gt;
** Use the library from a specified location, and test that this works, otherwise abort&lt;br /&gt;
** Search for the library, and use it if found, otherwise abort&lt;br /&gt;
** Search for the library, use if found, otherwise build&lt;br /&gt;
* Set Cactus include and link variables so that the library will be appropriately found by Cactus, as well as the HAVE_&amp;lt;lib&amp;gt; macro&lt;br /&gt;
&lt;br /&gt;
==Questions==&lt;br /&gt;
&lt;br /&gt;
* How should the user get the behaviour of setting &amp;lt;lib&amp;gt;_DIR to point to a directory, i.e. explicitly using a specific installation, if there is no such directory, and the include and lib dirs need to be specified separately?  Maybe setting any of these three variables (&amp;lt;lib&amp;gt;_DIR, &amp;lt;lib&amp;gt;_INC_DIRS and &amp;lt;lib&amp;gt;_LIB_DIRS) should trigger using exactly that version of the library.&lt;br /&gt;
&lt;br /&gt;
===Additional Issues===&lt;br /&gt;
&lt;br /&gt;
to be worked into the text above.&lt;br /&gt;
&lt;br /&gt;
* &amp;quot;Standard&amp;quot; paths such as those with prefix /usr or /usr/local must not be added to INC_DIRS and LIB_DIRS (BCM: or at least it should be possible to optionally add them at the end)&lt;br /&gt;
* Instead of a capitalised library name, we should pass the &amp;quot;natural&amp;quot; name, and capitalise within the script. This allows nicer error messages.&lt;br /&gt;
* Assuming that configure_library unpacks the library: It will be necessary to pass in also the directory in which the (unpacked) configure script is found.&lt;br /&gt;
* &amp;lt;patch&amp;gt;: Note that multiple patches may be required.&lt;br /&gt;
* Running a test program: Sometimes it is not possible to run a program (e.g. for MPI). In this case, building and linking is still a good idea for testing.&lt;br /&gt;
* We should think about cross-compiling. It needs to be supported at least to the extent that the configuration options can specify an existing library, which is then accepted by Cactus.&lt;br /&gt;
* Maybe there should be a generic mechanism to skip all testing?&lt;br /&gt;
* Having a _DIR variable containing &amp;quot;BUILD&amp;quot; and &amp;quot;NO_BUILD&amp;quot; doesn&amp;#039;t really make sense. Maybe we should set e.g. &amp;quot;HDF5=BUILD&amp;quot;, or &amp;quot;HDF5=NO_BUILD&amp;quot;, and use HDF5_DIR only for providing default values for HDF5_LIB_DIRS? In this case, &amp;quot;HDF5=NO_TEST&amp;quot; would also be possible.&lt;br /&gt;
* Certain environment variables (e.g. LIBS) should automatically be unset by configure_library, not by the thorn&amp;#039;s build script. These variables have a special, non-standard meaning in Cactus, and basically all configure scripts get confused by them.&lt;br /&gt;
&lt;br /&gt;
===Possible improvements===&lt;br /&gt;
&lt;br /&gt;
which are not really related to the topic discussed here.&lt;br /&gt;
&lt;br /&gt;
* In most cases, a library that has been built once can be re-used by all other builds on the same machine. (Exceptions exist.) Since reducing build time is mentioned as a goal above, we could install libraries into a specific directory (e.g. Cactus/exe/lib), and thus share external library builds between configurations. These would then not be deleted by a make realclean, but would be rebuilt when necessary. It is up to the option list to ensure that incompatible option lists specify different install directories. Maybe the option list name itself could be used as prefix.&lt;br /&gt;
* We should separate the distributed tarballs from the thorns containing the logic. This would save download time for those who don&amp;#039;t want / need the tarballs.&lt;br /&gt;
* We could allow the tarballs to be downloaded directly and only when needed, without storing them in svn.&lt;br /&gt;
&lt;br /&gt;
===Some high-level thoughts===&lt;br /&gt;
&lt;br /&gt;
which should probably be at the top.&lt;br /&gt;
&lt;br /&gt;
* Do we really want to continue to develop this mechanism? Or can we adopt rpm / dpkg / pkgconfig instead? In the long run, it may be easier to write a pkgconfig definition for LORENE than maintaining whole sets of configuration scripts ourselves.&lt;br /&gt;
&lt;br /&gt;
== Building from source ==&lt;br /&gt;
&lt;br /&gt;
(move this to a separate page)&lt;br /&gt;
&lt;br /&gt;
The current system of storing the source tarball in the thorn SVN repository is not ideal.  Included here is an email written by Ian in 2013 about this, with some ideas for improving the system.&lt;br /&gt;
&lt;br /&gt;
* The tarball would not be included in the repository. RH: I would prefer to store tarballs (or their content) in a repository we control, this does not have to be the same that holds the control files, the reason is that some of the ExternalLibraries may change their hosting url/not life as long as the ET. For example the oldest version of curl still available on the webserver at http://curl.haxx.se/ is from 2000 and anything older than 2010 is in a subdirectory archeology. &lt;br /&gt;
* The configuration.ccl file of the thorn would have a field for the URL of a tarball to download&lt;br /&gt;
* At configuration time, the thorn&amp;#039;s configure script (or something factored into a Cactus script) would download the tarball using the URL if it is necessary to build the library on that machine.&lt;br /&gt;
* The tarball would be cached in Cactus/librarycache or similar&lt;br /&gt;
* A script or makefile target would be provided to &amp;quot;pre-cache&amp;quot; the tarball of one or more thorns. RH: GetComponents can download arbitrary single files via http so we already have that possibility&lt;br /&gt;
&lt;br /&gt;
A checkout of the ET now would not download any external library tarballs.  If, on a given machine, a library is not installed and needs to be built, it would be downloaded when needed. If you want to make sure you have everything needed to build, for example if you are about to catch a plane, you could run something like &amp;quot;make get-libraries&amp;quot; and all library tarballs would be downloaded into Cactus/librarycache.  [It would be possible to do this using simfactory, which might be able to determine via its machine database which machines need which tarballs downloaded].  You could then choose to sync this to the remote machine, or not.  On a remote machine, you could run get-libraries on the head node which presumably has an internet connection so that the library tarballs are available to the build process which might, as Frank points out, not have internet access.&lt;br /&gt;
&lt;br /&gt;
The vast majority of users would notice little difference; the checkout would be faster, and less disk space would be used by their Cactus trees.  Edge-case users who have to compile on machines without internet connections would have a simple command to run on the head node of the machine which would restore the same functionality that we currently have.&lt;/div&gt;</summary>
		<author><name>Bmundim</name></author>
		
	</entry>
	<entry>
		<id>https://docs.einsteintoolkit.org/et-docs/index.php?title=Main_Page&amp;diff=3916</id>
		<title>Main Page</title>
		<link rel="alternate" type="text/html" href="https://docs.einsteintoolkit.org/et-docs/index.php?title=Main_Page&amp;diff=3916"/>
		<updated>2015-06-12T07:16:26Z</updated>

		<summary type="html">&lt;p&gt;Bmundim: /* Einstein Toolkit workshop information */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;==Instructions==&lt;br /&gt;
&lt;br /&gt;
Documentation for the [http://www.einsteintoolkit.org Einstein Toolkit] is a community effort and everyone is encouraged to contribute towards these pages. You need to login to the wiki to edit the documentation, to do this either&lt;br /&gt;
&lt;br /&gt;
* if you already have a personal LDAP login with the CCT use this &lt;br /&gt;
* create you own login/password for the wiki (select local domain)&lt;br /&gt;
&lt;br /&gt;
If you would like to make major changes to these pages please discuss first on the users@einsteintoolkit.org mail list. &lt;br /&gt;
&lt;br /&gt;
Thanks for your contributions!&lt;br /&gt;
&lt;br /&gt;
==Einstein Toolkit workshop information==&lt;br /&gt;
&lt;br /&gt;
=== Current ===&lt;br /&gt;
&lt;br /&gt;
* [[ET Workshop 2015| ET Workshop Summer 2015, Stockholm]]&lt;br /&gt;
&lt;br /&gt;
=== Past ===&lt;br /&gt;
&lt;br /&gt;
* [[ET_Workshop Summer 2013]] (shows both workshops)&lt;br /&gt;
** [[ET_Workshop Summer 2013 (New Users Workshop)]]&lt;br /&gt;
** [[ET_Workshop Summer 2013 (Developers Workshop)]]&lt;br /&gt;
* [[ET_Workshop Fall 2012]]&lt;br /&gt;
* [[ET_Workshop Spring 2012]]&lt;br /&gt;
* [[ET_Workshop Fall 2011]]&lt;br /&gt;
* [[ET_Workshop Spring 2011]]&lt;br /&gt;
* [http://ccrg.rit.edu/~carpet/index.php/Main_Page Carpet Developer Workshop Summer 2010]&lt;br /&gt;
&lt;br /&gt;
==Einstein Toolkit Seminars==&lt;br /&gt;
&lt;br /&gt;
It would be nice to organize a semi-regular series of talks with topics of general interest. This should include&lt;br /&gt;
not only people from within the Einstein Toolkit. The ET web page already contains a (currently quite short)&lt;br /&gt;
[http://einsteintoolkit.org/seminars/ list], and now it is time to propose upcoming talks. In order to record and&lt;br /&gt;
story voiced proposals, please use the wiki page [[Einstein Toolkit Seminar Proposals]].&lt;br /&gt;
&lt;br /&gt;
==Release planning==&lt;br /&gt;
* [[Release Details]]&lt;br /&gt;
* [[Release Process]]&lt;br /&gt;
&lt;br /&gt;
==Documentation==&lt;br /&gt;
&lt;br /&gt;
* [[Tutorial for New Users]]&lt;br /&gt;
* [[Tutorial for previous release]]&lt;br /&gt;
* [[Simplified Tutorial for New Users]] (requires Debian, Linux Mint, Fedora or Mac OSX)&lt;br /&gt;
* [[Getting Started for Cactus Experts]]&lt;br /&gt;
* [[Thorns_we_know_of|Non-Einstein-Toolkit thorns]]&lt;br /&gt;
* [[Einstein Toolkit standards]]: ADMBase, HydroBase, EOSBase, SphericalSurface&lt;br /&gt;
* [[Supported Machines]]&lt;br /&gt;
* [[Using Eclipse / Mojave]]&lt;br /&gt;
* [[Running Cactus On Windows]]&lt;br /&gt;
* Adding your own analysis method&lt;br /&gt;
* Adding your own [[adding initial data|initial data]]&lt;br /&gt;
* Adding a [[adding a test case|test case]]&lt;br /&gt;
* CCE [http://ccrg.rit.edu/~yosef/cce.html tutorial]&lt;br /&gt;
* [[Visualizing magnetic field lines]]&lt;br /&gt;
* [[Using the multi-model mechanism in Carpet]]&lt;br /&gt;
* [[Working with git]]&lt;br /&gt;
* [[FAQ]]&lt;br /&gt;
* [[Compiling the Einstein Toolkit]]&lt;br /&gt;
&lt;br /&gt;
==Regression Test Results==&lt;br /&gt;
You can run [[Simulation_Factory_Advanced_Tutorial#Test_suites | regression tests using SimFactory]].&lt;br /&gt;
&lt;br /&gt;
Results from automated tests are available at https://build.barrywardell.net.&lt;br /&gt;
&lt;br /&gt;
==Performance Test Results==&lt;br /&gt;
* [[Single-node benchmark results]] for the Einstein Toolkit&lt;br /&gt;
* TODO: Scalability benchmark results for the Einstein Toolkit&lt;br /&gt;
&lt;br /&gt;
==Projects==&lt;br /&gt;
&lt;br /&gt;
* [[Adding requirements to the Cactus scheduler]]&lt;br /&gt;
* [[Visualization of simulation results]]&lt;br /&gt;
* [[Automated testing]]&lt;br /&gt;
* [[Vectorization]] Improving code performance by using the CPU&amp;#039;s vector instructions&lt;br /&gt;
* [[Padding]] Improving code performance by optimizing cache access&lt;br /&gt;
* [[Making Cactus Installable]] like any other Ubuntu package&lt;br /&gt;
* [[Test suite results are unwieldy]]&lt;br /&gt;
* [[Summer student projects]]&lt;br /&gt;
* [[Improving the treatment of external libraries]]&lt;br /&gt;
* [[Piraha Parser Discussion]]&lt;br /&gt;
* [[Version control]]&lt;br /&gt;
* [[Rewrite McLachlan]]&lt;br /&gt;
&lt;br /&gt;
==Maintainers==&lt;br /&gt;
&lt;br /&gt;
* [[Organization and Responsibilities]]&lt;br /&gt;
* [[How to Review a Patch]]&lt;br /&gt;
* [[Policies to retire functionality]]&lt;br /&gt;
* [[Preparing a Patch for Review]]&lt;br /&gt;
* [http://einsteintoolkit.org/release-info/parse_testsuite_results.php Release Testsuite Status], [https://build.barrywardell.net/job/EinsteinToolkit/ Trunk Testsuite Status]&lt;br /&gt;
* [[Standard Emails]]&lt;br /&gt;
* [[MHD implementation details and discussions]]&lt;br /&gt;
* [[Carpet Wish List]]&lt;br /&gt;
* [[Editing the website]]&lt;br /&gt;
* [[Usage poll]]&lt;br /&gt;
* [[Repository transition]]&lt;br /&gt;
* [[Tickets]]&lt;br /&gt;
&lt;br /&gt;
== Getting Started with Wikis ==&lt;br /&gt;
&lt;br /&gt;
* Consult the [http://meta.wikimedia.org/wiki/Help:Contents User&amp;#039;s Guide] for information on using the wiki software.&lt;br /&gt;
* [http://www.mediawiki.org/wiki/Help:Configuration_settings Configuration settings list]&lt;br /&gt;
* [http://www.mediawiki.org/wiki/Help:FAQ MediaWiki FAQ]&lt;br /&gt;
* [http://mail.wikimedia.org/mailman/listinfo/mediawiki-announce MediaWiki release mailing list]&lt;/div&gt;</summary>
		<author><name>Bmundim</name></author>
		
	</entry>
	<entry>
		<id>https://docs.einsteintoolkit.org/et-docs/index.php?title=Getting_Started_for_Cactus_Experts&amp;diff=3745</id>
		<title>Getting Started for Cactus Experts</title>
		<link rel="alternate" type="text/html" href="https://docs.einsteintoolkit.org/et-docs/index.php?title=Getting_Started_for_Cactus_Experts&amp;diff=3745"/>
		<updated>2014-10-13T11:40:57Z</updated>

		<summary type="html">&lt;p&gt;Bmundim: /* Stable Version */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;=Stable Version=&lt;br /&gt;
&lt;br /&gt;
Use  [https://github.com/gridaphobe/CRL/raw/ET_2014_05/GetComponents GetComponents] (the new version of GetCactus) with the Einstein Toolkit [https://svn.einsteintoolkit.org/manifest/branches/ET_2014_05/einsteintoolkit.th thornlist]. This thornlist should work on platforms supported by the Cactus team using the usual  [http://www.cactuscode.org/download/configfiles configuration files] available on the Cactus web page or with the [http://www.cct.lsu.edu/~eschnett/SimFactory Simulation Factory].&lt;br /&gt;
&lt;br /&gt;
Example parameter files are provided in the Einstein Toolkit SVN repository:&lt;br /&gt;
&lt;br /&gt;
 svn checkout https://svn.einsteintoolkit.org/cactus/EinsteinExamples/branches/ET_2014_05/par&lt;br /&gt;
&lt;br /&gt;
=Development Version=&lt;br /&gt;
&lt;br /&gt;
For those experts interested in the development (unstable) branch of the toolkit,&lt;br /&gt;
please download GetComponents at:&lt;br /&gt;
&lt;br /&gt;
 wget --no-check-certificate https://github.com/gridaphobe/CRL/raw/master/GetComponents&lt;br /&gt;
 chmod 755 GetComponents&lt;br /&gt;
&lt;br /&gt;
and checkout the Einstein Toolkit thornlist at:&lt;br /&gt;
&lt;br /&gt;
 ./GetComponents -p -a https://bitbucket.org/einsteintoolkit/manifest/raw/master/einsteintoolkit.th&lt;br /&gt;
&lt;br /&gt;
Problems should be directed to [mailto:users@einsteintoolkit.org users@einsteintoolkit.org] or [mailto:users@cactuscode.org users@cactuscode.org] as appropriate.&lt;/div&gt;</summary>
		<author><name>Bmundim</name></author>
		
	</entry>
	<entry>
		<id>https://docs.einsteintoolkit.org/et-docs/index.php?title=Getting_Started_for_Cactus_Experts&amp;diff=3744</id>
		<title>Getting Started for Cactus Experts</title>
		<link rel="alternate" type="text/html" href="https://docs.einsteintoolkit.org/et-docs/index.php?title=Getting_Started_for_Cactus_Experts&amp;diff=3744"/>
		<updated>2014-10-13T11:38:38Z</updated>

		<summary type="html">&lt;p&gt;Bmundim: /* Development Version */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;=Stable Version=&lt;br /&gt;
&lt;br /&gt;
Use  [https://github.com/gridaphobe/CRL/raw/ET_2012_11/GetComponents GetComponents] (the new version of GetCactus) with the Einstein Toolkit [https://svn.einsteintoolkit.org/manifest/branches/ET_2012_11/einsteintoolkit.th thornlist]. This thornlist should work on platforms supported by the Cactus team using the usual  [http://www.cactuscode.org/download/configfiles configuration files] available on the Cactus web page or with the [http://www.cct.lsu.edu/~eschnett/SimFactory Simulation Factory].&lt;br /&gt;
&lt;br /&gt;
Example parameter files are provided in the Einstein Toolkit SVN repository:&lt;br /&gt;
&lt;br /&gt;
 svn checkout https://svn.einsteintoolkit.org/cactus/EinsteinExamples/branches/ET_2012_11/par&lt;br /&gt;
&lt;br /&gt;
=Development Version=&lt;br /&gt;
&lt;br /&gt;
For those experts interested in the development (unstable) branch of the toolkit,&lt;br /&gt;
please download GetComponents at:&lt;br /&gt;
&lt;br /&gt;
 wget --no-check-certificate https://github.com/gridaphobe/CRL/raw/master/GetComponents&lt;br /&gt;
 chmod 755 GetComponents&lt;br /&gt;
&lt;br /&gt;
and checkout the Einstein Toolkit thornlist at:&lt;br /&gt;
&lt;br /&gt;
 ./GetComponents -p -a https://bitbucket.org/einsteintoolkit/manifest/raw/master/einsteintoolkit.th&lt;br /&gt;
&lt;br /&gt;
Problems should be directed to [mailto:users@einsteintoolkit.org users@einsteintoolkit.org] or [mailto:users@cactuscode.org users@cactuscode.org] as appropriate.&lt;/div&gt;</summary>
		<author><name>Bmundim</name></author>
		
	</entry>
	<entry>
		<id>https://docs.einsteintoolkit.org/et-docs/index.php?title=Testsuite_Machines&amp;diff=3667</id>
		<title>Testsuite Machines</title>
		<link rel="alternate" type="text/html" href="https://docs.einsteintoolkit.org/et-docs/index.php?title=Testsuite_Machines&amp;diff=3667"/>
		<updated>2013-11-12T07:35:43Z</updated>

		<summary type="html">&lt;p&gt;Bmundim: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;This page contains notes and instructions for people running the ET testsuites on various different machines.  If you have experience running testsuites on a machine which is not listed here, please consider adding some information which might help others (or yourself!) in future.  &lt;br /&gt;
&lt;br /&gt;
=General=&lt;br /&gt;
&lt;br /&gt;
To check out the ET:&lt;br /&gt;
&lt;br /&gt;
  mkdir etrelease&lt;br /&gt;
  cd etrelease&lt;br /&gt;
  curl -O https://raw.github.com/gridaphobe/CRL/master/GetComponents &lt;br /&gt;
  chmod a+x GetComponents&lt;br /&gt;
  ./GetComponents --root=. -a https://svn.einsteintoolkit.org/manifest/trunk/einsteintoolkit.th&lt;br /&gt;
&lt;br /&gt;
  cp simfactory/etc/defs.local.ini.simple simfactory/etc/defs.local.ini&lt;br /&gt;
  nano simfactory/etc/defs.local.ini&lt;br /&gt;
&lt;br /&gt;
Edit defs.local.ini and replace&lt;br /&gt;
&lt;br /&gt;
  YOUR_LOGIN with your username&lt;br /&gt;
  YOUR@EMAIL.ADDRESS with your usual email address&lt;br /&gt;
  YOUR_ALLOCATION with your project allocation&lt;br /&gt;
  YOUR_THORNLIST with manifest/einsteintoolkit.th&lt;br /&gt;
&lt;br /&gt;
See the machine-specific notes below for any additional steps for each machine.&lt;br /&gt;
&lt;br /&gt;
  sim sync &amp;lt;machine&amp;gt;&lt;br /&gt;
  sim login &amp;lt;machine&amp;gt;&lt;br /&gt;
  sim build&lt;br /&gt;
  sim create-submit ettests_1proc --testsuite --procs &amp;lt;N&amp;gt; --num-threads &amp;lt;N&amp;gt; --walltime 3:00:00&lt;br /&gt;
  sim create-submit ettests_2proc --testsuite --procs &amp;lt;N&amp;gt; --num-threads &amp;lt;N/2&amp;gt; --walltime 3:00:00&lt;br /&gt;
&lt;br /&gt;
Replace &amp;lt;N&amp;gt; and &amp;lt;N/2&amp;gt; with the number of cores on each node, and half of this, respectively, for the machine you are using.  Remember that &amp;quot;procs&amp;quot; here means &amp;quot;cores&amp;quot; and &amp;quot;num-threads&amp;quot; means &amp;quot;number of threads per process&amp;quot;. The idea is to use a full node, i.e. all the cores, and then either one or two MPI processes.&lt;br /&gt;
&lt;br /&gt;
When the jobs have finished, you should have the summary.log files in&lt;br /&gt;
&lt;br /&gt;
  &amp;lt;simulations&amp;gt;/ettests_1proc/output-0000/TEST/sim/summary.log&lt;br /&gt;
  &amp;lt;simulations&amp;gt;/ettests_2proc/output-0000/TEST/sim/summary.log&lt;br /&gt;
&lt;br /&gt;
Update the testsuite status page by adding the log files to the release-info repository:&lt;br /&gt;
&lt;br /&gt;
  svn checkout https://svn.einsteintoolkit.org/www/release-info&lt;br /&gt;
  cd release-info&lt;br /&gt;
  scp machine:&amp;lt;simulations&amp;gt;/ettests_1proc/output-0000/TEST/sim/summary.log &amp;lt;machine&amp;gt;__1_&amp;lt;N&amp;gt;.log&lt;br /&gt;
  scp machine:&amp;lt;simulations&amp;gt;/ettests_2proc/output-0000/TEST/sim/summary.log &amp;lt;machine&amp;gt;__2_&amp;lt;N/2&amp;gt;.log&lt;br /&gt;
  svn commit &amp;lt;machine&amp;gt;*.log&lt;br /&gt;
&lt;br /&gt;
To re-run the tests with an updated checkout, run the GetComponents command above with the --update flag, rebuild, delete the &amp;quot;ettests_*&amp;quot; simulations, and resubmit the simulations.&lt;br /&gt;
&lt;br /&gt;
=Machines=&lt;br /&gt;
&lt;br /&gt;
==Kraken==&lt;br /&gt;
&lt;br /&gt;
N=12&lt;br /&gt;
&lt;br /&gt;
==Datura==&lt;br /&gt;
&lt;br /&gt;
N=12&lt;br /&gt;
&lt;br /&gt;
==SuperMUC==&lt;br /&gt;
&lt;br /&gt;
N=16&lt;br /&gt;
&lt;br /&gt;
==Stampede==&lt;br /&gt;
&lt;br /&gt;
N=16&lt;br /&gt;
&lt;br /&gt;
==Loewe==&lt;br /&gt;
&lt;br /&gt;
N=24&lt;/div&gt;</summary>
		<author><name>Bmundim</name></author>
		
	</entry>
	<entry>
		<id>https://docs.einsteintoolkit.org/et-docs/index.php?title=Preparing_a_Patch_for_Review&amp;diff=3281</id>
		<title>Preparing a Patch for Review</title>
		<link rel="alternate" type="text/html" href="https://docs.einsteintoolkit.org/et-docs/index.php?title=Preparing_a_Patch_for_Review&amp;diff=3281"/>
		<updated>2012-08-30T21:23:06Z</updated>

		<summary type="html">&lt;p&gt;Bmundim: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&amp;lt;h2&amp;gt;Best Practices&amp;lt;/h2&amp;gt;&lt;br /&gt;
&lt;br /&gt;
* Avoid saving tab characters in the patch. The main reason is that different text editors use different defaults to interpret tab characters as spaces. Also some people like to set 8 spaces as the default for a tab character while others prefer 4 or 3. The end result is that the proposed code will look unformatted, making hard to the eye to read and follow the code indentations. Possible ways to teach your text editor:&lt;br /&gt;
&lt;br /&gt;
 For vi family set the following in your .exrc:&lt;br /&gt;
  set expandtab&lt;br /&gt;
&lt;br /&gt;
 For emacs family add the following to your .emacs:&lt;br /&gt;
  (setq-default indent-tabs-mode nil);&lt;/div&gt;</summary>
		<author><name>Bmundim</name></author>
		
	</entry>
	<entry>
		<id>https://docs.einsteintoolkit.org/et-docs/index.php?title=Preparing_a_Patch_for_Review&amp;diff=3280</id>
		<title>Preparing a Patch for Review</title>
		<link rel="alternate" type="text/html" href="https://docs.einsteintoolkit.org/et-docs/index.php?title=Preparing_a_Patch_for_Review&amp;diff=3280"/>
		<updated>2012-08-30T21:18:24Z</updated>

		<summary type="html">&lt;p&gt;Bmundim: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&amp;lt;h2&amp;gt;Best Practices&amp;lt;/h2&amp;gt;&lt;br /&gt;
&lt;br /&gt;
* Avoid saving tab characters in the patch. The main reason is that different text editors use different defaults to interpret tab characters as spaces. Also some people like to set 8 spaces as the default for a tab character while others prefer 4 or 3. The end result is that the proposed code will look unformatted, making hard to the eye to read and follow the code indentations. Possible ways to teach your text editor:&lt;br /&gt;
&lt;br /&gt;
For vi family set the following in your .exrc:&lt;br /&gt;
 set expandtab&lt;br /&gt;
&lt;br /&gt;
For emacs family add the following to your .emacs:&lt;br /&gt;
 (setq-default indent-tabs-mode nil);&lt;/div&gt;</summary>
		<author><name>Bmundim</name></author>
		
	</entry>
	<entry>
		<id>https://docs.einsteintoolkit.org/et-docs/index.php?title=Preparing_a_Patch_for_Review&amp;diff=3279</id>
		<title>Preparing a Patch for Review</title>
		<link rel="alternate" type="text/html" href="https://docs.einsteintoolkit.org/et-docs/index.php?title=Preparing_a_Patch_for_Review&amp;diff=3279"/>
		<updated>2012-08-30T21:16:37Z</updated>

		<summary type="html">&lt;p&gt;Bmundim: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&amp;lt;h2&amp;gt;Best Practices&amp;lt;/h2&amp;gt;&lt;br /&gt;
&lt;br /&gt;
* Avoid saving tab characters in the patch. The main reason is that different text editors use different defaults to interpret tab characters as spaces. Also some people like to set 8 spaces as the default for a tab character while others prefer 4 or 3. The end result is that the proposed code will look unformatted, making hard to the eye to read and follow the code indentations.&lt;/div&gt;</summary>
		<author><name>Bmundim</name></author>
		
	</entry>
	<entry>
		<id>https://docs.einsteintoolkit.org/et-docs/index.php?title=Preparing_a_Patch_for_Review&amp;diff=3278</id>
		<title>Preparing a Patch for Review</title>
		<link rel="alternate" type="text/html" href="https://docs.einsteintoolkit.org/et-docs/index.php?title=Preparing_a_Patch_for_Review&amp;diff=3278"/>
		<updated>2012-08-30T21:16:17Z</updated>

		<summary type="html">&lt;p&gt;Bmundim: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&amp;lt;h2&amp;gt;Best Practices&amp;lt;/h2&amp;gt;&lt;br /&gt;
&lt;br /&gt;
* Avoid saving tab characters in the patch. The main reason is that different text editors use different defaults to interpret tab characters as spaces. Also some people like to set 8 spaces as the default for a tab character while others prefer 4 or 3. &lt;br /&gt;
The end result is that the proposed code will look unformatted, making hard to the eye to read and follow the code indentations.&lt;/div&gt;</summary>
		<author><name>Bmundim</name></author>
		
	</entry>
	<entry>
		<id>https://docs.einsteintoolkit.org/et-docs/index.php?title=Preparing_a_Patch_for_Review&amp;diff=3277</id>
		<title>Preparing a Patch for Review</title>
		<link rel="alternate" type="text/html" href="https://docs.einsteintoolkit.org/et-docs/index.php?title=Preparing_a_Patch_for_Review&amp;diff=3277"/>
		<updated>2012-08-30T21:15:59Z</updated>

		<summary type="html">&lt;p&gt;Bmundim: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&amp;lt;h2&amp;gt;Best Practices&amp;lt;/h2&amp;gt;&lt;br /&gt;
&lt;br /&gt;
* Avoid saving tab characters in the patch. The main reason is that different text editors use different defaults to interpret tab characters as spaces. Also some people like to set 8 spaces as the default for a tab character while others prefer 4 or 3. The &lt;br /&gt;
end result is that the proposed code will look unformatted, making hard to the eye to read and follow the code indentations.&lt;/div&gt;</summary>
		<author><name>Bmundim</name></author>
		
	</entry>
	<entry>
		<id>https://docs.einsteintoolkit.org/et-docs/index.php?title=Preparing_a_Patch_for_Review&amp;diff=3276</id>
		<title>Preparing a Patch for Review</title>
		<link rel="alternate" type="text/html" href="https://docs.einsteintoolkit.org/et-docs/index.php?title=Preparing_a_Patch_for_Review&amp;diff=3276"/>
		<updated>2012-08-30T21:15:49Z</updated>

		<summary type="html">&lt;p&gt;Bmundim: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&amp;lt;h2&amp;gt;Best Practices&amp;lt;/h2&amp;gt;&lt;br /&gt;
&lt;br /&gt;
 * Avoid saving tab characters in the patch. The main reason is that different text editors use different defaults to interpret tab characters as spaces. Also some people like to set 8 spaces as the default for a tab character while others prefer 4 or 3. The &lt;br /&gt;
end result is that the proposed code will look unformatted, making hard to the eye to read and follow the code indentations.&lt;/div&gt;</summary>
		<author><name>Bmundim</name></author>
		
	</entry>
	<entry>
		<id>https://docs.einsteintoolkit.org/et-docs/index.php?title=Preparing_a_Patch_for_Review&amp;diff=3275</id>
		<title>Preparing a Patch for Review</title>
		<link rel="alternate" type="text/html" href="https://docs.einsteintoolkit.org/et-docs/index.php?title=Preparing_a_Patch_for_Review&amp;diff=3275"/>
		<updated>2012-08-30T21:15:33Z</updated>

		<summary type="html">&lt;p&gt;Bmundim: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&amp;lt;h2&amp;gt;Best Practices&amp;lt;/h2&amp;gt;&lt;br /&gt;
&lt;br /&gt;
 Avoid saving tab characters in the patch. The main reason is that different text editors use different defaults to interpret tab characters as spaces. Also some people like to set 8 spaces as the default for a tab character while others prefer 4 or 3. The &lt;br /&gt;
end result is that the proposed code will look unformatted, making hard to the eye to read and follow the code indentations.&lt;/div&gt;</summary>
		<author><name>Bmundim</name></author>
		
	</entry>
	<entry>
		<id>https://docs.einsteintoolkit.org/et-docs/index.php?title=Preparing_a_Patch_for_Review&amp;diff=3274</id>
		<title>Preparing a Patch for Review</title>
		<link rel="alternate" type="text/html" href="https://docs.einsteintoolkit.org/et-docs/index.php?title=Preparing_a_Patch_for_Review&amp;diff=3274"/>
		<updated>2012-08-30T21:11:41Z</updated>

		<summary type="html">&lt;p&gt;Bmundim: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&amp;lt;h2&amp;gt;Best Practices&amp;lt;/h2&amp;gt;&lt;/div&gt;</summary>
		<author><name>Bmundim</name></author>
		
	</entry>
	<entry>
		<id>https://docs.einsteintoolkit.org/et-docs/index.php?title=Main_Page&amp;diff=3273</id>
		<title>Main Page</title>
		<link rel="alternate" type="text/html" href="https://docs.einsteintoolkit.org/et-docs/index.php?title=Main_Page&amp;diff=3273"/>
		<updated>2012-08-30T21:10:28Z</updated>

		<summary type="html">&lt;p&gt;Bmundim: /* Maintainers */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;==Instructions==&lt;br /&gt;
&lt;br /&gt;
Documentation for the [http://www.einsteintoolkit.org Einstein Toolkit] is a community effort and everyone is encouraged to contribute towards these pages. You need to login to the wiki to edit the documentation, to do this either&lt;br /&gt;
&lt;br /&gt;
* if you already have a personal LDAP login with the CCT use this &lt;br /&gt;
* create you own login/password for the wiki (select local domain)&lt;br /&gt;
&lt;br /&gt;
If you would like to make major changes to these pages please discuss first on the users@einsteintoolkit.org mail list. &lt;br /&gt;
&lt;br /&gt;
Thanks for your contributions!&lt;br /&gt;
&lt;br /&gt;
==Einstein Toolkit workshop information==&lt;br /&gt;
=== Current ===&lt;br /&gt;
* [[ET_Workshop Fall 2012]]&lt;br /&gt;
&lt;br /&gt;
=== Past ===&lt;br /&gt;
&lt;br /&gt;
* [[ET_Workshop Spring 2012]]&lt;br /&gt;
* [[ET_Workshop Fall 2011]]&lt;br /&gt;
* [[ET_Workshop Spring 2011]]&lt;br /&gt;
* [http://ccrg.rit.edu/~carpet/wiki/Main_Page Carpet Developer Workshop Summer 2010]&lt;br /&gt;
&lt;br /&gt;
==Einstein Toolkit Seminars==&lt;br /&gt;
&lt;br /&gt;
It would be nice to organize a semi-regular series of talks with topics of general interest. This should include&lt;br /&gt;
not only people from within the Einstein Toolkit. The ET web page already contains a (currently quite short)&lt;br /&gt;
[http://einsteintoolkit.org/seminars/ list], and now it is time to propose upcoming talks. In order to record and&lt;br /&gt;
story voiced proposals, please use the wiki page [[Einstein Toolkit Seminar Proposals]].&lt;br /&gt;
&lt;br /&gt;
==Documentation==&lt;br /&gt;
&lt;br /&gt;
* [[Tutorial for New Users]]&lt;br /&gt;
* [[Tutorial for previous release]]&lt;br /&gt;
* [[Simplified Tutorial for New Users]] (incomplete, and requires Debian or Fedora)&lt;br /&gt;
* [[Getting Started for Cactus Experts]]&lt;br /&gt;
* [[Thorns_we_know_of|Non-Einstein-Toolkit thorns]]&lt;br /&gt;
* [[Einstein Toolkit standards]]: ADMBase, HydroBase, EOSBase, SphericalSurface&lt;br /&gt;
* [[Supported Machines]]&lt;br /&gt;
* [[Using Eclipse / Mojave]]&lt;br /&gt;
* Adding your own analysis method&lt;br /&gt;
* Adding your own [[adding initial data|initial data]]&lt;br /&gt;
* Adding a [[adding a test case|test case]]&lt;br /&gt;
* CCE [http://ccrg.rit.edu/~yosef/cce.html tutorial]&lt;br /&gt;
* [[Working with git]]&lt;br /&gt;
* [[FAQ]]&lt;br /&gt;
&lt;br /&gt;
==Regression Test Results==&lt;br /&gt;
You can run regression tests with the command&lt;br /&gt;
 ./simfactory/bin/sim testsuite&lt;br /&gt;
&lt;br /&gt;
Results from automated tests are available at http://damiana2.aei.mpg.de/~ianhin/testreports/EinsteinToolkitTests/results.xml .&lt;br /&gt;
&lt;br /&gt;
==Projects==&lt;br /&gt;
&lt;br /&gt;
* [[Adding requirements to the Cactus scheduler]]&lt;br /&gt;
* [[Visualization of simulation results]]&lt;br /&gt;
* [[Automated testing]]&lt;br /&gt;
* [[Vectorisation]] Improving code performance by using the CPU&amp;#039;s vector instructions&lt;br /&gt;
* [[Padding]] Improving code performance by optimizing cache access&lt;br /&gt;
* [[Making Cactus Installable]] like any other Ubuntu package&lt;br /&gt;
* [[Test suite results are unwieldy]]&lt;br /&gt;
* [[Summer student projects]]&lt;br /&gt;
&lt;br /&gt;
==Maintainers==&lt;br /&gt;
&lt;br /&gt;
* [[Organization and Responsibilities]]&lt;br /&gt;
* [[How to Review a Patch]]&lt;br /&gt;
* [[Preparing a Patch for Review]]&lt;br /&gt;
* [[Release Details]]&lt;br /&gt;
* [[Release Process]]&lt;br /&gt;
* [http://einsteintoolkit.org/release-info/parse_testsuite_results.php Release Testsuite Status], [http://damiana2.aei.mpg.de/~ianhin/testsuites/einsteintoolkit/ Trunk Testsuite Status]&lt;br /&gt;
* [[Standard Emails]]&lt;br /&gt;
* [[MHD implementation details and discussions]]&lt;br /&gt;
* [[Carpet Wish List]]&lt;br /&gt;
* [[Editing the website]]&lt;br /&gt;
* [[Usage poll]]&lt;br /&gt;
&lt;br /&gt;
== Getting Started with Wikis ==&lt;br /&gt;
&lt;br /&gt;
* Consult the [http://meta.wikimedia.org/wiki/Help:Contents User&amp;#039;s Guide] for information on using the wiki software.&lt;br /&gt;
* [http://www.mediawiki.org/wiki/Help:Configuration_settings Configuration settings list]&lt;br /&gt;
* [http://www.mediawiki.org/wiki/Help:FAQ MediaWiki FAQ]&lt;br /&gt;
* [http://mail.wikimedia.org/mailman/listinfo/mediawiki-announce MediaWiki release mailing list]&lt;/div&gt;</summary>
		<author><name>Bmundim</name></author>
		
	</entry>
	<entry>
		<id>https://docs.einsteintoolkit.org/et-docs/index.php?title=ET_Workshop_Spring_2012&amp;diff=3178</id>
		<title>ET Workshop Spring 2012</title>
		<link rel="alternate" type="text/html" href="https://docs.einsteintoolkit.org/et-docs/index.php?title=ET_Workshop_Spring_2012&amp;diff=3178"/>
		<updated>2012-04-05T10:15:34Z</updated>

		<summary type="html">&lt;p&gt;Bmundim: /* Schedule */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Spring Einstein Toolkit Workshop 2012 ==&lt;br /&gt;
&lt;br /&gt;
We prepared a [https://svn.einsteintoolkit.org/documents/Workshop_Spring_2012/flyer/etk2.pdf flyer], which can be printed or otherwise&lt;br /&gt;
distributed.&lt;br /&gt;
&lt;br /&gt;
=== Announcement ===&lt;br /&gt;
The Einstein Toolkit (http://einsteintoolkit.org) will host its spring workshop 2012 following the April APS meeting in Atlanta, GA,&lt;br /&gt;
from Tuesday, April 3rd 4pm to Friday April 6th noon.&lt;br /&gt;
&lt;br /&gt;
This workshop is targeted at new and potential new users of the relativity infrastructure. It will provide a general introductions&lt;br /&gt;
into numerical relativity (although some previous knowledge would be beneficial) and in code development within large collaborations.&lt;br /&gt;
Hands-on sessions will help to familiarize attendees with the Einstein Toolkit. Participants are asked to bring their own laptops.&lt;br /&gt;
We would like to invite especially students from physics and computer science to participate.&lt;br /&gt;
&lt;br /&gt;
The number of attendees is limited, and while registration is free, it is required. We anticipate to be able to support a small&lt;br /&gt;
number of participants financially, by covering parts/all of their travel, hotel and meal cost. Preference will be given to students.&lt;br /&gt;
&lt;br /&gt;
In order to register, write an email to workshop@einsteintoolkit.org, specify:&lt;br /&gt;
* your name, affiliation and title&lt;br /&gt;
* your estimated arrival and departure time/date&lt;br /&gt;
* whether you apply for support (and if so, state if you are undergraduate / graduate student / postdoc)&lt;br /&gt;
* your special needs&lt;br /&gt;
&lt;br /&gt;
Detailed workshop information can be found at https://docs.einsteintoolkit.org/et-docs/ET_Workshop_Spring_2012.&lt;br /&gt;
&lt;br /&gt;
The Einstein Toolkit Consortium.&lt;br /&gt;
&lt;br /&gt;
=== Spacetime Coordinates and Contact Information ===&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot; border=&amp;quot;1&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
! Dates&lt;br /&gt;
| &amp;#039;&amp;#039;&amp;#039;Tues, 3. April @ 4pm -- Fri, 6. April @ noon&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
|-&lt;br /&gt;
! Location&lt;br /&gt;
| Room 319, Georgia Tech Student Center, Georgia Tech, Atlanta&lt;br /&gt;
|-&lt;br /&gt;
! Contacts&lt;br /&gt;
| Workshop email list: &amp;#039;&amp;#039;&amp;#039;workshop@einsteintoolkit.org&amp;#039;&amp;#039;&amp;#039;, emergencies: Frank Löffler (knarf@cct.lsu.edu, +1-225-202-1752) or Tanja Bode (tanja.bode@physics.gatech.edu, +1-814-360-2715)&lt;br /&gt;
|-&lt;br /&gt;
! Hotel&lt;br /&gt;
| A small block of rooms was reserved at the [http://hamptoninn.hilton.com/en/hp/groups/personalized/A/ATLGTHX-ETW-20120403/index.jhtml?WT.mc_id=POG Hampton Inn Atlanta - Georgia Tech], 244 North Ave NW (404-881-0881).  The group rate was &amp;#039;&amp;#039;&amp;#039;$117 per night plus tax (appr. 16%, resulting in a ~$136 rate)&amp;#039;&amp;#039;&amp;#039; and included a hot breakfast and high speed wireless access.  A [http://hamptoninn.hilton.com/en/hp/groups/personalized/A/ATLGTHX-ETW-20120403/index.jhtml?WT.mc_id=POG group web page] was available to book online, or you could reserve by phone at 404-881-0881 and ask for the &amp;#039;&amp;#039;&amp;#039;&amp;quot;Einstein Toolkit Workshop&amp;quot; rate&amp;#039;&amp;#039;&amp;#039;.  Attendees had until &amp;#039;&amp;#039;&amp;#039;20. March&amp;#039;&amp;#039;&amp;#039; to reserve.&lt;br /&gt;
&lt;br /&gt;
In addition, a small block of rooms were reserved at the [http://www.hotelmidtownatlanta.com Hotel Midtown Atlanta].  The group rate was &amp;#039;&amp;#039;&amp;#039;$89 per night&amp;#039;&amp;#039;&amp;#039; for single occupancy, including breakfast and high-speed internet.  For an additional person, add $10 (to cover breakfast costs).  Though less convenient to either the APS meeting or this workshop, both can be conveniently reached by transit from the Midtown MARTA station a block away. Reservations at this rate could be done by phone only at 404-873-4800. The block of rooms was released on &amp;#039;&amp;#039;&amp;#039;26. March&amp;#039;&amp;#039;&amp;#039;.&lt;br /&gt;
|-&lt;br /&gt;
! Transportation - Hotel&lt;br /&gt;
| The best way to get to the hotels from the airport (or elsewhere) is by taking [http://itsmarta.com MARTA]&amp;#039;s red or gold rail line, which costs $2.50 one-way.  The Hotel Midtown Atlanta is a block away from Midtown station.  For the Hampton Inn, get off at the North Avenue station. It should take approximately 20 minutes to either station.  From North Ave station, walk west for ~0.5 miles or transfer to MARTA bus route 26 to the stop immediately in front of the Hampton Inn.&lt;br /&gt;
|-&lt;br /&gt;
! Transportation - Workshop&lt;br /&gt;
| The student center is a 5-minute (~1/3 mile) walk [http://g.co/maps/hdjbt] from Hampton Inn.  From the Hotel Midtown Atlanta, Georgia Tech campus (specifically the student center) can be easily reached by taking the [http://pts.gatech.edu/ride/routes_schedules/Pages/TechTrolley.aspx Georgia Tech Trolley] (free) from the Midtown MARTA station to its end station.&lt;br /&gt;
|-&lt;br /&gt;
! Transportation - From the APS (Hyatt)&lt;br /&gt;
| The Workshop is a 1.5 mile walk from the Hyatt where the APS is taking place.  The most convenient way to reach the Workshop location on Tuesday is to take [http://itsmarta.com/1-w.aspx MARTA Bus Route 1] from Spring St [http://g.co/maps/jpf3h] (a block away from the Hyatt) directly to the workshop hotel.&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
== Participant List ==&lt;br /&gt;
&lt;br /&gt;
Below are the ET volunteers who will be presenting or heading parts of the sessions.&lt;br /&gt;
&lt;br /&gt;
{|class=&amp;quot;wikitable&amp;quot; border=&amp;quot;2&amp;quot; cellpadding=&amp;quot;2&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
! Name&lt;br /&gt;
! Affiliation&lt;br /&gt;
|- style=&amp;quot;background:lightgrey;&amp;quot;&lt;br /&gt;
| Tanja Bode || Georgia Tech&lt;br /&gt;
|-&lt;br /&gt;
| Dennis Castleberry || Louisiana State University&lt;br /&gt;
|- style=&amp;quot;background:lightgrey;&amp;quot;&lt;br /&gt;
| Peter Diener || Louisiana State University&lt;br /&gt;
|-&lt;br /&gt;
| Josh Faber || Rochester Institute of Technology&lt;br /&gt;
|- style=&amp;quot;background:lightgrey;&amp;quot;&lt;br /&gt;
| Roland Haas || Caltech&lt;br /&gt;
|-&lt;br /&gt;
| Frank Löffler || Louisiana State University&lt;br /&gt;
|- style=&amp;quot;background:lightgrey;&amp;quot;&lt;br /&gt;
| Bruno Mundim || Rochester Institute of Technology&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
The current participant list as of 4. April 2012 follows, in alphabetical order.&lt;br /&gt;
Please indicate whether you have already arranged for lodgings so that others looking for hotel roommates &lt;br /&gt;
may most easily find them.  This page is editable in general (though IPs are logged), so please manage your own &lt;br /&gt;
lodging status.&lt;br /&gt;
&lt;br /&gt;
{|class=&amp;quot;wikitable&amp;quot; border=&amp;quot;2&amp;quot; cellpadding=&amp;quot;2&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
! Name&lt;br /&gt;
! Affiliation&lt;br /&gt;
|- style=&amp;quot;background:lightgrey;&amp;quot;&lt;br /&gt;
| Majd Abdelqader || Queens University&lt;br /&gt;
|-&lt;br /&gt;
| Rafael Aranha || Georgia Tech&lt;br /&gt;
|- style=&amp;quot;background:lightgrey;&amp;quot;&lt;br /&gt;
| Grayson Carroll || Belmont University&lt;br /&gt;
|-&lt;br /&gt;
| Roseanne Cheng || UNC-Chapel Hill&lt;br /&gt;
|- style=&amp;quot;background:lightgrey;&amp;quot;&lt;br /&gt;
| Michael Clark || Georgia Tech&lt;br /&gt;
|-&lt;br /&gt;
| Brett Deaton || Washington University&lt;br /&gt;
|- style=&amp;quot;background:lightgrey;&amp;quot;&lt;br /&gt;
| Tehani K. Finch || Howard University&lt;br /&gt;
|- &lt;br /&gt;
| Gary Forrester || University of Massachusetts at Dartmouth&lt;br /&gt;
|- style=&amp;quot;background:lightgrey;&amp;quot;&lt;br /&gt;
| Brian Friesen || University of Oklahoma&lt;br /&gt;
|- &lt;br /&gt;
| Rita Garrido || Georgia Tech&lt;br /&gt;
|- style=&amp;quot;background:lightgrey;&amp;quot;&lt;br /&gt;
| Joshua Harris || Louisiana State University&lt;br /&gt;
|- &lt;br /&gt;
| Scott Hawley || Belmont University&lt;br /&gt;
|- style=&amp;quot;background:lightgrey;&amp;quot;&lt;br /&gt;
| Matt Kinsey || Georgia Tech&lt;br /&gt;
|- &lt;br /&gt;
| Jussara Marandola Kofuji || Georgia Tech&lt;br /&gt;
|- style=&amp;quot;background:lightgrey;&amp;quot;&lt;br /&gt;
| Kostas Kokkotas || Universität Tübingen&lt;br /&gt;
|- &lt;br /&gt;
| Hari Krishnan || Louisiana State University&lt;br /&gt;
|- style=&amp;quot;background:lightgrey;&amp;quot;&lt;br /&gt;
| Sean McWilliams || Princeton&lt;br /&gt;
|- &lt;br /&gt;
| Philipp Moesta || Caltech&lt;br /&gt;
|- style=&amp;quot;background:lightgrey;&amp;quot;&lt;br /&gt;
| Tuan Anh Nguyen || Georgia Tech&lt;br /&gt;
|- &lt;br /&gt;
| Prabath Peiris || Rochester Institute of Technology&lt;br /&gt;
|- style=&amp;quot;background:lightgrey;&amp;quot;&lt;br /&gt;
| Larne Pekowsky || Georgia Tech&lt;br /&gt;
|- &lt;br /&gt;
| Prayash Sharma Pyakurel || Truman State University&lt;br /&gt;
|- style=&amp;quot;background:lightgrey;&amp;quot;&lt;br /&gt;
| Christian Reisswig || Caltech&lt;br /&gt;
|- &lt;br /&gt;
| Ian Ruchlin || Rochester Institute of Technology&lt;br /&gt;
|- style=&amp;quot;background:lightgrey;&amp;quot;&lt;br /&gt;
| Carl Rodriguez || Northwestern University&lt;br /&gt;
|- &lt;br /&gt;
| Chao Shi || Georgia Tech&lt;br /&gt;
|- style=&amp;quot;background:lightgrey;&amp;quot;&lt;br /&gt;
| Cody Simmons || North Carolina State University&lt;br /&gt;
|- &lt;br /&gt;
| Magda Slawinska || Georgia Tech&lt;br /&gt;
|- style=&amp;quot;background:lightgrey;&amp;quot;&lt;br /&gt;
| Petr Tsatsin || Florida Atlantic University&lt;br /&gt;
|- &lt;br /&gt;
| Alex Vañô Viñuales || University of the Balearic Islands&lt;br /&gt;
|- style=&amp;quot;background:lightgrey;&amp;quot;&lt;br /&gt;
| Andrew Vu || Emory University&lt;br /&gt;
|- &lt;br /&gt;
| Konstantin Yakunin || Florida Atlantic University / ORNL&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
== In-Workshop Details ==&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
 &lt;br /&gt;
=== Schedule ===&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot; border=&amp;quot;1&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
| Day&lt;br /&gt;
| Time&lt;br /&gt;
| Activity&lt;br /&gt;
| Presenter / Responsible&lt;br /&gt;
|-&lt;br /&gt;
| Tue&lt;br /&gt;
| 16:00-17:30&lt;br /&gt;
| Setup for early birds&lt;br /&gt;
| Tanja Bode, Roland Haas, Frank Löffler&lt;br /&gt;
|-&lt;br /&gt;
| Wed&lt;br /&gt;
| 08:00-08:30&lt;br /&gt;
| Setup for late birds&lt;br /&gt;
| Tanja Bode, Roland Haas, Frank Löffler&lt;br /&gt;
|-&lt;br /&gt;
| Wed&lt;br /&gt;
| 08:30-09:00&lt;br /&gt;
| Opening, Introduction ([https://svn.einsteintoolkit.org/documents/Workshop_Spring_2012/introduction/introduction.pdf slides])&lt;br /&gt;
| Frank Löffler&lt;br /&gt;
|-&lt;br /&gt;
| Wed&lt;br /&gt;
| 09:00-09:30&lt;br /&gt;
| Introduction to Scientific Software &amp;amp; HPC ([https://svn.einsteintoolkit.org/documents/Workshop_Spring_2012/hpc_intro/hpc_intro.pdf slides])&lt;br /&gt;
| Frank Löffler&lt;br /&gt;
|-&lt;br /&gt;
| Wed&lt;br /&gt;
| 09:30-10:00&lt;br /&gt;
| Introduction to Cactus (high-level) ([https://svn.einsteintoolkit.org/documents/Workshop_Spring_2012/cactus_intro/cactus_intro.pdf slides])&lt;br /&gt;
| Frank Löffler&lt;br /&gt;
|-&lt;br /&gt;
| Wed&lt;br /&gt;
| 10:00-10:30&lt;br /&gt;
| Discussion and break&lt;br /&gt;
|-&lt;br /&gt;
| Wed&lt;br /&gt;
| 10:30-11:15&lt;br /&gt;
| [[Introduction to General Relativity]] ([https://svn.einsteintoolkit.org/documents/Workshop_Spring_2012/genrel/genrel.pdf slides])&lt;br /&gt;
| Joshua Faber&lt;br /&gt;
|-&lt;br /&gt;
| Wed&lt;br /&gt;
| 11:15-12:00&lt;br /&gt;
| [[Introduction on Cactus Thorn-Writing (lower level)]] ([https://svn.einsteintoolkit.org/documents/Workshop_Spring_2012/cactuswriting/cactuswriting.pdf slides])&lt;br /&gt;
| Joshua Faber&lt;br /&gt;
|-&lt;br /&gt;
| Wed&lt;br /&gt;
| 12:00-13:00&lt;br /&gt;
| Lunch break&lt;br /&gt;
|-&lt;br /&gt;
| Wed&lt;br /&gt;
| 13:00-13:30&lt;br /&gt;
| Introduction to Workshop development environment&lt;br /&gt;
| Dennis Castleberry&lt;br /&gt;
|-&lt;br /&gt;
| Wed&lt;br /&gt;
| 13:30-14:15&lt;br /&gt;
| Hands-on, provided Wave-Equation example within Cactus ([https://svn.einsteintoolkit.org/documents/Workshop_Spring_2012/example_wavetoy/example_wavetoy.pdf slides])&lt;br /&gt;
| Roland Haas&lt;br /&gt;
|-&lt;br /&gt;
| Wed&lt;br /&gt;
| 14:15-15:15&lt;br /&gt;
| [[Introduction numerical methods &amp;amp; numerical Relativity]] ([https://docs.einsteintoolkit.org/et-docs/images/e/eb/Numerical_relativity.pdf slides])&lt;br /&gt;
| Bruno Mundim, Peter Diener&lt;br /&gt;
|-&lt;br /&gt;
| Wed&lt;br /&gt;
| 15:15-15:45&lt;br /&gt;
| Discussion and break&lt;br /&gt;
|-&lt;br /&gt;
| Wed&lt;br /&gt;
| 15:45-17:30&lt;br /&gt;
| Running and extending (par-file) of two provided examples: perturbed, [https://docs.einsteintoolkit.org/et-docs/images/6/69/Onepuncture.par single BH], and perturbed, single TOV star &amp;lt;!--([ slides])--&amp;gt;&lt;br /&gt;
| Frank Löffler, Bruno Mundim&lt;br /&gt;
|-&lt;br /&gt;
| Thu&lt;br /&gt;
| 08:00-09:00&lt;br /&gt;
| Introduction in Scientific visualization - a bit of theory and a lot of practice ([https://svn.einsteintoolkit.org/documents/Workshop_Spring_2012/scientific_viz/scientific_viz.pdf slides])&lt;br /&gt;
| Tanja Bode&lt;br /&gt;
|-&lt;br /&gt;
| Thu&lt;br /&gt;
| 09:00-10:00&lt;br /&gt;
| Invited Talk I -- Matt Duez, Washington University: [https://svn.einsteintoolkit.org/documents/Workshop_Spring_2012/Matt_Duez_InterpretingDataPresentationSlides.pdf The Challenge of interpreting data in numerical relativity]&lt;br /&gt;
|-&lt;br /&gt;
| Thu&lt;br /&gt;
| 10:00-10:30&lt;br /&gt;
| Discussion and break&lt;br /&gt;
|-&lt;br /&gt;
| Thu&lt;br /&gt;
| 10:30-11:15&lt;br /&gt;
| Hands-on: Using visualization tools to look at meaningful quantities ( TOV profile evolutions ) ([https://svn.einsteintoolkit.org/documents/Workshop_Spring_2012/handson_sviz/handson_sviz.pdf slides])&lt;br /&gt;
| Tanja Bode&lt;br /&gt;
|-&lt;br /&gt;
| Thu&lt;br /&gt;
| 11:15-12:00&lt;br /&gt;
| Create movie of either BH+GW or TOV oscillations using VisIt ([https://svn.einsteintoolkit.org/documents/Workshop_Spring_2012/handson_viz/handson_viz.pdf slides], [https://svn.einsteintoolkit.org/documents/Workshop_Spring_2012/handson_viz/rho.final.session TOV session file], [http://www.physics.gatech.edu/~rhaas3/Workshop_Spring_2012/rho.rl4.h5.xz TOV data file], [https://svn.einsteintoolkit.org/documents/Workshop_Spring_2012/handson_viz/psi4.volume.session Psi4 session file], [http://www.physics.gatech.edu/~rhaas3/Workshop_Spring_2012/psir.h5.xz Psi4 data file])&lt;br /&gt;
| Roland Haas&lt;br /&gt;
|-&lt;br /&gt;
| Thu&lt;br /&gt;
| 12:00-13:00&lt;br /&gt;
| Lunch&lt;br /&gt;
|-&lt;br /&gt;
| Thu&lt;br /&gt;
| 13:00-14:15&lt;br /&gt;
| Hands-on: Implement your own thorn (neutron star tracking), and visualize it, in teams of about 5 people ([https://svn.einsteintoolkit.org/documents/Workshop_Spring_2012/handson_analysis/handson_analysis.pdf slides]), more information at end of wiki&lt;br /&gt;
| Roland Haas&lt;br /&gt;
|-&lt;br /&gt;
| Thu&lt;br /&gt;
| 14:15-15:15&lt;br /&gt;
| Invited Talk II -- John Wise, Georgia Tech&lt;br /&gt;
|-&lt;br /&gt;
| Thu&lt;br /&gt;
| 15:15-15:45&lt;br /&gt;
| Discussion and break&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
| Thu&lt;br /&gt;
| 15:45-17:30&lt;br /&gt;
| Hands-on: continuation&lt;br /&gt;
| Roland Haas&lt;br /&gt;
|-&lt;br /&gt;
| Fri&lt;br /&gt;
| 08:00-09:00&lt;br /&gt;
| Presentation of visualization of result of previous session, 6 teams: 8 min each&lt;br /&gt;
| Frank Löffler&lt;br /&gt;
|-&lt;br /&gt;
| Fri&lt;br /&gt;
| 09:00-10:00&lt;br /&gt;
| Invited talk III -- Gabrielle Allen, LSU&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
| Fri&lt;br /&gt;
| 10:00-10:30&lt;br /&gt;
| Discussion and break&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
| Fri&lt;br /&gt;
| 10:30-11:00&lt;br /&gt;
| Tour through available ET components&lt;br /&gt;
| Peter Diener&lt;br /&gt;
|-&lt;br /&gt;
| Fri&lt;br /&gt;
| 11:00-11:30&lt;br /&gt;
| Overview over supercomputing resources, introduction on how to get accounts / allocations, trends in HPC, reminder how to get ET help in the future&lt;br /&gt;
| Joshua Faber, Peter Diener&lt;br /&gt;
|-&lt;br /&gt;
| Fri&lt;br /&gt;
| 11:30-12:00&lt;br /&gt;
| The future of the ET: everything we didn&amp;#039;t talk about (EOSs, refluxing, multiblock, MHD, radiation ect.)&lt;br /&gt;
| Frank Löffler&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
=== Setup ===&lt;br /&gt;
* Wireless access is through the GTVisitor network. &amp;#039;&amp;#039;&amp;#039;One&amp;#039;&amp;#039;&amp;#039; account per person, please. It will work on multiple devices simultaneously.&lt;br /&gt;
* The virtual machine for the workshop is [http://cct.lsu.edu/~dcastl2/] and will run in [http://virtualbox.org virtualbox]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Area Details ==&lt;br /&gt;
&lt;br /&gt;
* For on-campus directions please consult the link of a detailed &amp;#039;&amp;#039;&amp;#039;map of the Georgia Tech Campus&amp;#039;&amp;#039;&amp;#039;: [http://map.gtalumni.org/]&lt;br /&gt;
* For directions of Midtown and Downtown Atlanta follow the link [http://www.atlantadowntown.com/guide]&lt;br /&gt;
&lt;br /&gt;
=== Restaurants ===&lt;br /&gt;
&amp;#039;&amp;#039;&amp;#039;Places to Eat On-Campus:&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
&amp;#039;&amp;#039;&amp;#039;Technology Square&amp;#039;&amp;#039;&amp;#039;, located on 5th Street and Spring Street, has a variety of good and cheap restaurants including:&lt;br /&gt;
* Tin Drum Asia Cafe &lt;br /&gt;
* Ray&amp;#039;s New York Pizza&lt;br /&gt;
* Chuck&amp;#039;s Famous&lt;br /&gt;
* Barrelhouse&lt;br /&gt;
* 5th Street Ribs n&amp;#039; Blues&lt;br /&gt;
* Umma&amp;#039;s House Restaurant and Cafe&lt;br /&gt;
* Waffle House&lt;br /&gt;
* Moe&amp;#039;s Southwest Grill&lt;br /&gt;
* St. Charles Deli&lt;br /&gt;
The &amp;#039;&amp;#039;&amp;#039;Student Center&amp;#039;&amp;#039;&amp;#039; [http://www.studentcenter.gatech.edu] has:&lt;br /&gt;
* Chick-fil-a&lt;br /&gt;
* Taco Bell&lt;br /&gt;
* Subway&lt;br /&gt;
* A pub style at Jackets&lt;br /&gt;
* Einstein&amp;#039;s Bagels&lt;br /&gt;
* Ferst Place (Located on the 3rd floor)&lt;br /&gt;
* Ferst Food Court (Located on the 2nd floor)&lt;br /&gt;
&lt;br /&gt;
&amp;#039;&amp;#039;&amp;#039;Places to Eat Off-campus :&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
* Varsity (American)&lt;br /&gt;
: 61 North Ave. NW&lt;br /&gt;
* Goodfellas (American)&lt;br /&gt;
: 615 Spring Street&lt;br /&gt;
* The Real Chow Baby (American Stir Fry)&lt;br /&gt;
: 1016 Howell Mill Road&lt;br /&gt;
* Zen on Ten Asian Bistro (Sushi)&lt;br /&gt;
:1000 Northside Dr. NW&lt;br /&gt;
* Spoon (Thai)&lt;br /&gt;
: 768 Marietta Street&lt;br /&gt;
* The Vortex (American)&lt;br /&gt;
: 878 Peachtree Street NE&lt;br /&gt;
* Taco Mac (American)&lt;br /&gt;
: 933 Peachtree St NE&lt;br /&gt;
* La Fonda Latina (Mexican)&lt;br /&gt;
: 1025 Howell Mill Road&lt;br /&gt;
* Prickly Pear (Mexican)&lt;br /&gt;
: 950 West Peachtree St NE&lt;br /&gt;
* TheTenth Thai&lt;br /&gt;
: 132 10th Street Northeast (Thai)&lt;br /&gt;
&lt;br /&gt;
=== Miscellaneous ===&lt;br /&gt;
* Publix at The Plaza Midtown (Supermarket)&lt;br /&gt;
: 950 W Peachtree St NW &lt;br /&gt;
* Midtown Market (Sundries)&lt;br /&gt;
: 225 10th St NE&lt;br /&gt;
* Walmart Supercenter (Supermarket)&lt;br /&gt;
: 1801 Howell Mill Rd Nw&lt;br /&gt;
* Walgreens (Pharmacy)&lt;br /&gt;
: 595 Piedmont Ave., Ste. 100&lt;br /&gt;
* CVS (Pharmacy)&lt;br /&gt;
: 842 Peachtree Street NE&lt;br /&gt;
&lt;br /&gt;
=== Entertainment ===&lt;br /&gt;
* Manuel&amp;#039;s Tavern [http://www.manuelstavern.com/] (also the site of Astrophysics unplugged)&lt;br /&gt;
* Blind Willie&amp;#039;s [http://www.blindwilliesblues.com/]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==Hands on material==&lt;br /&gt;
===WaveToy===&lt;br /&gt;
The source code for the example thorn and the slides is available at&lt;br /&gt;
via&lt;br /&gt;
  cd $HOME&lt;br /&gt;
  ./GetComponents -a https://svn.einsteintoolkit.org/documents/Workshop_Spring_2012/example_wavetoy/Cactus/misc/WaveToy.th&lt;br /&gt;
  cd Cactus&lt;br /&gt;
  echo &amp;#039;Introduction/WaveToy&amp;#039; &amp;gt;&amp;gt;configs/sim/ThornList&lt;br /&gt;
  simfactory/bin/sim build&lt;br /&gt;
Once built, you can run this in one line via simfactory&lt;br /&gt;
  simfactory/bin/sim create-run wavetoy --parfile wavetoy-misc/WaveToy.par&lt;br /&gt;
===Static TOV===&lt;br /&gt;
Edit par/static_tov.par as Frank indicated and save as $HOME/Cactus/fast_tov.par&lt;br /&gt;
&lt;br /&gt;
To run enter:&lt;br /&gt;
  cd $HOME/Cactus&lt;br /&gt;
  exe/cactus_sim fast_tov.par&lt;br /&gt;
&lt;br /&gt;
===Visualization, Hands-on I===&lt;br /&gt;
&lt;br /&gt;
Download the slides and some extra sample data via&lt;br /&gt;
  cd $HOME&lt;br /&gt;
  svn co https://svn.einsteintoolkit.org/documents/Workshop_Spring_2012/handson_sviz .&lt;br /&gt;
Make sure you have 3d data!  If not, add these lines to your tov parameter file and rerun for a bit:&lt;br /&gt;
  CarpetIOHDF5::out3d_every = 1&lt;br /&gt;
  CarpetIOHDF5::out3d_vars = &amp;quot; HydroBase::rho &amp;quot;&lt;br /&gt;
These give data under the file name &amp;#039;&amp;#039;rho.xyz.h5&amp;#039;&amp;#039;. Alternatively, add the following parameters&lt;br /&gt;
  CarpetIOHDF5::out_every = 1&lt;br /&gt;
  CarpetIOHDF5::out_vars = &amp;quot;HydroBase::rho&amp;quot;&lt;br /&gt;
which give data under the file &amp;#039;&amp;#039;rho.h5&amp;#039;&amp;#039;. Either way works fine. We will assume the latter for the moment.&lt;br /&gt;
&lt;br /&gt;
Follow the directions on the first slides to create a plot of how the evolving TOV differs from its initial state.&lt;br /&gt;
&lt;br /&gt;
Other suggestions for visualization tasks are contained in the slides.&lt;/div&gt;</summary>
		<author><name>Bmundim</name></author>
		
	</entry>
	<entry>
		<id>https://docs.einsteintoolkit.org/et-docs/index.php?title=File:Numerical_relativity.pdf&amp;diff=3177</id>
		<title>File:Numerical relativity.pdf</title>
		<link rel="alternate" type="text/html" href="https://docs.einsteintoolkit.org/et-docs/index.php?title=File:Numerical_relativity.pdf&amp;diff=3177"/>
		<updated>2012-04-05T10:14:25Z</updated>

		<summary type="html">&lt;p&gt;Bmundim: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;/div&gt;</summary>
		<author><name>Bmundim</name></author>
		
	</entry>
	<entry>
		<id>https://docs.einsteintoolkit.org/et-docs/index.php?title=ET_Workshop_Spring_2012&amp;diff=3176</id>
		<title>ET Workshop Spring 2012</title>
		<link rel="alternate" type="text/html" href="https://docs.einsteintoolkit.org/et-docs/index.php?title=ET_Workshop_Spring_2012&amp;diff=3176"/>
		<updated>2012-04-05T10:13:02Z</updated>

		<summary type="html">&lt;p&gt;Bmundim: /* Schedule */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Spring Einstein Toolkit Workshop 2012 ==&lt;br /&gt;
&lt;br /&gt;
We prepared a [https://svn.einsteintoolkit.org/documents/Workshop_Spring_2012/flyer/etk2.pdf flyer], which can be printed or otherwise&lt;br /&gt;
distributed.&lt;br /&gt;
&lt;br /&gt;
=== Announcement ===&lt;br /&gt;
The Einstein Toolkit (http://einsteintoolkit.org) will host its spring workshop 2012 following the April APS meeting in Atlanta, GA,&lt;br /&gt;
from Tuesday, April 3rd 4pm to Friday April 6th noon.&lt;br /&gt;
&lt;br /&gt;
This workshop is targeted at new and potential new users of the relativity infrastructure. It will provide a general introductions&lt;br /&gt;
into numerical relativity (although some previous knowledge would be beneficial) and in code development within large collaborations.&lt;br /&gt;
Hands-on sessions will help to familiarize attendees with the Einstein Toolkit. Participants are asked to bring their own laptops.&lt;br /&gt;
We would like to invite especially students from physics and computer science to participate.&lt;br /&gt;
&lt;br /&gt;
The number of attendees is limited, and while registration is free, it is required. We anticipate to be able to support a small&lt;br /&gt;
number of participants financially, by covering parts/all of their travel, hotel and meal cost. Preference will be given to students.&lt;br /&gt;
&lt;br /&gt;
In order to register, write an email to workshop@einsteintoolkit.org, specify:&lt;br /&gt;
* your name, affiliation and title&lt;br /&gt;
* your estimated arrival and departure time/date&lt;br /&gt;
* whether you apply for support (and if so, state if you are undergraduate / graduate student / postdoc)&lt;br /&gt;
* your special needs&lt;br /&gt;
&lt;br /&gt;
Detailed workshop information can be found at https://docs.einsteintoolkit.org/et-docs/ET_Workshop_Spring_2012.&lt;br /&gt;
&lt;br /&gt;
The Einstein Toolkit Consortium.&lt;br /&gt;
&lt;br /&gt;
=== Spacetime Coordinates and Contact Information ===&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot; border=&amp;quot;1&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
! Dates&lt;br /&gt;
| &amp;#039;&amp;#039;&amp;#039;Tues, 3. April @ 4pm -- Fri, 6. April @ noon&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
|-&lt;br /&gt;
! Location&lt;br /&gt;
| Room 319, Georgia Tech Student Center, Georgia Tech, Atlanta&lt;br /&gt;
|-&lt;br /&gt;
! Contacts&lt;br /&gt;
| Workshop email list: &amp;#039;&amp;#039;&amp;#039;workshop@einsteintoolkit.org&amp;#039;&amp;#039;&amp;#039;, emergencies: Frank Löffler (knarf@cct.lsu.edu, +1-225-202-1752) or Tanja Bode (tanja.bode@physics.gatech.edu, +1-814-360-2715)&lt;br /&gt;
|-&lt;br /&gt;
! Hotel&lt;br /&gt;
| A small block of rooms was reserved at the [http://hamptoninn.hilton.com/en/hp/groups/personalized/A/ATLGTHX-ETW-20120403/index.jhtml?WT.mc_id=POG Hampton Inn Atlanta - Georgia Tech], 244 North Ave NW (404-881-0881).  The group rate was &amp;#039;&amp;#039;&amp;#039;$117 per night plus tax (appr. 16%, resulting in a ~$136 rate)&amp;#039;&amp;#039;&amp;#039; and included a hot breakfast and high speed wireless access.  A [http://hamptoninn.hilton.com/en/hp/groups/personalized/A/ATLGTHX-ETW-20120403/index.jhtml?WT.mc_id=POG group web page] was available to book online, or you could reserve by phone at 404-881-0881 and ask for the &amp;#039;&amp;#039;&amp;#039;&amp;quot;Einstein Toolkit Workshop&amp;quot; rate&amp;#039;&amp;#039;&amp;#039;.  Attendees had until &amp;#039;&amp;#039;&amp;#039;20. March&amp;#039;&amp;#039;&amp;#039; to reserve.&lt;br /&gt;
&lt;br /&gt;
In addition, a small block of rooms were reserved at the [http://www.hotelmidtownatlanta.com Hotel Midtown Atlanta].  The group rate was &amp;#039;&amp;#039;&amp;#039;$89 per night&amp;#039;&amp;#039;&amp;#039; for single occupancy, including breakfast and high-speed internet.  For an additional person, add $10 (to cover breakfast costs).  Though less convenient to either the APS meeting or this workshop, both can be conveniently reached by transit from the Midtown MARTA station a block away. Reservations at this rate could be done by phone only at 404-873-4800. The block of rooms was released on &amp;#039;&amp;#039;&amp;#039;26. March&amp;#039;&amp;#039;&amp;#039;.&lt;br /&gt;
|-&lt;br /&gt;
! Transportation - Hotel&lt;br /&gt;
| The best way to get to the hotels from the airport (or elsewhere) is by taking [http://itsmarta.com MARTA]&amp;#039;s red or gold rail line, which costs $2.50 one-way.  The Hotel Midtown Atlanta is a block away from Midtown station.  For the Hampton Inn, get off at the North Avenue station. It should take approximately 20 minutes to either station.  From North Ave station, walk west for ~0.5 miles or transfer to MARTA bus route 26 to the stop immediately in front of the Hampton Inn.&lt;br /&gt;
|-&lt;br /&gt;
! Transportation - Workshop&lt;br /&gt;
| The student center is a 5-minute (~1/3 mile) walk [http://g.co/maps/hdjbt] from Hampton Inn.  From the Hotel Midtown Atlanta, Georgia Tech campus (specifically the student center) can be easily reached by taking the [http://pts.gatech.edu/ride/routes_schedules/Pages/TechTrolley.aspx Georgia Tech Trolley] (free) from the Midtown MARTA station to its end station.&lt;br /&gt;
|-&lt;br /&gt;
! Transportation - From the APS (Hyatt)&lt;br /&gt;
| The Workshop is a 1.5 mile walk from the Hyatt where the APS is taking place.  The most convenient way to reach the Workshop location on Tuesday is to take [http://itsmarta.com/1-w.aspx MARTA Bus Route 1] from Spring St [http://g.co/maps/jpf3h] (a block away from the Hyatt) directly to the workshop hotel.&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
== Participant List ==&lt;br /&gt;
&lt;br /&gt;
Below are the ET volunteers who will be presenting or heading parts of the sessions.&lt;br /&gt;
&lt;br /&gt;
{|class=&amp;quot;wikitable&amp;quot; border=&amp;quot;2&amp;quot; cellpadding=&amp;quot;2&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
! Name&lt;br /&gt;
! Affiliation&lt;br /&gt;
|- style=&amp;quot;background:lightgrey;&amp;quot;&lt;br /&gt;
| Tanja Bode || Georgia Tech&lt;br /&gt;
|-&lt;br /&gt;
| Dennis Castleberry || Louisiana State University&lt;br /&gt;
|- style=&amp;quot;background:lightgrey;&amp;quot;&lt;br /&gt;
| Peter Diener || Louisiana State University&lt;br /&gt;
|-&lt;br /&gt;
| Josh Faber || Rochester Institute of Technology&lt;br /&gt;
|- style=&amp;quot;background:lightgrey;&amp;quot;&lt;br /&gt;
| Roland Haas || Caltech&lt;br /&gt;
|-&lt;br /&gt;
| Frank Löffler || Louisiana State University&lt;br /&gt;
|- style=&amp;quot;background:lightgrey;&amp;quot;&lt;br /&gt;
| Bruno Mundim || Rochester Institute of Technology&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
The current participant list as of 4. April 2012 follows, in alphabetical order.&lt;br /&gt;
Please indicate whether you have already arranged for lodgings so that others looking for hotel roommates &lt;br /&gt;
may most easily find them.  This page is editable in general (though IPs are logged), so please manage your own &lt;br /&gt;
lodging status.&lt;br /&gt;
&lt;br /&gt;
{|class=&amp;quot;wikitable&amp;quot; border=&amp;quot;2&amp;quot; cellpadding=&amp;quot;2&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
! Name&lt;br /&gt;
! Affiliation&lt;br /&gt;
|- style=&amp;quot;background:lightgrey;&amp;quot;&lt;br /&gt;
| Majd Abdelqader || Queens University&lt;br /&gt;
|-&lt;br /&gt;
| Rafael Aranha || Georgia Tech&lt;br /&gt;
|- style=&amp;quot;background:lightgrey;&amp;quot;&lt;br /&gt;
| Grayson Carroll || Belmont University&lt;br /&gt;
|-&lt;br /&gt;
| Roseanne Cheng || UNC-Chapel Hill&lt;br /&gt;
|- style=&amp;quot;background:lightgrey;&amp;quot;&lt;br /&gt;
| Michael Clark || Georgia Tech&lt;br /&gt;
|-&lt;br /&gt;
| Brett Deaton || Washington University&lt;br /&gt;
|- style=&amp;quot;background:lightgrey;&amp;quot;&lt;br /&gt;
| Tehani K. Finch || Howard University&lt;br /&gt;
|- &lt;br /&gt;
| Gary Forrester || University of Massachusetts at Dartmouth&lt;br /&gt;
|- style=&amp;quot;background:lightgrey;&amp;quot;&lt;br /&gt;
| Brian Friesen || University of Oklahoma&lt;br /&gt;
|- &lt;br /&gt;
| Rita Garrido || Georgia Tech&lt;br /&gt;
|- style=&amp;quot;background:lightgrey;&amp;quot;&lt;br /&gt;
| Joshua Harris || Louisiana State University&lt;br /&gt;
|- &lt;br /&gt;
| Scott Hawley || Belmont University&lt;br /&gt;
|- style=&amp;quot;background:lightgrey;&amp;quot;&lt;br /&gt;
| Matt Kinsey || Georgia Tech&lt;br /&gt;
|- &lt;br /&gt;
| Jussara Marandola Kofuji || Georgia Tech&lt;br /&gt;
|- style=&amp;quot;background:lightgrey;&amp;quot;&lt;br /&gt;
| Kostas Kokkotas || Universität Tübingen&lt;br /&gt;
|- &lt;br /&gt;
| Hari Krishnan || Louisiana State University&lt;br /&gt;
|- style=&amp;quot;background:lightgrey;&amp;quot;&lt;br /&gt;
| Sean McWilliams || Princeton&lt;br /&gt;
|- &lt;br /&gt;
| Philipp Moesta || Caltech&lt;br /&gt;
|- style=&amp;quot;background:lightgrey;&amp;quot;&lt;br /&gt;
| Tuan Anh Nguyen || Georgia Tech&lt;br /&gt;
|- &lt;br /&gt;
| Prabath Peiris || Rochester Institute of Technology&lt;br /&gt;
|- style=&amp;quot;background:lightgrey;&amp;quot;&lt;br /&gt;
| Larne Pekowsky || Georgia Tech&lt;br /&gt;
|- &lt;br /&gt;
| Prayash Sharma Pyakurel || Truman State University&lt;br /&gt;
|- style=&amp;quot;background:lightgrey;&amp;quot;&lt;br /&gt;
| Christian Reisswig || Caltech&lt;br /&gt;
|- &lt;br /&gt;
| Ian Ruchlin || Rochester Institute of Technology&lt;br /&gt;
|- style=&amp;quot;background:lightgrey;&amp;quot;&lt;br /&gt;
| Carl Rodriguez || Northwestern University&lt;br /&gt;
|- &lt;br /&gt;
| Chao Shi || Georgia Tech&lt;br /&gt;
|- style=&amp;quot;background:lightgrey;&amp;quot;&lt;br /&gt;
| Cody Simmons || North Carolina State University&lt;br /&gt;
|- &lt;br /&gt;
| Magda Slawinska || Georgia Tech&lt;br /&gt;
|- style=&amp;quot;background:lightgrey;&amp;quot;&lt;br /&gt;
| Petr Tsatsin || Florida Atlantic University&lt;br /&gt;
|- &lt;br /&gt;
| Alex Vañô Viñuales || University of the Balearic Islands&lt;br /&gt;
|- style=&amp;quot;background:lightgrey;&amp;quot;&lt;br /&gt;
| Andrew Vu || Emory University&lt;br /&gt;
|- &lt;br /&gt;
| Konstantin Yakunin || Florida Atlantic University / ORNL&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
== In-Workshop Details ==&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
 &lt;br /&gt;
=== Schedule ===&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot; border=&amp;quot;1&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
| Day&lt;br /&gt;
| Time&lt;br /&gt;
| Activity&lt;br /&gt;
| Presenter / Responsible&lt;br /&gt;
|-&lt;br /&gt;
| Tue&lt;br /&gt;
| 16:00-17:30&lt;br /&gt;
| Setup for early birds&lt;br /&gt;
| Tanja Bode, Roland Haas, Frank Löffler&lt;br /&gt;
|-&lt;br /&gt;
| Wed&lt;br /&gt;
| 08:00-08:30&lt;br /&gt;
| Setup for late birds&lt;br /&gt;
| Tanja Bode, Roland Haas, Frank Löffler&lt;br /&gt;
|-&lt;br /&gt;
| Wed&lt;br /&gt;
| 08:30-09:00&lt;br /&gt;
| Opening, Introduction ([https://svn.einsteintoolkit.org/documents/Workshop_Spring_2012/introduction/introduction.pdf slides])&lt;br /&gt;
| Frank Löffler&lt;br /&gt;
|-&lt;br /&gt;
| Wed&lt;br /&gt;
| 09:00-09:30&lt;br /&gt;
| Introduction to Scientific Software &amp;amp; HPC ([https://svn.einsteintoolkit.org/documents/Workshop_Spring_2012/hpc_intro/hpc_intro.pdf slides])&lt;br /&gt;
| Frank Löffler&lt;br /&gt;
|-&lt;br /&gt;
| Wed&lt;br /&gt;
| 09:30-10:00&lt;br /&gt;
| Introduction to Cactus (high-level) ([https://svn.einsteintoolkit.org/documents/Workshop_Spring_2012/cactus_intro/cactus_intro.pdf slides])&lt;br /&gt;
| Frank Löffler&lt;br /&gt;
|-&lt;br /&gt;
| Wed&lt;br /&gt;
| 10:00-10:30&lt;br /&gt;
| Discussion and break&lt;br /&gt;
|-&lt;br /&gt;
| Wed&lt;br /&gt;
| 10:30-11:15&lt;br /&gt;
| [[Introduction to General Relativity]] ([https://svn.einsteintoolkit.org/documents/Workshop_Spring_2012/genrel/genrel.pdf slides])&lt;br /&gt;
| Joshua Faber&lt;br /&gt;
|-&lt;br /&gt;
| Wed&lt;br /&gt;
| 11:15-12:00&lt;br /&gt;
| [[Introduction on Cactus Thorn-Writing (lower level)]] ([https://svn.einsteintoolkit.org/documents/Workshop_Spring_2012/cactuswriting/cactuswriting.pdf slides])&lt;br /&gt;
| Joshua Faber&lt;br /&gt;
|-&lt;br /&gt;
| Wed&lt;br /&gt;
| 12:00-13:00&lt;br /&gt;
| Lunch break&lt;br /&gt;
|-&lt;br /&gt;
| Wed&lt;br /&gt;
| 13:00-13:30&lt;br /&gt;
| Introduction to Workshop development environment&lt;br /&gt;
| Dennis Castleberry&lt;br /&gt;
|-&lt;br /&gt;
| Wed&lt;br /&gt;
| 13:30-14:15&lt;br /&gt;
| Hands-on, provided Wave-Equation example within Cactus ([https://svn.einsteintoolkit.org/documents/Workshop_Spring_2012/example_wavetoy/example_wavetoy.pdf slides])&lt;br /&gt;
| Roland Haas&lt;br /&gt;
|-&lt;br /&gt;
| Wed&lt;br /&gt;
| 14:15-15:15&lt;br /&gt;
| [[Introduction numerical methods &amp;amp; numerical Relativity]] &amp;lt;!--([ slides])--&amp;gt;&lt;br /&gt;
| Bruno Mundim, Peter Diener&lt;br /&gt;
|-&lt;br /&gt;
| Wed&lt;br /&gt;
| 15:15-15:45&lt;br /&gt;
| Discussion and break&lt;br /&gt;
|-&lt;br /&gt;
| Wed&lt;br /&gt;
| 15:45-17:30&lt;br /&gt;
| Running and extending (par-file) of two provided examples: perturbed, [https://docs.einsteintoolkit.org/et-docs/images/6/69/Onepuncture.par single BH], and perturbed, single TOV star &amp;lt;!--([ slides])--&amp;gt;&lt;br /&gt;
| Frank Löffler, Bruno Mundim&lt;br /&gt;
|-&lt;br /&gt;
| Thu&lt;br /&gt;
| 08:00-09:00&lt;br /&gt;
| Introduction in Scientific visualization - a bit of theory and a lot of practice ([https://svn.einsteintoolkit.org/documents/Workshop_Spring_2012/scientific_viz/scientific_viz.pdf slides])&lt;br /&gt;
| Tanja Bode&lt;br /&gt;
|-&lt;br /&gt;
| Thu&lt;br /&gt;
| 09:00-10:00&lt;br /&gt;
| Invited Talk I -- Matt Duez, Washington University: [https://svn.einsteintoolkit.org/documents/Workshop_Spring_2012/Matt_Duez_InterpretingDataPresentationSlides.pdf The Challenge of interpreting data in numerical relativity]&lt;br /&gt;
|-&lt;br /&gt;
| Thu&lt;br /&gt;
| 10:00-10:30&lt;br /&gt;
| Discussion and break&lt;br /&gt;
|-&lt;br /&gt;
| Thu&lt;br /&gt;
| 10:30-11:15&lt;br /&gt;
| Hands-on: Using visualization tools to look at meaningful quantities ( TOV profile evolutions ) ([https://svn.einsteintoolkit.org/documents/Workshop_Spring_2012/handson_sviz/handson_sviz.pdf slides])&lt;br /&gt;
| Tanja Bode&lt;br /&gt;
|-&lt;br /&gt;
| Thu&lt;br /&gt;
| 11:15-12:00&lt;br /&gt;
| Create movie of either BH+GW or TOV oscillations using VisIt ([https://svn.einsteintoolkit.org/documents/Workshop_Spring_2012/handson_viz/handson_viz.pdf slides], [https://svn.einsteintoolkit.org/documents/Workshop_Spring_2012/handson_viz/rho.final.session TOV session file], [http://www.physics.gatech.edu/~rhaas3/Workshop_Spring_2012/rho.rl4.h5.xz TOV data file], [https://svn.einsteintoolkit.org/documents/Workshop_Spring_2012/handson_viz/psi4.volume.session Psi4 session file], [http://www.physics.gatech.edu/~rhaas3/Workshop_Spring_2012/psir.h5.xz Psi4 data file])&lt;br /&gt;
| Roland Haas&lt;br /&gt;
|-&lt;br /&gt;
| Thu&lt;br /&gt;
| 12:00-13:00&lt;br /&gt;
| Lunch&lt;br /&gt;
|-&lt;br /&gt;
| Thu&lt;br /&gt;
| 13:00-14:15&lt;br /&gt;
| Hands-on: Implement your own thorn (neutron star tracking), and visualize it, in teams of about 5 people ([https://svn.einsteintoolkit.org/documents/Workshop_Spring_2012/handson_analysis/handson_analysis.pdf slides]), more information at end of wiki&lt;br /&gt;
| Roland Haas&lt;br /&gt;
|-&lt;br /&gt;
| Thu&lt;br /&gt;
| 14:15-15:15&lt;br /&gt;
| Invited Talk II -- John Wise, Georgia Tech&lt;br /&gt;
|-&lt;br /&gt;
| Thu&lt;br /&gt;
| 15:15-15:45&lt;br /&gt;
| Discussion and break&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
| Thu&lt;br /&gt;
| 15:45-17:30&lt;br /&gt;
| Hands-on: continuation&lt;br /&gt;
| Roland Haas&lt;br /&gt;
|-&lt;br /&gt;
| Fri&lt;br /&gt;
| 08:00-09:00&lt;br /&gt;
| Presentation of visualization of result of previous session, 6 teams: 8 min each&lt;br /&gt;
| Frank Löffler&lt;br /&gt;
|-&lt;br /&gt;
| Fri&lt;br /&gt;
| 09:00-10:00&lt;br /&gt;
| Invited talk III -- Gabrielle Allen, LSU&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
| Fri&lt;br /&gt;
| 10:00-10:30&lt;br /&gt;
| Discussion and break&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
| Fri&lt;br /&gt;
| 10:30-11:00&lt;br /&gt;
| Tour through available ET components&lt;br /&gt;
| Peter Diener&lt;br /&gt;
|-&lt;br /&gt;
| Fri&lt;br /&gt;
| 11:00-11:30&lt;br /&gt;
| Overview over supercomputing resources, introduction on how to get accounts / allocations, trends in HPC, reminder how to get ET help in the future&lt;br /&gt;
| Joshua Faber, Peter Diener&lt;br /&gt;
|-&lt;br /&gt;
| Fri&lt;br /&gt;
| 11:30-12:00&lt;br /&gt;
| The future of the ET: everything we didn&amp;#039;t talk about (EOSs, refluxing, multiblock, MHD, radiation ect.)&lt;br /&gt;
| Frank Löffler&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
=== Setup ===&lt;br /&gt;
* Wireless access is through the GTVisitor network. &amp;#039;&amp;#039;&amp;#039;One&amp;#039;&amp;#039;&amp;#039; account per person, please. It will work on multiple devices simultaneously.&lt;br /&gt;
* The virtual machine for the workshop is [http://cct.lsu.edu/~dcastl2/] and will run in [http://virtualbox.org virtualbox]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Area Details ==&lt;br /&gt;
&lt;br /&gt;
* For on-campus directions please consult the link of a detailed &amp;#039;&amp;#039;&amp;#039;map of the Georgia Tech Campus&amp;#039;&amp;#039;&amp;#039;: [http://map.gtalumni.org/]&lt;br /&gt;
* For directions of Midtown and Downtown Atlanta follow the link [http://www.atlantadowntown.com/guide]&lt;br /&gt;
&lt;br /&gt;
=== Restaurants ===&lt;br /&gt;
&amp;#039;&amp;#039;&amp;#039;Places to Eat On-Campus:&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
&amp;#039;&amp;#039;&amp;#039;Technology Square&amp;#039;&amp;#039;&amp;#039;, located on 5th Street and Spring Street, has a variety of good and cheap restaurants including:&lt;br /&gt;
* Tin Drum Asia Cafe &lt;br /&gt;
* Ray&amp;#039;s New York Pizza&lt;br /&gt;
* Chuck&amp;#039;s Famous&lt;br /&gt;
* Barrelhouse&lt;br /&gt;
* 5th Street Ribs n&amp;#039; Blues&lt;br /&gt;
* Umma&amp;#039;s House Restaurant and Cafe&lt;br /&gt;
* Waffle House&lt;br /&gt;
* Moe&amp;#039;s Southwest Grill&lt;br /&gt;
* St. Charles Deli&lt;br /&gt;
The &amp;#039;&amp;#039;&amp;#039;Student Center&amp;#039;&amp;#039;&amp;#039; [http://www.studentcenter.gatech.edu] has:&lt;br /&gt;
* Chick-fil-a&lt;br /&gt;
* Taco Bell&lt;br /&gt;
* Subway&lt;br /&gt;
* A pub style at Jackets&lt;br /&gt;
* Einstein&amp;#039;s Bagels&lt;br /&gt;
* Ferst Place (Located on the 3rd floor)&lt;br /&gt;
* Ferst Food Court (Located on the 2nd floor)&lt;br /&gt;
&lt;br /&gt;
&amp;#039;&amp;#039;&amp;#039;Places to Eat Off-campus :&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
* Varsity (American)&lt;br /&gt;
: 61 North Ave. NW&lt;br /&gt;
* Goodfellas (American)&lt;br /&gt;
: 615 Spring Street&lt;br /&gt;
* The Real Chow Baby (American Stir Fry)&lt;br /&gt;
: 1016 Howell Mill Road&lt;br /&gt;
* Zen on Ten Asian Bistro (Sushi)&lt;br /&gt;
:1000 Northside Dr. NW&lt;br /&gt;
* Spoon (Thai)&lt;br /&gt;
: 768 Marietta Street&lt;br /&gt;
* The Vortex (American)&lt;br /&gt;
: 878 Peachtree Street NE&lt;br /&gt;
* Taco Mac (American)&lt;br /&gt;
: 933 Peachtree St NE&lt;br /&gt;
* La Fonda Latina (Mexican)&lt;br /&gt;
: 1025 Howell Mill Road&lt;br /&gt;
* Prickly Pear (Mexican)&lt;br /&gt;
: 950 West Peachtree St NE&lt;br /&gt;
* TheTenth Thai&lt;br /&gt;
: 132 10th Street Northeast (Thai)&lt;br /&gt;
&lt;br /&gt;
=== Miscellaneous ===&lt;br /&gt;
* Publix at The Plaza Midtown (Supermarket)&lt;br /&gt;
: 950 W Peachtree St NW &lt;br /&gt;
* Midtown Market (Sundries)&lt;br /&gt;
: 225 10th St NE&lt;br /&gt;
* Walmart Supercenter (Supermarket)&lt;br /&gt;
: 1801 Howell Mill Rd Nw&lt;br /&gt;
* Walgreens (Pharmacy)&lt;br /&gt;
: 595 Piedmont Ave., Ste. 100&lt;br /&gt;
* CVS (Pharmacy)&lt;br /&gt;
: 842 Peachtree Street NE&lt;br /&gt;
&lt;br /&gt;
=== Entertainment ===&lt;br /&gt;
* Manuel&amp;#039;s Tavern [http://www.manuelstavern.com/] (also the site of Astrophysics unplugged)&lt;br /&gt;
* Blind Willie&amp;#039;s [http://www.blindwilliesblues.com/]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==Hands on material==&lt;br /&gt;
===WaveToy===&lt;br /&gt;
The source code for the example thorn and the slides is available at&lt;br /&gt;
via&lt;br /&gt;
  cd $HOME&lt;br /&gt;
  ./GetComponents -a https://svn.einsteintoolkit.org/documents/Workshop_Spring_2012/example_wavetoy/Cactus/misc/WaveToy.th&lt;br /&gt;
  cd Cactus&lt;br /&gt;
  echo &amp;#039;Introduction/WaveToy&amp;#039; &amp;gt;&amp;gt;configs/sim/ThornList&lt;br /&gt;
  simfactory/bin/sim build&lt;br /&gt;
Once built, you can run this in one line via simfactory&lt;br /&gt;
  simfactory/bin/sim create-run wavetoy --parfile wavetoy-misc/WaveToy.par&lt;br /&gt;
===Static TOV===&lt;br /&gt;
Edit par/static_tov.par as Frank indicated and save as $HOME/Cactus/fast_tov.par&lt;br /&gt;
&lt;br /&gt;
To run enter:&lt;br /&gt;
  cd $HOME/Cactus&lt;br /&gt;
  exe/cactus_sim fast_tov.par&lt;br /&gt;
&lt;br /&gt;
===Visualization, Hands-on I===&lt;br /&gt;
&lt;br /&gt;
Download the slides and some extra sample data via&lt;br /&gt;
  cd $HOME&lt;br /&gt;
  svn co https://svn.einsteintoolkit.org/documents/Workshop_Spring_2012/handson_sviz .&lt;br /&gt;
Make sure you have 3d data!  If not, add these lines to your tov parameter file and rerun for a bit:&lt;br /&gt;
  CarpetIOHDF5::out3d_every = 1&lt;br /&gt;
  CarpetIOHDF5::out3d_vars = &amp;quot; HydroBase::rho &amp;quot;&lt;br /&gt;
These give data under the file name &amp;#039;&amp;#039;rho.xyz.h5&amp;#039;&amp;#039;. Alternatively, add the following parameters&lt;br /&gt;
  CarpetIOHDF5::out_every = 1&lt;br /&gt;
  CarpetIOHDF5::out_vars = &amp;quot;HydroBase::rho&amp;quot;&lt;br /&gt;
which give data under the file &amp;#039;&amp;#039;rho.h5&amp;#039;&amp;#039;. Either way works fine. We will assume the latter for the moment.&lt;br /&gt;
&lt;br /&gt;
Follow the directions on the first slides to create a plot of how the evolving TOV differs from its initial state.&lt;br /&gt;
&lt;br /&gt;
Other suggestions for visualization tasks are contained in the slides.&lt;/div&gt;</summary>
		<author><name>Bmundim</name></author>
		
	</entry>
	<entry>
		<id>https://docs.einsteintoolkit.org/et-docs/index.php?title=Introduction_numerical_methods&amp;diff=3175</id>
		<title>Introduction numerical methods</title>
		<link rel="alternate" type="text/html" href="https://docs.einsteintoolkit.org/et-docs/index.php?title=Introduction_numerical_methods&amp;diff=3175"/>
		<updated>2012-04-05T09:42:32Z</updated>

		<summary type="html">&lt;p&gt;Bmundim: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;* 3+1 spacetime decomposition&lt;br /&gt;
* BSSN formalism&lt;br /&gt;
* BHB: puncture initial data&lt;br /&gt;
* Method of lines&lt;br /&gt;
* Finite difference approximation&lt;br /&gt;
* GRMHD - Valencia Formulation&lt;br /&gt;
* Conservation laws&lt;br /&gt;
* Finite volume techniques&lt;br /&gt;
* Riemann Problem&lt;br /&gt;
* Example: Burgers Equation&lt;br /&gt;
* Approximate Riemann Solvers&lt;br /&gt;
* Slope Limiters&lt;br /&gt;
* Algorithm Overview&lt;/div&gt;</summary>
		<author><name>Bmundim</name></author>
		
	</entry>
	<entry>
		<id>https://docs.einsteintoolkit.org/et-docs/index.php?title=ET_Workshop_Spring_2012&amp;diff=3172</id>
		<title>ET Workshop Spring 2012</title>
		<link rel="alternate" type="text/html" href="https://docs.einsteintoolkit.org/et-docs/index.php?title=ET_Workshop_Spring_2012&amp;diff=3172"/>
		<updated>2012-04-05T09:05:36Z</updated>

		<summary type="html">&lt;p&gt;Bmundim: /* Schedule */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Spring Einstein Toolkit Workshop 2012 ==&lt;br /&gt;
&lt;br /&gt;
We prepared a [https://svn.einsteintoolkit.org/documents/Workshop_Spring_2012/flyer/etk2.pdf flyer], which can be printed or otherwise&lt;br /&gt;
distributed.&lt;br /&gt;
&lt;br /&gt;
=== Announcement ===&lt;br /&gt;
The Einstein Toolkit (http://einsteintoolkit.org) will host its spring workshop 2012 following the April APS meeting in Atlanta, GA,&lt;br /&gt;
from Tuesday, April 3rd 4pm to Friday April 6th noon.&lt;br /&gt;
&lt;br /&gt;
This workshop is targeted at new and potential new users of the relativity infrastructure. It will provide a general introductions&lt;br /&gt;
into numerical relativity (although some previous knowledge would be beneficial) and in code development within large collaborations.&lt;br /&gt;
Hands-on sessions will help to familiarize attendees with the Einstein Toolkit. Participants are asked to bring their own laptops.&lt;br /&gt;
We would like to invite especially students from physics and computer science to participate.&lt;br /&gt;
&lt;br /&gt;
The number of attendees is limited, and while registration is free, it is required. We anticipate to be able to support a small&lt;br /&gt;
number of participants financially, by covering parts/all of their travel, hotel and meal cost. Preference will be given to students.&lt;br /&gt;
&lt;br /&gt;
In order to register, write an email to workshop@einsteintoolkit.org, specify:&lt;br /&gt;
* your name, affiliation and title&lt;br /&gt;
* your estimated arrival and departure time/date&lt;br /&gt;
* whether you apply for support (and if so, state if you are undergraduate / graduate student / postdoc)&lt;br /&gt;
* your special needs&lt;br /&gt;
&lt;br /&gt;
Detailed workshop information can be found at https://docs.einsteintoolkit.org/et-docs/ET_Workshop_Spring_2012.&lt;br /&gt;
&lt;br /&gt;
The Einstein Toolkit Consortium.&lt;br /&gt;
&lt;br /&gt;
=== Spacetime Coordinates and Contact Information ===&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot; border=&amp;quot;1&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
! Dates&lt;br /&gt;
| &amp;#039;&amp;#039;&amp;#039;Tues, 3. April @ 4pm -- Fri, 6. April @ noon&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
|-&lt;br /&gt;
! Location&lt;br /&gt;
| Room 319, Georgia Tech Student Center, Georgia Tech, Atlanta&lt;br /&gt;
|-&lt;br /&gt;
! Contacts&lt;br /&gt;
| Workshop email list: &amp;#039;&amp;#039;&amp;#039;workshop@einsteintoolkit.org&amp;#039;&amp;#039;&amp;#039;, emergencies: Frank Löffler (knarf@cct.lsu.edu, +1-225-202-1752) or Tanja Bode (tanja.bode@physics.gatech.edu, +1-814-360-2715)&lt;br /&gt;
|-&lt;br /&gt;
! Hotel&lt;br /&gt;
| A small block of rooms was reserved at the [http://hamptoninn.hilton.com/en/hp/groups/personalized/A/ATLGTHX-ETW-20120403/index.jhtml?WT.mc_id=POG Hampton Inn Atlanta - Georgia Tech], 244 North Ave NW (404-881-0881).  The group rate was &amp;#039;&amp;#039;&amp;#039;$117 per night plus tax (appr. 16%, resulting in a ~$136 rate)&amp;#039;&amp;#039;&amp;#039; and included a hot breakfast and high speed wireless access.  A [http://hamptoninn.hilton.com/en/hp/groups/personalized/A/ATLGTHX-ETW-20120403/index.jhtml?WT.mc_id=POG group web page] was available to book online, or you could reserve by phone at 404-881-0881 and ask for the &amp;#039;&amp;#039;&amp;#039;&amp;quot;Einstein Toolkit Workshop&amp;quot; rate&amp;#039;&amp;#039;&amp;#039;.  Attendees had until &amp;#039;&amp;#039;&amp;#039;20. March&amp;#039;&amp;#039;&amp;#039; to reserve.&lt;br /&gt;
&lt;br /&gt;
In addition, a small block of rooms were reserved at the [http://www.hotelmidtownatlanta.com Hotel Midtown Atlanta].  The group rate was &amp;#039;&amp;#039;&amp;#039;$89 per night&amp;#039;&amp;#039;&amp;#039; for single occupancy, including breakfast and high-speed internet.  For an additional person, add $10 (to cover breakfast costs).  Though less convenient to either the APS meeting or this workshop, both can be conveniently reached by transit from the Midtown MARTA station a block away. Reservations at this rate could be done by phone only at 404-873-4800. The block of rooms was released on &amp;#039;&amp;#039;&amp;#039;26. March&amp;#039;&amp;#039;&amp;#039;.&lt;br /&gt;
|-&lt;br /&gt;
! Transportation - Hotel&lt;br /&gt;
| The best way to get to the hotels from the airport (or elsewhere) is by taking [http://itsmarta.com MARTA]&amp;#039;s red or gold rail line, which costs $2.50 one-way.  The Hotel Midtown Atlanta is a block away from Midtown station.  For the Hampton Inn, get off at the North Avenue station. It should take approximately 20 minutes to either station.  From North Ave station, walk west for ~0.5 miles or transfer to MARTA bus route 26 to the stop immediately in front of the Hampton Inn.&lt;br /&gt;
|-&lt;br /&gt;
! Transportation - Workshop&lt;br /&gt;
| The student center is a 5-minute (~1/3 mile) walk [http://g.co/maps/hdjbt] from Hampton Inn.  From the Hotel Midtown Atlanta, Georgia Tech campus (specifically the student center) can be easily reached by taking the [http://pts.gatech.edu/ride/routes_schedules/Pages/TechTrolley.aspx Georgia Tech Trolley] (free) from the Midtown MARTA station to its end station.&lt;br /&gt;
|-&lt;br /&gt;
! Transportation - From the APS (Hyatt)&lt;br /&gt;
| The Workshop is a 1.5 mile walk from the Hyatt where the APS is taking place.  The most convenient way to reach the Workshop location on Tuesday is to take [http://itsmarta.com/1-w.aspx MARTA Bus Route 1] from Spring St [http://g.co/maps/jpf3h] (a block away from the Hyatt) directly to the workshop hotel.&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
== Participant List ==&lt;br /&gt;
&lt;br /&gt;
Below are the ET volunteers who will be presenting or heading parts of the sessions.&lt;br /&gt;
&lt;br /&gt;
{|class=&amp;quot;wikitable&amp;quot; border=&amp;quot;2&amp;quot; cellpadding=&amp;quot;2&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
! Name&lt;br /&gt;
! Affiliation&lt;br /&gt;
|- style=&amp;quot;background:lightgrey;&amp;quot;&lt;br /&gt;
| Tanja Bode || Georgia Tech&lt;br /&gt;
|-&lt;br /&gt;
| Dennis Castleberry || Louisiana State University&lt;br /&gt;
|- style=&amp;quot;background:lightgrey;&amp;quot;&lt;br /&gt;
| Peter Diener || Louisiana State University&lt;br /&gt;
|-&lt;br /&gt;
| Josh Faber || Rochester Institute of Technology&lt;br /&gt;
|- style=&amp;quot;background:lightgrey;&amp;quot;&lt;br /&gt;
| Roland Haas || Caltech&lt;br /&gt;
|-&lt;br /&gt;
| Frank Löffler || Louisiana State University&lt;br /&gt;
|- style=&amp;quot;background:lightgrey;&amp;quot;&lt;br /&gt;
| Bruno Mundim || Rochester Institute of Technology&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
The current participant list as of 4. April 2012 follows, in alphabetical order.&lt;br /&gt;
Please indicate whether you have already arranged for lodgings so that others looking for hotel roommates &lt;br /&gt;
may most easily find them.  This page is editable in general (though IPs are logged), so please manage your own &lt;br /&gt;
lodging status.&lt;br /&gt;
&lt;br /&gt;
{|class=&amp;quot;wikitable&amp;quot; border=&amp;quot;2&amp;quot; cellpadding=&amp;quot;2&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
! Name&lt;br /&gt;
! Affiliation&lt;br /&gt;
|- style=&amp;quot;background:lightgrey;&amp;quot;&lt;br /&gt;
| Majd Abdelqader || Queens University&lt;br /&gt;
|-&lt;br /&gt;
| Rafael Aranha || Georgia Tech&lt;br /&gt;
|- style=&amp;quot;background:lightgrey;&amp;quot;&lt;br /&gt;
| Grayson Carroll || Belmont University&lt;br /&gt;
|-&lt;br /&gt;
| Roseanne Cheng || UNC-Chapel Hill&lt;br /&gt;
|- style=&amp;quot;background:lightgrey;&amp;quot;&lt;br /&gt;
| Michael Clark || Georgia Tech&lt;br /&gt;
|-&lt;br /&gt;
| Brett Deaton || Washington University&lt;br /&gt;
|- style=&amp;quot;background:lightgrey;&amp;quot;&lt;br /&gt;
| Tehani K. Finch || Howard University&lt;br /&gt;
|- &lt;br /&gt;
| Gary Forrester || University of Massachusetts at Dartmouth&lt;br /&gt;
|- style=&amp;quot;background:lightgrey;&amp;quot;&lt;br /&gt;
| Brian Friesen || University of Oklahoma&lt;br /&gt;
|- &lt;br /&gt;
| Rita Garrido || Georgia Tech&lt;br /&gt;
|- style=&amp;quot;background:lightgrey;&amp;quot;&lt;br /&gt;
| Joshua Harris || Louisiana State University&lt;br /&gt;
|- &lt;br /&gt;
| Scott Hawley || Belmont University&lt;br /&gt;
|- style=&amp;quot;background:lightgrey;&amp;quot;&lt;br /&gt;
| Matt Kinsey || Georgia Tech&lt;br /&gt;
|- &lt;br /&gt;
| Jussara Marandola Kofuji || Georgia Tech&lt;br /&gt;
|- style=&amp;quot;background:lightgrey;&amp;quot;&lt;br /&gt;
| Kostas Kokkotas || Universität Tübingen&lt;br /&gt;
|- &lt;br /&gt;
| Hari Krishnan || Louisiana State University&lt;br /&gt;
|- style=&amp;quot;background:lightgrey;&amp;quot;&lt;br /&gt;
| Sean McWilliams || Princeton&lt;br /&gt;
|- &lt;br /&gt;
| Philipp Moesta || Caltech&lt;br /&gt;
|- style=&amp;quot;background:lightgrey;&amp;quot;&lt;br /&gt;
| Tuan Anh Nguyen || Georgia Tech&lt;br /&gt;
|- &lt;br /&gt;
| Prabath Peiris || Rochester Institute of Technology&lt;br /&gt;
|- style=&amp;quot;background:lightgrey;&amp;quot;&lt;br /&gt;
| Larne Pekowsky || Georgia Tech&lt;br /&gt;
|- &lt;br /&gt;
| Prayash Sharma Pyakurel || Truman State University&lt;br /&gt;
|- style=&amp;quot;background:lightgrey;&amp;quot;&lt;br /&gt;
| Christian Reisswig || Caltech&lt;br /&gt;
|- &lt;br /&gt;
| Ian Ruchlin || Rochester Institute of Technology&lt;br /&gt;
|- style=&amp;quot;background:lightgrey;&amp;quot;&lt;br /&gt;
| Carl Rodriguez || Northwestern University&lt;br /&gt;
|- &lt;br /&gt;
| Chao Shi || Georgia Tech&lt;br /&gt;
|- style=&amp;quot;background:lightgrey;&amp;quot;&lt;br /&gt;
| Cody Simmons || North Carolina State University&lt;br /&gt;
|- &lt;br /&gt;
| Magda Slawinska || Georgia Tech&lt;br /&gt;
|- style=&amp;quot;background:lightgrey;&amp;quot;&lt;br /&gt;
| Petr Tsatsin || Florida Atlantic University&lt;br /&gt;
|- &lt;br /&gt;
| Alex Vañô Viñuales || University of the Balearic Islands&lt;br /&gt;
|- style=&amp;quot;background:lightgrey;&amp;quot;&lt;br /&gt;
| Andrew Vu || Emory University&lt;br /&gt;
|- &lt;br /&gt;
| Konstantin Yakunin || Florida Atlantic University / ORNL&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
== In-Workshop Details ==&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
 &lt;br /&gt;
=== Schedule ===&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot; border=&amp;quot;1&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
| Day&lt;br /&gt;
| Time&lt;br /&gt;
| Activity&lt;br /&gt;
| Presenter / Responsible&lt;br /&gt;
|-&lt;br /&gt;
| Tue&lt;br /&gt;
| 16:00-17:30&lt;br /&gt;
| Setup for early birds&lt;br /&gt;
| Tanja Bode, Roland Haas, Frank Löffler&lt;br /&gt;
|-&lt;br /&gt;
| Wed&lt;br /&gt;
| 08:00-08:30&lt;br /&gt;
| Setup for late birds&lt;br /&gt;
| Tanja Bode, Roland Haas, Frank Löffler&lt;br /&gt;
|-&lt;br /&gt;
| Wed&lt;br /&gt;
| 08:30-09:00&lt;br /&gt;
| Opening, Introduction ([https://svn.einsteintoolkit.org/documents/Workshop_Spring_2012/introduction/introduction.pdf slides])&lt;br /&gt;
| Frank Löffler&lt;br /&gt;
|-&lt;br /&gt;
| Wed&lt;br /&gt;
| 09:00-09:30&lt;br /&gt;
| Introduction to Scientific Software &amp;amp; HPC ([https://svn.einsteintoolkit.org/documents/Workshop_Spring_2012/hpc_intro/hpc_intro.pdf slides])&lt;br /&gt;
| Frank Löffler&lt;br /&gt;
|-&lt;br /&gt;
| Wed&lt;br /&gt;
| 09:30-10:00&lt;br /&gt;
| Introduction to Cactus (high-level) ([https://svn.einsteintoolkit.org/documents/Workshop_Spring_2012/cactus_intro/cactus_intro.pdf slides])&lt;br /&gt;
| Frank Löffler&lt;br /&gt;
|-&lt;br /&gt;
| Wed&lt;br /&gt;
| 10:00-10:30&lt;br /&gt;
| Discussion and break&lt;br /&gt;
|-&lt;br /&gt;
| Wed&lt;br /&gt;
| 10:30-11:15&lt;br /&gt;
| [[Introduction to General Relativity]] ([https://svn.einsteintoolkit.org/documents/Workshop_Spring_2012/genrel/genrel.pdf slides])&lt;br /&gt;
| Joshua Faber&lt;br /&gt;
|-&lt;br /&gt;
| Wed&lt;br /&gt;
| 11:15-12:00&lt;br /&gt;
| [[Introduction on Cactus Thorn-Writing (lower level)]] ([https://svn.einsteintoolkit.org/documents/Workshop_Spring_2012/cactuswriting/cactuswriting.pdf slides])&lt;br /&gt;
| Joshua Faber&lt;br /&gt;
|-&lt;br /&gt;
| Wed&lt;br /&gt;
| 12:00-13:00&lt;br /&gt;
| Lunch break&lt;br /&gt;
|-&lt;br /&gt;
| Wed&lt;br /&gt;
| 13:00-13:30&lt;br /&gt;
| Introduction to Workshop development environment&lt;br /&gt;
| Dennis Castleberry&lt;br /&gt;
|-&lt;br /&gt;
| Wed&lt;br /&gt;
| 13:30-14:15&lt;br /&gt;
| Hands-on, provided Wave-Equation example within Cactus ([https://svn.einsteintoolkit.org/documents/Workshop_Spring_2012/example_wavetoy/example_wavetoy.pdf slides])&lt;br /&gt;
| Roland Haas&lt;br /&gt;
|-&lt;br /&gt;
| Wed&lt;br /&gt;
| 14:15-15:15&lt;br /&gt;
| [[Introduction numerical methods &amp;amp; numerical Relativity]] &amp;lt;!--([ slides])--&amp;gt;&lt;br /&gt;
| Bruno Mundim, Peter Diener&lt;br /&gt;
|-&lt;br /&gt;
| Wed&lt;br /&gt;
| 15:15-15:45&lt;br /&gt;
| Discussion and break&lt;br /&gt;
|-&lt;br /&gt;
| Wed&lt;br /&gt;
| 15:45-17:30&lt;br /&gt;
| Running and extending (par-file) of two provided examples: perturbed, single [https://docs.einsteintoolkit.org/et-docs/images/6/69/Onepuncture.par BH], and perturbed, single TOV star &amp;lt;!--([ slides])--&amp;gt;&lt;br /&gt;
| Frank Löffler, Bruno Mundim&lt;br /&gt;
|-&lt;br /&gt;
| Thu&lt;br /&gt;
| 08:00-09:00&lt;br /&gt;
| Introduction in Scientific visualization - a bit of theory and a lot of practice ([https://svn.einsteintoolkit.org/documents/Workshop_Spring_2012/scientific_viz/scientific_viz.pdf slides])&lt;br /&gt;
| Tanja Bode&lt;br /&gt;
|-&lt;br /&gt;
| Thu&lt;br /&gt;
| 09:00-10:00&lt;br /&gt;
| Invited Talk I -- Matt Duez, Washington University: The Challenge of interpreting data in numerical relativity &amp;lt;!--([ slides])--&amp;gt;&lt;br /&gt;
|-&lt;br /&gt;
| Thu&lt;br /&gt;
| 10:00-10:30&lt;br /&gt;
| Discussion and break&lt;br /&gt;
|-&lt;br /&gt;
| Thu&lt;br /&gt;
| 10:30-11:15&lt;br /&gt;
| Hands-on: Using visualization tools to look at meaningful quantities ( TOV profile evolutions ) ([https://svn.einsteintoolkit.org/documents/Workshop_Spring_2012/handson_sviz/handson_sviz.pdf slides])&lt;br /&gt;
| Tanja Bode&lt;br /&gt;
|-&lt;br /&gt;
| Thu&lt;br /&gt;
| 11:15-12:00&lt;br /&gt;
| Create movie of either BH+GW or TOV oscillations using VisIt ([https://svn.einsteintoolkit.org/documents/Workshop_Spring_2012/handson_viz/handson_viz.pdf slides], [https://svn.einsteintoolkit.org/documents/Workshop_Spring_2012/handson_viz/rho.final.session TOV session file], [http://www.physics.gatech.edu/~rhaas3/Workshop_Spring_2012/rho.rl4.h5.xz TOV data file], [https://svn.einsteintoolkit.org/documents/Workshop_Spring_2012/handson_viz/psi4.volume.session Psi4 session file], [http://www.physics.gatech.edu/~rhaas3/Workshop_Spring_2012/psir.h5.xz Psi4 data file])&lt;br /&gt;
| Roland Haas&lt;br /&gt;
|-&lt;br /&gt;
| Thu&lt;br /&gt;
| 12:00-13:00&lt;br /&gt;
| Lunch&lt;br /&gt;
|-&lt;br /&gt;
| Thu&lt;br /&gt;
| 13:00-14:15&lt;br /&gt;
| Hands-on: Implement your own thorn (neutron star tracking), and visualize it, in teams of about 5 people ([https://svn.einsteintoolkit.org/documents/Workshop_Spring_2012/handson_analysis/handson_analysis.pdf slides]), more information at end of wiki&lt;br /&gt;
| Roland Haas&lt;br /&gt;
|-&lt;br /&gt;
| Thu&lt;br /&gt;
| 14:15-15:15&lt;br /&gt;
| Invited Talk II -- John Wise, Georgia Tech&lt;br /&gt;
|-&lt;br /&gt;
| Thu&lt;br /&gt;
| 15:15-15:45&lt;br /&gt;
| Discussion and break&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
| Thu&lt;br /&gt;
| 15:45-17:30&lt;br /&gt;
| Hands-on: continuation&lt;br /&gt;
| Roland Haas&lt;br /&gt;
|-&lt;br /&gt;
| Fri&lt;br /&gt;
| 08:00-09:00&lt;br /&gt;
| Presentation of visualization of result of previous session, 6 teams: 8 min each&lt;br /&gt;
| Frank Löffler&lt;br /&gt;
|-&lt;br /&gt;
| Fri&lt;br /&gt;
| 09:00-10:00&lt;br /&gt;
| Invited talk III -- Gabrielle Allen, LSU&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
| Fri&lt;br /&gt;
| 10:00-10:30&lt;br /&gt;
| Discussion and break&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
| Fri&lt;br /&gt;
| 10:30-11:00&lt;br /&gt;
| Tour through available ET components&lt;br /&gt;
| Peter Diener&lt;br /&gt;
|-&lt;br /&gt;
| Fri&lt;br /&gt;
| 11:00-11:30&lt;br /&gt;
| Overview over supercomputing resources, introduction on how to get accounts / allocations, trends in HPC, reminder how to get ET help in the future&lt;br /&gt;
| Joshua Faber, Peter Diener&lt;br /&gt;
|-&lt;br /&gt;
| Fri&lt;br /&gt;
| 11:30-12:00&lt;br /&gt;
| The future of the ET: everything we didn&amp;#039;t talk about (EOSs, refluxing, multiblock, MHD, radiation ect.)&lt;br /&gt;
| Frank Löffler&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
=== Setup ===&lt;br /&gt;
* Wireless access is through the GTVisitor network. &amp;#039;&amp;#039;&amp;#039;One&amp;#039;&amp;#039;&amp;#039; account per person, please. It will work on multiple devices simultaneously.&lt;br /&gt;
* The virtual machine for the workshop is [http://cct.lsu.edu/~dcastl2/] and will run in [http://virtualbox.org virtualbox]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Area Details ==&lt;br /&gt;
&lt;br /&gt;
* For on-campus directions please consult the link of a detailed &amp;#039;&amp;#039;&amp;#039;map of the Georgia Tech Campus&amp;#039;&amp;#039;&amp;#039;: [http://map.gtalumni.org/]&lt;br /&gt;
* For directions of Midtown and Downtown Atlanta follow the link [http://www.atlantadowntown.com/guide]&lt;br /&gt;
&lt;br /&gt;
=== Restaurants ===&lt;br /&gt;
&amp;#039;&amp;#039;&amp;#039;Places to Eat On-Campus:&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
&amp;#039;&amp;#039;&amp;#039;Technology Square&amp;#039;&amp;#039;&amp;#039;, located on 5th Street and Spring Street, has a variety of good and cheap restaurants including:&lt;br /&gt;
* Tin Drum Asia Cafe &lt;br /&gt;
* Ray&amp;#039;s New York Pizza&lt;br /&gt;
* Chuck&amp;#039;s Famous&lt;br /&gt;
* Barrelhouse&lt;br /&gt;
* 5th Street Ribs n&amp;#039; Blues&lt;br /&gt;
* Umma&amp;#039;s House Restaurant and Cafe&lt;br /&gt;
* Waffle House&lt;br /&gt;
* Moe&amp;#039;s Southwest Grill&lt;br /&gt;
* St. Charles Deli&lt;br /&gt;
The &amp;#039;&amp;#039;&amp;#039;Student Center&amp;#039;&amp;#039;&amp;#039; [http://www.studentcenter.gatech.edu] has:&lt;br /&gt;
* Chick-fil-a&lt;br /&gt;
* Taco Bell&lt;br /&gt;
* Subway&lt;br /&gt;
* A pub style at Jackets&lt;br /&gt;
* Einstein&amp;#039;s Bagels&lt;br /&gt;
* Ferst Place (Located on the 3rd floor)&lt;br /&gt;
* Ferst Food Court (Located on the 2nd floor)&lt;br /&gt;
&lt;br /&gt;
&amp;#039;&amp;#039;&amp;#039;Places to Eat Off-campus :&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
* Varsity (American)&lt;br /&gt;
: 61 North Ave. NW&lt;br /&gt;
* Goodfellas (American)&lt;br /&gt;
: 615 Spring Street&lt;br /&gt;
* The Real Chow Baby (American Stir Fry)&lt;br /&gt;
: 1016 Howell Mill Road&lt;br /&gt;
* Zen on Ten Asian Bistro (Sushi)&lt;br /&gt;
:1000 Northside Dr. NW&lt;br /&gt;
* Spoon (Thai)&lt;br /&gt;
: 768 Marietta Street&lt;br /&gt;
* The Vortex (American)&lt;br /&gt;
: 878 Peachtree Street NE&lt;br /&gt;
* Taco Mac (American)&lt;br /&gt;
: 933 Peachtree St NE&lt;br /&gt;
* La Fonda Latina (Mexican)&lt;br /&gt;
: 1025 Howell Mill Road&lt;br /&gt;
* Prickly Pear (Mexican)&lt;br /&gt;
: 950 West Peachtree St NE&lt;br /&gt;
* TheTenth Thai&lt;br /&gt;
: 132 10th Street Northeast (Thai)&lt;br /&gt;
&lt;br /&gt;
=== Miscellaneous ===&lt;br /&gt;
* Publix at The Plaza Midtown (Supermarket)&lt;br /&gt;
: 950 W Peachtree St NW &lt;br /&gt;
* Midtown Market (Sundries)&lt;br /&gt;
: 225 10th St NE&lt;br /&gt;
* Walmart Supercenter (Supermarket)&lt;br /&gt;
: 1801 Howell Mill Rd Nw&lt;br /&gt;
* Walgreens (Pharmacy)&lt;br /&gt;
: 595 Piedmont Ave., Ste. 100&lt;br /&gt;
* CVS (Pharmacy)&lt;br /&gt;
: 842 Peachtree Street NE&lt;br /&gt;
&lt;br /&gt;
=== Entertainment ===&lt;br /&gt;
* Manuel&amp;#039;s Tavern [http://www.manuelstavern.com/] (also the site of Astrophysics unplugged)&lt;br /&gt;
* Blind Willie&amp;#039;s [http://www.blindwilliesblues.com/]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==Hands on material==&lt;br /&gt;
===WaveToy===&lt;br /&gt;
The source code for the example thorn and the slides is available at&lt;br /&gt;
via&lt;br /&gt;
  cd $HOME&lt;br /&gt;
  ./GetComponents -a https://svn.einsteintoolkit.org/documents/Workshop_Spring_2012/example_wavetoy/Cactus/misc/WaveToy.th&lt;br /&gt;
  cd Cactus&lt;br /&gt;
  echo &amp;#039;Introduction/WaveToy&amp;#039; &amp;gt;&amp;gt;configs/sim/ThornList&lt;br /&gt;
  simfactory/bin/sim build&lt;br /&gt;
Once built, you can run this in one line via simfactory&lt;br /&gt;
  simfactory/bin/sim create-run wavetoy --parfile wavetoy-misc/WaveToy.par&lt;br /&gt;
===Static TOV===&lt;br /&gt;
Edit par/static_tov.par as Frank indicated and save as $HOME/Cactus/fast_tov.par&lt;br /&gt;
&lt;br /&gt;
To run enter:&lt;br /&gt;
  cd $HOME/Cactus&lt;br /&gt;
  exe/cactus_sim fast_tov.par&lt;br /&gt;
&lt;br /&gt;
===Visualization, Hands-on I===&lt;br /&gt;
Download the slides and some extra sample data via&lt;br /&gt;
  cd $HOME&lt;br /&gt;
  svn co https://svn.einsteintoolkit.org/documents/Workshop_Spring_2012/handson_sviz .&lt;br /&gt;
Make sure you have 3d data!  If not, add these lines to your tov parameter file and rerun for a bit:&lt;br /&gt;
  CarpetIOHDF5::out3d_every = 1&lt;br /&gt;
  CarpetIOHDF5::out3d_vars = &amp;quot; HydroBase::rho &amp;quot;&lt;/div&gt;</summary>
		<author><name>Bmundim</name></author>
		
	</entry>
	<entry>
		<id>https://docs.einsteintoolkit.org/et-docs/index.php?title=File:Onepuncture.par&amp;diff=3171</id>
		<title>File:Onepuncture.par</title>
		<link rel="alternate" type="text/html" href="https://docs.einsteintoolkit.org/et-docs/index.php?title=File:Onepuncture.par&amp;diff=3171"/>
		<updated>2012-04-05T09:04:09Z</updated>

		<summary type="html">&lt;p&gt;Bmundim: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;/div&gt;</summary>
		<author><name>Bmundim</name></author>
		
	</entry>
	<entry>
		<id>https://docs.einsteintoolkit.org/et-docs/index.php?title=Introduction_numerical_methods&amp;diff=3060</id>
		<title>Introduction numerical methods</title>
		<link rel="alternate" type="text/html" href="https://docs.einsteintoolkit.org/et-docs/index.php?title=Introduction_numerical_methods&amp;diff=3060"/>
		<updated>2012-02-27T17:35:10Z</updated>

		<summary type="html">&lt;p&gt;Bmundim: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;* 3+1 spacetime decomposition&lt;br /&gt;
* BSSN formalism&lt;br /&gt;
* BHB: puncture initial data&lt;br /&gt;
* Method of lines&lt;br /&gt;
* Finite difference approximation&lt;br /&gt;
* Conservation laws&lt;br /&gt;
* Finite volume techniques&lt;br /&gt;
* High resolution shock capturing&lt;br /&gt;
* etc...&lt;/div&gt;</summary>
		<author><name>Bmundim</name></author>
		
	</entry>
	<entry>
		<id>https://docs.einsteintoolkit.org/et-docs/index.php?title=Schedule_Proposal&amp;diff=3059</id>
		<title>Schedule Proposal</title>
		<link rel="alternate" type="text/html" href="https://docs.einsteintoolkit.org/et-docs/index.php?title=Schedule_Proposal&amp;diff=3059"/>
		<updated>2012-02-27T10:59:38Z</updated>

		<summary type="html">&lt;p&gt;Bmundim: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Volunteers to head sessions, please add your name to those sessions you &amp;#039;&amp;#039;could&amp;#039;&amp;#039; head and indicate those you &amp;#039;&amp;#039;prefer&amp;#039;&amp;#039; to head by an * by your name.&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot; border=&amp;quot;1&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
| Day&lt;br /&gt;
| Time&lt;br /&gt;
| Activity&lt;br /&gt;
| Volunteers&lt;br /&gt;
|-&lt;br /&gt;
| Tue&lt;br /&gt;
| 16:00-17:30&lt;br /&gt;
| Setup for early birds&lt;br /&gt;
| Tanja, Roland, Frank&lt;br /&gt;
|-&lt;br /&gt;
| Wed&lt;br /&gt;
| 08:00-08:30&lt;br /&gt;
| Setup for late birds&lt;br /&gt;
| Tanja, Roland, Frank&lt;br /&gt;
|-&lt;br /&gt;
| Wed&lt;br /&gt;
| 08:30-09:00&lt;br /&gt;
| Opening, Introduction&lt;br /&gt;
| Frank&lt;br /&gt;
|-&lt;br /&gt;
| Wed&lt;br /&gt;
| 09:00-10:00&lt;br /&gt;
| Invited Talk I&lt;br /&gt;
|-&lt;br /&gt;
| Wed&lt;br /&gt;
| 10:00-10:30&lt;br /&gt;
| Discussion and break&lt;br /&gt;
|-&lt;br /&gt;
| Wed&lt;br /&gt;
| 10:30-11:15&lt;br /&gt;
| [[Introduction to General Relativity]]&lt;br /&gt;
| Bruno, Tanja, Frank, Josh&lt;br /&gt;
|-&lt;br /&gt;
| Wed&lt;br /&gt;
| 11:15-12:00&lt;br /&gt;
| Introduction to Scientific Software &amp;amp; HPC&lt;br /&gt;
| Frank&lt;br /&gt;
|-&lt;br /&gt;
| Wed&lt;br /&gt;
| 12:00-13:00&lt;br /&gt;
| Lunch break&lt;br /&gt;
|-&lt;br /&gt;
| Wed&lt;br /&gt;
| 13:00-13:30&lt;br /&gt;
| Introduction to Workshop development environment&lt;br /&gt;
| Dennis&lt;br /&gt;
|-&lt;br /&gt;
| Wed&lt;br /&gt;
| 13:30-14:15&lt;br /&gt;
| Hands-on, provided Wave-Equation example within Cactus&lt;br /&gt;
| Tanja, Roland, Frank&lt;br /&gt;
|-&lt;br /&gt;
| Wed&lt;br /&gt;
| 14:15-15:15&lt;br /&gt;
| [[Introduction numerical methods &amp;amp; numerical Relativity]]&lt;br /&gt;
| Tanja, Bruno, Frank, Josh&lt;br /&gt;
|-&lt;br /&gt;
| Wed&lt;br /&gt;
| 15:15-15:45&lt;br /&gt;
| Discussion and break&lt;br /&gt;
|-&lt;br /&gt;
| Wed&lt;br /&gt;
| 15:45-17:30&lt;br /&gt;
| Running and extending (par-file) of two provided examples: perturbed, single BH, and perturbed, single TOV star&lt;br /&gt;
| Tanja, Roland, Frank, Josh, Bruno&lt;br /&gt;
|-&lt;br /&gt;
| Thu&lt;br /&gt;
| 08:00-09:00&lt;br /&gt;
| Introduction in Scientific visualization - a bit of theory and a lot of practice&lt;br /&gt;
| Tanja, Roland, Frank&lt;br /&gt;
|-&lt;br /&gt;
| Thu&lt;br /&gt;
| 09:00-10:00&lt;br /&gt;
| Invited Talk II&lt;br /&gt;
|-&lt;br /&gt;
| Thu&lt;br /&gt;
| 10:00-10:30&lt;br /&gt;
| Discussion and break&lt;br /&gt;
|-&lt;br /&gt;
| Thu&lt;br /&gt;
| 10:30-11:15&lt;br /&gt;
| Hands-on: Using visualization tools to analyze simulations of previous evening session (BH mass and area, GWs, conserved TOV mass, TOV density profiles, advanced: convergence factor)&lt;br /&gt;
| Tanja, Roland, Frank&lt;br /&gt;
|-&lt;br /&gt;
| Thu&lt;br /&gt;
| 11:15-12:00&lt;br /&gt;
| Create movie of either BH+GW or TOV oscillations using VisIt&lt;br /&gt;
| Tanja, Roland&lt;br /&gt;
|-&lt;br /&gt;
| Thu&lt;br /&gt;
| 12:00-13:00&lt;br /&gt;
| Lunch&lt;br /&gt;
|-&lt;br /&gt;
| Thu&lt;br /&gt;
| 13:00-13:30&lt;br /&gt;
| Introduction to Cactus (high-level)&lt;br /&gt;
| Frank&lt;br /&gt;
|-&lt;br /&gt;
| Thu&lt;br /&gt;
| 13:30-14:15&lt;br /&gt;
| Introduction on Cactus Thorn-Writing (lower level)&lt;br /&gt;
| Roland, Frank, Josh&lt;br /&gt;
|-&lt;br /&gt;
| Thu&lt;br /&gt;
| 14:15-15:15&lt;br /&gt;
| Hands-on: Implement your own thorn (some analysis routine - ideas?), and visualize it, in teams of about 5 people&lt;br /&gt;
| Roland (proposal: NS tracker that tracks the center of mass of a region with density above threshold not further than X units from the last known position. This can be used to get smooth tracking of multiple NS. Requires use of grid functions, grid scalars, reduction interface.)&lt;br /&gt;
|-&lt;br /&gt;
| Thu&lt;br /&gt;
| 15:15-15:45&lt;br /&gt;
| Discussion and break&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
| Thu&lt;br /&gt;
| 15:45-16:30&lt;br /&gt;
| Hands-on: continuation&lt;br /&gt;
| Frank&lt;br /&gt;
|-&lt;br /&gt;
| Thu&lt;br /&gt;
| 16:30-17:30&lt;br /&gt;
| Presentation of visualization of result of previous session, 3-5 min per team.&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
| Fri&lt;br /&gt;
| 08:00-09:00&lt;br /&gt;
| Tour through available ET components&lt;br /&gt;
| Frank, Josh&lt;br /&gt;
|-&lt;br /&gt;
| Fri&lt;br /&gt;
| 09:00-10:00&lt;br /&gt;
| Invited talk III&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
| Fri&lt;br /&gt;
| 10:00-10:30&lt;br /&gt;
| Discussion and break&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
| Fri&lt;br /&gt;
| 10:30-11:15&lt;br /&gt;
| Overview over supercomputing resources, introduction on how to get accounts / allocations, trends in HPC, reminder how to get ET help in the future&lt;br /&gt;
| Frank, Josh&lt;br /&gt;
|-&lt;br /&gt;
| Fri&lt;br /&gt;
| 11:15-12:00&lt;br /&gt;
| The future of the ET: everything we didn&amp;#039;t talk about (EOSs, refluxing, multiblock, MHD, radiation ect.)&lt;br /&gt;
| Frank, Josh&lt;br /&gt;
|}&lt;/div&gt;</summary>
		<author><name>Bmundim</name></author>
		
	</entry>
	<entry>
		<id>https://docs.einsteintoolkit.org/et-docs/index.php?title=Introduction_to_General_Relativity&amp;diff=3058</id>
		<title>Introduction to General Relativity</title>
		<link rel="alternate" type="text/html" href="https://docs.einsteintoolkit.org/et-docs/index.php?title=Introduction_to_General_Relativity&amp;diff=3058"/>
		<updated>2012-02-27T10:56:56Z</updated>

		<summary type="html">&lt;p&gt;Bmundim: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;* Prerelativity physics and notion of space and time.&lt;br /&gt;
* Spacetime Metric and geometry.&lt;br /&gt;
* Manifolds, vectors, tensors.&lt;br /&gt;
* Derivative operators.&lt;br /&gt;
* Curvature.&lt;br /&gt;
* Geodesics.&lt;br /&gt;
* Einstein&amp;#039;s equation.&lt;br /&gt;
* Schwarzschild solution (at least in two different coordinates).&lt;br /&gt;
* Linearized gravity.&lt;br /&gt;
* Gravitational radiation.&lt;br /&gt;
* Stress-energy-momentum tensor.&lt;br /&gt;
** scalar field.&lt;br /&gt;
** electromagnetic field.&lt;br /&gt;
** perfect fluid.&lt;br /&gt;
** GRMHD.&lt;br /&gt;
* etc...&lt;/div&gt;</summary>
		<author><name>Bmundim</name></author>
		
	</entry>
	<entry>
		<id>https://docs.einsteintoolkit.org/et-docs/index.php?title=Introduction_numerical_methods&amp;diff=3057</id>
		<title>Introduction numerical methods</title>
		<link rel="alternate" type="text/html" href="https://docs.einsteintoolkit.org/et-docs/index.php?title=Introduction_numerical_methods&amp;diff=3057"/>
		<updated>2012-02-27T10:54:07Z</updated>

		<summary type="html">&lt;p&gt;Bmundim: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;* 3+1 spacetime decomposition&lt;br /&gt;
* BSSN formalism&lt;br /&gt;
* BHB: puncture initial data&lt;br /&gt;
* Method of lines&lt;br /&gt;
* Finite discretization approximation&lt;br /&gt;
* Conservation laws&lt;br /&gt;
* Finite volume techniques&lt;br /&gt;
* High resolution shock capturing&lt;br /&gt;
* etc...&lt;/div&gt;</summary>
		<author><name>Bmundim</name></author>
		
	</entry>
	<entry>
		<id>https://docs.einsteintoolkit.org/et-docs/index.php?title=Introduction_to_General_Relativity&amp;diff=3056</id>
		<title>Introduction to General Relativity</title>
		<link rel="alternate" type="text/html" href="https://docs.einsteintoolkit.org/et-docs/index.php?title=Introduction_to_General_Relativity&amp;diff=3056"/>
		<updated>2012-02-27T10:49:15Z</updated>

		<summary type="html">&lt;p&gt;Bmundim: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;* Prerelativity physics and notion of space and time.&lt;br /&gt;
* Spacetime Metric and geometry.&lt;br /&gt;
* Manifolds, vectors, tensors.&lt;br /&gt;
* Derivative operators.&lt;br /&gt;
* Curvature.&lt;br /&gt;
* Geodesics.&lt;br /&gt;
* Einstein&amp;#039;s equation.&lt;br /&gt;
* Schwarzschild solution (at least in two different coordinates).&lt;br /&gt;
* Linearized gravity.&lt;br /&gt;
* Gravitational radiation.&lt;br /&gt;
* etc...&lt;/div&gt;</summary>
		<author><name>Bmundim</name></author>
		
	</entry>
	<entry>
		<id>https://docs.einsteintoolkit.org/et-docs/index.php?title=Introduction_to_General_Relativity&amp;diff=3055</id>
		<title>Introduction to General Relativity</title>
		<link rel="alternate" type="text/html" href="https://docs.einsteintoolkit.org/et-docs/index.php?title=Introduction_to_General_Relativity&amp;diff=3055"/>
		<updated>2012-02-27T10:44:45Z</updated>

		<summary type="html">&lt;p&gt;Bmundim: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;test&lt;/div&gt;</summary>
		<author><name>Bmundim</name></author>
		
	</entry>
	<entry>
		<id>https://docs.einsteintoolkit.org/et-docs/index.php?title=Schedule_Proposal&amp;diff=3054</id>
		<title>Schedule Proposal</title>
		<link rel="alternate" type="text/html" href="https://docs.einsteintoolkit.org/et-docs/index.php?title=Schedule_Proposal&amp;diff=3054"/>
		<updated>2012-02-27T10:44:30Z</updated>

		<summary type="html">&lt;p&gt;Bmundim: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Volunteers to head sessions, please add your name to those sessions you &amp;#039;&amp;#039;could&amp;#039;&amp;#039; head and indicate those you &amp;#039;&amp;#039;prefer&amp;#039;&amp;#039; to head by an * by your name.&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot; border=&amp;quot;1&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
| Day&lt;br /&gt;
| Time&lt;br /&gt;
| Activity&lt;br /&gt;
| Volunteers&lt;br /&gt;
|-&lt;br /&gt;
| Tue&lt;br /&gt;
| 16:00-17:30&lt;br /&gt;
| Setup for early birds&lt;br /&gt;
| Tanja, Roland, Frank&lt;br /&gt;
|-&lt;br /&gt;
| Wed&lt;br /&gt;
| 08:00-08:30&lt;br /&gt;
| Setup for late birds&lt;br /&gt;
| Tanja, Roland, Frank&lt;br /&gt;
|-&lt;br /&gt;
| Wed&lt;br /&gt;
| 08:30-09:00&lt;br /&gt;
| Opening, Introduction&lt;br /&gt;
| Frank&lt;br /&gt;
|-&lt;br /&gt;
| Wed&lt;br /&gt;
| 09:00-10:00&lt;br /&gt;
| Invited Talk I&lt;br /&gt;
|-&lt;br /&gt;
| Wed&lt;br /&gt;
| 10:00-10:30&lt;br /&gt;
| Discussion and break&lt;br /&gt;
|-&lt;br /&gt;
| Wed&lt;br /&gt;
| 10:30-11:15&lt;br /&gt;
| [[Introduction to General Relativity]]&lt;br /&gt;
| Bruno, Tanja, Frank, Josh&lt;br /&gt;
|-&lt;br /&gt;
| Wed&lt;br /&gt;
| 11:15-12:00&lt;br /&gt;
| Introduction to Scientific Software &amp;amp; HPC&lt;br /&gt;
| Frank&lt;br /&gt;
|-&lt;br /&gt;
| Wed&lt;br /&gt;
| 12:00-13:00&lt;br /&gt;
| Lunch break&lt;br /&gt;
|-&lt;br /&gt;
| Wed&lt;br /&gt;
| 13:00-13:30&lt;br /&gt;
| Introduction to Workshop development environment&lt;br /&gt;
| Dennis&lt;br /&gt;
|-&lt;br /&gt;
| Wed&lt;br /&gt;
| 13:30-14:15&lt;br /&gt;
| Hands-on, provided Wave-Equation example within Cactus&lt;br /&gt;
| Tanja, Roland, Frank&lt;br /&gt;
|-&lt;br /&gt;
| Wed&lt;br /&gt;
| 14:15-15:15&lt;br /&gt;
| [[Introduction numerical methods &amp;amp; numerical Relativity]]&lt;br /&gt;
| Tanja, Bruno, Frank, Josh&lt;br /&gt;
|-&lt;br /&gt;
| Wed&lt;br /&gt;
| 15:15-15:45&lt;br /&gt;
| Discussion and break&lt;br /&gt;
|-&lt;br /&gt;
| Wed&lt;br /&gt;
| 15:45-17:30&lt;br /&gt;
| Running and extending (par-file) of two provided examples: perturbed, single BH, and perturbed, single TOV star&lt;br /&gt;
| Tanja, Roland, Frank, Josh&lt;br /&gt;
|-&lt;br /&gt;
| Thu&lt;br /&gt;
| 08:00-09:00&lt;br /&gt;
| Introduction in Scientific visualization - a bit of theory and a lot of practice&lt;br /&gt;
| Tanja, Roland, Frank&lt;br /&gt;
|-&lt;br /&gt;
| Thu&lt;br /&gt;
| 09:00-10:00&lt;br /&gt;
| Invited Talk II&lt;br /&gt;
|-&lt;br /&gt;
| Thu&lt;br /&gt;
| 10:00-10:30&lt;br /&gt;
| Discussion and break&lt;br /&gt;
|-&lt;br /&gt;
| Thu&lt;br /&gt;
| 10:30-11:15&lt;br /&gt;
| Hands-on: Using visualization tools to analyze simulations of previous evening session (BH mass and area, GWs, conserved TOV mass, TOV density profiles, advanced: convergence factor)&lt;br /&gt;
| Tanja, Roland, Frank&lt;br /&gt;
|-&lt;br /&gt;
| Thu&lt;br /&gt;
| 11:15-12:00&lt;br /&gt;
| Create movie of either BH+GW or TOV oscillations using VisIt&lt;br /&gt;
| Tanja, Roland&lt;br /&gt;
|-&lt;br /&gt;
| Thu&lt;br /&gt;
| 12:00-13:00&lt;br /&gt;
| Lunch&lt;br /&gt;
|-&lt;br /&gt;
| Thu&lt;br /&gt;
| 13:00-13:30&lt;br /&gt;
| Introduction to Cactus (high-level)&lt;br /&gt;
| Frank&lt;br /&gt;
|-&lt;br /&gt;
| Thu&lt;br /&gt;
| 13:30-14:15&lt;br /&gt;
| Introduction on Cactus Thorn-Writing (lower level)&lt;br /&gt;
| Roland, Frank, Josh&lt;br /&gt;
|-&lt;br /&gt;
| Thu&lt;br /&gt;
| 14:15-15:15&lt;br /&gt;
| Hands-on: Implement your own thorn (some analysis routine - ideas?), and visualize it, in teams of about 5 people&lt;br /&gt;
| Roland (proposal: NS tracker that tracks the center of mass of a region with density above threshold not further than X units from the last known position. This can be used to get smooth tracking of multiple NS. Requires use of grid functions, grid scalars, reduction interface.)&lt;br /&gt;
|-&lt;br /&gt;
| Thu&lt;br /&gt;
| 15:15-15:45&lt;br /&gt;
| Discussion and break&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
| Thu&lt;br /&gt;
| 15:45-16:30&lt;br /&gt;
| Hands-on: continuation&lt;br /&gt;
| Frank&lt;br /&gt;
|-&lt;br /&gt;
| Thu&lt;br /&gt;
| 16:30-17:30&lt;br /&gt;
| Presentation of visualization of result of previous session, 3-5 min per team.&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
| Fri&lt;br /&gt;
| 08:00-09:00&lt;br /&gt;
| Tour through available ET components&lt;br /&gt;
| Frank, Josh&lt;br /&gt;
|-&lt;br /&gt;
| Fri&lt;br /&gt;
| 09:00-10:00&lt;br /&gt;
| Invited talk III&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
| Fri&lt;br /&gt;
| 10:00-10:30&lt;br /&gt;
| Discussion and break&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
| Fri&lt;br /&gt;
| 10:30-11:15&lt;br /&gt;
| Overview over supercomputing resources, introduction on how to get accounts / allocations, trends in HPC, reminder how to get ET help in the future&lt;br /&gt;
| Frank, Josh&lt;br /&gt;
|-&lt;br /&gt;
| Fri&lt;br /&gt;
| 11:15-12:00&lt;br /&gt;
| The future of the ET: everything we didn&amp;#039;t talk about (EOSs, refluxing, multiblock, MHD, radiation ect.)&lt;br /&gt;
| Frank, Josh&lt;br /&gt;
|}&lt;/div&gt;</summary>
		<author><name>Bmundim</name></author>
		
	</entry>
	<entry>
		<id>https://docs.einsteintoolkit.org/et-docs/index.php?title=Introduction_numerical_methods&amp;diff=3053</id>
		<title>Introduction numerical methods</title>
		<link rel="alternate" type="text/html" href="https://docs.einsteintoolkit.org/et-docs/index.php?title=Introduction_numerical_methods&amp;diff=3053"/>
		<updated>2012-02-27T10:40:56Z</updated>

		<summary type="html">&lt;p&gt;Bmundim: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;* 3+1 spacetime decomposition&lt;br /&gt;
* BSSN formalism&lt;br /&gt;
* BHB: puncture initial data&lt;br /&gt;
* Method of lines&lt;br /&gt;
* Finite discretization approximation&lt;br /&gt;
* Finite volume techniques&lt;br /&gt;
* High resolution shock capturing&lt;br /&gt;
* etc...&lt;/div&gt;</summary>
		<author><name>Bmundim</name></author>
		
	</entry>
	<entry>
		<id>https://docs.einsteintoolkit.org/et-docs/index.php?title=Introduction_numerical_methods&amp;diff=3052</id>
		<title>Introduction numerical methods</title>
		<link rel="alternate" type="text/html" href="https://docs.einsteintoolkit.org/et-docs/index.php?title=Introduction_numerical_methods&amp;diff=3052"/>
		<updated>2012-02-27T10:39:37Z</updated>

		<summary type="html">&lt;p&gt;Bmundim: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;3+1 spacetime decomposition&lt;br /&gt;
BSSN formalism&lt;br /&gt;
BHB: puncture initial data&lt;br /&gt;
Method of lines&lt;br /&gt;
Finite discretization approximation&lt;br /&gt;
Finite volume techniques&lt;br /&gt;
High resolution shock capturing&lt;br /&gt;
etc...&lt;/div&gt;</summary>
		<author><name>Bmundim</name></author>
		
	</entry>
	<entry>
		<id>https://docs.einsteintoolkit.org/et-docs/index.php?title=Introduction_numerical_methods&amp;diff=3051</id>
		<title>Introduction numerical methods</title>
		<link rel="alternate" type="text/html" href="https://docs.einsteintoolkit.org/et-docs/index.php?title=Introduction_numerical_methods&amp;diff=3051"/>
		<updated>2012-02-27T10:37:56Z</updated>

		<summary type="html">&lt;p&gt;Bmundim: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;3+1 spacetime decomposition&lt;/div&gt;</summary>
		<author><name>Bmundim</name></author>
		
	</entry>
	<entry>
		<id>https://docs.einsteintoolkit.org/et-docs/index.php?title=Introduction_numerical_methods&amp;diff=3050</id>
		<title>Introduction numerical methods</title>
		<link rel="alternate" type="text/html" href="https://docs.einsteintoolkit.org/et-docs/index.php?title=Introduction_numerical_methods&amp;diff=3050"/>
		<updated>2012-02-27T10:37:17Z</updated>

		<summary type="html">&lt;p&gt;Bmundim: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Test&lt;/div&gt;</summary>
		<author><name>Bmundim</name></author>
		
	</entry>
	<entry>
		<id>https://docs.einsteintoolkit.org/et-docs/index.php?title=Introduction_numerical_methods_%26_numerical_Relativity&amp;diff=3049</id>
		<title>Introduction numerical methods &amp; numerical Relativity</title>
		<link rel="alternate" type="text/html" href="https://docs.einsteintoolkit.org/et-docs/index.php?title=Introduction_numerical_methods_%26_numerical_Relativity&amp;diff=3049"/>
		<updated>2012-02-27T10:35:59Z</updated>

		<summary type="html">&lt;p&gt;Bmundim: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;3+1 spacetime decomposition&lt;br /&gt;
BSSN formalism&lt;br /&gt;
BHB puncture initial data&lt;br /&gt;
Method of lines&lt;br /&gt;
Finite discretization approximations&lt;br /&gt;
Finite Volume techniques&lt;br /&gt;
High resolution shock capturing&lt;br /&gt;
etc...&lt;/div&gt;</summary>
		<author><name>Bmundim</name></author>
		
	</entry>
	<entry>
		<id>https://docs.einsteintoolkit.org/et-docs/index.php?title=Schedule_Proposal&amp;diff=3048</id>
		<title>Schedule Proposal</title>
		<link rel="alternate" type="text/html" href="https://docs.einsteintoolkit.org/et-docs/index.php?title=Schedule_Proposal&amp;diff=3048"/>
		<updated>2012-02-27T10:33:26Z</updated>

		<summary type="html">&lt;p&gt;Bmundim: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Volunteers to head sessions, please add your name to those sessions you &amp;#039;&amp;#039;could&amp;#039;&amp;#039; head and indicate those you &amp;#039;&amp;#039;prefer&amp;#039;&amp;#039; to head by an * by your name.&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot; border=&amp;quot;1&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
| Day&lt;br /&gt;
| Time&lt;br /&gt;
| Activity&lt;br /&gt;
| Volunteers&lt;br /&gt;
|-&lt;br /&gt;
| Tue&lt;br /&gt;
| 16:00-17:30&lt;br /&gt;
| Setup for early birds&lt;br /&gt;
| Tanja, Roland, Frank&lt;br /&gt;
|-&lt;br /&gt;
| Wed&lt;br /&gt;
| 08:00-08:30&lt;br /&gt;
| Setup for late birds&lt;br /&gt;
| Tanja, Roland, Frank&lt;br /&gt;
|-&lt;br /&gt;
| Wed&lt;br /&gt;
| 08:30-09:00&lt;br /&gt;
| Opening, Introduction&lt;br /&gt;
| Frank&lt;br /&gt;
|-&lt;br /&gt;
| Wed&lt;br /&gt;
| 09:00-10:00&lt;br /&gt;
| Invited Talk I&lt;br /&gt;
|-&lt;br /&gt;
| Wed&lt;br /&gt;
| 10:00-10:30&lt;br /&gt;
| Discussion and break&lt;br /&gt;
|-&lt;br /&gt;
| Wed&lt;br /&gt;
| 10:30-11:15&lt;br /&gt;
| Introduction to General Relativity&lt;br /&gt;
| Bruno, Tanja, Frank, Josh&lt;br /&gt;
|-&lt;br /&gt;
| Wed&lt;br /&gt;
| 11:15-12:00&lt;br /&gt;
| Introduction to Scientific Software &amp;amp; HPC&lt;br /&gt;
| Frank&lt;br /&gt;
|-&lt;br /&gt;
| Wed&lt;br /&gt;
| 12:00-13:00&lt;br /&gt;
| Lunch break&lt;br /&gt;
|-&lt;br /&gt;
| Wed&lt;br /&gt;
| 13:00-13:30&lt;br /&gt;
| Introduction to Workshop development environment&lt;br /&gt;
| Dennis&lt;br /&gt;
|-&lt;br /&gt;
| Wed&lt;br /&gt;
| 13:30-14:15&lt;br /&gt;
| Hands-on, provided Wave-Equation example within Cactus&lt;br /&gt;
| Tanja, Roland, Frank&lt;br /&gt;
|-&lt;br /&gt;
| Wed&lt;br /&gt;
| 14:15-15:15&lt;br /&gt;
| [[Introduction numerical methods &amp;amp; numerical Relativity]]&lt;br /&gt;
| Tanja, Bruno, Frank, Josh&lt;br /&gt;
|-&lt;br /&gt;
| Wed&lt;br /&gt;
| 15:15-15:45&lt;br /&gt;
| Discussion and break&lt;br /&gt;
|-&lt;br /&gt;
| Wed&lt;br /&gt;
| 15:45-17:30&lt;br /&gt;
| Running and extending (par-file) of two provided examples: perturbed, single BH, and perturbed, single TOV star&lt;br /&gt;
| Tanja, Roland, Frank, Josh&lt;br /&gt;
|-&lt;br /&gt;
| Thu&lt;br /&gt;
| 08:00-09:00&lt;br /&gt;
| Introduction in Scientific visualization - a bit of theory and a lot of practice&lt;br /&gt;
| Tanja, Roland, Frank&lt;br /&gt;
|-&lt;br /&gt;
| Thu&lt;br /&gt;
| 09:00-10:00&lt;br /&gt;
| Invited Talk II&lt;br /&gt;
|-&lt;br /&gt;
| Thu&lt;br /&gt;
| 10:00-10:30&lt;br /&gt;
| Discussion and break&lt;br /&gt;
|-&lt;br /&gt;
| Thu&lt;br /&gt;
| 10:30-11:15&lt;br /&gt;
| Hands-on: Using visualization tools to analyze simulations of previous evening session (BH mass and area, GWs, conserved TOV mass, TOV density profiles, advanced: convergence factor)&lt;br /&gt;
| Tanja, Roland, Frank&lt;br /&gt;
|-&lt;br /&gt;
| Thu&lt;br /&gt;
| 11:15-12:00&lt;br /&gt;
| Create movie of either BH+GW or TOV oscillations using VisIt&lt;br /&gt;
| Tanja, Roland&lt;br /&gt;
|-&lt;br /&gt;
| Thu&lt;br /&gt;
| 12:00-13:00&lt;br /&gt;
| Lunch&lt;br /&gt;
|-&lt;br /&gt;
| Thu&lt;br /&gt;
| 13:00-13:30&lt;br /&gt;
| Introduction to Cactus (high-level)&lt;br /&gt;
| Frank&lt;br /&gt;
|-&lt;br /&gt;
| Thu&lt;br /&gt;
| 13:30-14:15&lt;br /&gt;
| Introduction on Cactus Thorn-Writing (lower level)&lt;br /&gt;
| Roland, Frank, Josh&lt;br /&gt;
|-&lt;br /&gt;
| Thu&lt;br /&gt;
| 14:15-15:15&lt;br /&gt;
| Hands-on: Implement your own thorn (some analysis routine - ideas?), and visualize it, in teams of about 5 people&lt;br /&gt;
| Roland (proposal: NS tracker that tracks the center of mass of a region with density above threshold not further than X units from the last known position. This can be used to get smooth tracking of multiple NS. Requires use of grid functions, grid scalars, reduction interface.)&lt;br /&gt;
|-&lt;br /&gt;
| Thu&lt;br /&gt;
| 15:15-15:45&lt;br /&gt;
| Discussion and break&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
| Thu&lt;br /&gt;
| 15:45-16:30&lt;br /&gt;
| Hands-on: continuation&lt;br /&gt;
| Frank&lt;br /&gt;
|-&lt;br /&gt;
| Thu&lt;br /&gt;
| 16:30-17:30&lt;br /&gt;
| Presentation of visualization of result of previous session, 3-5 min per team.&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
| Fri&lt;br /&gt;
| 08:00-09:00&lt;br /&gt;
| Tour through available ET components&lt;br /&gt;
| Frank, Josh&lt;br /&gt;
|-&lt;br /&gt;
| Fri&lt;br /&gt;
| 09:00-10:00&lt;br /&gt;
| Invited talk III&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
| Fri&lt;br /&gt;
| 10:00-10:30&lt;br /&gt;
| Discussion and break&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
| Fri&lt;br /&gt;
| 10:30-11:15&lt;br /&gt;
| Overview over supercomputing resources, introduction on how to get accounts / allocations, trends in HPC, reminder how to get ET help in the future&lt;br /&gt;
| Frank, Josh&lt;br /&gt;
|-&lt;br /&gt;
| Fri&lt;br /&gt;
| 11:15-12:00&lt;br /&gt;
| The future of the ET: everything we didn&amp;#039;t talk about (EOSs, refluxing, multiblock, MHD, radiation ect.)&lt;br /&gt;
| Frank, Josh&lt;br /&gt;
|}&lt;/div&gt;</summary>
		<author><name>Bmundim</name></author>
		
	</entry>
	<entry>
		<id>https://docs.einsteintoolkit.org/et-docs/index.php?title=Test_suite_results_are_unwieldy&amp;diff=2578</id>
		<title>Test suite results are unwieldy</title>
		<link rel="alternate" type="text/html" href="https://docs.einsteintoolkit.org/et-docs/index.php?title=Test_suite_results_are_unwieldy&amp;diff=2578"/>
		<updated>2011-10-14T11:37:17Z</updated>

		<summary type="html">&lt;p&gt;Bmundim: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;They consume disk space, they consume time when downloading and when copying to a remote machine. People view them as &amp;quot;unimportant&amp;quot; (when compared to source files), and are generally annoyed. What can we do about this?&lt;br /&gt;
&lt;br /&gt;
Some suggestions include:&lt;br /&gt;
* Do nothing; explain to people that test suite results are very important to ensure correctness, tell them to suffer through transmit times and ask for larger quota&lt;br /&gt;
** That&amp;#039;s not a solution.&lt;br /&gt;
* Don&amp;#039;t copy test suite results to remote machines by default; only copy them when requested&lt;br /&gt;
** This makes it more difficult to run the test suite, which should (ideally) be run every time a new executable has been created for a production run.&lt;br /&gt;
* tar/gzip test suite results to save disk space, possibly also storing them this way in the SVN repository&lt;br /&gt;
** This doesn&amp;#039;t save transmit time (since rsync already compresses), and (if used in the repository) doesn&amp;#039;t allow delta compression&lt;br /&gt;
* Combine test suite results from different source trees into a single directory (with soft links or hard links or similarly)&lt;br /&gt;
** This would be an extra step that runs after all files are there, already consuming disk space.&lt;br /&gt;
* Use HDF5 instead of ASCII&lt;br /&gt;
** Binary files are not well handled by SVN.&lt;br /&gt;
* Combine several ASCII files into one (fewer files are handled more efficiently), e.g. designing a simple ASCII container format for test cases, or even using this format in CarpetIOASCII&lt;br /&gt;
** Wouldn&amp;#039;t save disk space.&lt;br /&gt;
* Use a different ASCII format that doesn&amp;#039;t store 13 columns for 1 data field&lt;br /&gt;
** Maybe we could use the ygraph format?&lt;br /&gt;
* BCM: Separate the test suite results (data) from the source tree.&lt;br /&gt;
** This allows a unified management of the data: when to check it out, when to sync it to a remote machine, etc. &lt;br /&gt;
** The user could choose not to checkout the data if she has a laptop with very little hard drive space left, for example.&lt;br /&gt;
** The test suite data could be laid out similarly to the source tree: ./Cactus/arrangements/ARRANGEMENTNAME/THORNNAME ==&amp;gt; ./Cactus/testsuites/ARRANGEMENTNAME/THORNNAME&lt;/div&gt;</summary>
		<author><name>Bmundim</name></author>
		
	</entry>
	<entry>
		<id>https://docs.einsteintoolkit.org/et-docs/index.php?title=Test_suite_results_are_unwieldy&amp;diff=2577</id>
		<title>Test suite results are unwieldy</title>
		<link rel="alternate" type="text/html" href="https://docs.einsteintoolkit.org/et-docs/index.php?title=Test_suite_results_are_unwieldy&amp;diff=2577"/>
		<updated>2011-10-14T11:36:53Z</updated>

		<summary type="html">&lt;p&gt;Bmundim: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;They consume disk space, they consume time when downloading and when copying to a remote machine. People view them as &amp;quot;unimportant&amp;quot; (when compared to source files), and are generally annoyed. What can we do about this?&lt;br /&gt;
&lt;br /&gt;
Some suggestions include:&lt;br /&gt;
* Do nothing; explain to people that test suite results are very important to ensure correctness, tell them to suffer through transmit times and ask for larger quota&lt;br /&gt;
** That&amp;#039;s not a solution.&lt;br /&gt;
* Con&amp;#039;t copy test suite results to remote machines by default; only copy them when requested&lt;br /&gt;
** This makes it more difficult to run the test suite, which should (ideally) be run every time a new executable has been created for a production run.&lt;br /&gt;
* tar/gzip test suite results to save disk space, possibly also storing them this way in the SVN repository&lt;br /&gt;
** This doesn&amp;#039;t save transmit time (since rsync already compresses), and (if used in the repository) doesn&amp;#039;t allow delta compression&lt;br /&gt;
* Combine test suite results from different source trees into a single directory (with soft links or hard links or similarly)&lt;br /&gt;
** This would be an extra step that runs after all files are there, already consuming disk space.&lt;br /&gt;
* Use HDF5 instead of ASCII&lt;br /&gt;
** Binary files are not well handled by SVN.&lt;br /&gt;
* Combine several ASCII files into one (fewer files are handled more efficiently), e.g. designing a simple ASCII container format for test cases, or even using this format in CarpetIOASCII&lt;br /&gt;
** Wouldn&amp;#039;t save disk space.&lt;br /&gt;
* Use a different ASCII format that doesn&amp;#039;t store 13 columns for 1 data field&lt;br /&gt;
** Maybe we could use the ygraph format?&lt;br /&gt;
* BCM: Separate the test suite results (data) from the source tree.&lt;br /&gt;
** This allows a unified management of the data: when to check it out, when to sync it to a remote machine, etc. &lt;br /&gt;
** The user could choose not to checkout the data if she has a laptop with very little hard drive space left, for example.&lt;br /&gt;
** The test suite data could be laid out similarly to the source tree: ./Cactus/arrangements/ARRANGEMENTNAME/THORNNAME ==&amp;gt; ./Cactus/testsuites/ARRANGEMENTNAME/THORNNAME&lt;/div&gt;</summary>
		<author><name>Bmundim</name></author>
		
	</entry>
	<entry>
		<id>https://docs.einsteintoolkit.org/et-docs/index.php?title=ET_Workshop_Spring_2011&amp;diff=2313</id>
		<title>ET Workshop Spring 2011</title>
		<link rel="alternate" type="text/html" href="https://docs.einsteintoolkit.org/et-docs/index.php?title=ET_Workshop_Spring_2011&amp;diff=2313"/>
		<updated>2011-04-27T00:22:01Z</updated>

		<summary type="html">&lt;p&gt;Bmundim: /* Suggested close by restaurants */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;= Welcome to the Einstein Toolkit Spring workshop =&lt;br /&gt;
&lt;br /&gt;
This workshop is focussed on improving the hydrodynamics of the ET: &amp;#039;&amp;#039;&amp;#039;GRHydro&amp;#039;&amp;#039;&amp;#039;.&lt;br /&gt;
&lt;br /&gt;
=== Program ===&lt;br /&gt;
&lt;br /&gt;
&amp;#039;&amp;#039;&amp;#039;Tue 04/26&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
&lt;br /&gt;
14:00 - 17:00 First Session&lt;br /&gt;
&lt;br /&gt;
: - Welcome, introductions (lead: Ott) &lt;br /&gt;
&lt;br /&gt;
: - Setting goals for the workshop (lead: Ott)&lt;br /&gt;
&lt;br /&gt;
: - Status of the EinsteinToolkit and the EinsteinToolkit paper (lead: Loeffler)&lt;br /&gt;
&lt;br /&gt;
: - Status of the CIGR project (discussion, lead: Schnetter, Ott)&lt;br /&gt;
&lt;br /&gt;
: - Goals for ET and CIGR in the next 3 months&lt;br /&gt;
&lt;br /&gt;
: - Status report: MHD (Faber, Mundim)&lt;br /&gt;
&lt;br /&gt;
: - Status report: Microphysics and EOS (Ott)&lt;br /&gt;
&lt;br /&gt;
: - Status report: Refluxing (Schnetter)&lt;br /&gt;
&lt;br /&gt;
: - Status report: BHNS initial data project (Haas, Loeffler, Mundim, Bode)&lt;br /&gt;
&lt;br /&gt;
: - Status of other projects within CIGR/ET (anybody doing anything related)&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&amp;#039;&amp;#039;&amp;#039;Wed 04/27&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
&lt;br /&gt;
09:00 - 12:00 Hands on coding/testing 1 (TBD)&lt;br /&gt;
&lt;br /&gt;
14:00 - 15:00 An overview of the Caltech-Cornell-CITA-WSU code SpEC (Szylagyi)&lt;br /&gt;
&lt;br /&gt;
15:00 - 17:00 Hands on coding/testing 2 (TBD)&lt;br /&gt;
&lt;br /&gt;
19:00 Workshop dinner (TBD)&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&amp;#039;&amp;#039;&amp;#039;Thu 04/28&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
&lt;br /&gt;
09:00 - 12:00 Hands on coding/testing 3 (TBD)&lt;br /&gt;
&lt;br /&gt;
14:00 - 15:00 2 30 min Science talks (practice for APS? TBD)&lt;br /&gt;
&lt;br /&gt;
15:00 - 17:00 Hands on coding/testing 4 (TBD)&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&amp;#039;&amp;#039;&amp;#039;Fri 04/29&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
&lt;br /&gt;
09:00 - 11:00 Hands on coding/testing 5 (TBD)&lt;br /&gt;
&lt;br /&gt;
11:00 - 11:30 Closing discussion (lead: Ott)&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Location in Space and Time ===&lt;br /&gt;
&lt;br /&gt;
The ET Spring workshop will be held from Tue, 04/26/11 (morning; official start 2pm afternoon) - Fri, 04/29/11 (morning)&lt;br /&gt;
at the [http://maps.google.com/maps?f=q&amp;amp;source=s_q&amp;amp;hl=en&amp;amp;geocode=&amp;amp;q=caltech&amp;amp;aq=&amp;amp;sll=37.0625,-95.677068&amp;amp;sspn=66.70144,135.263672&amp;amp;ie=UTF8&amp;amp;hq=California+Institute+of+Technology&amp;amp;hnear=California+Institute+of+Technology,+1200+E+California+Blvd,+Pasadena,+Los+Angeles,+California+91125&amp;amp;ll=34.135911,-118.125609&amp;amp;spn=0.001093,0.002064&amp;amp;t=h&amp;amp;z=20&amp;amp;layer=c&amp;amp;cbll=34.135912,-118.1259&amp;amp;panoid=ohdCQ9peJ5k6yTRF0Saqwg&amp;amp;cbp=12,213.32,,0,-7.95 Cahill Center for Astronomy and Astrophysics at Caltech] and is organized&lt;br /&gt;
by [http://www.tapir.caltech.edu/ TAPIR].&lt;br /&gt;
The meeting will be in room Cahill 273.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Registration ===&lt;br /&gt;
&lt;br /&gt;
Please send an email to reisswig@tapir.caltech.edu for registration.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Accommodation ===&lt;br /&gt;
&lt;br /&gt;
You are responsible for arranging your accommodation. We recommend the [http://www.thesagamotorhotel.com/ Saga Motor Hotel] or the [http://www.vagabondinn-pasadena-hotel.com/ Vagabond Inn], which are both within&lt;br /&gt;
walking distance to Caltech.&lt;br /&gt;
Please request the &amp;#039;&amp;#039;&amp;#039;special Caltech rate&amp;#039;&amp;#039;&amp;#039;. This cannot be done online and must be booked by calling.&lt;br /&gt;
&lt;br /&gt;
: &amp;#039;&amp;#039;&amp;#039;Saga Motor Hotel&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
:: 1635 E Colorado Blvd, Pasadena, CA 91106&lt;br /&gt;
:: Phone: 626-795-0431&lt;br /&gt;
:: Caltech rate: $77+tax (single occupancy)&lt;br /&gt;
&lt;br /&gt;
: &amp;#039;&amp;#039;&amp;#039;Vagabond Inn&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
:: 1203 E. Colorado Blvd, Pasadena, CA 91106&lt;br /&gt;
:: Phone: 626-449-3170&lt;br /&gt;
:: Caltech rate: $79+tax (1-2 people)&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== From LAX to Pasadena ===&lt;br /&gt;
&lt;br /&gt;
There are many possible ways of getting from the airport to Pasadena:&lt;br /&gt;
&lt;br /&gt;
:- Taxi (~$100)&lt;br /&gt;
:- Super Shuttle (~$40)&lt;br /&gt;
:- FlyAway Bus + Metro Gold Line (~$9 in total)&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
At any terminal at LAX, you will find departure platforms for all of the above&lt;br /&gt;
transportation systems just outside the terminals.&lt;br /&gt;
&lt;br /&gt;
The FlyAway Bus + Metro is usually very convenient.&lt;br /&gt;
To get on it, just wait by the blue sign that says &amp;quot;FlyAway Busses&amp;quot;.&lt;br /&gt;
Wait until a FlyAway Bus with sign &amp;quot;Union Station&amp;quot; arrives (it departs every ~30min).&lt;br /&gt;
Jump on it and go until Union Station (its only and final destination).&lt;br /&gt;
You pay $7 upon arrival (they have change if you don&amp;#039;t exactly have $7).&lt;br /&gt;
At Union Station, go to the platform that says &amp;quot;Metro Gold Line&amp;quot;.&lt;br /&gt;
Pay $1.50 at the ticket machine (one way ticket).&lt;br /&gt;
Take the Metro Gold Line (direction &amp;quot;Sierra Madre Station&amp;quot;)&lt;br /&gt;
and exit at &amp;quot;Lake Station&amp;quot; or &amp;quot;Allen Station&amp;quot; (best for the Saga Motor Hotel).&lt;br /&gt;
Check out google maps for further info.&lt;br /&gt;
Here&amp;#039;s a link to [http://www.metro.net/around/rail/gold-line/ Metro Gold Line], including a link to this [http://socaltransport.org/tm_pub_start.php trip planer] (it also knows about FlyAway busses).&lt;br /&gt;
&lt;br /&gt;
=== Additional Information ===&lt;br /&gt;
&lt;br /&gt;
There will be coffee &amp;amp; pastries in the morning and afternoon.&lt;br /&gt;
Unfortunately, we will not be able to provide or pay for lunch/dinner.&lt;br /&gt;
&lt;br /&gt;
=== Suggested close by restaurants ===&lt;br /&gt;
&lt;br /&gt;
Bar: Lucky Baldwins&lt;br /&gt;
&lt;br /&gt;
Restaurants: My Back (?)&lt;br /&gt;
&lt;br /&gt;
=== List of participants ===&lt;br /&gt;
&lt;br /&gt;
: Frank Loeffler&lt;br /&gt;
: Roland Haas&lt;br /&gt;
: Jose Manuel Torres Chavez&lt;br /&gt;
: Maria C. Babiuc-Hamilton&lt;br /&gt;
: Erik Schnetter&lt;br /&gt;
: Bruno Coutinho Mundim&lt;br /&gt;
: Tanja Bode&lt;br /&gt;
: Joshua Faber&lt;br /&gt;
: Evan O&amp;#039;Connor&lt;br /&gt;
: Christian Ott&lt;br /&gt;
: Peter Kalmus&lt;br /&gt;
: Christian Reisswig&lt;br /&gt;
: Ernazar Abdikamalov&lt;br /&gt;
: Bela Szilagyi&lt;br /&gt;
: Peter Diener&lt;/div&gt;</summary>
		<author><name>Bmundim</name></author>
		
	</entry>
	<entry>
		<id>https://docs.einsteintoolkit.org/et-docs/index.php?title=ET_Workshop_Spring_2011&amp;diff=2312</id>
		<title>ET Workshop Spring 2011</title>
		<link rel="alternate" type="text/html" href="https://docs.einsteintoolkit.org/et-docs/index.php?title=ET_Workshop_Spring_2011&amp;diff=2312"/>
		<updated>2011-04-27T00:19:54Z</updated>

		<summary type="html">&lt;p&gt;Bmundim: /* Welcome to the Einstein Toolkit Spring workshop */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;= Welcome to the Einstein Toolkit Spring workshop =&lt;br /&gt;
&lt;br /&gt;
This workshop is focussed on improving the hydrodynamics of the ET: &amp;#039;&amp;#039;&amp;#039;GRHydro&amp;#039;&amp;#039;&amp;#039;.&lt;br /&gt;
&lt;br /&gt;
=== Program ===&lt;br /&gt;
&lt;br /&gt;
&amp;#039;&amp;#039;&amp;#039;Tue 04/26&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
&lt;br /&gt;
14:00 - 17:00 First Session&lt;br /&gt;
&lt;br /&gt;
: - Welcome, introductions (lead: Ott) &lt;br /&gt;
&lt;br /&gt;
: - Setting goals for the workshop (lead: Ott)&lt;br /&gt;
&lt;br /&gt;
: - Status of the EinsteinToolkit and the EinsteinToolkit paper (lead: Loeffler)&lt;br /&gt;
&lt;br /&gt;
: - Status of the CIGR project (discussion, lead: Schnetter, Ott)&lt;br /&gt;
&lt;br /&gt;
: - Goals for ET and CIGR in the next 3 months&lt;br /&gt;
&lt;br /&gt;
: - Status report: MHD (Faber, Mundim)&lt;br /&gt;
&lt;br /&gt;
: - Status report: Microphysics and EOS (Ott)&lt;br /&gt;
&lt;br /&gt;
: - Status report: Refluxing (Schnetter)&lt;br /&gt;
&lt;br /&gt;
: - Status report: BHNS initial data project (Haas, Loeffler, Mundim, Bode)&lt;br /&gt;
&lt;br /&gt;
: - Status of other projects within CIGR/ET (anybody doing anything related)&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&amp;#039;&amp;#039;&amp;#039;Wed 04/27&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
&lt;br /&gt;
09:00 - 12:00 Hands on coding/testing 1 (TBD)&lt;br /&gt;
&lt;br /&gt;
14:00 - 15:00 An overview of the Caltech-Cornell-CITA-WSU code SpEC (Szylagyi)&lt;br /&gt;
&lt;br /&gt;
15:00 - 17:00 Hands on coding/testing 2 (TBD)&lt;br /&gt;
&lt;br /&gt;
19:00 Workshop dinner (TBD)&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&amp;#039;&amp;#039;&amp;#039;Thu 04/28&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
&lt;br /&gt;
09:00 - 12:00 Hands on coding/testing 3 (TBD)&lt;br /&gt;
&lt;br /&gt;
14:00 - 15:00 2 30 min Science talks (practice for APS? TBD)&lt;br /&gt;
&lt;br /&gt;
15:00 - 17:00 Hands on coding/testing 4 (TBD)&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&amp;#039;&amp;#039;&amp;#039;Fri 04/29&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
&lt;br /&gt;
09:00 - 11:00 Hands on coding/testing 5 (TBD)&lt;br /&gt;
&lt;br /&gt;
11:00 - 11:30 Closing discussion (lead: Ott)&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Location in Space and Time ===&lt;br /&gt;
&lt;br /&gt;
The ET Spring workshop will be held from Tue, 04/26/11 (morning; official start 2pm afternoon) - Fri, 04/29/11 (morning)&lt;br /&gt;
at the [http://maps.google.com/maps?f=q&amp;amp;source=s_q&amp;amp;hl=en&amp;amp;geocode=&amp;amp;q=caltech&amp;amp;aq=&amp;amp;sll=37.0625,-95.677068&amp;amp;sspn=66.70144,135.263672&amp;amp;ie=UTF8&amp;amp;hq=California+Institute+of+Technology&amp;amp;hnear=California+Institute+of+Technology,+1200+E+California+Blvd,+Pasadena,+Los+Angeles,+California+91125&amp;amp;ll=34.135911,-118.125609&amp;amp;spn=0.001093,0.002064&amp;amp;t=h&amp;amp;z=20&amp;amp;layer=c&amp;amp;cbll=34.135912,-118.1259&amp;amp;panoid=ohdCQ9peJ5k6yTRF0Saqwg&amp;amp;cbp=12,213.32,,0,-7.95 Cahill Center for Astronomy and Astrophysics at Caltech] and is organized&lt;br /&gt;
by [http://www.tapir.caltech.edu/ TAPIR].&lt;br /&gt;
The meeting will be in room Cahill 273.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Registration ===&lt;br /&gt;
&lt;br /&gt;
Please send an email to reisswig@tapir.caltech.edu for registration.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Accommodation ===&lt;br /&gt;
&lt;br /&gt;
You are responsible for arranging your accommodation. We recommend the [http://www.thesagamotorhotel.com/ Saga Motor Hotel] or the [http://www.vagabondinn-pasadena-hotel.com/ Vagabond Inn], which are both within&lt;br /&gt;
walking distance to Caltech.&lt;br /&gt;
Please request the &amp;#039;&amp;#039;&amp;#039;special Caltech rate&amp;#039;&amp;#039;&amp;#039;. This cannot be done online and must be booked by calling.&lt;br /&gt;
&lt;br /&gt;
: &amp;#039;&amp;#039;&amp;#039;Saga Motor Hotel&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
:: 1635 E Colorado Blvd, Pasadena, CA 91106&lt;br /&gt;
:: Phone: 626-795-0431&lt;br /&gt;
:: Caltech rate: $77+tax (single occupancy)&lt;br /&gt;
&lt;br /&gt;
: &amp;#039;&amp;#039;&amp;#039;Vagabond Inn&amp;#039;&amp;#039;&amp;#039;&lt;br /&gt;
:: 1203 E. Colorado Blvd, Pasadena, CA 91106&lt;br /&gt;
:: Phone: 626-449-3170&lt;br /&gt;
:: Caltech rate: $79+tax (1-2 people)&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== From LAX to Pasadena ===&lt;br /&gt;
&lt;br /&gt;
There are many possible ways of getting from the airport to Pasadena:&lt;br /&gt;
&lt;br /&gt;
:- Taxi (~$100)&lt;br /&gt;
:- Super Shuttle (~$40)&lt;br /&gt;
:- FlyAway Bus + Metro Gold Line (~$9 in total)&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
At any terminal at LAX, you will find departure platforms for all of the above&lt;br /&gt;
transportation systems just outside the terminals.&lt;br /&gt;
&lt;br /&gt;
The FlyAway Bus + Metro is usually very convenient.&lt;br /&gt;
To get on it, just wait by the blue sign that says &amp;quot;FlyAway Busses&amp;quot;.&lt;br /&gt;
Wait until a FlyAway Bus with sign &amp;quot;Union Station&amp;quot; arrives (it departs every ~30min).&lt;br /&gt;
Jump on it and go until Union Station (its only and final destination).&lt;br /&gt;
You pay $7 upon arrival (they have change if you don&amp;#039;t exactly have $7).&lt;br /&gt;
At Union Station, go to the platform that says &amp;quot;Metro Gold Line&amp;quot;.&lt;br /&gt;
Pay $1.50 at the ticket machine (one way ticket).&lt;br /&gt;
Take the Metro Gold Line (direction &amp;quot;Sierra Madre Station&amp;quot;)&lt;br /&gt;
and exit at &amp;quot;Lake Station&amp;quot; or &amp;quot;Allen Station&amp;quot; (best for the Saga Motor Hotel).&lt;br /&gt;
Check out google maps for further info.&lt;br /&gt;
Here&amp;#039;s a link to [http://www.metro.net/around/rail/gold-line/ Metro Gold Line], including a link to this [http://socaltransport.org/tm_pub_start.php trip planer] (it also knows about FlyAway busses).&lt;br /&gt;
&lt;br /&gt;
=== Additional Information ===&lt;br /&gt;
&lt;br /&gt;
There will be coffee &amp;amp; pastries in the morning and afternoon.&lt;br /&gt;
Unfortunately, we will not be able to provide or pay for lunch/dinner.&lt;br /&gt;
&lt;br /&gt;
=== Suggested close by restaurants ===&lt;br /&gt;
&lt;br /&gt;
=== List of participants ===&lt;br /&gt;
&lt;br /&gt;
: Frank Loeffler&lt;br /&gt;
: Roland Haas&lt;br /&gt;
: Jose Manuel Torres Chavez&lt;br /&gt;
: Maria C. Babiuc-Hamilton&lt;br /&gt;
: Erik Schnetter&lt;br /&gt;
: Bruno Coutinho Mundim&lt;br /&gt;
: Tanja Bode&lt;br /&gt;
: Joshua Faber&lt;br /&gt;
: Evan O&amp;#039;Connor&lt;br /&gt;
: Christian Ott&lt;br /&gt;
: Peter Kalmus&lt;br /&gt;
: Christian Reisswig&lt;br /&gt;
: Ernazar Abdikamalov&lt;br /&gt;
: Bela Szilagyi&lt;br /&gt;
: Peter Diener&lt;/div&gt;</summary>
		<author><name>Bmundim</name></author>
		
	</entry>
	<entry>
		<id>https://docs.einsteintoolkit.org/et-docs/index.php?title=Getting_Started_for_Cactus_Experts&amp;diff=2293</id>
		<title>Getting Started for Cactus Experts</title>
		<link rel="alternate" type="text/html" href="https://docs.einsteintoolkit.org/et-docs/index.php?title=Getting_Started_for_Cactus_Experts&amp;diff=2293"/>
		<updated>2011-04-21T17:38:58Z</updated>

		<summary type="html">&lt;p&gt;Bmundim: /* Development Version */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;=Stable Version=&lt;br /&gt;
&lt;br /&gt;
Use  [https://github.com/gridaphobe/CRL/raw/ET_2011_05/GetComponents GetComponents] (the new version of GetCactus) with the Einstein Toolkit [https://svn.einsteintoolkit.org/manifest/branches/ET_2011_05/einsteintoolkit.th thornlist]. This thornlist should work on platforms supported by the Cactus team using the usual  [http://www.cactuscode.org/download/configfiles configuration files] available on the Cactus web page or with the [http://www.cct.lsu.edu/~eschnett/SimFactory Simulation Factory].&lt;br /&gt;
&lt;br /&gt;
Example parameter files are provided in the Einstein Toolkit SVN repository:&lt;br /&gt;
&lt;br /&gt;
 svn checkout https://svn.einsteintoolkit.org/cactus/EinsteinExamples/branches/ET_2011_05/par&lt;br /&gt;
&lt;br /&gt;
=Development Version=&lt;br /&gt;
&lt;br /&gt;
For those experts interested in the development (unstable) branch of the toolkit,&lt;br /&gt;
please download GetComponents at:&lt;br /&gt;
&lt;br /&gt;
 wget --no-check-certificate https://github.com/gridaphobe/CRL/raw/master/GetComponents&lt;br /&gt;
 chmod 755 GetComponents&lt;br /&gt;
&lt;br /&gt;
and checkout the Einstein Toolkit thornlist at:&lt;br /&gt;
&lt;br /&gt;
 ./GetComponents -p -a https://svn.einsteintoolkit.org/manifest/trunk/einsteintoolkit.th&lt;br /&gt;
&lt;br /&gt;
Problems should be directed to [mailto:users@einsteintoolkit.org users@einsteintoolkit.org] or [mailto:users@cactuscode.org users@cactuscode.org] as appropriate.&lt;/div&gt;</summary>
		<author><name>Bmundim</name></author>
		
	</entry>
	<entry>
		<id>https://docs.einsteintoolkit.org/et-docs/index.php?title=Tutorial_for_New_Users&amp;diff=2292</id>
		<title>Tutorial for New Users</title>
		<link rel="alternate" type="text/html" href="https://docs.einsteintoolkit.org/et-docs/index.php?title=Tutorial_for_New_Users&amp;diff=2292"/>
		<updated>2011-04-21T17:23:42Z</updated>

		<summary type="html">&lt;p&gt;Bmundim: /* Download, Configure, and Build */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;This section provides a simple guide for compiling and running an example parameter file for the Einstein Toolkit.&lt;br /&gt;
&lt;br /&gt;
One complexity of high performance computing is the heterogeneous environments presented by different resources with different core software installations and local setups. For example, Einstein Toolkit codes require compiling with MPI and then running the resulting application in a batch queue. This complexity is hidden as much as possible in Cactus and accompanying tools such as the Simulation Factory.&lt;br /&gt;
&lt;br /&gt;
The example worked through below assumes that you are using the NSF TeraGrid resource [http://www.loni.org/systems/system.php?system=QueenBee Queen Bee]. If you don&amp;#039;t have an existing account on Queen Bee you can [http://einsteintoolkit.org/info/documentation/request request an account] to use for these examples.&lt;br /&gt;
&lt;br /&gt;
==Prepare Tools==&lt;br /&gt;
&lt;br /&gt;
On Queen Bee (qb.loni.org), the &amp;lt;tt&amp;gt;git&amp;lt;/tt&amp;gt; client may not be in your path by default. To add this type:&lt;br /&gt;
&lt;br /&gt;
 soft add +git&lt;br /&gt;
&lt;br /&gt;
Download [https://github.com/gridaphobe/CRL/raw/ET_2011_05/GetComponents GetComponents] to checkout all the components of the Einstein Toolkit, and ensure it is executable:&lt;br /&gt;
&lt;br /&gt;
 wget --no-check-certificate https://github.com/gridaphobe/CRL/raw/ET_2011_05/GetComponents &lt;br /&gt;
 chmod 755 GetComponents&lt;br /&gt;
&lt;br /&gt;
==Download, Configure, and Build==&lt;br /&gt;
&lt;br /&gt;
Checkout the Einstein Toolkit using anonymous authentication (this may take a few minutes):&lt;br /&gt;
&lt;br /&gt;
 ./GetComponents -p -a http://svn.einsteintoolkit.org/manifest/branches/ET_2011_05/einsteintoolkit.th													 &lt;br /&gt;
&lt;br /&gt;
This checks out Cactus, the Einstein Toolkit thorns, the Simulation Factory and example parameter files into a directory named Cactus.&lt;br /&gt;
&lt;br /&gt;
===Configure the Simulation Factory===&lt;br /&gt;
&lt;br /&gt;
 cd Cactus&lt;br /&gt;
 cp simfactory/udb.example.pm simfactory/udb.pm &lt;br /&gt;
 vi simfactory/udb.pm													&lt;br /&gt;
&lt;br /&gt;
Edit udb.pm and replace&lt;br /&gt;
&amp;lt;ul&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;YOUR_LOGIN with your username on Queen Bee&lt;br /&gt;
&amp;lt;li&amp;gt;YOUR@EMAIL.ADDRESS with your usual email address &lt;br /&gt;
&amp;lt;li&amp;gt;YOUR_ALLOCATION with your project allocation on Queen Bee &lt;br /&gt;
&amp;lt;/ul&amp;gt;&lt;br /&gt;
&lt;br /&gt;
===Compile Executable===&lt;br /&gt;
&lt;br /&gt;
 ./simfactory/sim build --thornlist=manifest/einsteintoolkit.th&lt;br /&gt;
&lt;br /&gt;
This may take a few minutes. You may receive an error message that building the utilities&lt;br /&gt;
failed.  This is fine as long as the main executable has been built correctly.  You can check this with the command &amp;lt;tt&amp;gt;ls exe&amp;lt;/tt&amp;gt;; if this shows a file &amp;lt;tt&amp;gt;cactus_sim&amp;lt;/tt&amp;gt;, then you are fine.)&lt;br /&gt;
&lt;br /&gt;
==Run a Simulation==&lt;br /&gt;
&lt;br /&gt;
From the Cactus directory, create a batch queue script and submit it to queue an example simulation:&lt;br /&gt;
	&lt;br /&gt;
 ./simfactory/sim create-submit static_tov --parfile=par/static_tov.par --procs=32 --walltime=8:0:0&lt;br /&gt;
&lt;br /&gt;
This parameter file sets up a static TOV star (a model of a single neutron star) with a mass of 1.4 solar masses and integrates the combined relativistic fluid dynamics and spacetime evolution equations in time. The spacetime is evolved using the BSSN 3+1 formulation of Einstein&amp;#039;s equations and the fluid is evolved using a high resolution shock capturing method.&lt;br /&gt;
&lt;br /&gt;
To check the status of the simulation, use&lt;br /&gt;
&lt;br /&gt;
 ./simfactory/sim list-simulations&lt;br /&gt;
&lt;br /&gt;
==Look at Results==&lt;br /&gt;
&lt;br /&gt;
For the following make sure that you have logged in to Queen Bee with X-forwarding enabled, i.e.&lt;br /&gt;
&lt;br /&gt;
 ssh -Y qb.loni.org&lt;br /&gt;
&lt;br /&gt;
When the simulation is complete, move to the output directory. On Queen Bee&lt;br /&gt;
(qb.loni.org) the command will be (replace &amp;lt;user&amp;gt; with your own login name):&lt;br /&gt;
&lt;br /&gt;
 cd /scratch/&amp;lt;user&amp;gt;/simulations/static_tov/output-0000/static_tov&lt;br /&gt;
&lt;br /&gt;
You should see a number of files with the extenstion  &amp;#039;&amp;#039;.asc&amp;#039;&amp;#039;. These are 0-D &lt;br /&gt;
(reductions of 3-D grid functions to scalar values) and 1-D ASCII output files that&lt;br /&gt;
can be plotted with gnuplot. &lt;br /&gt;
&lt;br /&gt;
In this case it&amp;#039;s interesting to look at the maximum of the density (in the file hydrobase::rho.maximum.asc). Start gnuplot with the command:&lt;br /&gt;
&lt;br /&gt;
 gnuplot&lt;br /&gt;
&lt;br /&gt;
and at the gnuplot prompt type:&lt;br /&gt;
&lt;br /&gt;
 p &amp;#039;hydrobase::rho.maximum.asc&amp;#039; u 2:3 w lp&lt;br /&gt;
&lt;br /&gt;
This plots the data in column 3 (rho) as a function of the data in column 2 (time).&lt;br /&gt;
&lt;br /&gt;
[[Image:rho_of_time.png]]&lt;br /&gt;
&lt;br /&gt;
As can be seen from the plot, the maximum of the density oscillates with decreasing amplitude around the initial value with a small drift upwards. Even though the initial model is supposed to be in equilibrium, numerical errors means that the numerical model is not exactly in equilibrium and it starts to oscillate. The oscillation energy is slowly dissipated by shocks, decreasing the oscillation amplitude, while the star contracts in response, increasing the maximum density.&lt;br /&gt;
&lt;br /&gt;
A consistent picture can be seen by plotting the minimum of the lapse:&lt;br /&gt;
&lt;br /&gt;
 p &amp;#039;admbase::lapse.minimum.asc&amp;#039; u 2:3 w lp&lt;br /&gt;
&lt;br /&gt;
[[Image:Lapse_of_time.png]]&lt;br /&gt;
&lt;br /&gt;
The quantity shows the same features as the maximum of the density, except the drift is downwards.  The downwards trend stems from the contraction of the star.  As the star contracts, the curvature of spacetime increases slightly.  In response, the singularity avoiding lapse condition used here decreases the lapse.&lt;br /&gt;
&lt;br /&gt;
As the oscillations and subsequent drift of the density and the lapse are caused by numerical error, increasing the numerical resolution will decrease these effects.&lt;br /&gt;
&lt;br /&gt;
==Additional Example Parameter Files==&lt;br /&gt;
&lt;br /&gt;
In addition to the TOV star parameter file, we also provide a couple of vacuum parameter files: ks-mclachlan.par and qc0-mclachlan.par.&lt;br /&gt;
The first (ks-mclachlan.par) evolves a single isolated rotating black hole with the initial data (M=1 and a/M=0.8) specified in Kerr-Schild coordinates. The second (qc0-mclachlan.par) evolves a binary black hole system using the moving puncture technique. The black holes start at a close separation and only complete about one half of an orbit before merging. You can run these additional parameter files using a similar command in the Cactus directory as for the TOV star above:&lt;br /&gt;
&lt;br /&gt;
 ./simfactory/sim create-submit ks-mclachlan --parfile=par/ks-mclachlan.par --procs=32 --walltime=8:0:0&lt;br /&gt;
&lt;br /&gt;
and&lt;br /&gt;
&lt;br /&gt;
 ./simfactory/sim create-submit qc0-mclachlan --parfile=par/qc0-mclachlan.par --procs=32 --walltime=8:0:0&lt;br /&gt;
&lt;br /&gt;
==Additional Simulation Factory Configuration==&lt;br /&gt;
&lt;br /&gt;
The example worked out above works out of the box for the Queen Bee machine.&lt;br /&gt;
You may also be interested though in configuring the Simulation Factory for your&lt;br /&gt;
own machine or other Teragrid machines. In this section we provide a quick&lt;br /&gt;
example of what need to be changed or considered in simfactory/udb.pm&lt;br /&gt;
in order to configure Simulation Factory for your needs. More specifically&lt;br /&gt;
we are going to work out an example for the TeraGrid machine Ranger.&lt;br /&gt;
&lt;br /&gt;
The first step is to set your username for the machine. This means&lt;br /&gt;
to modify simfactory/udb.pm customization section to reflect&lt;br /&gt;
&amp;#039;YOUR_LOGIN&amp;#039; on Ranger, for example:&lt;br /&gt;
&lt;br /&gt;
    set_option &amp;#039;ranger&amp;#039;, &amp;#039;user&amp;#039;,          &amp;#039;YOUR_LOGIN&amp;#039;&lt;br /&gt;
&lt;br /&gt;
You also need to provide your allocation.  For example, if your allocation&lt;br /&gt;
on Ranger is TG-PHY0123456N, just enter:&lt;br /&gt;
&lt;br /&gt;
    set_option &amp;#039;ranger&amp;#039;, &amp;#039;allocation&amp;#039;, &amp;#039;TG-PHY0123456N&amp;#039;&lt;br /&gt;
&lt;br /&gt;
Each machine has different policies on which file system to use to build&lt;br /&gt;
your application and run your simulation or how the file system tree&lt;br /&gt;
is organized. Simulation Factory keeps a database for several different&lt;br /&gt;
machines. You can peek at simfactory/mdb.pm to have an idea of the list&lt;br /&gt;
of machines and what the default configuration is for each of them.&lt;br /&gt;
In particular for Ranger, the configuration for the source code path and&lt;br /&gt;
the simulation path defaults to &amp;#039;/work/00507/@USER@&amp;#039; and&lt;br /&gt;
&amp;#039;/scratch/00507/@USER@/simulations&amp;#039; respectively. You may need to&lt;br /&gt;
change it to reflect the group number (00507 here) you belong to.&lt;br /&gt;
For example you could just set:&lt;br /&gt;
&lt;br /&gt;
    set_option &amp;#039;ranger&amp;#039;  , &amp;#039;sourcebasedir&amp;#039;, &amp;#039;/work/05555/@USER@&amp;#039;;&lt;br /&gt;
    set_option &amp;#039;ranger&amp;#039;  , &amp;#039;basedir&amp;#039;, &amp;#039;/work/05555/@USER@/simulations&amp;#039;;&lt;br /&gt;
&lt;br /&gt;
if your group number is &amp;#039;05555&amp;#039;. With these basic changes to&lt;br /&gt;
simfactory/udb.pm, you are all set to configure and build the&lt;br /&gt;
Einstein Toolkit application on Ranger as well.&lt;br /&gt;
&lt;br /&gt;
===New machines===&lt;br /&gt;
&lt;br /&gt;
Instead of using one of the existing configurations you might want to add&lt;br /&gt;
a configuration for a new machine. udb.example.pm contains an example for&lt;br /&gt;
such an entry: udb_generic. You can either copy this entry and configure it&lt;br /&gt;
as you like, or configure this directly. Below this entry is used to add a&lt;br /&gt;
new machine to the machine database like this:&lt;br /&gt;
&lt;br /&gt;
    $mdb::machine_database{&amp;#039;redshift&amp;#039;} = $udb_generic;&lt;br /&gt;
&lt;br /&gt;
where you can replace &amp;#039;redshift&amp;#039; my your machine name.    Once this is done, you&lt;br /&gt;
can (&amp;#039;&amp;#039;&amp;#039;must?&amp;#039;&amp;#039;&amp;#039;) set various options (nickname, hostname, user, basedir, etc.) for this new&lt;br /&gt;
machine as above.   The generic configuration is supported by a generic optionlist (see &amp;lt;tt&amp;gt; simfactory/optionlists/generic.cfg &amp;lt;/tt&amp;gt;).  These examples require several settings unavailable in that default configuration.  You will need to customize an optionlist and set it, either in udb.pm as&lt;br /&gt;
    set_option &amp;#039;redshift&amp;#039;, &amp;#039;optionlist&amp;#039;,  &amp;#039;optionlistname.cfg&amp;#039;&lt;br /&gt;
or on the command-line; see the [https://svn.cct.lsu.edu/repos/numrel/simfactory/doc/simfactory.pdf simfactory documentation] for more details.&lt;br /&gt;
&lt;br /&gt;
If the machine you added is a bigger resource (e.g. more than your personal&lt;br /&gt;
laptop or workstation), or can serve as example for some particular machine type,&lt;br /&gt;
we are happy to include its configuration in the main machine database.&lt;br /&gt;
&lt;br /&gt;
If you are using Mac OS X, then [[ConfiguringMacOSX|here]] are instructions for setting it up for Cactus.&lt;br /&gt;
&lt;br /&gt;
==Using simfactory to manage simulations==&lt;br /&gt;
&lt;br /&gt;
&amp;lt;tt&amp;gt; simfactory &amp;lt;/tt&amp;gt;  is a wrapper to download, compile, and run code on available machines.  See [[Simulation_Factory_Advanced_Tutorial]] for more details.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&amp;#039;&amp;#039;FAQ&amp;#039;&amp;#039;&lt;br /&gt;
* &amp;#039;&amp;#039;What if my compile fails?&amp;#039;&amp;#039;: This can occur for example if your config file is improperly set up.&lt;br /&gt;
  cd Cactus/simfactory&lt;br /&gt;
  make sim-delete&lt;br /&gt;
&lt;br /&gt;
==Going further==&lt;br /&gt;
&lt;br /&gt;
===Development version===&lt;br /&gt;
&lt;br /&gt;
Instead of using the release version listed above, you might want the latest development version.  Proceed as above, but download from the trunk:&lt;br /&gt;
  (GetComponents from trunk)&lt;br /&gt;
  ....  -a http://svn.einsteintoolkit.org/manifest/trunk/einsteintoolkit.th&lt;br /&gt;
&lt;br /&gt;
===More about Cactus===&lt;br /&gt;
The EinsteinToolkit is built on top of Cactus.  Development requires some familiarity with it.  Start reading &lt;br /&gt;
* [https://svn.cactuscode.org/tutorials/introduction/introduction.pdf Introduction to cactus]&lt;br /&gt;
* [http://cactuscode.org/documentation/tutorials/ Cactus tutorials], particularly the [http://cactuscode.org/documentation/tutorials/wavetoydemo/ WaveToy demo]&lt;br /&gt;
&lt;br /&gt;
==Any Problems?==&lt;br /&gt;
&lt;br /&gt;
This example should work smoothly on the TeraGrid machines Queen Bee, Ranger, Kraken and Abe. If you have any problems, please send details to [mailto:users@einsteintoolkit.org users@einsteintoolkit.org].&lt;/div&gt;</summary>
		<author><name>Bmundim</name></author>
		
	</entry>
	<entry>
		<id>https://docs.einsteintoolkit.org/et-docs/index.php?title=Release_Details&amp;diff=2291</id>
		<title>Release Details</title>
		<link rel="alternate" type="text/html" href="https://docs.einsteintoolkit.org/et-docs/index.php?title=Release_Details&amp;diff=2291"/>
		<updated>2011-04-21T17:13:04Z</updated>

		<summary type="html">&lt;p&gt;Bmundim: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&amp;lt;table border=&amp;quot;1&amp;quot;&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;h2&amp;gt;Tools/Links&amp;lt;/h2&amp;gt;&lt;br /&gt;
&amp;lt;ul&amp;gt;&lt;br /&gt;
 &amp;lt;li&amp;gt;The release branch name will be ET_2011_05&amp;lt;/li&amp;gt;&lt;br /&gt;
 &amp;lt;li&amp;gt;[http://einsteintoolkit.org/release-info/parse_testsuite_results.php Testsuite Status page]&lt;br /&gt;
     (add the testsuite *.log files created by scripts below to the repository at [https://svn.einsteintoolkit.org/www/release-info/] to&lt;br /&gt;
      have them automatically included)&amp;lt;/li&amp;gt;&lt;br /&gt;
 &amp;lt;li&amp;gt;Helpful scripts to compile and run testsuites in an almost automatic way can be found [http://einsteintoolkit.org/release-info/ here]&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt; Information on running the tests on different machines (some duplication with release-info page): [http://docs.einsteintoolkit.org/et-docs/Testsuite_Machines Testsuite Machines]&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;Release announcements: [[Release Announcement|short]] and [[Detailed Release Announcement|long]]&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;Release announced to: users@einsteintoolkit.org, {news|users}@cactuscode.org, Jennifer Claudet &amp;lt;jennifer@cct.lsu.edu&amp;gt; for AllCCT, http://hyperspace.aei.mpg.de/, http://astro-sim.org/&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;/ul&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;h2&amp;gt;Release Plan&amp;lt;/h2&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;table border=&amp;quot;1&amp;quot;&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;tr&amp;gt;&amp;lt;th colspan=&amp;quot;2&amp;quot;&amp;gt;Task&amp;lt;/th&amp;gt;&amp;lt;th&amp;gt;Due date&amp;lt;/th&amp;gt;&amp;lt;th&amp;gt;Responsible&amp;lt;/th&amp;gt;&amp;lt;th&amp;gt;Status&amp;lt;/th&amp;gt;&amp;lt;/tr&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;tr&amp;gt;&amp;lt;td rowspan=&amp;quot;10&amp;quot;&amp;gt;(Re)run Testsuites&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;amarok   &amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;as necessary&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;Peter &amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;?&amp;lt;/td&amp;gt;&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;                                        &amp;lt;td&amp;gt;bluedrop &amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;as necessary&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;Bruno &amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;Machine is down due to OS upgrade.&amp;lt;/td&amp;gt;&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;                                        &amp;lt;td&amp;gt;datura   &amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;as necessary&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;Ian   &amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;?&amp;lt;/td&amp;gt;&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;                                        &amp;lt;td&amp;gt;hopper   &amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;as necessary&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;Erik  &amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;?&amp;lt;/td&amp;gt;&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;                                        &amp;lt;td&amp;gt;lonestar &amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;as necessary&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;Erik  &amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;?&amp;lt;/td&amp;gt;&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;                                        &amp;lt;td&amp;gt;minkowski&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;as necessary&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;Roland&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;?&amp;lt;/td&amp;gt;&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;                                        &amp;lt;td&amp;gt;numrel   &amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;as necessary&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;Frank &amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;?&amp;lt;/td&amp;gt;&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;                                        &amp;lt;td&amp;gt;pandora  &amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;as necessary&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;Peter &amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;?&amp;lt;/td&amp;gt;&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;                                        &amp;lt;td&amp;gt;ranger   &amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;as necessary&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;Tanja &amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;?&amp;lt;/td&amp;gt;&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;                                        &amp;lt;td&amp;gt;redshift &amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;as necessary&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;Erik  &amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;?&amp;lt;/td&amp;gt;&amp;lt;/tr&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;tr&amp;gt;&amp;lt;td rowspan=&amp;quot;9&amp;quot;&amp;gt;Fix Testsuites&amp;lt;/td&amp;gt;&lt;br /&gt;
      &amp;lt;td&amp;gt;AHFinderDirect                           &amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;Apr 11&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;Peter        &amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;√&amp;lt;/td&amp;gt;&amp;lt;/tr&amp;gt;&lt;br /&gt;
  &amp;lt;tr&amp;gt;&amp;lt;td&amp;gt;CarpetReduce                             &amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;Apr 11&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;Erik?        &amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;?&amp;lt;/td&amp;gt;&amp;lt;/tr&amp;gt;&lt;br /&gt;
  &amp;lt;tr&amp;gt;&amp;lt;td&amp;gt;Exact                                    &amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;Apr 11&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;Roland       &amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;?&amp;lt;/td&amp;gt;&amp;lt;/tr&amp;gt;&lt;br /&gt;
  &amp;lt;tr&amp;gt;&amp;lt;td&amp;gt;GRHydro                                  &amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;Apr 11&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;Roland       &amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;?&amp;lt;/td&amp;gt;&amp;lt;/tr&amp;gt;&lt;br /&gt;
  &amp;lt;tr&amp;gt;&amp;lt;td&amp;gt;McLachlan                                &amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;Apr 11&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;Ian          &amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;√&amp;lt;/td&amp;gt;&amp;lt;/tr&amp;gt;&lt;br /&gt;
  &amp;lt;tr&amp;gt;&amp;lt;td&amp;gt;QuasiLocalMeasures                       &amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;Apr 11&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;Peter / Frank&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;?&amp;lt;/td&amp;gt;&amp;lt;/tr&amp;gt;&lt;br /&gt;
  &amp;lt;tr&amp;gt;&amp;lt;td&amp;gt;ADM/test_ADM_2                           &amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;Apr 11&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;Peter        &amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;√&amp;lt;/td&amp;gt;&amp;lt;/tr&amp;gt;&lt;br /&gt;
  &amp;lt;tr&amp;gt;&amp;lt;td&amp;gt;RotatingSymmetry*                        &amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;Apr 11&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;Roland       &amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;√&amp;lt;/td&amp;gt;&amp;lt;/tr&amp;gt;&lt;br /&gt;
  &amp;lt;tr&amp;gt;&amp;lt;td&amp;gt;TwoPunctures                             &amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;Apr 11&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;Frank        &amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;√&amp;lt;/td&amp;gt;&amp;lt;/tr&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;tr&amp;gt;&amp;lt;td colspan=&amp;quot;2&amp;quot;&amp;gt;Check &amp;amp;amp; Improve Documentation (www, wiki)&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;Apr 11&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;everyone&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;?&amp;lt;/td&amp;gt;&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;&amp;lt;td colspan=&amp;quot;2&amp;quot;&amp;gt;Write announcement texts ([[Release Announcement|short]] and [[Detailed Release Announcement|long]])&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;Apr 11&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;Frank&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;(√), mostly ready - please add if needed&amp;lt;/td&amp;gt;&amp;lt;/tr&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;tr&amp;gt;&amp;lt;td rowspan=&amp;quot;7&amp;quot;&amp;gt;Create release branch&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;svn.einsteintoolkit.org&amp;lt;/td&amp;gt;       &amp;lt;td&amp;gt;Apr 20&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;Frank&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;?&amp;lt;/td&amp;gt;&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;                                          &amp;lt;td&amp;gt;svn.cactuscode.org     &amp;lt;/td&amp;gt;       &amp;lt;td&amp;gt;Apr 20&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;Frank&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;?&amp;lt;/td&amp;gt;&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;                                          &amp;lt;td&amp;gt;carpetcode.org         &amp;lt;/td&amp;gt;       &amp;lt;td&amp;gt;Apr 20&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;Ian  &amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;?&amp;lt;/td&amp;gt;&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;                                          &amp;lt;td&amp;gt;aei.mpg.de             &amp;lt;/td&amp;gt;       &amp;lt;td&amp;gt;Apr 20&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;Frank&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;?&amp;lt;/td&amp;gt;&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;                                          &amp;lt;td&amp;gt;svn.cct.lsu.edu        &amp;lt;/td&amp;gt;       &amp;lt;td&amp;gt;Apr 20&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;Frank&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;?&amp;lt;/td&amp;gt;&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;                                          &amp;lt;td&amp;gt;github.com/ianhinder/Kranc.git&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;Apr 20&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;Ian  &amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;?&amp;lt;/td&amp;gt;&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;tr&amp;gt;                                          &amp;lt;td&amp;gt;github.com:gridaphobe/CRL.git&amp;lt;/td&amp;gt; &amp;lt;td&amp;gt;Apr 20&amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;Eric &amp;lt;/td&amp;gt;&amp;lt;td&amp;gt;?&amp;lt;/td&amp;gt;&amp;lt;/tr&amp;gt;&lt;br /&gt;
&amp;lt;/table&amp;gt;&lt;/div&gt;</summary>
		<author><name>Bmundim</name></author>
		
	</entry>
	<entry>
		<id>https://docs.einsteintoolkit.org/et-docs/index.php?title=Release_Process&amp;diff=2290</id>
		<title>Release Process</title>
		<link rel="alternate" type="text/html" href="https://docs.einsteintoolkit.org/et-docs/index.php?title=Release_Process&amp;diff=2290"/>
		<updated>2011-04-21T16:23:12Z</updated>

		<summary type="html">&lt;p&gt;Bmundim: /* The release */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;=Release Process=&lt;br /&gt;
&lt;br /&gt;
This page describes the release process in some detail.  Getting a release out of the door without embarrassing oversights requires a bit more planning and care than one would like.&lt;br /&gt;
&lt;br /&gt;
==Long-term planning==&lt;br /&gt;
&lt;br /&gt;
A few months or weeks before the release:&lt;br /&gt;
* Decide it is time to make another release&lt;br /&gt;
* Choose features which are going to be included, and those which won&amp;#039;t be included&lt;br /&gt;
* Choose a tentative date&lt;br /&gt;
* Begin discussions on the mailing list, reminding people to look at test cases, review patches etc.&lt;br /&gt;
&lt;br /&gt;
==One or two weeks before the release==&lt;br /&gt;
* Set up a wiki planning page for the release&lt;br /&gt;
* Ask for volunteers, assign tasks to people&lt;br /&gt;
* Review thorns for code quality, documentation, test cases&lt;br /&gt;
* Decide on a thorn list&lt;br /&gt;
* Decide on a list of release-critical systems&lt;br /&gt;
* Collect list of new features, newsworthy items, and acknowledgements for release announcement on wiki&lt;br /&gt;
* Choose a concrete date&lt;br /&gt;
* Announce date publicly&lt;br /&gt;
&lt;br /&gt;
==One or two days before the release==&lt;br /&gt;
* Have a telecon with the release team, discuss (and modify if necessary) release process and responsibilities&lt;br /&gt;
* Get a list of all repositories that are involved (including repositories for tools such as GetComponents)&lt;br /&gt;
* Publicly declare a freeze on all involved thorns and tools&lt;br /&gt;
* Test all thorns on all systems, collect status reports on wiki&lt;br /&gt;
* Update release planning wiki page with peoples&amp;#039;, thorns&amp;#039;, and systems&amp;#039; statuses&lt;br /&gt;
* Set up a (smaller) technical release team who will be available all day on the day of the release&lt;br /&gt;
* Draft release announcement&lt;br /&gt;
&lt;br /&gt;
==The release==&lt;br /&gt;
* Have the technical release team meet in the same room (brick, EVO, chat, phone)&lt;br /&gt;
* Briefly re-check status of thorns and machines&lt;br /&gt;
* Possibly disable all outside write access to all critical repositories&lt;br /&gt;
* CREATE THE RELEASE BRANCH&lt;br /&gt;
* * cvs: ???&lt;br /&gt;
* * svn: &amp;lt;nowiki&amp;gt;svn copy https://&amp;lt;repository-server&amp;gt;/&amp;lt;repository-path&amp;gt;/trunk https://&amp;lt;repository-server&amp;gt;/&amp;lt;repository-path&amp;gt;/branches/ET_2011_05&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
* * darcs: clone the repository, appending a suffix to the name&lt;br /&gt;
* * git: git push origin origin:refs/heads/ET_2011_05&lt;br /&gt;
* * hg: ???&lt;br /&gt;
* Possibly update version numbers in stable/development branches&lt;br /&gt;
* Update component lists to point to new stable version&lt;br /&gt;
* Check out release branch on all systems, re-run all quick tests&lt;br /&gt;
* Update documentation on web sites (set up fresh copies of pdfs/htmls)&lt;br /&gt;
* Update tutorials on web sites (update version numbers, urls)&lt;br /&gt;
* Re-enable write access to all repositories&lt;br /&gt;
* Finalise release announcement&lt;br /&gt;
* ANNOUNCE&lt;br /&gt;
&lt;br /&gt;
==After the release==&lt;br /&gt;
* Watch mailing lists for problem reports&lt;br /&gt;
* Use released version to repeat a few production simulations&lt;br /&gt;
&lt;br /&gt;
=Helpful Tools=&lt;br /&gt;
&lt;br /&gt;
This section collects a handful of useful commands that may become critical&lt;br /&gt;
to guarantee the quality of the release. The descriptions below are quite&lt;br /&gt;
technical and intended for the developers and maintainers only.&lt;br /&gt;
&lt;br /&gt;
==Creating and working with git branches==&lt;br /&gt;
&lt;br /&gt;
Some basic git commands to create and work with branches:&lt;br /&gt;
&lt;br /&gt;
Check in your local repository which branch you are in:&lt;br /&gt;
&lt;br /&gt;
 %git branch&lt;br /&gt;
 * master&lt;br /&gt;
&lt;br /&gt;
Check the branches of your project in the remote repository:&lt;br /&gt;
&lt;br /&gt;
 %git branch -r&lt;br /&gt;
   origin/HEAD&lt;br /&gt;
   origin/master&lt;br /&gt;
&lt;br /&gt;
Create a new branch called test:&lt;br /&gt;
&lt;br /&gt;
 %git checkout -b test&lt;br /&gt;
 Switched to a new branch &amp;quot;test&amp;quot;&lt;br /&gt;
 %git branch  &lt;br /&gt;
   master&lt;br /&gt;
 * test&lt;br /&gt;
&lt;br /&gt;
Work on files in that branch:&lt;br /&gt;
&lt;br /&gt;
 %vi test.txt&lt;br /&gt;
 &lt;br /&gt;
Verify the status of files you modified in that branch:&lt;br /&gt;
&lt;br /&gt;
 %git status&lt;br /&gt;
  # On branch test&lt;br /&gt;
  # Untracked files:&lt;br /&gt;
  #   (use &amp;quot;git add &amp;lt;file&amp;gt;...&amp;quot; to include in what will be committed)&lt;br /&gt;
  #&lt;br /&gt;
  #       test.txt&lt;br /&gt;
  nothing added to commit but untracked files present (use &amp;quot;git add&amp;quot; to track)&lt;br /&gt;
&lt;br /&gt;
Add the file(s) edited to the git stage area:&lt;br /&gt;
&lt;br /&gt;
 %git add test.txt&lt;br /&gt;
 %git status&lt;br /&gt;
  # On branch test&lt;br /&gt;
  # Changes to be committed:&lt;br /&gt;
  #   (use &amp;quot;git reset HEAD &amp;lt;file&amp;gt;...&amp;quot; to unstage)&lt;br /&gt;
  #&lt;br /&gt;
  #       new file:   test.txt&lt;br /&gt;
  #&lt;br /&gt;
&lt;br /&gt;
Commit your changes to your local repository:&lt;br /&gt;
&lt;br /&gt;
 %git commit -m &amp;quot;test file only&amp;quot;&lt;br /&gt;
  Created commit 14644af: test file only&lt;br /&gt;
   1 files changed, 1 insertions(+), 0 deletions(-)&lt;br /&gt;
   create mode 100644 test.txt&lt;br /&gt;
&lt;br /&gt;
Now you want to push these changes to a remote repository that you have&lt;br /&gt;
writing permission:&lt;br /&gt;
&lt;br /&gt;
 %git push origin test&lt;br /&gt;
&lt;br /&gt;
Note however that, unless git is configured so, your local branch of &amp;quot;test&amp;quot;&lt;br /&gt;
does not track any changes committed by others to the remote branch &amp;quot;test&amp;quot;. &lt;br /&gt;
Maybe the simplest way to proceed then is just to delete your local branch:&lt;br /&gt;
&lt;br /&gt;
 %git branch -D test&lt;br /&gt;
 Deleted branch test.&lt;br /&gt;
&lt;br /&gt;
and checkout the remote branch you just created but letting git know you want&lt;br /&gt;
to track remote changes to that branch as well:&lt;br /&gt;
&lt;br /&gt;
 %git checkout --track -b test origin/test&lt;br /&gt;
&lt;br /&gt;
You may want to see how two branches differ or how your modifications of the&lt;br /&gt;
branch compare to the HEAD of the branch, for example. Suppose you just&lt;br /&gt;
added the test.txt file to the staged git area called the index. To know &lt;br /&gt;
the difference between the index and the HEAD, essentially what would be &lt;br /&gt;
committed if &amp;#039;git commit&amp;#039; is issued, just use git diff as follows:&lt;br /&gt;
&lt;br /&gt;
 %git diff  --cached&lt;br /&gt;
  diff --git a/test.txt b/test.txt&lt;br /&gt;
  new file mode 100644&lt;br /&gt;
  index 0000000..373c7b0&lt;br /&gt;
  --- /dev/null&lt;br /&gt;
  +++ b/test.txt&lt;br /&gt;
  @@ -0,0 +1 @@&lt;br /&gt;
  +Hello, world!&lt;/div&gt;</summary>
		<author><name>Bmundim</name></author>
		
	</entry>
	<entry>
		<id>https://docs.einsteintoolkit.org/et-docs/index.php?title=Testsuite_Machines&amp;diff=2235</id>
		<title>Testsuite Machines</title>
		<link rel="alternate" type="text/html" href="https://docs.einsteintoolkit.org/et-docs/index.php?title=Testsuite_Machines&amp;diff=2235"/>
		<updated>2011-04-06T05:27:09Z</updated>

		<summary type="html">&lt;p&gt;Bmundim: /* BlueDrop */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;This page contains notes and instructions for people running the ET testsuites on various different machines.  If you have experience running testsuites on a machine which is not listed here, please consider adding some information which might help others (or yourself!) in future.  &lt;br /&gt;
&lt;br /&gt;
=General=&lt;br /&gt;
&lt;br /&gt;
To check out the ET:&lt;br /&gt;
&lt;br /&gt;
  mkdir etrelease&lt;br /&gt;
  cd etrelease&lt;br /&gt;
  curl -O https://github.com/gridaphobe/CRL/raw/master/GetComponents &lt;br /&gt;
  chmod a+x GetComponents&lt;br /&gt;
  ./GetComponents --root=. -a https://svn.einsteintoolkit.org/manifest/trunk/einsteintoolkit.th&lt;br /&gt;
  cp udb.example.pm udb.pm&lt;br /&gt;
&lt;br /&gt;
In udb.pm, &lt;br /&gt;
&lt;br /&gt;
* Replace &amp;quot;redshift&amp;quot; with the name of your local machine, unless you are running on one of the supported machines.&lt;br /&gt;
&lt;br /&gt;
* Replace YOUR_LOGIN, YOUR_EMAIL_ADDRESS and YOUR_ALLOCATION as appropriate.&lt;br /&gt;
&lt;br /&gt;
* Set sourcebasedir for your local machine to be the directory containing etrelease (do not set it to etrelease itself).&lt;br /&gt;
&lt;br /&gt;
* Set your username on each machine:&lt;br /&gt;
    set_option &amp;#039;MACHINE&amp;#039;  , &amp;#039;user&amp;#039;, &amp;#039;USERNAME&amp;#039;;&lt;br /&gt;
&lt;br /&gt;
See the machine-specific notes below for any additional steps for each machine.&lt;br /&gt;
&lt;br /&gt;
  touch par/testsuite.par&lt;br /&gt;
  sim sync &amp;lt;machine&amp;gt;&lt;br /&gt;
  sim build --thornlist manifest/einsteintoolkit.th --scriptfile &amp;lt;machine&amp;gt;-testsuite.sh&lt;br /&gt;
  sim remote &amp;lt;machine&amp;gt; create-submit par/testsuite.par NSLOTS 6:00:00&lt;br /&gt;
&lt;br /&gt;
This is a dummy parameter file.&lt;br /&gt;
&lt;br /&gt;
When the job is finished, you should have the required &amp;lt;machine&amp;gt;_i_j.log files in machine:etrelease/*.log.  The testsuite output will also be stored in machine:TEST_XXX, where XXX is constructed from the date at which the job was run.&lt;br /&gt;
&lt;br /&gt;
Update the testsuite status page by adding the log files to the release-info repository:&lt;br /&gt;
&lt;br /&gt;
  svn co https://svn.einsteintoolkit.org/www/release-info&lt;br /&gt;
  cd release-info&lt;br /&gt;
  scp machine:etrelease/*.log .&lt;br /&gt;
&lt;br /&gt;
Then commit the new/updated files.  &lt;br /&gt;
&lt;br /&gt;
To re-run the tests with an updated checkout, run the GetComponents command above with the --update flag, rebuild, delete the &amp;quot;testsuites&amp;quot; output simulation, and resubmit the job.&lt;br /&gt;
&lt;br /&gt;
=Machines=&lt;br /&gt;
&lt;br /&gt;
==Kraken==&lt;br /&gt;
&lt;br /&gt;
Edit simfactory/mdb.pm&lt;br /&gt;
&lt;br /&gt;
  -        myproxy-logon -p 7514 -s myproxy.teragrid.org -T -l @USER@ -o @SOURCEDIR@/.globus/proxy-teragrid&lt;br /&gt;
  +        myproxy-logon -p 7514 -s myproxy.teragrid.org -T -l &amp;lt;username&amp;gt; -o @SOURCEDIR@/.globus/proxy-teragrid&lt;br /&gt;
&lt;br /&gt;
where &amp;lt;username&amp;gt; is your user name on Kraken.  This is related to [https://trac.einsteintoolkit.org/ticket/381 Ticket #381]&lt;br /&gt;
&lt;br /&gt;
Change the sourcebasedir in simfactory/udb.pm to be under /lustre/scratch.  This is necessary because the Cactus directory must be visible from the compute node when running the tests (to see the parameter files, testsuite reference output and test.ccl files), and the home directory on Kraken is not visible from the compute nodes.&lt;br /&gt;
&lt;br /&gt;
    set_option &amp;#039;kraken&amp;#039;, &amp;#039;sourcebasedir&amp;#039;, &amp;#039;/lustre/scratch/USERNAME&amp;#039;;&lt;br /&gt;
&lt;br /&gt;
Copy kraken.sh as kraken-testsuite.sh in simfactory/scriptfiles.  Replace the aprun command with the following:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
cd @SOURCEDIR@&lt;br /&gt;
&lt;br /&gt;
export CCTK_TESTSUITE_RUN_COMMAND=&amp;quot;aprun -n \$nprocs -d 1 \$exe \$parfile&amp;quot;&lt;br /&gt;
&lt;br /&gt;
test_dir=TEST_$(date +%Y-%m-%d-%H%M%S)&lt;br /&gt;
mkdir $test_dir&lt;br /&gt;
&lt;br /&gt;
CONFIGNAME=$(ls configs|tail) # SimFactory should provide the configuration name&lt;br /&gt;
&lt;br /&gt;
for i in 1 2 3; do&lt;br /&gt;
  case $i in&lt;br /&gt;
    1 )&lt;br /&gt;
      export CCTK_TESTSUITE_RUN_PROCESSORS=1&lt;br /&gt;
      export OMP_NUM_THREADS=1;;&lt;br /&gt;
    2 )&lt;br /&gt;
      export CCTK_TESTSUITE_RUN_PROCESSORS=2&lt;br /&gt;
      export OMP_NUM_THREADS=1;;&lt;br /&gt;
    3 )&lt;br /&gt;
      export CCTK_TESTSUITE_RUN_PROCESSORS=2&lt;br /&gt;
      export OMP_NUM_THREADS=2;;&lt;br /&gt;
  esac&lt;br /&gt;
  make $CONFIGNAME-testsuite PROMPT=no&lt;br /&gt;
  cp TEST/$CONFIGNAME/summary.log kraken__${CCTK_TESTSUITE_RUN_PROCESSORS}_${OMP_NUM_THREADS}.log&lt;br /&gt;
  mv TEST $test_dir/TEST.$i&lt;br /&gt;
done&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==Datura==&lt;br /&gt;
&lt;br /&gt;
Copy datura.sh as datura-testsuite.sh in simfactory/scriptfiles.  Replace the mpirun command with the following:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
cd @SOURCEDIR@&lt;br /&gt;
&lt;br /&gt;
test_dir=TEST_$(date +%Y-%m-%d-%H%M%S)&lt;br /&gt;
mkdir $test_dir&lt;br /&gt;
&lt;br /&gt;
CONFIGNAME=$(ls configs|tail) # SimFactory should provide the configuration name&lt;br /&gt;
&lt;br /&gt;
export CACTUS_STARTTIME=$(date +%s)&lt;br /&gt;
&lt;br /&gt;
for i in 1 2 3; do&lt;br /&gt;
  case $i in&lt;br /&gt;
    1 )&lt;br /&gt;
      export CCTK_TESTSUITE_RUN_PROCESSORS=1&lt;br /&gt;
      export OMP_NUM_THREADS=1;;&lt;br /&gt;
    2 )&lt;br /&gt;
      export CCTK_TESTSUITE_RUN_PROCESSORS=2&lt;br /&gt;
      export OMP_NUM_THREADS=1;;&lt;br /&gt;
    3 )&lt;br /&gt;
      export CCTK_TESTSUITE_RUN_PROCESSORS=2&lt;br /&gt;
      export OMP_NUM_THREADS=2;;&lt;br /&gt;
  esac&lt;br /&gt;
  export CCTK_TESTSUITE_RUN_COMMAND=&amp;quot;${MPIDIR}/bin/mpirun -v --mca btl openib,self --mca mpi_leave_pinned 0 -np \$nprocs -npernode $CCTK_TESTSUITE_RUN_PROCESSORS \$exe -L 3 \$parfile&amp;quot;&lt;br /&gt;
  make $CONFIGNAME-testsuite PROMPT=no&lt;br /&gt;
  cp TEST/$CONFIGNAME/summary.log datura__${CCTK_TESTSUITE_RUN_PROCESSORS}_${OMP_NUM_THREADS}.log&lt;br /&gt;
  mv TEST $test_dir/TEST.$i&lt;br /&gt;
done&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==BlueDrop==&lt;br /&gt;
&lt;br /&gt;
The following script is a slightly modified version of run_tests adapted to run on &lt;br /&gt;
the Power7 machine BlueDrop:&lt;br /&gt;
&lt;br /&gt;
 set -e&lt;br /&gt;
 &lt;br /&gt;
 cd Cactus&lt;br /&gt;
 &lt;br /&gt;
 #Blue drop (Note that we need to specify the absolute path for the bluedrop_run*.ll files):&lt;br /&gt;
 &lt;br /&gt;
 for i in 1 2 3; do&lt;br /&gt;
  case $i in&lt;br /&gt;
    1 )&lt;br /&gt;
     hostname | grep ^bd &amp;amp;&amp;amp; export CCTK_TESTSUITE_RUN_COMMAND=&amp;quot;poe \$exe \$parfile -retry -1 -llfile /home/bcmundim/bluedrop_run_1.ll&amp;quot;&lt;br /&gt;
      export CCTK_TESTSUITE_RUN_PROCESSORS=1&lt;br /&gt;
      export OMP_NUM_THREADS=1;;&lt;br /&gt;
    2 )&lt;br /&gt;
      hostname | grep ^bd &amp;amp;&amp;amp; export CCTK_TESTSUITE_RUN_COMMAND=&amp;quot;poe \$exe \$parfile -retry -1 -llfile /home/bcmundim/bluedrop_run_2.ll&amp;quot;&lt;br /&gt;
      export CCTK_TESTSUITE_RUN_PROCESSORS=2&lt;br /&gt;
      export OMP_NUM_THREADS=1;;&lt;br /&gt;
    3 )&lt;br /&gt;
      hostname | grep ^bd &amp;amp;&amp;amp; export CCTK_TESTSUITE_RUN_COMMAND=&amp;quot;poe \$exe \$parfile -retry -1 -llfile /home/bcmundim/bluedrop_run_2.ll&amp;quot;&lt;br /&gt;
      export CCTK_TESTSUITE_RUN_PROCESSORS=2&lt;br /&gt;
      export OMP_NUM_THREADS=2;;&lt;br /&gt;
  esac&lt;br /&gt;
  make sim-testsuite PROMPT=no&lt;br /&gt;
  mv TEST/sim/summary.log ../${HOSTNAME}__${CCTK_TESTSUITE_RUN_PROCESSORS}_${OMP_NUM_THREADS}.log&lt;br /&gt;
 done&lt;br /&gt;
&lt;br /&gt;
Remember to change the absolute path (/home/bcmundim in the script above) to the appropriate location &lt;br /&gt;
of your LoadLeveler batch job script files, the bluedrop_run_*.ll. The following batch job scripts &lt;br /&gt;
were used to run the test suites; bluedrop_run_1.ll and bluedrop_run_2.ll, respectively:&lt;br /&gt;
&lt;br /&gt;
 ## Comment the class line to run on short queue:&lt;br /&gt;
 #@ class = debug&lt;br /&gt;
 #@ job_type = parallel&lt;br /&gt;
 ##@ node_usage = not_shared&lt;br /&gt;
 #@ node_usage = shared&lt;br /&gt;
 #@ environment = COPY_ALL&lt;br /&gt;
 #@ tasks_per_node = 1&lt;br /&gt;
 #@ node = 1&lt;br /&gt;
 #@ wall_clock_limit = 0:30:00&lt;br /&gt;
 ### uncomment below for a normal batch job&lt;br /&gt;
 # #@ output = $(host).$(jobid).$(stepid).out&lt;br /&gt;
 # #@ error = $(host).$(jobid).$(stepid).err&lt;br /&gt;
 &lt;br /&gt;
 #@ queue&lt;br /&gt;
 ## uncomment for a normal batch job&lt;br /&gt;
 # $HOME/a.out&lt;br /&gt;
&lt;br /&gt;
 ## Comment the class line to run on short queue:&lt;br /&gt;
 #@ class = debug&lt;br /&gt;
 #@ job_type = parallel&lt;br /&gt;
 ##@ node_usage = not_shared&lt;br /&gt;
 #@ node_usage = shared&lt;br /&gt;
 #@ environment = COPY_ALL&lt;br /&gt;
 #@ tasks_per_node = 2&lt;br /&gt;
 #@ node = 1&lt;br /&gt;
 #@ wall_clock_limit = 0:30:00&lt;br /&gt;
 ### uncomment below for a normal batch job&lt;br /&gt;
 # #@ output = $(host).$(jobid).$(stepid).out&lt;br /&gt;
 # #@ error = $(host).$(jobid).$(stepid).err&lt;br /&gt;
 &lt;br /&gt;
 #@ queue&lt;br /&gt;
 ## uncomment for a normal batch job&lt;br /&gt;
 # $HOME/a.out&lt;/div&gt;</summary>
		<author><name>Bmundim</name></author>
		
	</entry>
	<entry>
		<id>https://docs.einsteintoolkit.org/et-docs/index.php?title=Testsuite_Machines&amp;diff=2234</id>
		<title>Testsuite Machines</title>
		<link rel="alternate" type="text/html" href="https://docs.einsteintoolkit.org/et-docs/index.php?title=Testsuite_Machines&amp;diff=2234"/>
		<updated>2011-04-06T05:24:09Z</updated>

		<summary type="html">&lt;p&gt;Bmundim: /* BlueDrop */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;This page contains notes and instructions for people running the ET testsuites on various different machines.  If you have experience running testsuites on a machine which is not listed here, please consider adding some information which might help others (or yourself!) in future.  &lt;br /&gt;
&lt;br /&gt;
=General=&lt;br /&gt;
&lt;br /&gt;
To check out the ET:&lt;br /&gt;
&lt;br /&gt;
  mkdir etrelease&lt;br /&gt;
  cd etrelease&lt;br /&gt;
  curl -O https://github.com/gridaphobe/CRL/raw/master/GetComponents &lt;br /&gt;
  chmod a+x GetComponents&lt;br /&gt;
  ./GetComponents --root=. -a https://svn.einsteintoolkit.org/manifest/trunk/einsteintoolkit.th&lt;br /&gt;
  cp udb.example.pm udb.pm&lt;br /&gt;
&lt;br /&gt;
In udb.pm, &lt;br /&gt;
&lt;br /&gt;
* Replace &amp;quot;redshift&amp;quot; with the name of your local machine, unless you are running on one of the supported machines.&lt;br /&gt;
&lt;br /&gt;
* Replace YOUR_LOGIN, YOUR_EMAIL_ADDRESS and YOUR_ALLOCATION as appropriate.&lt;br /&gt;
&lt;br /&gt;
* Set sourcebasedir for your local machine to be the directory containing etrelease (do not set it to etrelease itself).&lt;br /&gt;
&lt;br /&gt;
* Set your username on each machine:&lt;br /&gt;
    set_option &amp;#039;MACHINE&amp;#039;  , &amp;#039;user&amp;#039;, &amp;#039;USERNAME&amp;#039;;&lt;br /&gt;
&lt;br /&gt;
See the machine-specific notes below for any additional steps for each machine.&lt;br /&gt;
&lt;br /&gt;
  touch par/testsuite.par&lt;br /&gt;
  sim sync &amp;lt;machine&amp;gt;&lt;br /&gt;
  sim build --thornlist manifest/einsteintoolkit.th --scriptfile &amp;lt;machine&amp;gt;-testsuite.sh&lt;br /&gt;
  sim remote &amp;lt;machine&amp;gt; create-submit par/testsuite.par NSLOTS 6:00:00&lt;br /&gt;
&lt;br /&gt;
This is a dummy parameter file.&lt;br /&gt;
&lt;br /&gt;
When the job is finished, you should have the required &amp;lt;machine&amp;gt;_i_j.log files in machine:etrelease/*.log.  The testsuite output will also be stored in machine:TEST_XXX, where XXX is constructed from the date at which the job was run.&lt;br /&gt;
&lt;br /&gt;
Update the testsuite status page by adding the log files to the release-info repository:&lt;br /&gt;
&lt;br /&gt;
  svn co https://svn.einsteintoolkit.org/www/release-info&lt;br /&gt;
  cd release-info&lt;br /&gt;
  scp machine:etrelease/*.log .&lt;br /&gt;
&lt;br /&gt;
Then commit the new/updated files.  &lt;br /&gt;
&lt;br /&gt;
To re-run the tests with an updated checkout, run the GetComponents command above with the --update flag, rebuild, delete the &amp;quot;testsuites&amp;quot; output simulation, and resubmit the job.&lt;br /&gt;
&lt;br /&gt;
=Machines=&lt;br /&gt;
&lt;br /&gt;
==Kraken==&lt;br /&gt;
&lt;br /&gt;
Edit simfactory/mdb.pm&lt;br /&gt;
&lt;br /&gt;
  -        myproxy-logon -p 7514 -s myproxy.teragrid.org -T -l @USER@ -o @SOURCEDIR@/.globus/proxy-teragrid&lt;br /&gt;
  +        myproxy-logon -p 7514 -s myproxy.teragrid.org -T -l &amp;lt;username&amp;gt; -o @SOURCEDIR@/.globus/proxy-teragrid&lt;br /&gt;
&lt;br /&gt;
where &amp;lt;username&amp;gt; is your user name on Kraken.  This is related to [https://trac.einsteintoolkit.org/ticket/381 Ticket #381]&lt;br /&gt;
&lt;br /&gt;
Change the sourcebasedir in simfactory/udb.pm to be under /lustre/scratch.  This is necessary because the Cactus directory must be visible from the compute node when running the tests (to see the parameter files, testsuite reference output and test.ccl files), and the home directory on Kraken is not visible from the compute nodes.&lt;br /&gt;
&lt;br /&gt;
    set_option &amp;#039;kraken&amp;#039;, &amp;#039;sourcebasedir&amp;#039;, &amp;#039;/lustre/scratch/USERNAME&amp;#039;;&lt;br /&gt;
&lt;br /&gt;
Copy kraken.sh as kraken-testsuite.sh in simfactory/scriptfiles.  Replace the aprun command with the following:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
cd @SOURCEDIR@&lt;br /&gt;
&lt;br /&gt;
export CCTK_TESTSUITE_RUN_COMMAND=&amp;quot;aprun -n \$nprocs -d 1 \$exe \$parfile&amp;quot;&lt;br /&gt;
&lt;br /&gt;
test_dir=TEST_$(date +%Y-%m-%d-%H%M%S)&lt;br /&gt;
mkdir $test_dir&lt;br /&gt;
&lt;br /&gt;
CONFIGNAME=$(ls configs|tail) # SimFactory should provide the configuration name&lt;br /&gt;
&lt;br /&gt;
for i in 1 2 3; do&lt;br /&gt;
  case $i in&lt;br /&gt;
    1 )&lt;br /&gt;
      export CCTK_TESTSUITE_RUN_PROCESSORS=1&lt;br /&gt;
      export OMP_NUM_THREADS=1;;&lt;br /&gt;
    2 )&lt;br /&gt;
      export CCTK_TESTSUITE_RUN_PROCESSORS=2&lt;br /&gt;
      export OMP_NUM_THREADS=1;;&lt;br /&gt;
    3 )&lt;br /&gt;
      export CCTK_TESTSUITE_RUN_PROCESSORS=2&lt;br /&gt;
      export OMP_NUM_THREADS=2;;&lt;br /&gt;
  esac&lt;br /&gt;
  make $CONFIGNAME-testsuite PROMPT=no&lt;br /&gt;
  cp TEST/$CONFIGNAME/summary.log kraken__${CCTK_TESTSUITE_RUN_PROCESSORS}_${OMP_NUM_THREADS}.log&lt;br /&gt;
  mv TEST $test_dir/TEST.$i&lt;br /&gt;
done&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==Datura==&lt;br /&gt;
&lt;br /&gt;
Copy datura.sh as datura-testsuite.sh in simfactory/scriptfiles.  Replace the mpirun command with the following:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
cd @SOURCEDIR@&lt;br /&gt;
&lt;br /&gt;
test_dir=TEST_$(date +%Y-%m-%d-%H%M%S)&lt;br /&gt;
mkdir $test_dir&lt;br /&gt;
&lt;br /&gt;
CONFIGNAME=$(ls configs|tail) # SimFactory should provide the configuration name&lt;br /&gt;
&lt;br /&gt;
export CACTUS_STARTTIME=$(date +%s)&lt;br /&gt;
&lt;br /&gt;
for i in 1 2 3; do&lt;br /&gt;
  case $i in&lt;br /&gt;
    1 )&lt;br /&gt;
      export CCTK_TESTSUITE_RUN_PROCESSORS=1&lt;br /&gt;
      export OMP_NUM_THREADS=1;;&lt;br /&gt;
    2 )&lt;br /&gt;
      export CCTK_TESTSUITE_RUN_PROCESSORS=2&lt;br /&gt;
      export OMP_NUM_THREADS=1;;&lt;br /&gt;
    3 )&lt;br /&gt;
      export CCTK_TESTSUITE_RUN_PROCESSORS=2&lt;br /&gt;
      export OMP_NUM_THREADS=2;;&lt;br /&gt;
  esac&lt;br /&gt;
  export CCTK_TESTSUITE_RUN_COMMAND=&amp;quot;${MPIDIR}/bin/mpirun -v --mca btl openib,self --mca mpi_leave_pinned 0 -np \$nprocs -npernode $CCTK_TESTSUITE_RUN_PROCESSORS \$exe -L 3 \$parfile&amp;quot;&lt;br /&gt;
  make $CONFIGNAME-testsuite PROMPT=no&lt;br /&gt;
  cp TEST/$CONFIGNAME/summary.log datura__${CCTK_TESTSUITE_RUN_PROCESSORS}_${OMP_NUM_THREADS}.log&lt;br /&gt;
  mv TEST $test_dir/TEST.$i&lt;br /&gt;
done&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==BlueDrop==&lt;br /&gt;
&lt;br /&gt;
The following script is a slightly modified version of run_tests adapted to run on &lt;br /&gt;
the Power7 machine BlueDrop:&lt;br /&gt;
&lt;br /&gt;
 set -e&lt;br /&gt;
 &lt;br /&gt;
 cd Cactus&lt;br /&gt;
 &lt;br /&gt;
 #Blue drop (Note that we need to specify the absolute path for the bluedrop_run*.ll files):&lt;br /&gt;
 &lt;br /&gt;
 for i in 1 2 3; do&lt;br /&gt;
  case $i in&lt;br /&gt;
    1 )&lt;br /&gt;
     hostname | grep ^bd &amp;amp;&amp;amp; export CCTK_TESTSUITE_RUN_COMMAND=&amp;quot;poe \$exe \$parfile -retry -1 -llfile /home/bcmundim/bluedrop_run_1.ll&amp;quot;&lt;br /&gt;
      export CCTK_TESTSUITE_RUN_PROCESSORS=1&lt;br /&gt;
      export OMP_NUM_THREADS=1;;&lt;br /&gt;
    2 )&lt;br /&gt;
      hostname | grep ^bd &amp;amp;&amp;amp; export CCTK_TESTSUITE_RUN_COMMAND=&amp;quot;poe \$exe \$parfile -retry -1 -llfile /home/bcmundim/bluedrop_run_2.ll&amp;quot;&lt;br /&gt;
      export CCTK_TESTSUITE_RUN_PROCESSORS=2&lt;br /&gt;
      export OMP_NUM_THREADS=1;;&lt;br /&gt;
    3 )&lt;br /&gt;
      hostname | grep ^bd &amp;amp;&amp;amp; export CCTK_TESTSUITE_RUN_COMMAND=&amp;quot;poe \$exe \$parfile -retry -1 -llfile /home/bcmundim/bluedrop_run_2.ll&amp;quot;&lt;br /&gt;
      export CCTK_TESTSUITE_RUN_PROCESSORS=2&lt;br /&gt;
      export OMP_NUM_THREADS=2;;&lt;br /&gt;
  esac&lt;br /&gt;
  make sim-testsuite PROMPT=no&lt;br /&gt;
  mv TEST/sim/summary.log ../${HOSTNAME}__${CCTK_TESTSUITE_RUN_PROCESSORS}_${OMP_NUM_THREADS}.log&lt;br /&gt;
 done&lt;br /&gt;
&lt;br /&gt;
Remember to change the absolute path (/home/bcmundim in the script above) to the appropriate location &lt;br /&gt;
of your LoadLeveler batch job script files: bluedrop_run_*.ll. The following batch job scripts &lt;br /&gt;
were used to run the test suites; bluedrop_run_1.ll and bluedrop_run_2.ll, respectively:&lt;br /&gt;
&lt;br /&gt;
 ## Comment the class line to run on short queue:&lt;br /&gt;
 #@ class = debug&lt;br /&gt;
 #@ job_type = parallel&lt;br /&gt;
 ##@ node_usage = not_shared&lt;br /&gt;
 #@ node_usage = shared&lt;br /&gt;
 #@ environment = COPY_ALL&lt;br /&gt;
 #@ tasks_per_node = 1&lt;br /&gt;
 #@ node = 1&lt;br /&gt;
 #@ wall_clock_limit = 0:30:00&lt;br /&gt;
 ### uncomment below for a normal batch job&lt;br /&gt;
 # #@ output = $(host).$(jobid).$(stepid).out&lt;br /&gt;
 # #@ error = $(host).$(jobid).$(stepid).err&lt;br /&gt;
 &lt;br /&gt;
 #@ queue&lt;br /&gt;
 ## uncomment for a normal batch job&lt;br /&gt;
 # $HOME/a.out&lt;br /&gt;
&lt;br /&gt;
 ## Comment the class line to run on short queue:&lt;br /&gt;
 #@ class = debug&lt;br /&gt;
 #@ job_type = parallel&lt;br /&gt;
 ##@ node_usage = not_shared&lt;br /&gt;
 #@ node_usage = shared&lt;br /&gt;
 #@ environment = COPY_ALL&lt;br /&gt;
 #@ tasks_per_node = 2&lt;br /&gt;
 #@ node = 1&lt;br /&gt;
 #@ wall_clock_limit = 0:30:00&lt;br /&gt;
 ### uncomment below for a normal batch job&lt;br /&gt;
 # #@ output = $(host).$(jobid).$(stepid).out&lt;br /&gt;
 # #@ error = $(host).$(jobid).$(stepid).err&lt;br /&gt;
 &lt;br /&gt;
 #@ queue&lt;br /&gt;
 ## uncomment for a normal batch job&lt;br /&gt;
 # $HOME/a.out&lt;/div&gt;</summary>
		<author><name>Bmundim</name></author>
		
	</entry>
	<entry>
		<id>https://docs.einsteintoolkit.org/et-docs/index.php?title=Testsuite_Machines&amp;diff=2233</id>
		<title>Testsuite Machines</title>
		<link rel="alternate" type="text/html" href="https://docs.einsteintoolkit.org/et-docs/index.php?title=Testsuite_Machines&amp;diff=2233"/>
		<updated>2011-04-06T05:22:17Z</updated>

		<summary type="html">&lt;p&gt;Bmundim: /* BlueDrop */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;This page contains notes and instructions for people running the ET testsuites on various different machines.  If you have experience running testsuites on a machine which is not listed here, please consider adding some information which might help others (or yourself!) in future.  &lt;br /&gt;
&lt;br /&gt;
=General=&lt;br /&gt;
&lt;br /&gt;
To check out the ET:&lt;br /&gt;
&lt;br /&gt;
  mkdir etrelease&lt;br /&gt;
  cd etrelease&lt;br /&gt;
  curl -O https://github.com/gridaphobe/CRL/raw/master/GetComponents &lt;br /&gt;
  chmod a+x GetComponents&lt;br /&gt;
  ./GetComponents --root=. -a https://svn.einsteintoolkit.org/manifest/trunk/einsteintoolkit.th&lt;br /&gt;
  cp udb.example.pm udb.pm&lt;br /&gt;
&lt;br /&gt;
In udb.pm, &lt;br /&gt;
&lt;br /&gt;
* Replace &amp;quot;redshift&amp;quot; with the name of your local machine, unless you are running on one of the supported machines.&lt;br /&gt;
&lt;br /&gt;
* Replace YOUR_LOGIN, YOUR_EMAIL_ADDRESS and YOUR_ALLOCATION as appropriate.&lt;br /&gt;
&lt;br /&gt;
* Set sourcebasedir for your local machine to be the directory containing etrelease (do not set it to etrelease itself).&lt;br /&gt;
&lt;br /&gt;
* Set your username on each machine:&lt;br /&gt;
    set_option &amp;#039;MACHINE&amp;#039;  , &amp;#039;user&amp;#039;, &amp;#039;USERNAME&amp;#039;;&lt;br /&gt;
&lt;br /&gt;
See the machine-specific notes below for any additional steps for each machine.&lt;br /&gt;
&lt;br /&gt;
  touch par/testsuite.par&lt;br /&gt;
  sim sync &amp;lt;machine&amp;gt;&lt;br /&gt;
  sim build --thornlist manifest/einsteintoolkit.th --scriptfile &amp;lt;machine&amp;gt;-testsuite.sh&lt;br /&gt;
  sim remote &amp;lt;machine&amp;gt; create-submit par/testsuite.par NSLOTS 6:00:00&lt;br /&gt;
&lt;br /&gt;
This is a dummy parameter file.&lt;br /&gt;
&lt;br /&gt;
When the job is finished, you should have the required &amp;lt;machine&amp;gt;_i_j.log files in machine:etrelease/*.log.  The testsuite output will also be stored in machine:TEST_XXX, where XXX is constructed from the date at which the job was run.&lt;br /&gt;
&lt;br /&gt;
Update the testsuite status page by adding the log files to the release-info repository:&lt;br /&gt;
&lt;br /&gt;
  svn co https://svn.einsteintoolkit.org/www/release-info&lt;br /&gt;
  cd release-info&lt;br /&gt;
  scp machine:etrelease/*.log .&lt;br /&gt;
&lt;br /&gt;
Then commit the new/updated files.  &lt;br /&gt;
&lt;br /&gt;
To re-run the tests with an updated checkout, run the GetComponents command above with the --update flag, rebuild, delete the &amp;quot;testsuites&amp;quot; output simulation, and resubmit the job.&lt;br /&gt;
&lt;br /&gt;
=Machines=&lt;br /&gt;
&lt;br /&gt;
==Kraken==&lt;br /&gt;
&lt;br /&gt;
Edit simfactory/mdb.pm&lt;br /&gt;
&lt;br /&gt;
  -        myproxy-logon -p 7514 -s myproxy.teragrid.org -T -l @USER@ -o @SOURCEDIR@/.globus/proxy-teragrid&lt;br /&gt;
  +        myproxy-logon -p 7514 -s myproxy.teragrid.org -T -l &amp;lt;username&amp;gt; -o @SOURCEDIR@/.globus/proxy-teragrid&lt;br /&gt;
&lt;br /&gt;
where &amp;lt;username&amp;gt; is your user name on Kraken.  This is related to [https://trac.einsteintoolkit.org/ticket/381 Ticket #381]&lt;br /&gt;
&lt;br /&gt;
Change the sourcebasedir in simfactory/udb.pm to be under /lustre/scratch.  This is necessary because the Cactus directory must be visible from the compute node when running the tests (to see the parameter files, testsuite reference output and test.ccl files), and the home directory on Kraken is not visible from the compute nodes.&lt;br /&gt;
&lt;br /&gt;
    set_option &amp;#039;kraken&amp;#039;, &amp;#039;sourcebasedir&amp;#039;, &amp;#039;/lustre/scratch/USERNAME&amp;#039;;&lt;br /&gt;
&lt;br /&gt;
Copy kraken.sh as kraken-testsuite.sh in simfactory/scriptfiles.  Replace the aprun command with the following:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
cd @SOURCEDIR@&lt;br /&gt;
&lt;br /&gt;
export CCTK_TESTSUITE_RUN_COMMAND=&amp;quot;aprun -n \$nprocs -d 1 \$exe \$parfile&amp;quot;&lt;br /&gt;
&lt;br /&gt;
test_dir=TEST_$(date +%Y-%m-%d-%H%M%S)&lt;br /&gt;
mkdir $test_dir&lt;br /&gt;
&lt;br /&gt;
CONFIGNAME=$(ls configs|tail) # SimFactory should provide the configuration name&lt;br /&gt;
&lt;br /&gt;
for i in 1 2 3; do&lt;br /&gt;
  case $i in&lt;br /&gt;
    1 )&lt;br /&gt;
      export CCTK_TESTSUITE_RUN_PROCESSORS=1&lt;br /&gt;
      export OMP_NUM_THREADS=1;;&lt;br /&gt;
    2 )&lt;br /&gt;
      export CCTK_TESTSUITE_RUN_PROCESSORS=2&lt;br /&gt;
      export OMP_NUM_THREADS=1;;&lt;br /&gt;
    3 )&lt;br /&gt;
      export CCTK_TESTSUITE_RUN_PROCESSORS=2&lt;br /&gt;
      export OMP_NUM_THREADS=2;;&lt;br /&gt;
  esac&lt;br /&gt;
  make $CONFIGNAME-testsuite PROMPT=no&lt;br /&gt;
  cp TEST/$CONFIGNAME/summary.log kraken__${CCTK_TESTSUITE_RUN_PROCESSORS}_${OMP_NUM_THREADS}.log&lt;br /&gt;
  mv TEST $test_dir/TEST.$i&lt;br /&gt;
done&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==Datura==&lt;br /&gt;
&lt;br /&gt;
Copy datura.sh as datura-testsuite.sh in simfactory/scriptfiles.  Replace the mpirun command with the following:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
cd @SOURCEDIR@&lt;br /&gt;
&lt;br /&gt;
test_dir=TEST_$(date +%Y-%m-%d-%H%M%S)&lt;br /&gt;
mkdir $test_dir&lt;br /&gt;
&lt;br /&gt;
CONFIGNAME=$(ls configs|tail) # SimFactory should provide the configuration name&lt;br /&gt;
&lt;br /&gt;
export CACTUS_STARTTIME=$(date +%s)&lt;br /&gt;
&lt;br /&gt;
for i in 1 2 3; do&lt;br /&gt;
  case $i in&lt;br /&gt;
    1 )&lt;br /&gt;
      export CCTK_TESTSUITE_RUN_PROCESSORS=1&lt;br /&gt;
      export OMP_NUM_THREADS=1;;&lt;br /&gt;
    2 )&lt;br /&gt;
      export CCTK_TESTSUITE_RUN_PROCESSORS=2&lt;br /&gt;
      export OMP_NUM_THREADS=1;;&lt;br /&gt;
    3 )&lt;br /&gt;
      export CCTK_TESTSUITE_RUN_PROCESSORS=2&lt;br /&gt;
      export OMP_NUM_THREADS=2;;&lt;br /&gt;
  esac&lt;br /&gt;
  export CCTK_TESTSUITE_RUN_COMMAND=&amp;quot;${MPIDIR}/bin/mpirun -v --mca btl openib,self --mca mpi_leave_pinned 0 -np \$nprocs -npernode $CCTK_TESTSUITE_RUN_PROCESSORS \$exe -L 3 \$parfile&amp;quot;&lt;br /&gt;
  make $CONFIGNAME-testsuite PROMPT=no&lt;br /&gt;
  cp TEST/$CONFIGNAME/summary.log datura__${CCTK_TESTSUITE_RUN_PROCESSORS}_${OMP_NUM_THREADS}.log&lt;br /&gt;
  mv TEST $test_dir/TEST.$i&lt;br /&gt;
done&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==BlueDrop==&lt;br /&gt;
&lt;br /&gt;
The following script is a slightly modified version of run_tests adapted to run on &lt;br /&gt;
the Power7 machine BlueDrop:&lt;br /&gt;
&lt;br /&gt;
 set -e&lt;br /&gt;
 &lt;br /&gt;
 cd Cactus&lt;br /&gt;
 &lt;br /&gt;
 #Blue drop (Note that we need to specify the absolute path for the bluedrop_run*.ll files):&lt;br /&gt;
 &lt;br /&gt;
 for i in 1 2 3; do&lt;br /&gt;
  case $i in&lt;br /&gt;
    1 )&lt;br /&gt;
     hostname | grep ^bd &amp;amp;&amp;amp; export CCTK_TESTSUITE_RUN_COMMAND=&amp;quot;poe \$exe \$parfile -retry -1 -llfile /home/bcmundim/bluedrop_run_1.ll&amp;quot;&lt;br /&gt;
      export CCTK_TESTSUITE_RUN_PROCESSORS=1&lt;br /&gt;
      export OMP_NUM_THREADS=1;;&lt;br /&gt;
    2 )&lt;br /&gt;
      hostname | grep ^bd &amp;amp;&amp;amp; export CCTK_TESTSUITE_RUN_COMMAND=&amp;quot;poe \$exe \$parfile -retry -1 -llfile /home/bcmundim/bluedrop_run_2.ll&amp;quot;&lt;br /&gt;
      export CCTK_TESTSUITE_RUN_PROCESSORS=2&lt;br /&gt;
      export OMP_NUM_THREADS=1;;&lt;br /&gt;
    3 )&lt;br /&gt;
      hostname | grep ^bd &amp;amp;&amp;amp; export CCTK_TESTSUITE_RUN_COMMAND=&amp;quot;poe \$exe \$parfile -retry -1 -llfile /home/bcmundim/bluedrop_run_2.ll&amp;quot;&lt;br /&gt;
      export CCTK_TESTSUITE_RUN_PROCESSORS=2&lt;br /&gt;
      export OMP_NUM_THREADS=2;;&lt;br /&gt;
  esac&lt;br /&gt;
  make sim-testsuite PROMPT=no&lt;br /&gt;
  mv TEST/sim/summary.log ../${HOSTNAME}__${CCTK_TESTSUITE_RUN_PROCESSORS}_${OMP_NUM_THREADS}.log&lt;br /&gt;
 done&lt;br /&gt;
&lt;br /&gt;
Remember to change the absolute path (/home/bcmundim in the script above) to bluedrop_run_*.ll files &lt;br /&gt;
to the appropriate location of your LoadLeveler batch job script files. The following batch job scripts &lt;br /&gt;
were used to run the test suites; bluedrop_run_1.ll and bluedrop_run_2.ll, respectively:&lt;br /&gt;
&lt;br /&gt;
 ## Comment the class line to run on short queue:&lt;br /&gt;
 #@ class = debug&lt;br /&gt;
 #@ job_type = parallel&lt;br /&gt;
 ##@ node_usage = not_shared&lt;br /&gt;
 #@ node_usage = shared&lt;br /&gt;
 #@ environment = COPY_ALL&lt;br /&gt;
 #@ tasks_per_node = 1&lt;br /&gt;
 #@ node = 1&lt;br /&gt;
 #@ wall_clock_limit = 0:30:00&lt;br /&gt;
 ### uncomment below for a normal batch job&lt;br /&gt;
 # #@ output = $(host).$(jobid).$(stepid).out&lt;br /&gt;
 # #@ error = $(host).$(jobid).$(stepid).err&lt;br /&gt;
 &lt;br /&gt;
 #@ queue&lt;br /&gt;
 ## uncomment for a normal batch job&lt;br /&gt;
 # $HOME/a.out&lt;br /&gt;
&lt;br /&gt;
 ## Comment the class line to run on short queue:&lt;br /&gt;
 #@ class = debug&lt;br /&gt;
 #@ job_type = parallel&lt;br /&gt;
 ##@ node_usage = not_shared&lt;br /&gt;
 #@ node_usage = shared&lt;br /&gt;
 #@ environment = COPY_ALL&lt;br /&gt;
 #@ tasks_per_node = 2&lt;br /&gt;
 #@ node = 1&lt;br /&gt;
 #@ wall_clock_limit = 0:30:00&lt;br /&gt;
 ### uncomment below for a normal batch job&lt;br /&gt;
 # #@ output = $(host).$(jobid).$(stepid).out&lt;br /&gt;
 # #@ error = $(host).$(jobid).$(stepid).err&lt;br /&gt;
 &lt;br /&gt;
 #@ queue&lt;br /&gt;
 ## uncomment for a normal batch job&lt;br /&gt;
 # $HOME/a.out&lt;/div&gt;</summary>
		<author><name>Bmundim</name></author>
		
	</entry>
	<entry>
		<id>https://docs.einsteintoolkit.org/et-docs/index.php?title=Testsuite_Machines&amp;diff=2232</id>
		<title>Testsuite Machines</title>
		<link rel="alternate" type="text/html" href="https://docs.einsteintoolkit.org/et-docs/index.php?title=Testsuite_Machines&amp;diff=2232"/>
		<updated>2011-04-06T05:19:05Z</updated>

		<summary type="html">&lt;p&gt;Bmundim: /* BlueDrop */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;This page contains notes and instructions for people running the ET testsuites on various different machines.  If you have experience running testsuites on a machine which is not listed here, please consider adding some information which might help others (or yourself!) in future.  &lt;br /&gt;
&lt;br /&gt;
=General=&lt;br /&gt;
&lt;br /&gt;
To check out the ET:&lt;br /&gt;
&lt;br /&gt;
  mkdir etrelease&lt;br /&gt;
  cd etrelease&lt;br /&gt;
  curl -O https://github.com/gridaphobe/CRL/raw/master/GetComponents &lt;br /&gt;
  chmod a+x GetComponents&lt;br /&gt;
  ./GetComponents --root=. -a https://svn.einsteintoolkit.org/manifest/trunk/einsteintoolkit.th&lt;br /&gt;
  cp udb.example.pm udb.pm&lt;br /&gt;
&lt;br /&gt;
In udb.pm, &lt;br /&gt;
&lt;br /&gt;
* Replace &amp;quot;redshift&amp;quot; with the name of your local machine, unless you are running on one of the supported machines.&lt;br /&gt;
&lt;br /&gt;
* Replace YOUR_LOGIN, YOUR_EMAIL_ADDRESS and YOUR_ALLOCATION as appropriate.&lt;br /&gt;
&lt;br /&gt;
* Set sourcebasedir for your local machine to be the directory containing etrelease (do not set it to etrelease itself).&lt;br /&gt;
&lt;br /&gt;
* Set your username on each machine:&lt;br /&gt;
    set_option &amp;#039;MACHINE&amp;#039;  , &amp;#039;user&amp;#039;, &amp;#039;USERNAME&amp;#039;;&lt;br /&gt;
&lt;br /&gt;
See the machine-specific notes below for any additional steps for each machine.&lt;br /&gt;
&lt;br /&gt;
  touch par/testsuite.par&lt;br /&gt;
  sim sync &amp;lt;machine&amp;gt;&lt;br /&gt;
  sim build --thornlist manifest/einsteintoolkit.th --scriptfile &amp;lt;machine&amp;gt;-testsuite.sh&lt;br /&gt;
  sim remote &amp;lt;machine&amp;gt; create-submit par/testsuite.par NSLOTS 6:00:00&lt;br /&gt;
&lt;br /&gt;
This is a dummy parameter file.&lt;br /&gt;
&lt;br /&gt;
When the job is finished, you should have the required &amp;lt;machine&amp;gt;_i_j.log files in machine:etrelease/*.log.  The testsuite output will also be stored in machine:TEST_XXX, where XXX is constructed from the date at which the job was run.&lt;br /&gt;
&lt;br /&gt;
Update the testsuite status page by adding the log files to the release-info repository:&lt;br /&gt;
&lt;br /&gt;
  svn co https://svn.einsteintoolkit.org/www/release-info&lt;br /&gt;
  cd release-info&lt;br /&gt;
  scp machine:etrelease/*.log .&lt;br /&gt;
&lt;br /&gt;
Then commit the new/updated files.  &lt;br /&gt;
&lt;br /&gt;
To re-run the tests with an updated checkout, run the GetComponents command above with the --update flag, rebuild, delete the &amp;quot;testsuites&amp;quot; output simulation, and resubmit the job.&lt;br /&gt;
&lt;br /&gt;
=Machines=&lt;br /&gt;
&lt;br /&gt;
==Kraken==&lt;br /&gt;
&lt;br /&gt;
Edit simfactory/mdb.pm&lt;br /&gt;
&lt;br /&gt;
  -        myproxy-logon -p 7514 -s myproxy.teragrid.org -T -l @USER@ -o @SOURCEDIR@/.globus/proxy-teragrid&lt;br /&gt;
  +        myproxy-logon -p 7514 -s myproxy.teragrid.org -T -l &amp;lt;username&amp;gt; -o @SOURCEDIR@/.globus/proxy-teragrid&lt;br /&gt;
&lt;br /&gt;
where &amp;lt;username&amp;gt; is your user name on Kraken.  This is related to [https://trac.einsteintoolkit.org/ticket/381 Ticket #381]&lt;br /&gt;
&lt;br /&gt;
Change the sourcebasedir in simfactory/udb.pm to be under /lustre/scratch.  This is necessary because the Cactus directory must be visible from the compute node when running the tests (to see the parameter files, testsuite reference output and test.ccl files), and the home directory on Kraken is not visible from the compute nodes.&lt;br /&gt;
&lt;br /&gt;
    set_option &amp;#039;kraken&amp;#039;, &amp;#039;sourcebasedir&amp;#039;, &amp;#039;/lustre/scratch/USERNAME&amp;#039;;&lt;br /&gt;
&lt;br /&gt;
Copy kraken.sh as kraken-testsuite.sh in simfactory/scriptfiles.  Replace the aprun command with the following:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
cd @SOURCEDIR@&lt;br /&gt;
&lt;br /&gt;
export CCTK_TESTSUITE_RUN_COMMAND=&amp;quot;aprun -n \$nprocs -d 1 \$exe \$parfile&amp;quot;&lt;br /&gt;
&lt;br /&gt;
test_dir=TEST_$(date +%Y-%m-%d-%H%M%S)&lt;br /&gt;
mkdir $test_dir&lt;br /&gt;
&lt;br /&gt;
CONFIGNAME=$(ls configs|tail) # SimFactory should provide the configuration name&lt;br /&gt;
&lt;br /&gt;
for i in 1 2 3; do&lt;br /&gt;
  case $i in&lt;br /&gt;
    1 )&lt;br /&gt;
      export CCTK_TESTSUITE_RUN_PROCESSORS=1&lt;br /&gt;
      export OMP_NUM_THREADS=1;;&lt;br /&gt;
    2 )&lt;br /&gt;
      export CCTK_TESTSUITE_RUN_PROCESSORS=2&lt;br /&gt;
      export OMP_NUM_THREADS=1;;&lt;br /&gt;
    3 )&lt;br /&gt;
      export CCTK_TESTSUITE_RUN_PROCESSORS=2&lt;br /&gt;
      export OMP_NUM_THREADS=2;;&lt;br /&gt;
  esac&lt;br /&gt;
  make $CONFIGNAME-testsuite PROMPT=no&lt;br /&gt;
  cp TEST/$CONFIGNAME/summary.log kraken__${CCTK_TESTSUITE_RUN_PROCESSORS}_${OMP_NUM_THREADS}.log&lt;br /&gt;
  mv TEST $test_dir/TEST.$i&lt;br /&gt;
done&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==Datura==&lt;br /&gt;
&lt;br /&gt;
Copy datura.sh as datura-testsuite.sh in simfactory/scriptfiles.  Replace the mpirun command with the following:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
cd @SOURCEDIR@&lt;br /&gt;
&lt;br /&gt;
test_dir=TEST_$(date +%Y-%m-%d-%H%M%S)&lt;br /&gt;
mkdir $test_dir&lt;br /&gt;
&lt;br /&gt;
CONFIGNAME=$(ls configs|tail) # SimFactory should provide the configuration name&lt;br /&gt;
&lt;br /&gt;
export CACTUS_STARTTIME=$(date +%s)&lt;br /&gt;
&lt;br /&gt;
for i in 1 2 3; do&lt;br /&gt;
  case $i in&lt;br /&gt;
    1 )&lt;br /&gt;
      export CCTK_TESTSUITE_RUN_PROCESSORS=1&lt;br /&gt;
      export OMP_NUM_THREADS=1;;&lt;br /&gt;
    2 )&lt;br /&gt;
      export CCTK_TESTSUITE_RUN_PROCESSORS=2&lt;br /&gt;
      export OMP_NUM_THREADS=1;;&lt;br /&gt;
    3 )&lt;br /&gt;
      export CCTK_TESTSUITE_RUN_PROCESSORS=2&lt;br /&gt;
      export OMP_NUM_THREADS=2;;&lt;br /&gt;
  esac&lt;br /&gt;
  export CCTK_TESTSUITE_RUN_COMMAND=&amp;quot;${MPIDIR}/bin/mpirun -v --mca btl openib,self --mca mpi_leave_pinned 0 -np \$nprocs -npernode $CCTK_TESTSUITE_RUN_PROCESSORS \$exe -L 3 \$parfile&amp;quot;&lt;br /&gt;
  make $CONFIGNAME-testsuite PROMPT=no&lt;br /&gt;
  cp TEST/$CONFIGNAME/summary.log datura__${CCTK_TESTSUITE_RUN_PROCESSORS}_${OMP_NUM_THREADS}.log&lt;br /&gt;
  mv TEST $test_dir/TEST.$i&lt;br /&gt;
done&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==BlueDrop==&lt;br /&gt;
&lt;br /&gt;
The following script is a slightly modified version of run_tests adapted to run on &lt;br /&gt;
the Power7 machine BlueDrop:&lt;br /&gt;
&lt;br /&gt;
 set -e&lt;br /&gt;
 &lt;br /&gt;
 cd Cactus&lt;br /&gt;
 &lt;br /&gt;
 #Blue drop (Note that we need to specify the absolute path for the bluedrop_run*.ll files):&lt;br /&gt;
 &lt;br /&gt;
 for i in 1 2 3; do&lt;br /&gt;
  case $i in&lt;br /&gt;
    1 )&lt;br /&gt;
     hostname | grep ^bd &amp;amp;&amp;amp; export CCTK_TESTSUITE_RUN_COMMAND=&amp;quot;poe \$exe \$parfile -retry -1 -llfile /home/bcmundim/bluedrop_run_1.ll&amp;quot;&lt;br /&gt;
      export CCTK_TESTSUITE_RUN_PROCESSORS=1&lt;br /&gt;
      export OMP_NUM_THREADS=1;;&lt;br /&gt;
    2 )&lt;br /&gt;
      hostname | grep ^bd &amp;amp;&amp;amp; export CCTK_TESTSUITE_RUN_COMMAND=&amp;quot;poe \$exe \$parfile -retry -1 -llfile /home/bcmundim/bluedrop_run_2.ll&amp;quot;&lt;br /&gt;
      export CCTK_TESTSUITE_RUN_PROCESSORS=2&lt;br /&gt;
      export OMP_NUM_THREADS=1;;&lt;br /&gt;
    3 )&lt;br /&gt;
      hostname | grep ^bd &amp;amp;&amp;amp; export CCTK_TESTSUITE_RUN_COMMAND=&amp;quot;poe \$exe \$parfile -retry -1 -llfile /home/bcmundim/bluedrop_run_2.ll&amp;quot;&lt;br /&gt;
      export CCTK_TESTSUITE_RUN_PROCESSORS=2&lt;br /&gt;
      export OMP_NUM_THREADS=2;;&lt;br /&gt;
  esac&lt;br /&gt;
  make sim-testsuite PROMPT=no&lt;br /&gt;
  mv TEST/sim/summary.log ../${HOSTNAME}__${CCTK_TESTSUITE_RUN_PROCESSORS}_${OMP_NUM_THREADS}.log&lt;br /&gt;
 done&lt;br /&gt;
&lt;br /&gt;
Remember to change the absolute path to bluedrop_run_*.ll (/home/bcmundim above) to the appropriate location &lt;br /&gt;
of your LoadLeveler batch job script files. The following job scripts were used to run the test suites; bluedrop_run_1.ll and bluedrop_run_2.ll, respectively:&lt;br /&gt;
&lt;br /&gt;
 ## Comment the class line to run on short queue:&lt;br /&gt;
 #@ class = debug&lt;br /&gt;
 #@ job_type = parallel&lt;br /&gt;
 ##@ node_usage = not_shared&lt;br /&gt;
 #@ node_usage = shared&lt;br /&gt;
 #@ environment = COPY_ALL&lt;br /&gt;
 #@ tasks_per_node = 1&lt;br /&gt;
 #@ node = 1&lt;br /&gt;
 #@ wall_clock_limit = 0:30:00&lt;br /&gt;
 ### uncomment below for a normal batch job&lt;br /&gt;
 # #@ output = $(host).$(jobid).$(stepid).out&lt;br /&gt;
 # #@ error = $(host).$(jobid).$(stepid).err&lt;br /&gt;
 &lt;br /&gt;
 #@ queue&lt;br /&gt;
 ## uncomment for a normal batch job&lt;br /&gt;
 # $HOME/a.out&lt;br /&gt;
&lt;br /&gt;
 ## Comment the class line to run on short queue:&lt;br /&gt;
 #@ class = debug&lt;br /&gt;
 #@ job_type = parallel&lt;br /&gt;
 ##@ node_usage = not_shared&lt;br /&gt;
 #@ node_usage = shared&lt;br /&gt;
 #@ environment = COPY_ALL&lt;br /&gt;
 #@ tasks_per_node = 2&lt;br /&gt;
 #@ node = 1&lt;br /&gt;
 #@ wall_clock_limit = 0:30:00&lt;br /&gt;
 ### uncomment below for a normal batch job&lt;br /&gt;
 # #@ output = $(host).$(jobid).$(stepid).out&lt;br /&gt;
 # #@ error = $(host).$(jobid).$(stepid).err&lt;br /&gt;
 &lt;br /&gt;
 #@ queue&lt;br /&gt;
 ## uncomment for a normal batch job&lt;br /&gt;
 # $HOME/a.out&lt;/div&gt;</summary>
		<author><name>Bmundim</name></author>
		
	</entry>
	<entry>
		<id>https://docs.einsteintoolkit.org/et-docs/index.php?title=Testsuite_Machines&amp;diff=2231</id>
		<title>Testsuite Machines</title>
		<link rel="alternate" type="text/html" href="https://docs.einsteintoolkit.org/et-docs/index.php?title=Testsuite_Machines&amp;diff=2231"/>
		<updated>2011-04-06T05:17:31Z</updated>

		<summary type="html">&lt;p&gt;Bmundim: /* BlueDrop */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;This page contains notes and instructions for people running the ET testsuites on various different machines.  If you have experience running testsuites on a machine which is not listed here, please consider adding some information which might help others (or yourself!) in future.  &lt;br /&gt;
&lt;br /&gt;
=General=&lt;br /&gt;
&lt;br /&gt;
To check out the ET:&lt;br /&gt;
&lt;br /&gt;
  mkdir etrelease&lt;br /&gt;
  cd etrelease&lt;br /&gt;
  curl -O https://github.com/gridaphobe/CRL/raw/master/GetComponents &lt;br /&gt;
  chmod a+x GetComponents&lt;br /&gt;
  ./GetComponents --root=. -a https://svn.einsteintoolkit.org/manifest/trunk/einsteintoolkit.th&lt;br /&gt;
  cp udb.example.pm udb.pm&lt;br /&gt;
&lt;br /&gt;
In udb.pm, &lt;br /&gt;
&lt;br /&gt;
* Replace &amp;quot;redshift&amp;quot; with the name of your local machine, unless you are running on one of the supported machines.&lt;br /&gt;
&lt;br /&gt;
* Replace YOUR_LOGIN, YOUR_EMAIL_ADDRESS and YOUR_ALLOCATION as appropriate.&lt;br /&gt;
&lt;br /&gt;
* Set sourcebasedir for your local machine to be the directory containing etrelease (do not set it to etrelease itself).&lt;br /&gt;
&lt;br /&gt;
* Set your username on each machine:&lt;br /&gt;
    set_option &amp;#039;MACHINE&amp;#039;  , &amp;#039;user&amp;#039;, &amp;#039;USERNAME&amp;#039;;&lt;br /&gt;
&lt;br /&gt;
See the machine-specific notes below for any additional steps for each machine.&lt;br /&gt;
&lt;br /&gt;
  touch par/testsuite.par&lt;br /&gt;
  sim sync &amp;lt;machine&amp;gt;&lt;br /&gt;
  sim build --thornlist manifest/einsteintoolkit.th --scriptfile &amp;lt;machine&amp;gt;-testsuite.sh&lt;br /&gt;
  sim remote &amp;lt;machine&amp;gt; create-submit par/testsuite.par NSLOTS 6:00:00&lt;br /&gt;
&lt;br /&gt;
This is a dummy parameter file.&lt;br /&gt;
&lt;br /&gt;
When the job is finished, you should have the required &amp;lt;machine&amp;gt;_i_j.log files in machine:etrelease/*.log.  The testsuite output will also be stored in machine:TEST_XXX, where XXX is constructed from the date at which the job was run.&lt;br /&gt;
&lt;br /&gt;
Update the testsuite status page by adding the log files to the release-info repository:&lt;br /&gt;
&lt;br /&gt;
  svn co https://svn.einsteintoolkit.org/www/release-info&lt;br /&gt;
  cd release-info&lt;br /&gt;
  scp machine:etrelease/*.log .&lt;br /&gt;
&lt;br /&gt;
Then commit the new/updated files.  &lt;br /&gt;
&lt;br /&gt;
To re-run the tests with an updated checkout, run the GetComponents command above with the --update flag, rebuild, delete the &amp;quot;testsuites&amp;quot; output simulation, and resubmit the job.&lt;br /&gt;
&lt;br /&gt;
=Machines=&lt;br /&gt;
&lt;br /&gt;
==Kraken==&lt;br /&gt;
&lt;br /&gt;
Edit simfactory/mdb.pm&lt;br /&gt;
&lt;br /&gt;
  -        myproxy-logon -p 7514 -s myproxy.teragrid.org -T -l @USER@ -o @SOURCEDIR@/.globus/proxy-teragrid&lt;br /&gt;
  +        myproxy-logon -p 7514 -s myproxy.teragrid.org -T -l &amp;lt;username&amp;gt; -o @SOURCEDIR@/.globus/proxy-teragrid&lt;br /&gt;
&lt;br /&gt;
where &amp;lt;username&amp;gt; is your user name on Kraken.  This is related to [https://trac.einsteintoolkit.org/ticket/381 Ticket #381]&lt;br /&gt;
&lt;br /&gt;
Change the sourcebasedir in simfactory/udb.pm to be under /lustre/scratch.  This is necessary because the Cactus directory must be visible from the compute node when running the tests (to see the parameter files, testsuite reference output and test.ccl files), and the home directory on Kraken is not visible from the compute nodes.&lt;br /&gt;
&lt;br /&gt;
    set_option &amp;#039;kraken&amp;#039;, &amp;#039;sourcebasedir&amp;#039;, &amp;#039;/lustre/scratch/USERNAME&amp;#039;;&lt;br /&gt;
&lt;br /&gt;
Copy kraken.sh as kraken-testsuite.sh in simfactory/scriptfiles.  Replace the aprun command with the following:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
cd @SOURCEDIR@&lt;br /&gt;
&lt;br /&gt;
export CCTK_TESTSUITE_RUN_COMMAND=&amp;quot;aprun -n \$nprocs -d 1 \$exe \$parfile&amp;quot;&lt;br /&gt;
&lt;br /&gt;
test_dir=TEST_$(date +%Y-%m-%d-%H%M%S)&lt;br /&gt;
mkdir $test_dir&lt;br /&gt;
&lt;br /&gt;
CONFIGNAME=$(ls configs|tail) # SimFactory should provide the configuration name&lt;br /&gt;
&lt;br /&gt;
for i in 1 2 3; do&lt;br /&gt;
  case $i in&lt;br /&gt;
    1 )&lt;br /&gt;
      export CCTK_TESTSUITE_RUN_PROCESSORS=1&lt;br /&gt;
      export OMP_NUM_THREADS=1;;&lt;br /&gt;
    2 )&lt;br /&gt;
      export CCTK_TESTSUITE_RUN_PROCESSORS=2&lt;br /&gt;
      export OMP_NUM_THREADS=1;;&lt;br /&gt;
    3 )&lt;br /&gt;
      export CCTK_TESTSUITE_RUN_PROCESSORS=2&lt;br /&gt;
      export OMP_NUM_THREADS=2;;&lt;br /&gt;
  esac&lt;br /&gt;
  make $CONFIGNAME-testsuite PROMPT=no&lt;br /&gt;
  cp TEST/$CONFIGNAME/summary.log kraken__${CCTK_TESTSUITE_RUN_PROCESSORS}_${OMP_NUM_THREADS}.log&lt;br /&gt;
  mv TEST $test_dir/TEST.$i&lt;br /&gt;
done&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==Datura==&lt;br /&gt;
&lt;br /&gt;
Copy datura.sh as datura-testsuite.sh in simfactory/scriptfiles.  Replace the mpirun command with the following:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
cd @SOURCEDIR@&lt;br /&gt;
&lt;br /&gt;
test_dir=TEST_$(date +%Y-%m-%d-%H%M%S)&lt;br /&gt;
mkdir $test_dir&lt;br /&gt;
&lt;br /&gt;
CONFIGNAME=$(ls configs|tail) # SimFactory should provide the configuration name&lt;br /&gt;
&lt;br /&gt;
export CACTUS_STARTTIME=$(date +%s)&lt;br /&gt;
&lt;br /&gt;
for i in 1 2 3; do&lt;br /&gt;
  case $i in&lt;br /&gt;
    1 )&lt;br /&gt;
      export CCTK_TESTSUITE_RUN_PROCESSORS=1&lt;br /&gt;
      export OMP_NUM_THREADS=1;;&lt;br /&gt;
    2 )&lt;br /&gt;
      export CCTK_TESTSUITE_RUN_PROCESSORS=2&lt;br /&gt;
      export OMP_NUM_THREADS=1;;&lt;br /&gt;
    3 )&lt;br /&gt;
      export CCTK_TESTSUITE_RUN_PROCESSORS=2&lt;br /&gt;
      export OMP_NUM_THREADS=2;;&lt;br /&gt;
  esac&lt;br /&gt;
  export CCTK_TESTSUITE_RUN_COMMAND=&amp;quot;${MPIDIR}/bin/mpirun -v --mca btl openib,self --mca mpi_leave_pinned 0 -np \$nprocs -npernode $CCTK_TESTSUITE_RUN_PROCESSORS \$exe -L 3 \$parfile&amp;quot;&lt;br /&gt;
  make $CONFIGNAME-testsuite PROMPT=no&lt;br /&gt;
  cp TEST/$CONFIGNAME/summary.log datura__${CCTK_TESTSUITE_RUN_PROCESSORS}_${OMP_NUM_THREADS}.log&lt;br /&gt;
  mv TEST $test_dir/TEST.$i&lt;br /&gt;
done&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==BlueDrop==&lt;br /&gt;
&lt;br /&gt;
The following script is a slightly modified version of run_tests adapted to run on &lt;br /&gt;
the Power7 machine BlueDrop:&lt;br /&gt;
&lt;br /&gt;
 set -e&lt;br /&gt;
 &lt;br /&gt;
 cd Cactus&lt;br /&gt;
 &lt;br /&gt;
 #Blue drop (Note that we need to specify the absolute path for the bluedrop_run*.ll files):&lt;br /&gt;
 &lt;br /&gt;
 for i in 1 2 3; do&lt;br /&gt;
  case $i in&lt;br /&gt;
    1 )&lt;br /&gt;
     hostname | grep ^bd &amp;amp;&amp;amp; export CCTK_TESTSUITE_RUN_COMMAND=&amp;quot;poe \$exe \$parfile -retry -1 -llfile /home/bcmundim/bluedrop_run_1.ll&amp;quot;&lt;br /&gt;
      export CCTK_TESTSUITE_RUN_PROCESSORS=1&lt;br /&gt;
      export OMP_NUM_THREADS=1;;&lt;br /&gt;
    2 )&lt;br /&gt;
      hostname | grep ^bd &amp;amp;&amp;amp; export CCTK_TESTSUITE_RUN_COMMAND=&amp;quot;poe \$exe \$parfile -retry -1 -llfile /home/bcmundim/bluedrop_run_2.ll&amp;quot;&lt;br /&gt;
      export CCTK_TESTSUITE_RUN_PROCESSORS=2&lt;br /&gt;
      export OMP_NUM_THREADS=1;;&lt;br /&gt;
    3 )&lt;br /&gt;
      hostname | grep ^bd &amp;amp;&amp;amp; export CCTK_TESTSUITE_RUN_COMMAND=&amp;quot;poe \$exe \$parfile -retry -1 -llfile /home/bcmundim/bluedrop_run_2.ll&amp;quot;&lt;br /&gt;
      export CCTK_TESTSUITE_RUN_PROCESSORS=2&lt;br /&gt;
      export OMP_NUM_THREADS=2;;&lt;br /&gt;
  esac&lt;br /&gt;
  make sim-testsuite PROMPT=no&lt;br /&gt;
  mv TEST/sim/summary.log ../${HOSTNAME}__${CCTK_TESTSUITE_RUN_PROCESSORS}_${OMP_NUM_THREADS}.log&lt;br /&gt;
 done&lt;br /&gt;
&lt;br /&gt;
Remember to change the absolute path to bluedrop_run_*.ll, as in /home/bcmundim above, to the appropriate location &lt;br /&gt;
of your LoadLeveler batch job script files. The following job scripts were used to run the test suites; bluedrop_run_1.ll and bluedrop_run_2.ll, respectively:&lt;br /&gt;
&lt;br /&gt;
 ## Comment the class line to run on short queue:&lt;br /&gt;
 #@ class = debug&lt;br /&gt;
 #@ job_type = parallel&lt;br /&gt;
 ##@ node_usage = not_shared&lt;br /&gt;
 #@ node_usage = shared&lt;br /&gt;
 #@ environment = COPY_ALL&lt;br /&gt;
 #@ tasks_per_node = 1&lt;br /&gt;
 #@ node = 1&lt;br /&gt;
 #@ wall_clock_limit = 0:30:00&lt;br /&gt;
 ### uncomment below for a normal batch job&lt;br /&gt;
 # #@ output = $(host).$(jobid).$(stepid).out&lt;br /&gt;
 # #@ error = $(host).$(jobid).$(stepid).err&lt;br /&gt;
 &lt;br /&gt;
 #@ queue&lt;br /&gt;
 ## uncomment for a normal batch job&lt;br /&gt;
 # $HOME/a.out&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
 ## Comment the class line to run on short queue:&lt;br /&gt;
 #@ class = debug&lt;br /&gt;
 #@ job_type = parallel&lt;br /&gt;
 ##@ node_usage = not_shared&lt;br /&gt;
 #@ node_usage = shared&lt;br /&gt;
 #@ environment = COPY_ALL&lt;br /&gt;
 #@ tasks_per_node = 2&lt;br /&gt;
 #@ node = 1&lt;br /&gt;
 #@ wall_clock_limit = 0:30:00&lt;br /&gt;
 ### uncomment below for a normal batch job&lt;br /&gt;
 # #@ output = $(host).$(jobid).$(stepid).out&lt;br /&gt;
 # #@ error = $(host).$(jobid).$(stepid).err&lt;br /&gt;
 &lt;br /&gt;
 #@ queue&lt;br /&gt;
 ## uncomment for a normal batch job&lt;br /&gt;
 # $HOME/a.out&lt;/div&gt;</summary>
		<author><name>Bmundim</name></author>
		
	</entry>
	<entry>
		<id>https://docs.einsteintoolkit.org/et-docs/index.php?title=Testsuite_Machines&amp;diff=2230</id>
		<title>Testsuite Machines</title>
		<link rel="alternate" type="text/html" href="https://docs.einsteintoolkit.org/et-docs/index.php?title=Testsuite_Machines&amp;diff=2230"/>
		<updated>2011-04-06T05:17:12Z</updated>

		<summary type="html">&lt;p&gt;Bmundim: /* BlueDrop */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;This page contains notes and instructions for people running the ET testsuites on various different machines.  If you have experience running testsuites on a machine which is not listed here, please consider adding some information which might help others (or yourself!) in future.  &lt;br /&gt;
&lt;br /&gt;
=General=&lt;br /&gt;
&lt;br /&gt;
To check out the ET:&lt;br /&gt;
&lt;br /&gt;
  mkdir etrelease&lt;br /&gt;
  cd etrelease&lt;br /&gt;
  curl -O https://github.com/gridaphobe/CRL/raw/master/GetComponents &lt;br /&gt;
  chmod a+x GetComponents&lt;br /&gt;
  ./GetComponents --root=. -a https://svn.einsteintoolkit.org/manifest/trunk/einsteintoolkit.th&lt;br /&gt;
  cp udb.example.pm udb.pm&lt;br /&gt;
&lt;br /&gt;
In udb.pm, &lt;br /&gt;
&lt;br /&gt;
* Replace &amp;quot;redshift&amp;quot; with the name of your local machine, unless you are running on one of the supported machines.&lt;br /&gt;
&lt;br /&gt;
* Replace YOUR_LOGIN, YOUR_EMAIL_ADDRESS and YOUR_ALLOCATION as appropriate.&lt;br /&gt;
&lt;br /&gt;
* Set sourcebasedir for your local machine to be the directory containing etrelease (do not set it to etrelease itself).&lt;br /&gt;
&lt;br /&gt;
* Set your username on each machine:&lt;br /&gt;
    set_option &amp;#039;MACHINE&amp;#039;  , &amp;#039;user&amp;#039;, &amp;#039;USERNAME&amp;#039;;&lt;br /&gt;
&lt;br /&gt;
See the machine-specific notes below for any additional steps for each machine.&lt;br /&gt;
&lt;br /&gt;
  touch par/testsuite.par&lt;br /&gt;
  sim sync &amp;lt;machine&amp;gt;&lt;br /&gt;
  sim build --thornlist manifest/einsteintoolkit.th --scriptfile &amp;lt;machine&amp;gt;-testsuite.sh&lt;br /&gt;
  sim remote &amp;lt;machine&amp;gt; create-submit par/testsuite.par NSLOTS 6:00:00&lt;br /&gt;
&lt;br /&gt;
This is a dummy parameter file.&lt;br /&gt;
&lt;br /&gt;
When the job is finished, you should have the required &amp;lt;machine&amp;gt;_i_j.log files in machine:etrelease/*.log.  The testsuite output will also be stored in machine:TEST_XXX, where XXX is constructed from the date at which the job was run.&lt;br /&gt;
&lt;br /&gt;
Update the testsuite status page by adding the log files to the release-info repository:&lt;br /&gt;
&lt;br /&gt;
  svn co https://svn.einsteintoolkit.org/www/release-info&lt;br /&gt;
  cd release-info&lt;br /&gt;
  scp machine:etrelease/*.log .&lt;br /&gt;
&lt;br /&gt;
Then commit the new/updated files.  &lt;br /&gt;
&lt;br /&gt;
To re-run the tests with an updated checkout, run the GetComponents command above with the --update flag, rebuild, delete the &amp;quot;testsuites&amp;quot; output simulation, and resubmit the job.&lt;br /&gt;
&lt;br /&gt;
=Machines=&lt;br /&gt;
&lt;br /&gt;
==Kraken==&lt;br /&gt;
&lt;br /&gt;
Edit simfactory/mdb.pm&lt;br /&gt;
&lt;br /&gt;
  -        myproxy-logon -p 7514 -s myproxy.teragrid.org -T -l @USER@ -o @SOURCEDIR@/.globus/proxy-teragrid&lt;br /&gt;
  +        myproxy-logon -p 7514 -s myproxy.teragrid.org -T -l &amp;lt;username&amp;gt; -o @SOURCEDIR@/.globus/proxy-teragrid&lt;br /&gt;
&lt;br /&gt;
where &amp;lt;username&amp;gt; is your user name on Kraken.  This is related to [https://trac.einsteintoolkit.org/ticket/381 Ticket #381]&lt;br /&gt;
&lt;br /&gt;
Change the sourcebasedir in simfactory/udb.pm to be under /lustre/scratch.  This is necessary because the Cactus directory must be visible from the compute node when running the tests (to see the parameter files, testsuite reference output and test.ccl files), and the home directory on Kraken is not visible from the compute nodes.&lt;br /&gt;
&lt;br /&gt;
    set_option &amp;#039;kraken&amp;#039;, &amp;#039;sourcebasedir&amp;#039;, &amp;#039;/lustre/scratch/USERNAME&amp;#039;;&lt;br /&gt;
&lt;br /&gt;
Copy kraken.sh as kraken-testsuite.sh in simfactory/scriptfiles.  Replace the aprun command with the following:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
cd @SOURCEDIR@&lt;br /&gt;
&lt;br /&gt;
export CCTK_TESTSUITE_RUN_COMMAND=&amp;quot;aprun -n \$nprocs -d 1 \$exe \$parfile&amp;quot;&lt;br /&gt;
&lt;br /&gt;
test_dir=TEST_$(date +%Y-%m-%d-%H%M%S)&lt;br /&gt;
mkdir $test_dir&lt;br /&gt;
&lt;br /&gt;
CONFIGNAME=$(ls configs|tail) # SimFactory should provide the configuration name&lt;br /&gt;
&lt;br /&gt;
for i in 1 2 3; do&lt;br /&gt;
  case $i in&lt;br /&gt;
    1 )&lt;br /&gt;
      export CCTK_TESTSUITE_RUN_PROCESSORS=1&lt;br /&gt;
      export OMP_NUM_THREADS=1;;&lt;br /&gt;
    2 )&lt;br /&gt;
      export CCTK_TESTSUITE_RUN_PROCESSORS=2&lt;br /&gt;
      export OMP_NUM_THREADS=1;;&lt;br /&gt;
    3 )&lt;br /&gt;
      export CCTK_TESTSUITE_RUN_PROCESSORS=2&lt;br /&gt;
      export OMP_NUM_THREADS=2;;&lt;br /&gt;
  esac&lt;br /&gt;
  make $CONFIGNAME-testsuite PROMPT=no&lt;br /&gt;
  cp TEST/$CONFIGNAME/summary.log kraken__${CCTK_TESTSUITE_RUN_PROCESSORS}_${OMP_NUM_THREADS}.log&lt;br /&gt;
  mv TEST $test_dir/TEST.$i&lt;br /&gt;
done&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==Datura==&lt;br /&gt;
&lt;br /&gt;
Copy datura.sh as datura-testsuite.sh in simfactory/scriptfiles.  Replace the mpirun command with the following:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
cd @SOURCEDIR@&lt;br /&gt;
&lt;br /&gt;
test_dir=TEST_$(date +%Y-%m-%d-%H%M%S)&lt;br /&gt;
mkdir $test_dir&lt;br /&gt;
&lt;br /&gt;
CONFIGNAME=$(ls configs|tail) # SimFactory should provide the configuration name&lt;br /&gt;
&lt;br /&gt;
export CACTUS_STARTTIME=$(date +%s)&lt;br /&gt;
&lt;br /&gt;
for i in 1 2 3; do&lt;br /&gt;
  case $i in&lt;br /&gt;
    1 )&lt;br /&gt;
      export CCTK_TESTSUITE_RUN_PROCESSORS=1&lt;br /&gt;
      export OMP_NUM_THREADS=1;;&lt;br /&gt;
    2 )&lt;br /&gt;
      export CCTK_TESTSUITE_RUN_PROCESSORS=2&lt;br /&gt;
      export OMP_NUM_THREADS=1;;&lt;br /&gt;
    3 )&lt;br /&gt;
      export CCTK_TESTSUITE_RUN_PROCESSORS=2&lt;br /&gt;
      export OMP_NUM_THREADS=2;;&lt;br /&gt;
  esac&lt;br /&gt;
  export CCTK_TESTSUITE_RUN_COMMAND=&amp;quot;${MPIDIR}/bin/mpirun -v --mca btl openib,self --mca mpi_leave_pinned 0 -np \$nprocs -npernode $CCTK_TESTSUITE_RUN_PROCESSORS \$exe -L 3 \$parfile&amp;quot;&lt;br /&gt;
  make $CONFIGNAME-testsuite PROMPT=no&lt;br /&gt;
  cp TEST/$CONFIGNAME/summary.log datura__${CCTK_TESTSUITE_RUN_PROCESSORS}_${OMP_NUM_THREADS}.log&lt;br /&gt;
  mv TEST $test_dir/TEST.$i&lt;br /&gt;
done&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==BlueDrop==&lt;br /&gt;
&lt;br /&gt;
The following script is a slightly modified version of run_tests adapted to run on &lt;br /&gt;
the Power7 machine BlueDrop:&lt;br /&gt;
&lt;br /&gt;
 set -e&lt;br /&gt;
 &lt;br /&gt;
 cd Cactus&lt;br /&gt;
 &lt;br /&gt;
 #Blue drop (Note that we need to specify the absolute path for the bluedrop_run*.ll files):&lt;br /&gt;
 &lt;br /&gt;
 for i in 1 2 3; do&lt;br /&gt;
  case $i in&lt;br /&gt;
    1 )&lt;br /&gt;
     hostname | grep ^bd &amp;amp;&amp;amp; export CCTK_TESTSUITE_RUN_COMMAND=&amp;quot;poe \$exe \$parfile -retry -1 -llfile /home/bcmundim/bluedrop_run_1.ll&amp;quot;&lt;br /&gt;
      export CCTK_TESTSUITE_RUN_PROCESSORS=1&lt;br /&gt;
      export OMP_NUM_THREADS=1;;&lt;br /&gt;
    2 )&lt;br /&gt;
      hostname | grep ^bd &amp;amp;&amp;amp; export CCTK_TESTSUITE_RUN_COMMAND=&amp;quot;poe \$exe \$parfile -retry -1 -llfile /home/bcmundim/bluedrop_run_2.ll&amp;quot;&lt;br /&gt;
      export CCTK_TESTSUITE_RUN_PROCESSORS=2&lt;br /&gt;
      export OMP_NUM_THREADS=1;;&lt;br /&gt;
    3 )&lt;br /&gt;
      hostname | grep ^bd &amp;amp;&amp;amp; export CCTK_TESTSUITE_RUN_COMMAND=&amp;quot;poe \$exe \$parfile -retry -1 -llfile /home/bcmundim/bluedrop_run_2.ll&amp;quot;&lt;br /&gt;
      export CCTK_TESTSUITE_RUN_PROCESSORS=2&lt;br /&gt;
      export OMP_NUM_THREADS=2;;&lt;br /&gt;
  esac&lt;br /&gt;
  make sim-testsuite PROMPT=no&lt;br /&gt;
  mv TEST/sim/summary.log ../${HOSTNAME}__${CCTK_TESTSUITE_RUN_PROCESSORS}_${OMP_NUM_THREADS}.log&lt;br /&gt;
 done&lt;br /&gt;
&lt;br /&gt;
Remember to change the absolute path to bluedrop_run_*.ll, as in /home/bcmundim above, to the appropriate location &lt;br /&gt;
of your LoadLeveler batch job script files. The following job scripts were used to run the test suites; bluedrop_run_1.ll and bluedrop_run_2.ll, respectively:&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
 ## Comment the class line to run on short queue:&lt;br /&gt;
 #@ class = debug&lt;br /&gt;
 #@ job_type = parallel&lt;br /&gt;
 ##@ node_usage = not_shared&lt;br /&gt;
 #@ node_usage = shared&lt;br /&gt;
 #@ environment = COPY_ALL&lt;br /&gt;
 #@ tasks_per_node = 1&lt;br /&gt;
 #@ node = 1&lt;br /&gt;
 #@ wall_clock_limit = 0:30:00&lt;br /&gt;
 ### uncomment below for a normal batch job&lt;br /&gt;
 # #@ output = $(host).$(jobid).$(stepid).out&lt;br /&gt;
 # #@ error = $(host).$(jobid).$(stepid).err&lt;br /&gt;
 &lt;br /&gt;
 #@ queue&lt;br /&gt;
 ## uncomment for a normal batch job&lt;br /&gt;
 # $HOME/a.out&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
 ## Comment the class line to run on short queue:&lt;br /&gt;
 #@ class = debug&lt;br /&gt;
 #@ job_type = parallel&lt;br /&gt;
 ##@ node_usage = not_shared&lt;br /&gt;
 #@ node_usage = shared&lt;br /&gt;
 #@ environment = COPY_ALL&lt;br /&gt;
 #@ tasks_per_node = 2&lt;br /&gt;
 #@ node = 1&lt;br /&gt;
 #@ wall_clock_limit = 0:30:00&lt;br /&gt;
 ### uncomment below for a normal batch job&lt;br /&gt;
 # #@ output = $(host).$(jobid).$(stepid).out&lt;br /&gt;
 # #@ error = $(host).$(jobid).$(stepid).err&lt;br /&gt;
 &lt;br /&gt;
 #@ queue&lt;br /&gt;
 ## uncomment for a normal batch job&lt;br /&gt;
 # $HOME/a.out&lt;/div&gt;</summary>
		<author><name>Bmundim</name></author>
		
	</entry>
	<entry>
		<id>https://docs.einsteintoolkit.org/et-docs/index.php?title=Testsuite_Machines&amp;diff=2229</id>
		<title>Testsuite Machines</title>
		<link rel="alternate" type="text/html" href="https://docs.einsteintoolkit.org/et-docs/index.php?title=Testsuite_Machines&amp;diff=2229"/>
		<updated>2011-04-06T05:16:23Z</updated>

		<summary type="html">&lt;p&gt;Bmundim: /* BlueDrop */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;This page contains notes and instructions for people running the ET testsuites on various different machines.  If you have experience running testsuites on a machine which is not listed here, please consider adding some information which might help others (or yourself!) in future.  &lt;br /&gt;
&lt;br /&gt;
=General=&lt;br /&gt;
&lt;br /&gt;
To check out the ET:&lt;br /&gt;
&lt;br /&gt;
  mkdir etrelease&lt;br /&gt;
  cd etrelease&lt;br /&gt;
  curl -O https://github.com/gridaphobe/CRL/raw/master/GetComponents &lt;br /&gt;
  chmod a+x GetComponents&lt;br /&gt;
  ./GetComponents --root=. -a https://svn.einsteintoolkit.org/manifest/trunk/einsteintoolkit.th&lt;br /&gt;
  cp udb.example.pm udb.pm&lt;br /&gt;
&lt;br /&gt;
In udb.pm, &lt;br /&gt;
&lt;br /&gt;
* Replace &amp;quot;redshift&amp;quot; with the name of your local machine, unless you are running on one of the supported machines.&lt;br /&gt;
&lt;br /&gt;
* Replace YOUR_LOGIN, YOUR_EMAIL_ADDRESS and YOUR_ALLOCATION as appropriate.&lt;br /&gt;
&lt;br /&gt;
* Set sourcebasedir for your local machine to be the directory containing etrelease (do not set it to etrelease itself).&lt;br /&gt;
&lt;br /&gt;
* Set your username on each machine:&lt;br /&gt;
    set_option &amp;#039;MACHINE&amp;#039;  , &amp;#039;user&amp;#039;, &amp;#039;USERNAME&amp;#039;;&lt;br /&gt;
&lt;br /&gt;
See the machine-specific notes below for any additional steps for each machine.&lt;br /&gt;
&lt;br /&gt;
  touch par/testsuite.par&lt;br /&gt;
  sim sync &amp;lt;machine&amp;gt;&lt;br /&gt;
  sim build --thornlist manifest/einsteintoolkit.th --scriptfile &amp;lt;machine&amp;gt;-testsuite.sh&lt;br /&gt;
  sim remote &amp;lt;machine&amp;gt; create-submit par/testsuite.par NSLOTS 6:00:00&lt;br /&gt;
&lt;br /&gt;
This is a dummy parameter file.&lt;br /&gt;
&lt;br /&gt;
When the job is finished, you should have the required &amp;lt;machine&amp;gt;_i_j.log files in machine:etrelease/*.log.  The testsuite output will also be stored in machine:TEST_XXX, where XXX is constructed from the date at which the job was run.&lt;br /&gt;
&lt;br /&gt;
Update the testsuite status page by adding the log files to the release-info repository:&lt;br /&gt;
&lt;br /&gt;
  svn co https://svn.einsteintoolkit.org/www/release-info&lt;br /&gt;
  cd release-info&lt;br /&gt;
  scp machine:etrelease/*.log .&lt;br /&gt;
&lt;br /&gt;
Then commit the new/updated files.  &lt;br /&gt;
&lt;br /&gt;
To re-run the tests with an updated checkout, run the GetComponents command above with the --update flag, rebuild, delete the &amp;quot;testsuites&amp;quot; output simulation, and resubmit the job.&lt;br /&gt;
&lt;br /&gt;
=Machines=&lt;br /&gt;
&lt;br /&gt;
==Kraken==&lt;br /&gt;
&lt;br /&gt;
Edit simfactory/mdb.pm&lt;br /&gt;
&lt;br /&gt;
  -        myproxy-logon -p 7514 -s myproxy.teragrid.org -T -l @USER@ -o @SOURCEDIR@/.globus/proxy-teragrid&lt;br /&gt;
  +        myproxy-logon -p 7514 -s myproxy.teragrid.org -T -l &amp;lt;username&amp;gt; -o @SOURCEDIR@/.globus/proxy-teragrid&lt;br /&gt;
&lt;br /&gt;
where &amp;lt;username&amp;gt; is your user name on Kraken.  This is related to [https://trac.einsteintoolkit.org/ticket/381 Ticket #381]&lt;br /&gt;
&lt;br /&gt;
Change the sourcebasedir in simfactory/udb.pm to be under /lustre/scratch.  This is necessary because the Cactus directory must be visible from the compute node when running the tests (to see the parameter files, testsuite reference output and test.ccl files), and the home directory on Kraken is not visible from the compute nodes.&lt;br /&gt;
&lt;br /&gt;
    set_option &amp;#039;kraken&amp;#039;, &amp;#039;sourcebasedir&amp;#039;, &amp;#039;/lustre/scratch/USERNAME&amp;#039;;&lt;br /&gt;
&lt;br /&gt;
Copy kraken.sh as kraken-testsuite.sh in simfactory/scriptfiles.  Replace the aprun command with the following:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
cd @SOURCEDIR@&lt;br /&gt;
&lt;br /&gt;
export CCTK_TESTSUITE_RUN_COMMAND=&amp;quot;aprun -n \$nprocs -d 1 \$exe \$parfile&amp;quot;&lt;br /&gt;
&lt;br /&gt;
test_dir=TEST_$(date +%Y-%m-%d-%H%M%S)&lt;br /&gt;
mkdir $test_dir&lt;br /&gt;
&lt;br /&gt;
CONFIGNAME=$(ls configs|tail) # SimFactory should provide the configuration name&lt;br /&gt;
&lt;br /&gt;
for i in 1 2 3; do&lt;br /&gt;
  case $i in&lt;br /&gt;
    1 )&lt;br /&gt;
      export CCTK_TESTSUITE_RUN_PROCESSORS=1&lt;br /&gt;
      export OMP_NUM_THREADS=1;;&lt;br /&gt;
    2 )&lt;br /&gt;
      export CCTK_TESTSUITE_RUN_PROCESSORS=2&lt;br /&gt;
      export OMP_NUM_THREADS=1;;&lt;br /&gt;
    3 )&lt;br /&gt;
      export CCTK_TESTSUITE_RUN_PROCESSORS=2&lt;br /&gt;
      export OMP_NUM_THREADS=2;;&lt;br /&gt;
  esac&lt;br /&gt;
  make $CONFIGNAME-testsuite PROMPT=no&lt;br /&gt;
  cp TEST/$CONFIGNAME/summary.log kraken__${CCTK_TESTSUITE_RUN_PROCESSORS}_${OMP_NUM_THREADS}.log&lt;br /&gt;
  mv TEST $test_dir/TEST.$i&lt;br /&gt;
done&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==Datura==&lt;br /&gt;
&lt;br /&gt;
Copy datura.sh as datura-testsuite.sh in simfactory/scriptfiles.  Replace the mpirun command with the following:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
cd @SOURCEDIR@&lt;br /&gt;
&lt;br /&gt;
test_dir=TEST_$(date +%Y-%m-%d-%H%M%S)&lt;br /&gt;
mkdir $test_dir&lt;br /&gt;
&lt;br /&gt;
CONFIGNAME=$(ls configs|tail) # SimFactory should provide the configuration name&lt;br /&gt;
&lt;br /&gt;
export CACTUS_STARTTIME=$(date +%s)&lt;br /&gt;
&lt;br /&gt;
for i in 1 2 3; do&lt;br /&gt;
  case $i in&lt;br /&gt;
    1 )&lt;br /&gt;
      export CCTK_TESTSUITE_RUN_PROCESSORS=1&lt;br /&gt;
      export OMP_NUM_THREADS=1;;&lt;br /&gt;
    2 )&lt;br /&gt;
      export CCTK_TESTSUITE_RUN_PROCESSORS=2&lt;br /&gt;
      export OMP_NUM_THREADS=1;;&lt;br /&gt;
    3 )&lt;br /&gt;
      export CCTK_TESTSUITE_RUN_PROCESSORS=2&lt;br /&gt;
      export OMP_NUM_THREADS=2;;&lt;br /&gt;
  esac&lt;br /&gt;
  export CCTK_TESTSUITE_RUN_COMMAND=&amp;quot;${MPIDIR}/bin/mpirun -v --mca btl openib,self --mca mpi_leave_pinned 0 -np \$nprocs -npernode $CCTK_TESTSUITE_RUN_PROCESSORS \$exe -L 3 \$parfile&amp;quot;&lt;br /&gt;
  make $CONFIGNAME-testsuite PROMPT=no&lt;br /&gt;
  cp TEST/$CONFIGNAME/summary.log datura__${CCTK_TESTSUITE_RUN_PROCESSORS}_${OMP_NUM_THREADS}.log&lt;br /&gt;
  mv TEST $test_dir/TEST.$i&lt;br /&gt;
done&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==BlueDrop==&lt;br /&gt;
&lt;br /&gt;
The following script is a slightly modified version of run_tests adapted to run on &lt;br /&gt;
the Power7 machine BlueDrop:&lt;br /&gt;
&lt;br /&gt;
 set -e&lt;br /&gt;
 &lt;br /&gt;
 cd Cactus&lt;br /&gt;
 &lt;br /&gt;
 #Blue drop (Note that we need to specify the absolute path for the bluedrop_run*.ll files):&lt;br /&gt;
 &lt;br /&gt;
 for i in 1 2 3; do&lt;br /&gt;
  case $i in&lt;br /&gt;
    1 )&lt;br /&gt;
     hostname | grep ^bd &amp;amp;&amp;amp; export CCTK_TESTSUITE_RUN_COMMAND=&amp;quot;poe \$exe \$parfile -retry -1 -llfile /home/bcmundim/bluedrop_run_1.ll&amp;quot;&lt;br /&gt;
      export CCTK_TESTSUITE_RUN_PROCESSORS=1&lt;br /&gt;
      export OMP_NUM_THREADS=1;;&lt;br /&gt;
    2 )&lt;br /&gt;
      hostname | grep ^bd &amp;amp;&amp;amp; export CCTK_TESTSUITE_RUN_COMMAND=&amp;quot;poe \$exe \$parfile -retry -1 -llfile /home/bcmundim/bluedrop_run_2.ll&amp;quot;&lt;br /&gt;
      export CCTK_TESTSUITE_RUN_PROCESSORS=2&lt;br /&gt;
      export OMP_NUM_THREADS=1;;&lt;br /&gt;
    3 )&lt;br /&gt;
      hostname | grep ^bd &amp;amp;&amp;amp; export CCTK_TESTSUITE_RUN_COMMAND=&amp;quot;poe \$exe \$parfile -retry -1 -llfile /home/bcmundim/bluedrop_run_2.ll&amp;quot;&lt;br /&gt;
      export CCTK_TESTSUITE_RUN_PROCESSORS=2&lt;br /&gt;
      export OMP_NUM_THREADS=2;;&lt;br /&gt;
  esac&lt;br /&gt;
  make sim-testsuite PROMPT=no&lt;br /&gt;
  mv TEST/sim/summary.log ../${HOSTNAME}__${CCTK_TESTSUITE_RUN_PROCESSORS}_${OMP_NUM_THREADS}.log&lt;br /&gt;
 done&lt;br /&gt;
&lt;br /&gt;
Remember to change the absolute path to bluedrop_run_*.ll, as in /home/bcmundim above, to the appropriate location &lt;br /&gt;
of your LoadLeveler batch job script files. The following job scripts were used to run the test suites; bluedrop_run_1.ll and bluedrop_run_2.ll, respectively:&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
 ## Comment the class line to run on short queue:&lt;br /&gt;
 #@ class = debug&lt;br /&gt;
 #@ job_type = parallel&lt;br /&gt;
 ##@ node_usage = not_shared&lt;br /&gt;
 #@ node_usage = shared&lt;br /&gt;
 #@ environment = COPY_ALL&lt;br /&gt;
 #@ tasks_per_node = 1&lt;br /&gt;
 #@ node = 1&lt;br /&gt;
 #@ wall_clock_limit = 0:30:00&lt;br /&gt;
 ### uncomment below for a normal batch job&lt;br /&gt;
 # #@ output = $(host).$(jobid).$(stepid).out&lt;br /&gt;
 # #@ error = $(host).$(jobid).$(stepid).err&lt;br /&gt;
&lt;br /&gt;
 #@ queue&lt;br /&gt;
 ## uncomment for a normal batch job&lt;br /&gt;
 # $HOME/a.out&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
 ## Comment the class line to run on short queue:&lt;br /&gt;
 #@ class = debug&lt;br /&gt;
 #@ job_type = parallel&lt;br /&gt;
 ##@ node_usage = not_shared&lt;br /&gt;
 #@ node_usage = shared&lt;br /&gt;
 #@ environment = COPY_ALL&lt;br /&gt;
 #@ tasks_per_node = 2&lt;br /&gt;
 #@ node = 1&lt;br /&gt;
 #@ wall_clock_limit = 0:30:00&lt;br /&gt;
 ### uncomment below for a normal batch job&lt;br /&gt;
 # #@ output = $(host).$(jobid).$(stepid).out&lt;br /&gt;
 # #@ error = $(host).$(jobid).$(stepid).err&lt;br /&gt;
&lt;br /&gt;
 #@ queue&lt;br /&gt;
 ## uncomment for a normal batch job&lt;br /&gt;
 # $HOME/a.out&lt;/div&gt;</summary>
		<author><name>Bmundim</name></author>
		
	</entry>
	<entry>
		<id>https://docs.einsteintoolkit.org/et-docs/index.php?title=Testsuite_Machines&amp;diff=2228</id>
		<title>Testsuite Machines</title>
		<link rel="alternate" type="text/html" href="https://docs.einsteintoolkit.org/et-docs/index.php?title=Testsuite_Machines&amp;diff=2228"/>
		<updated>2011-04-06T05:09:22Z</updated>

		<summary type="html">&lt;p&gt;Bmundim: /* BlueDrop */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;This page contains notes and instructions for people running the ET testsuites on various different machines.  If you have experience running testsuites on a machine which is not listed here, please consider adding some information which might help others (or yourself!) in future.  &lt;br /&gt;
&lt;br /&gt;
=General=&lt;br /&gt;
&lt;br /&gt;
To check out the ET:&lt;br /&gt;
&lt;br /&gt;
  mkdir etrelease&lt;br /&gt;
  cd etrelease&lt;br /&gt;
  curl -O https://github.com/gridaphobe/CRL/raw/master/GetComponents &lt;br /&gt;
  chmod a+x GetComponents&lt;br /&gt;
  ./GetComponents --root=. -a https://svn.einsteintoolkit.org/manifest/trunk/einsteintoolkit.th&lt;br /&gt;
  cp udb.example.pm udb.pm&lt;br /&gt;
&lt;br /&gt;
In udb.pm, &lt;br /&gt;
&lt;br /&gt;
* Replace &amp;quot;redshift&amp;quot; with the name of your local machine, unless you are running on one of the supported machines.&lt;br /&gt;
&lt;br /&gt;
* Replace YOUR_LOGIN, YOUR_EMAIL_ADDRESS and YOUR_ALLOCATION as appropriate.&lt;br /&gt;
&lt;br /&gt;
* Set sourcebasedir for your local machine to be the directory containing etrelease (do not set it to etrelease itself).&lt;br /&gt;
&lt;br /&gt;
* Set your username on each machine:&lt;br /&gt;
    set_option &amp;#039;MACHINE&amp;#039;  , &amp;#039;user&amp;#039;, &amp;#039;USERNAME&amp;#039;;&lt;br /&gt;
&lt;br /&gt;
See the machine-specific notes below for any additional steps for each machine.&lt;br /&gt;
&lt;br /&gt;
  touch par/testsuite.par&lt;br /&gt;
  sim sync &amp;lt;machine&amp;gt;&lt;br /&gt;
  sim build --thornlist manifest/einsteintoolkit.th --scriptfile &amp;lt;machine&amp;gt;-testsuite.sh&lt;br /&gt;
  sim remote &amp;lt;machine&amp;gt; create-submit par/testsuite.par NSLOTS 6:00:00&lt;br /&gt;
&lt;br /&gt;
This is a dummy parameter file.&lt;br /&gt;
&lt;br /&gt;
When the job is finished, you should have the required &amp;lt;machine&amp;gt;_i_j.log files in machine:etrelease/*.log.  The testsuite output will also be stored in machine:TEST_XXX, where XXX is constructed from the date at which the job was run.&lt;br /&gt;
&lt;br /&gt;
Update the testsuite status page by adding the log files to the release-info repository:&lt;br /&gt;
&lt;br /&gt;
  svn co https://svn.einsteintoolkit.org/www/release-info&lt;br /&gt;
  cd release-info&lt;br /&gt;
  scp machine:etrelease/*.log .&lt;br /&gt;
&lt;br /&gt;
Then commit the new/updated files.  &lt;br /&gt;
&lt;br /&gt;
To re-run the tests with an updated checkout, run the GetComponents command above with the --update flag, rebuild, delete the &amp;quot;testsuites&amp;quot; output simulation, and resubmit the job.&lt;br /&gt;
&lt;br /&gt;
=Machines=&lt;br /&gt;
&lt;br /&gt;
==Kraken==&lt;br /&gt;
&lt;br /&gt;
Edit simfactory/mdb.pm&lt;br /&gt;
&lt;br /&gt;
  -        myproxy-logon -p 7514 -s myproxy.teragrid.org -T -l @USER@ -o @SOURCEDIR@/.globus/proxy-teragrid&lt;br /&gt;
  +        myproxy-logon -p 7514 -s myproxy.teragrid.org -T -l &amp;lt;username&amp;gt; -o @SOURCEDIR@/.globus/proxy-teragrid&lt;br /&gt;
&lt;br /&gt;
where &amp;lt;username&amp;gt; is your user name on Kraken.  This is related to [https://trac.einsteintoolkit.org/ticket/381 Ticket #381]&lt;br /&gt;
&lt;br /&gt;
Change the sourcebasedir in simfactory/udb.pm to be under /lustre/scratch.  This is necessary because the Cactus directory must be visible from the compute node when running the tests (to see the parameter files, testsuite reference output and test.ccl files), and the home directory on Kraken is not visible from the compute nodes.&lt;br /&gt;
&lt;br /&gt;
    set_option &amp;#039;kraken&amp;#039;, &amp;#039;sourcebasedir&amp;#039;, &amp;#039;/lustre/scratch/USERNAME&amp;#039;;&lt;br /&gt;
&lt;br /&gt;
Copy kraken.sh as kraken-testsuite.sh in simfactory/scriptfiles.  Replace the aprun command with the following:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
cd @SOURCEDIR@&lt;br /&gt;
&lt;br /&gt;
export CCTK_TESTSUITE_RUN_COMMAND=&amp;quot;aprun -n \$nprocs -d 1 \$exe \$parfile&amp;quot;&lt;br /&gt;
&lt;br /&gt;
test_dir=TEST_$(date +%Y-%m-%d-%H%M%S)&lt;br /&gt;
mkdir $test_dir&lt;br /&gt;
&lt;br /&gt;
CONFIGNAME=$(ls configs|tail) # SimFactory should provide the configuration name&lt;br /&gt;
&lt;br /&gt;
for i in 1 2 3; do&lt;br /&gt;
  case $i in&lt;br /&gt;
    1 )&lt;br /&gt;
      export CCTK_TESTSUITE_RUN_PROCESSORS=1&lt;br /&gt;
      export OMP_NUM_THREADS=1;;&lt;br /&gt;
    2 )&lt;br /&gt;
      export CCTK_TESTSUITE_RUN_PROCESSORS=2&lt;br /&gt;
      export OMP_NUM_THREADS=1;;&lt;br /&gt;
    3 )&lt;br /&gt;
      export CCTK_TESTSUITE_RUN_PROCESSORS=2&lt;br /&gt;
      export OMP_NUM_THREADS=2;;&lt;br /&gt;
  esac&lt;br /&gt;
  make $CONFIGNAME-testsuite PROMPT=no&lt;br /&gt;
  cp TEST/$CONFIGNAME/summary.log kraken__${CCTK_TESTSUITE_RUN_PROCESSORS}_${OMP_NUM_THREADS}.log&lt;br /&gt;
  mv TEST $test_dir/TEST.$i&lt;br /&gt;
done&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==Datura==&lt;br /&gt;
&lt;br /&gt;
Copy datura.sh as datura-testsuite.sh in simfactory/scriptfiles.  Replace the mpirun command with the following:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
cd @SOURCEDIR@&lt;br /&gt;
&lt;br /&gt;
test_dir=TEST_$(date +%Y-%m-%d-%H%M%S)&lt;br /&gt;
mkdir $test_dir&lt;br /&gt;
&lt;br /&gt;
CONFIGNAME=$(ls configs|tail) # SimFactory should provide the configuration name&lt;br /&gt;
&lt;br /&gt;
export CACTUS_STARTTIME=$(date +%s)&lt;br /&gt;
&lt;br /&gt;
for i in 1 2 3; do&lt;br /&gt;
  case $i in&lt;br /&gt;
    1 )&lt;br /&gt;
      export CCTK_TESTSUITE_RUN_PROCESSORS=1&lt;br /&gt;
      export OMP_NUM_THREADS=1;;&lt;br /&gt;
    2 )&lt;br /&gt;
      export CCTK_TESTSUITE_RUN_PROCESSORS=2&lt;br /&gt;
      export OMP_NUM_THREADS=1;;&lt;br /&gt;
    3 )&lt;br /&gt;
      export CCTK_TESTSUITE_RUN_PROCESSORS=2&lt;br /&gt;
      export OMP_NUM_THREADS=2;;&lt;br /&gt;
  esac&lt;br /&gt;
  export CCTK_TESTSUITE_RUN_COMMAND=&amp;quot;${MPIDIR}/bin/mpirun -v --mca btl openib,self --mca mpi_leave_pinned 0 -np \$nprocs -npernode $CCTK_TESTSUITE_RUN_PROCESSORS \$exe -L 3 \$parfile&amp;quot;&lt;br /&gt;
  make $CONFIGNAME-testsuite PROMPT=no&lt;br /&gt;
  cp TEST/$CONFIGNAME/summary.log datura__${CCTK_TESTSUITE_RUN_PROCESSORS}_${OMP_NUM_THREADS}.log&lt;br /&gt;
  mv TEST $test_dir/TEST.$i&lt;br /&gt;
done&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==BlueDrop==&lt;br /&gt;
&lt;br /&gt;
The following script is a slightly modified version of run_tests adapted to run on &lt;br /&gt;
the Power7 machine BlueDrop:&lt;br /&gt;
&lt;br /&gt;
 set -e&lt;br /&gt;
 &lt;br /&gt;
 cd Cactus&lt;br /&gt;
 &lt;br /&gt;
 #Blue drop (Note that we need to specify the absolute path for the bluedrop_run*.ll files):&lt;br /&gt;
 &lt;br /&gt;
 for i in 1 2 3; do&lt;br /&gt;
  case $i in&lt;br /&gt;
    1 )&lt;br /&gt;
     hostname | grep ^bd &amp;amp;&amp;amp; export CCTK_TESTSUITE_RUN_COMMAND=&amp;quot;poe \$exe \$parfile -retry -1 -llfile /home/bcmundim/bluedrop_run_1.ll&amp;quot;&lt;br /&gt;
      export CCTK_TESTSUITE_RUN_PROCESSORS=1&lt;br /&gt;
      export OMP_NUM_THREADS=1;;&lt;br /&gt;
    2 )&lt;br /&gt;
      hostname | grep ^bd &amp;amp;&amp;amp; export CCTK_TESTSUITE_RUN_COMMAND=&amp;quot;poe \$exe \$parfile -retry -1 -llfile /home/bcmundim/bluedrop_run_2.ll&amp;quot;&lt;br /&gt;
      export CCTK_TESTSUITE_RUN_PROCESSORS=2&lt;br /&gt;
      export OMP_NUM_THREADS=1;;&lt;br /&gt;
    3 )&lt;br /&gt;
      hostname | grep ^bd &amp;amp;&amp;amp; export CCTK_TESTSUITE_RUN_COMMAND=&amp;quot;poe \$exe \$parfile -retry -1 -llfile /home/bcmundim/bluedrop_run_2.ll&amp;quot;&lt;br /&gt;
      export CCTK_TESTSUITE_RUN_PROCESSORS=2&lt;br /&gt;
      export OMP_NUM_THREADS=2;;&lt;br /&gt;
  esac&lt;br /&gt;
  make sim-testsuite PROMPT=no&lt;br /&gt;
  mv TEST/sim/summary.log ../${HOSTNAME}__${CCTK_TESTSUITE_RUN_PROCESSORS}_${OMP_NUM_THREADS}.log&lt;br /&gt;
 done&lt;br /&gt;
&lt;br /&gt;
Remember to change the absolute path to bluedrop_run_*.ll, as in /home/bcmundim above, to the appropriate location &lt;br /&gt;
of your loadlever submission script files.&lt;/div&gt;</summary>
		<author><name>Bmundim</name></author>
		
	</entry>
	<entry>
		<id>https://docs.einsteintoolkit.org/et-docs/index.php?title=Testsuite_Machines&amp;diff=2227</id>
		<title>Testsuite Machines</title>
		<link rel="alternate" type="text/html" href="https://docs.einsteintoolkit.org/et-docs/index.php?title=Testsuite_Machines&amp;diff=2227"/>
		<updated>2011-04-06T05:05:51Z</updated>

		<summary type="html">&lt;p&gt;Bmundim: /* BlueDrop */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;This page contains notes and instructions for people running the ET testsuites on various different machines.  If you have experience running testsuites on a machine which is not listed here, please consider adding some information which might help others (or yourself!) in future.  &lt;br /&gt;
&lt;br /&gt;
=General=&lt;br /&gt;
&lt;br /&gt;
To check out the ET:&lt;br /&gt;
&lt;br /&gt;
  mkdir etrelease&lt;br /&gt;
  cd etrelease&lt;br /&gt;
  curl -O https://github.com/gridaphobe/CRL/raw/master/GetComponents &lt;br /&gt;
  chmod a+x GetComponents&lt;br /&gt;
  ./GetComponents --root=. -a https://svn.einsteintoolkit.org/manifest/trunk/einsteintoolkit.th&lt;br /&gt;
  cp udb.example.pm udb.pm&lt;br /&gt;
&lt;br /&gt;
In udb.pm, &lt;br /&gt;
&lt;br /&gt;
* Replace &amp;quot;redshift&amp;quot; with the name of your local machine, unless you are running on one of the supported machines.&lt;br /&gt;
&lt;br /&gt;
* Replace YOUR_LOGIN, YOUR_EMAIL_ADDRESS and YOUR_ALLOCATION as appropriate.&lt;br /&gt;
&lt;br /&gt;
* Set sourcebasedir for your local machine to be the directory containing etrelease (do not set it to etrelease itself).&lt;br /&gt;
&lt;br /&gt;
* Set your username on each machine:&lt;br /&gt;
    set_option &amp;#039;MACHINE&amp;#039;  , &amp;#039;user&amp;#039;, &amp;#039;USERNAME&amp;#039;;&lt;br /&gt;
&lt;br /&gt;
See the machine-specific notes below for any additional steps for each machine.&lt;br /&gt;
&lt;br /&gt;
  touch par/testsuite.par&lt;br /&gt;
  sim sync &amp;lt;machine&amp;gt;&lt;br /&gt;
  sim build --thornlist manifest/einsteintoolkit.th --scriptfile &amp;lt;machine&amp;gt;-testsuite.sh&lt;br /&gt;
  sim remote &amp;lt;machine&amp;gt; create-submit par/testsuite.par NSLOTS 6:00:00&lt;br /&gt;
&lt;br /&gt;
This is a dummy parameter file.&lt;br /&gt;
&lt;br /&gt;
When the job is finished, you should have the required &amp;lt;machine&amp;gt;_i_j.log files in machine:etrelease/*.log.  The testsuite output will also be stored in machine:TEST_XXX, where XXX is constructed from the date at which the job was run.&lt;br /&gt;
&lt;br /&gt;
Update the testsuite status page by adding the log files to the release-info repository:&lt;br /&gt;
&lt;br /&gt;
  svn co https://svn.einsteintoolkit.org/www/release-info&lt;br /&gt;
  cd release-info&lt;br /&gt;
  scp machine:etrelease/*.log .&lt;br /&gt;
&lt;br /&gt;
Then commit the new/updated files.  &lt;br /&gt;
&lt;br /&gt;
To re-run the tests with an updated checkout, run the GetComponents command above with the --update flag, rebuild, delete the &amp;quot;testsuites&amp;quot; output simulation, and resubmit the job.&lt;br /&gt;
&lt;br /&gt;
=Machines=&lt;br /&gt;
&lt;br /&gt;
==Kraken==&lt;br /&gt;
&lt;br /&gt;
Edit simfactory/mdb.pm&lt;br /&gt;
&lt;br /&gt;
  -        myproxy-logon -p 7514 -s myproxy.teragrid.org -T -l @USER@ -o @SOURCEDIR@/.globus/proxy-teragrid&lt;br /&gt;
  +        myproxy-logon -p 7514 -s myproxy.teragrid.org -T -l &amp;lt;username&amp;gt; -o @SOURCEDIR@/.globus/proxy-teragrid&lt;br /&gt;
&lt;br /&gt;
where &amp;lt;username&amp;gt; is your user name on Kraken.  This is related to [https://trac.einsteintoolkit.org/ticket/381 Ticket #381]&lt;br /&gt;
&lt;br /&gt;
Change the sourcebasedir in simfactory/udb.pm to be under /lustre/scratch.  This is necessary because the Cactus directory must be visible from the compute node when running the tests (to see the parameter files, testsuite reference output and test.ccl files), and the home directory on Kraken is not visible from the compute nodes.&lt;br /&gt;
&lt;br /&gt;
    set_option &amp;#039;kraken&amp;#039;, &amp;#039;sourcebasedir&amp;#039;, &amp;#039;/lustre/scratch/USERNAME&amp;#039;;&lt;br /&gt;
&lt;br /&gt;
Copy kraken.sh as kraken-testsuite.sh in simfactory/scriptfiles.  Replace the aprun command with the following:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
cd @SOURCEDIR@&lt;br /&gt;
&lt;br /&gt;
export CCTK_TESTSUITE_RUN_COMMAND=&amp;quot;aprun -n \$nprocs -d 1 \$exe \$parfile&amp;quot;&lt;br /&gt;
&lt;br /&gt;
test_dir=TEST_$(date +%Y-%m-%d-%H%M%S)&lt;br /&gt;
mkdir $test_dir&lt;br /&gt;
&lt;br /&gt;
CONFIGNAME=$(ls configs|tail) # SimFactory should provide the configuration name&lt;br /&gt;
&lt;br /&gt;
for i in 1 2 3; do&lt;br /&gt;
  case $i in&lt;br /&gt;
    1 )&lt;br /&gt;
      export CCTK_TESTSUITE_RUN_PROCESSORS=1&lt;br /&gt;
      export OMP_NUM_THREADS=1;;&lt;br /&gt;
    2 )&lt;br /&gt;
      export CCTK_TESTSUITE_RUN_PROCESSORS=2&lt;br /&gt;
      export OMP_NUM_THREADS=1;;&lt;br /&gt;
    3 )&lt;br /&gt;
      export CCTK_TESTSUITE_RUN_PROCESSORS=2&lt;br /&gt;
      export OMP_NUM_THREADS=2;;&lt;br /&gt;
  esac&lt;br /&gt;
  make $CONFIGNAME-testsuite PROMPT=no&lt;br /&gt;
  cp TEST/$CONFIGNAME/summary.log kraken__${CCTK_TESTSUITE_RUN_PROCESSORS}_${OMP_NUM_THREADS}.log&lt;br /&gt;
  mv TEST $test_dir/TEST.$i&lt;br /&gt;
done&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==Datura==&lt;br /&gt;
&lt;br /&gt;
Copy datura.sh as datura-testsuite.sh in simfactory/scriptfiles.  Replace the mpirun command with the following:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
cd @SOURCEDIR@&lt;br /&gt;
&lt;br /&gt;
test_dir=TEST_$(date +%Y-%m-%d-%H%M%S)&lt;br /&gt;
mkdir $test_dir&lt;br /&gt;
&lt;br /&gt;
CONFIGNAME=$(ls configs|tail) # SimFactory should provide the configuration name&lt;br /&gt;
&lt;br /&gt;
export CACTUS_STARTTIME=$(date +%s)&lt;br /&gt;
&lt;br /&gt;
for i in 1 2 3; do&lt;br /&gt;
  case $i in&lt;br /&gt;
    1 )&lt;br /&gt;
      export CCTK_TESTSUITE_RUN_PROCESSORS=1&lt;br /&gt;
      export OMP_NUM_THREADS=1;;&lt;br /&gt;
    2 )&lt;br /&gt;
      export CCTK_TESTSUITE_RUN_PROCESSORS=2&lt;br /&gt;
      export OMP_NUM_THREADS=1;;&lt;br /&gt;
    3 )&lt;br /&gt;
      export CCTK_TESTSUITE_RUN_PROCESSORS=2&lt;br /&gt;
      export OMP_NUM_THREADS=2;;&lt;br /&gt;
  esac&lt;br /&gt;
  export CCTK_TESTSUITE_RUN_COMMAND=&amp;quot;${MPIDIR}/bin/mpirun -v --mca btl openib,self --mca mpi_leave_pinned 0 -np \$nprocs -npernode $CCTK_TESTSUITE_RUN_PROCESSORS \$exe -L 3 \$parfile&amp;quot;&lt;br /&gt;
  make $CONFIGNAME-testsuite PROMPT=no&lt;br /&gt;
  cp TEST/$CONFIGNAME/summary.log datura__${CCTK_TESTSUITE_RUN_PROCESSORS}_${OMP_NUM_THREADS}.log&lt;br /&gt;
  mv TEST $test_dir/TEST.$i&lt;br /&gt;
done&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==BlueDrop==&lt;br /&gt;
&lt;br /&gt;
The following script is a slightly modified version of run_tests adapted to run on &lt;br /&gt;
the Power7 machine BlueDrop:&lt;br /&gt;
&lt;br /&gt;
 set -e&lt;br /&gt;
 &lt;br /&gt;
 cd Cactus&lt;br /&gt;
 &lt;br /&gt;
 #Blue drop (Note that we need to specify the absolute path for the bluedrop_run*.ll files):&lt;br /&gt;
 &lt;br /&gt;
 for i in 1 2 3; do&lt;br /&gt;
  case $i in&lt;br /&gt;
    1 )&lt;br /&gt;
     hostname | grep ^bd &amp;amp;&amp;amp; export CCTK_TESTSUITE_RUN_COMMAND=&amp;quot;poe \$exe \$parfile -retry -1 -llfile /home/bcmundim/bluedrop_run_1.ll&amp;quot;&lt;br /&gt;
      export CCTK_TESTSUITE_RUN_PROCESSORS=1&lt;br /&gt;
      export OMP_NUM_THREADS=1;;&lt;br /&gt;
    2 )&lt;br /&gt;
      hostname | grep ^bd &amp;amp;&amp;amp; export CCTK_TESTSUITE_RUN_COMMAND=&amp;quot;poe \$exe \$parfile -retry -1 -llfile /home/bcmundim/bluedrop_run_2.ll&amp;quot;&lt;br /&gt;
      export CCTK_TESTSUITE_RUN_PROCESSORS=2&lt;br /&gt;
      export OMP_NUM_THREADS=1;;&lt;br /&gt;
    3 )&lt;br /&gt;
      hostname | grep ^bd &amp;amp;&amp;amp; export CCTK_TESTSUITE_RUN_COMMAND=&amp;quot;poe \$exe \$parfile -retry -1 -llfile /home/bcmundim/bluedrop_run_2.ll&amp;quot;&lt;br /&gt;
      export CCTK_TESTSUITE_RUN_PROCESSORS=2&lt;br /&gt;
      export OMP_NUM_THREADS=2;;&lt;br /&gt;
  esac&lt;br /&gt;
  make sim-testsuite PROMPT=no&lt;br /&gt;
  mv TEST/sim/summary.log ../${HOSTNAME}__${CCTK_TESTSUITE_RUN_PROCESSORS}_${OMP_NUM_THREADS}.log&lt;br /&gt;
 done&lt;/div&gt;</summary>
		<author><name>Bmundim</name></author>
		
	</entry>
</feed>