Installing and running on Stampede2 - Revision history

Rhaas: remove page since its content is very generic and by now stampede2 is "just another cluster"

2018-08-31T14:36:04Z

remove page since its content is very generic and by now stampede2 is "just another cluster"

98.194.49.173 at 16:48, 25 December 2017

2017-12-25T16:48:57Z

98.194.49.173 at 16:35, 25 December 2017

2017-12-25T16:35:44Z

Noncct giedt at 21:07, 22 December 2017

2017-12-22T21:07:13Z

Noncct giedt at 22:24, 17 December 2017

2017-12-17T22:24:08Z

Noncct giedt at 22:21, 17 December 2017

2017-12-17T22:21:35Z

Noncct giedt at 22:19, 17 December 2017

2017-12-17T22:19:11Z

New page

The beginning steps are quite similar to the tutorial for beginners listed above. However, various modifications have to be made in order to accommodate the working environment at Stampede2, which is the successor to Stampede1. The guide given below will walk you through this process. Anyone who knows better ways to do what is outlined here is welcome to edit this page (mercilessly, as stated elsewhere!).

←Older revision		Revision as of 14:36, 31 August 2018
Line 1:		Line 1:
−	The beginning steps are quite similar to the tutorial for beginners listed above. However, various modifications have to be made in order to accommodate the working environment at Stampede2, which is the successor to Stampede1. The guide given below will walk you through this process. Anyone who knows better ways to do what is outlined here is welcome to edit this page (mercilessly, as stated elsewhere!).

−	~~The first step is, as usual, to grab GetComponents and make it executable:~~
−
−	~~curl -O -L https://raw.githubusercontent.com/gridaphobe/CRL/ET_2017_06/GetComponents~~
−	~~chmod +x GetComponents~~
−
−	~~Then you have to retrieve everything~~
−
−	~~./GetComponents https://bitbucket.org/einsteintoolkit/manifest/raw/ET_2017_06/einsteintoolkit.th~~
−
−	~~Next move into Cactus and run the setup~~
−
−	~~cd Cactus~~
−	~~./simfactory/bin/sim setup~~
−
−	This will produce the file "simfactory/etc/defs.local.ini". You will be prompted for, among other things, your allocation. That will be something like TG-TRA160063. You will need this in order to run jobs in the batch queues.
−
−	~~Next comes the build. Be prepared to wait quit a while (and leave your computer up, running and connected to Stampede2 for possibly a few hours):~~
−
−	~~./simfactory/bin/sim build --machine stampede2 --thornlist manifest/einsteintoolkit.th sim-knl~~

←Older revision		Revision as of 16:48, 25 December 2017
Line 20:		Line 20:

	./simfactory/bin/sim build --machine stampede2 --thornlist manifest/einsteintoolkit.th sim-knl		./simfactory/bin/sim build --machine stampede2 --thornlist manifest/einsteintoolkit.th sim-knl
−
−	~~This does not work since the simfactory folder does not contain stampede2~~

←Older revision		Revision as of 16:35, 25 December 2017
Line 20:		Line 20:

	./simfactory/bin/sim build --machine stampede2 --thornlist manifest/einsteintoolkit.th sim-knl		./simfactory/bin/sim build --machine stampede2 --thornlist manifest/einsteintoolkit.th sim-knl
		+
		+	This does not work since the simfactory folder does not contain stampede2

←Older revision		Revision as of 21:07, 22 December 2017
Line 1:		Line 1:
	The beginning steps are quite similar to the tutorial for beginners listed above. However, various modifications have to be made in order to accommodate the working environment at Stampede2, which is the successor to Stampede1. The guide given below will walk you through this process. Anyone who knows better ways to do what is outlined here is welcome to edit this page (mercilessly, as stated elsewhere!).		The beginning steps are quite similar to the tutorial for beginners listed above. However, various modifications have to be made in order to accommodate the working environment at Stampede2, which is the successor to Stampede1. The guide given below will walk you through this process. Anyone who knows better ways to do what is outlined here is welcome to edit this page (mercilessly, as stated elsewhere!).

−	~~Once~~ you have ~~grabbed~~ GetComponents and ~~retrieved everything,~~ run the ./simfactory/bin/sim setup. This will produce the file "simfactory/etc/defs.local.ini". ~~The first job is to edit~~ this to ~~have~~ the ~~module loads that are consistent with~~ the Stampede2 ~~environment~~.	+	The first step is, as usual, to grab GetComponents and make it executable:
		+
		+	curl -O -L https://raw.githubusercontent.com/gridaphobe/CRL/ET_2017_06/GetComponents
		+	chmod +x GetComponents
		+
		+	Then you have to retrieve everything
		+
		+	./GetComponents https://bitbucket.org/einsteintoolkit/manifest/raw/ET_2017_06/einsteintoolkit.th
		+
		+	Next move into Cactus and run the setup
		+
		+	cd Cactus
		+	./simfactory/bin/sim setup
		+
		+	This will produce the file "simfactory/etc/defs.local.ini". You will be prompted for, among other things, your allocation. That will be something like TG-TRA160063. You will need this in order to run jobs in the batch queues.
		+
		+	Next comes the build. Be prepared to wait quit a while (and leave your computer up, running and connected to Stampede2 for possibly a few hours):
		+
		+	./simfactory/bin/sim build --machine stampede2 --thornlist manifest/einsteintoolkit.th sim-knl

←Older revision		Revision as of 22:24, 17 December 2017
Line 1:		Line 1:
	The beginning steps are quite similar to the tutorial for beginners listed above. However, various modifications have to be made in order to accommodate the working environment at Stampede2, which is the successor to Stampede1. The guide given below will walk you through this process. Anyone who knows better ways to do what is outlined here is welcome to edit this page (mercilessly, as stated elsewhere!).		The beginning steps are quite similar to the tutorial for beginners listed above. However, various modifications have to be made in order to accommodate the working environment at Stampede2, which is the successor to Stampede1. The guide given below will walk you through this process. Anyone who knows better ways to do what is outlined here is welcome to edit this page (mercilessly, as stated elsewhere!).

−	Once you have grabbed GetComponents and retrieved everything, run the ./simfactory/bin/sim setup	+	Once you have grabbed GetComponents and retrieved everything, run the ./simfactory/bin/sim setup. This will produce the file "simfactory/etc/defs.local.ini". The first job is to edit this to have the module loads that are consistent with the Stampede2 environment.

←Older revision		Revision as of 22:21, 17 December 2017
Line 1:		Line 1:
	The beginning steps are quite similar to the tutorial for beginners listed above. However, various modifications have to be made in order to accommodate the working environment at Stampede2, which is the successor to Stampede1. The guide given below will walk you through this process. Anyone who knows better ways to do what is outlined here is welcome to edit this page (mercilessly, as stated elsewhere!).		The beginning steps are quite similar to the tutorial for beginners listed above. However, various modifications have to be made in order to accommodate the working environment at Stampede2, which is the successor to Stampede1. The guide given below will walk you through this process. Anyone who knows better ways to do what is outlined here is welcome to edit this page (mercilessly, as stated elsewhere!).
		+
		+	Once you have grabbed GetComponents and retrieved everything, run the ./simfactory/bin/sim setup