NAS - Revision history

Conrad54418: /* Running TotalView on NAS */

2024-05-02T18:39:05Z

‎Running TotalView on NAS

Conrad54418: /* Running TotalView on NAS */

2024-05-02T18:38:41Z

‎Running TotalView on NAS

Conrad54418: /* Running TotalView on NAS */

2024-05-02T18:35:56Z

‎Running TotalView on NAS

Conrad54418: /* Running TotalView on NAS */

2024-05-02T18:30:37Z

‎Running TotalView on NAS

Conrad54418: /* Running TotalView on NAS */

2024-05-02T18:29:18Z

‎Running TotalView on NAS

Conrad54418 at 18:25, 2 May 2024

2024-05-02T18:25:38Z

Conrad54418 at 18:24, 2 May 2024

2024-05-02T18:24:58Z

Jrwrigh: Add mention of using MPICC_CC

2022-11-09T16:32:33Z

Add mention of using MPICC_CC

Jrwrigh: Add Aitken to machine list

2022-10-12T22:35:25Z

Add Aitken to machine list

Jrwrigh: Add common commands

2022-09-11T22:35:19Z

Add common commands

@@ Line 155: / Line 155: @@
   totalview mpiexec_mpt.real -a -np 8 $PHASTA_CONFIG/bin/phastaC.exe
-One useful TotalView feature to use while running on NAS is "rescan libraries" which can be found in the "File" drop-down menu. You can select this option after recompiling the PHASTA code which will allow you to restart the job in TotalView without having to close and reopen the application, saving time.
+A TotalView feature that is useful while running on NAS is "rescan libraries" which can be found in the "File" drop-down menu. You can select this option after recompiling the PHASTA code which will allow you to restart the job in TotalView without having to close and reopen the application, saving time.
 With that, you should be all set! For more information about using TotalView on NAS you can visit this website: https://www.nas.nasa.gov/hecc/support/kb/totalview_95.html

← Older revision		Revision as of 18:38, 2 May 2024
Line 154:		Line 154:

	totalview mpiexec_mpt.real -a -np 8 $PHASTA_CONFIG/bin/phastaC.exe		totalview mpiexec_mpt.real -a -np 8 $PHASTA_CONFIG/bin/phastaC.exe
		+
		+	One useful TotalView feature to use while running on NAS is "rescan libraries" which can be found in the "File" drop-down menu. You can select this option after recompiling the PHASTA code which will allow you to restart the job in TotalView without having to close and reopen the application, saving time.

	With that, you should be all set! For more information about using TotalView on NAS you can visit this website: https://www.nas.nasa.gov/hecc/support/kb/totalview_95.html		With that, you should be all set! For more information about using TotalView on NAS you can visit this website: https://www.nas.nasa.gov/hecc/support/kb/totalview_95.html

← Older revision		Revision as of 18:35, 2 May 2024
Line 155:		Line 155:
	totalview mpiexec_mpt.real -a -np 8 $PHASTA_CONFIG/bin/phastaC.exe		totalview mpiexec_mpt.real -a -np 8 $PHASTA_CONFIG/bin/phastaC.exe

−	With that, you should be all set! For more information about using ~~totalview~~ on NAS you can visit this website: https://www.nas.nasa.gov/hecc/support/kb/totalview_95.html	+	With that, you should be all set! For more information about using TotalView on NAS you can visit this website: https://www.nas.nasa.gov/hecc/support/kb/totalview_95.html

@@ Line 143: / Line 143: @@
   module load comp-intel/2020.4.304
