Tutorial for New Users - Revision history

Rhaas at 13:37, 10 February 2023

2023-02-10T13:37:28Z

Rhaas: make obsolete warning red and frame it

2023-02-10T13:30:39Z

make obsolete warning red and frame it

141.142.42.12: add warning about tutorial beng obsolete

2017-12-12T22:54:43Z

add warning about tutorial beng obsolete

Noncct giedt at 14:53, 9 December 2017

2017-12-09T14:53:47Z

184.184.191.10: /* Download, Configure, and Build */

2017-07-16T23:49:54Z

‎Download, Configure, and Build

184.184.191.10: update for release

2017-07-16T23:48:39Z

update for release

Knarf at 08:23, 10 April 2017

2017-04-10T08:23:15Z

Knarf at 08:21, 10 April 2017

2017-04-10T08:21:55Z

115.186.61.2 at 23:44, 16 February 2017

2017-02-16T23:44:51Z

129.59.117.15: /* Look at Results */

2017-02-01T14:54:03Z

‎Look at Results

@@ Line 1: / Line 1: @@
 <div style="border: 2px solid black; padding: 4px">
-<span style="color:red">'''This tutorial is obsolete.'''</span> Please use: the [http://einsteintoolkit.org/documentation/new-user-tutorial jupyter based one instead]
+[[File:warning.png|24px]]
 </div>

←Older revision		Revision as of 13:30, 10 February 2023
Line 1:		Line 1:
−	'''This tutorial is obsolete.''' Please use: the [http://einsteintoolkit.org/documentation/new-user-tutorial jupyter based one instead]	+	<div style="border: 2px solid black; padding: 4px">
		+	<span style="color:red">'''This tutorial is obsolete.'''</span> Please use: the [http://einsteintoolkit.org/documentation/new-user-tutorial jupyter based one instead]
		+	</div>

	This section provides a simple guide for compiling and running an example parameter file for the Einstein Toolkit.		This section provides a simple guide for compiling and running an example parameter file for the Einstein Toolkit.

←Older revision		Revision as of 22:54, 12 December 2017
Line 1:		Line 1:
		+	'''This tutorial is obsolete.''' Please use: the [http://einsteintoolkit.org/documentation/new-user-tutorial jupyter based one instead]
		+
	This section provides a simple guide for compiling and running an example parameter file for the Einstein Toolkit.		This section provides a simple guide for compiling and running an example parameter file for the Einstein Toolkit.

@@ Line 3: / Line 3: @@
 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.
-The example worked through below assumes that you are using the LONI resource [http://hpc.loni.org/resources/hpc/system.php?system=QB2]. If you don't have an existing account on Queen Bee you can [http://einsteintoolkit.org/request_testaccount request an account] to use for these examples.
+The example worked through below assumes that you are using the LONI resource [http://hpc.loni.org/resources/hpc/system.php?system=QB2]. If you don't have an existing account on Queen Bee you can [http://einsteintoolkit.org/request_testaccount request an account] to use for these examples.  The tutorial below assumes that you have some familiarity with Linux/UNIX command-line driven computing.  If this is something new to you, there are many resources on-line to provide basic skills in this environment.  The terminal environment used below can be opened on any Linux machine, which could be either a base-level installation, or a virtual machine (e.g., using Oracle VirtualBox [https://www.oracle.com/virtualization/virtualbox/index.html]) on top of any platform you are using, including Windows, Mac, etc.  Alternatively you can use a terminal client such as Putty [https://www.ssh.com/ssh/putty/].
 ==Prepare Tools==
-Download [https://raw.github.com/gridaphobe/CRL/ET_2017_06/GetComponents GetComponents] to checkout all the components of the Einstein Toolkit, and ensure it is executable:
+Once you have opened a terminal log-in on Queen Bee,
   wget --no-check-certificate https://raw.github.com/gridaphobe/CRL/ET_2017_06/GetComponents

@@ Line 20: / Line 20: @@
 This checks out Cactus, the Einstein Toolkit thorns, the Simulation Factory and example parameter files into a directory named Cactus.
-Note: New versions of svn (>=1.7) might show problems with the parallel checkout. If you see errors like (svn: E155037: Previous operation has not finished), try without the --parallel option.
+Note: Some versions of svn might show problems with the parallel checkout. If you see errors like (svn: E155037: Previous operation has not finished), try without the --parallel option.
 Note: If svn checkout fails for certain repository domains with a message like "Server SSL certificate verification failed: issuer is not trusted", you can force your system to accept the new certificate by checking out one of that repository's modules by hand. E.g.,

@@ Line 7: / Line 7: @@
 ==Prepare Tools==
-Download [https://raw.github.com/gridaphobe/CRL/ET_2016_11/GetComponents GetComponents] to checkout all the components of the Einstein Toolkit, and ensure it is executable:
+Download [https://raw.github.com/gridaphobe/CRL/ET_2017_06/GetComponents GetComponents] to checkout all the components of the Einstein Toolkit, and ensure it is executable:
-  wget --no-check-certificate https://raw.github.com/gridaphobe/CRL/ET_2016_11/GetComponents
+  wget --no-check-certificate https://raw.github.com/gridaphobe/CRL/ET_2017_06/GetComponents
   chmod +x GetComponents
@@ Line 16: / Line 16: @@
 Checkout the Einstein Toolkit using anonymous authentication (this may take a few minutes):
-  ./GetComponents --parallel https://bitbucket.org/einsteintoolkit/manifest/raw/ET_2016_11/einsteintoolkit.th
+  ./GetComponents --parallel https://bitbucket.org/einsteintoolkit/manifest/raw/ET_2017_06/einsteintoolkit.th
 This checks out Cactus, the Einstein Toolkit thorns, the Simulation Factory and example parameter files into a directory named Cactus.
@@ Line 24: / Line 24: @@
 Note: If svn checkout fails for certain repository domains with a message like "Server SSL certificate verification failed: issuer is not trusted", you can force your system to accept the new certificate by checking out one of that repository's modules by hand. E.g.,
-  svn co http://svn.cactuscode.org/projects/ExternalLibraries/pciutils/branches/ET_2016_11
+  svn co http://svn.cactuscode.org/projects/ExternalLibraries/pciutils/branches/ET_2017_06
 This will fail with a similar message to before, but will give you the option of accepting the certificate. Accept it permanently (p), and hit Enter. Running the GetComponents script should now work for all modules on that repository.

←Older revision		Revision as of 08:23, 10 April 2017
Line 1:		Line 1:
−	~~[[Image:Example.jpg]]~~This section provides a simple guide for compiling and running an example parameter file for the Einstein Toolkit.	+	This section provides a simple guide for compiling and running an example parameter file for the Einstein Toolkit.

	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.		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.

←Older revision		Revision as of 23:44, 16 February 2017
Line 1:		Line 1:
−	This section provides a simple guide for compiling and running an example parameter file for the Einstein Toolkit.	+	[[Image:Example.jpg]]This section provides a simple guide for compiling and running an example parameter file for the Einstein Toolkit.

	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.		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.

@@ Line 94: / Line 94: @@
 and at the gnuplot prompt type:
-  p 'hydrobase::rho.maximum.asc' u 2:3 w lp
+  p 'hydrobase-rho.maximum.asc' u 2:3 w lp
 This plots the data in column 3 (rho) as a function of the data in column 2 (time).
@@ Line 104: / Line 104: @@
 A consistent picture can be seen by plotting the minimum of the lapse:
-  p 'admbase::lapse.minimum.asc' u 2:3 w lp
+  p 'admbase-lapse.minimum.asc' u 2:3 w lp
 [[Image:Lapse_of_time.png]]