-It is important to note that the build of PHASTA on NAS that you want to debug must be built as the debug version. This will allow you to place breakpoints in the code using TotalView. PHASTA can be built as the debug version by setting the "-DCMAKE_BUILD_TYPE=Debug \" flag in the cmake file. Now, navigate to the directory in nobackup where you have your case setup to run. Define the path to the PHASTA build by running this command:
+It is important to note that the build of PHASTA on NAS that you want to debug must be built as the debug version. This will allow you to place breakpoints in the code using TotalView. PHASTA can be built as the debug version by setting the "-DCMAKE_BUILD_TYPE=Debug \" flag in the cmake file. Now, navigate to the directory in nobackup where you have your case setup to run. Define the path to the PHASTA build by executing this command:
   export PHASTA_CONFIG=[path to PHASTA build]
@@ Line 151: / Line 151: @@
   module load totalview/2023.4.16
-You may need to manually remove the "doubleRun-check" folder from the "procs_case" folder before running PHASTA. Now, to run PHASTA and debug with TotalView, run this command:
+You may need to manually remove the "doubleRun-check" folder from the "procs_case" folder before running PHASTA. Now, to run PHASTA and debug with TotalView, execute this command:
   totalview mpiexec_mpt.real -a -np 8 $PHASTA_CONFIG/bin/phastaC.exe
 With that, you should be all set! For more information about using totalview on NAS you can visit this website: https://www.nas.nasa.gov/hecc/support/kb/totalview_95.html

@@ Line 130: / Line 130: @@
   ssh -X pfe
-You'll need to again enter a NAS secure passcode. The next step is optional. If you want to use the older totalview interface that looks like the one on the viz nodes, run this command:
+You'll need to again enter a NAS secure passcode. The next step is optional. If you want to use the older TotalView interface that looks like the one on the viz nodes, run this command:
   echo false > ~/.totalview/.tvnewui
@@ Line 143: / Line 143: @@
   module load comp-intel/2020.4.304
-It is important to note that the build of PHASTA on NAS that you want to debug must be built as the debug version. This will allow you to place breakpoints in the code using totalview. PHASTA can be built as the debug version by setting the "-DCMAKE_BUILD_TYPE=Debug \" flag in the cmake file. Now, navigate to the directory in nobackup where you have your case setup to run. Define the path to the PHASTA build by running this command:
+It is important to note that the build of PHASTA on NAS that you want to debug must be built as the debug version. This will allow you to place breakpoints in the code using TotalView. PHASTA can be built as the debug version by setting the "-DCMAKE_BUILD_TYPE=Debug \" flag in the cmake file. Now, navigate to the directory in nobackup where you have your case setup to run. Define the path to the PHASTA build by running this command:
   export PHASTA_CONFIG=[path to PHASTA build]
-Now load the totalview module:
+Now load the TotalView module:
   module load totalview/2023.4.16
-You may need to manually remove the "doubleRun-check" folder from the "procs_case" folder before running PHASTA. Now, to run PHASTA and debug with totalview, run this command:
+You may need to manually remove the "doubleRun-check" folder from the "procs_case" folder before running PHASTA. Now, to run PHASTA and debug with TotalView, run this command:
   totalview mpiexec_mpt.real -a -np 8 $PHASTA_CONFIG/bin/phastaC.exe
-With that, you should be all set! For more information about using totalview on NAS you can watch the tutorial video I wrote this page based on here or visit this website: https://www.nas.nasa.gov/hecc/support/kb/totalview_95.html
+With that, you should be all set! For more information about using totalview on NAS you can visit this website: https://www.nas.nasa.gov/hecc/support/kb/totalview_95.html

← Older revision		Revision as of 18:24, 2 May 2024
Line 114:		Line 114:
	* Sometimes, <code>mpi{cc,cxx,f90}</code> will not pick the Intel compilers by default. You can check this by running <code>mpi{cc,cxx,f90} --version</code> to verify the compiler it links to.		* Sometimes, <code>mpi{cc,cxx,f90}</code> will not pick the Intel compilers by default. You can check this by running <code>mpi{cc,cxx,f90} --version</code> to verify the compiler it links to.
	** To fix this, you can set <code>export MPICC_CC=icc MPICXX_CXX=icpc MPIF90_F90=ifort</code> to force it to use the Intel compilers		** To fix this, you can set <code>export MPICC_CC=icc MPICXX_CXX=icpc MPIF90_F90=ifort</code> to force it to use the Intel compilers
		+
		+	=== Running TotalView on NAS ===
		+
		+	Using TotalView on NAS starts with adding a configuration file which will enable port forwarding on the viz nodes. On the viz nodes, run these commands:
		+
		+	cd ~/.ssh/
		+	cp ~kjansen/sshconfig config
		+
		+	Now, login to NAS sfe with X forwarding:
		+
		+	ssh -X [nas username here]@sfe6.nas.nasa.gov
		+
		+	You'll need to enter your password and NAS secure passcode. Next transfer to NAS pfe, also with X forwarding:
		+
		+	ssh -X pfe
		+
		+	You'll need to again enter a NAS secure passcode. The next step is optional. If you want to use the older totalview interface that looks like the one on the viz nodes, run this command:
		+
		+	echo false > ~/.totalview/.tvnewui
		+
		+	Now start an interactive job on NAS pfe with the following command:
		+
		+	qsub -X -I -q devel -lselect=1:ncpus=8:model=sky_ele,walltime=2:00:00
		+
		+	The number of cpus (8) should match the number of processes for the case you'll be debugging. Now on the interactive session on NAS pfe, load the correct environment that matches the build of your code. In my case it was:
		+
		+	module load mpi-hpe/mpt
		+	module load comp-intel/2020.4.304
		+
		+	It is important to note that the build of PHASTA on NAS that you want to debug must be built as the debug version. This will allow you to place breakpoints in the code using totalview. PHASTA can be built as the debug version by setting the "-DCMAKE_BUILD_TYPE=Debug \" flag in the cmake file. Now, navigate to the directory in nobackup where you have your case setup to run. Define the path to the PHASTA build by running this command:
		+
		+	export PHASTA_CONFIG=[path to PHASTA build]
		+
		+	Now load the totalview module:
		+
		+	module load totalview/2023.4.16
		+
		+	You may need to manually remove the "doubleRun-check" folder from the "procs_case" folder before running PHASTA. Now, to run PHASTA and debug with totalview, run this command:
		+
		+	totalview mpiexec_mpt.real -a -np 8 $PHASTA_CONFIG/bin/phastaC.exe
		+
		+	With that, you should be all set! For more information about using totalview on NAS you can watch the tutorial video I wrote this page based on here or visit this website:
		+
		+	https://www.nas.nasa.gov/hecc/support/kb/totalview_95.html

← Older revision		Revision as of 16:32, 9 November 2022
Line 109:		Line 109:
	* If you don't have any jobs running, you get an addition +10 to the score		* If you don't have any jobs running, you get an addition +10 to the score
	** This score bump is removed as soon as you have a running job		** This score bump is removed as soon as you have a running job
		+
		+	=== Compiling ===
		+	* Generally will want use <code>module load hpe-mpi/mpt comp-intel</code> for compiling
		+	* Sometimes, <code>mpi{cc,cxx,f90}</code> will not pick the Intel compilers by default. You can check this by running <code>mpi{cc,cxx,f90} --version</code> to verify the compiler it links to.
		+	** To fix this, you can set <code>export MPICC_CC=icc MPICXX_CXX=icpc MPIF90_F90=ifort</code> to force it to use the Intel compilers

@@ Line 26: / Line 26: @@
+|
 | Merope
 | Compute
 |-

@@ Line 87: / Line 87: @@
 Note that <code>mbind.x</code> is also socket aware, so it will distribute nodes evenly between nodes ''and'' between CPU's in each node (NAS nodes have 2 CPU's per node).
 For more information on <code>mbind.x</code>, see it's help flag (<code>mbind.x -help</code>) or [https://www.nas.nasa.gov/hecc/support/kb/using-the-mbind-tool-for-pinning_288.html NAS's documentation website].
 === See Priority "Score" in Queue ===