Janus Cheat Sheet - Revision history

Nmati: /* Allocation Status */

2013-06-25T00:11:48Z

‎Allocation Status

2013-06-18T22:41:57Z

‎Debugging PHASTA

2012-09-28T22:25:38Z

‎Running Jobs

2012-08-20T21:11:34Z

2012-08-20T21:10:47Z

2012-08-06T16:39:23Z

‎Debugging PHASTA

2012-08-06T16:38:46Z

2012-08-06T16:35:55Z

2012-08-06T16:34:35Z

2012-08-06T16:34:16Z

@@ Line 84: / Line 84: @@
 == Allocation Status ==
-   use Crc-allocations
+   module load utils/Crc-allocations
-   check_allocation.py
+   check_allocation
-   use Moab
+   module load Moab
    showstats -u $USER

@@ Line 60: / Line 60: @@
 == Debugging PHASTA ==
-  If you are getting hanging codes or crashing codes, compile with the pgi compilers and try the following flags on  C, C++ and Fortran:
+If you are getting hanging codes or crashing codes, compile with the pgi compilers and try the following flags on  C, C++ and Fortran:
        -Ktrap=fp -Mbounds -Kieee
-  For PHASTA with cmake, you need to:
+For PHASTA with cmake, you need to:
       CC=pgcc CXX=pgCC FC=pgfortran ccmake ../phasta
-  Then, add the compilation flags above to the following variables:
+Then, add the compilation flags above to the following variables:
      CMAKE_CXX_FLAGS and CMAKE_C_FLAGS and CMAKE_Fortran_FLAGS variables
-  Basically this will make your code crash where you get floating point exceptions, go out of bounds with arrays, or have ieee exceptions. Then if you type
+Basically this will make your code crash where you get floating point exceptions, go out of bounds with arrays, or have ieee exceptions. Then if you type
        set catchDebugger=1
-  and then
+and then
        mpirun  <exec>
-  it will launch debug windows which when you release them will stop at the point of your "foul" which REALLY helps.
+it will launch debug windows which when you release them will stop at the point of your "foul" which REALLY helps.
    More info: http://www.pgroup.com/userforum/viewtopic.php?t=1898&postdays=0&postorder=asc&start=0&sid=719a9d9871bf16add8565a398ba548f3

← Older revision		Revision as of 22:25, 28 September 2012
Line 12:		Line 12:
	use Subversion		use Subversion

		+	Viewing the list of dotkit modules (software) that you have loaded
		+	echo $_dk_inuse
	available nodes/cores:		available nodes/cores:

@@ Line 46: / Line 46: @@
 Interactive, for debugging (with totalviewer)
-   ssh -Y "login_name"@janus.rc.colorado.edu
+   ssh -Y "user_id"@janus.rc.colorado.edu
    qsub -I -X -l nodes=1:ppn=12,walltime=1:00:00 -q janus-debug

@@ Line 45: / Line 45: @@
 Interactive, for debugging (with totalviewer)
-   qsub -X -I -l nodes=1:ppn=12,walltime=1:00:00 -q janus-debug
+   qsub -I -X -l nodes=1:ppn=12,walltime=1:00:00 -q janus-debug
 Non Default allocation:

← Older revision		Revision as of 16:38, 6 August 2012
Line 59:		Line 59:

	-Ktrap=fp -Mbounds -Kieee		-Ktrap=fp -Mbounds -Kieee
		+
		+	For PHASTA with cmake, you need to:
		+
		+	CC=pgcc CXX=pgCC FC=pgfortran ccmake ../phasta
		+
		+	Then, add the compilation flags above to the following variables:
		+
		+	CMAKE_CXX_FLAGS and CMAKE_C_FLAGS and CMAKE_Fortran_FLAGS variables

	Basically this will make your code crash where you get floating point exceptions, go out of bounds with arrays, or have ieee exceptions. Then if you type		Basically this will make your code crash where you get floating point exceptions, go out of bounds with arrays, or have ieee exceptions. Then if you type

← Older revision		Revision as of 16:35, 6 August 2012
Line 69:		Line 69:

	it will launch debug windows which when you release them will stop at the point of your "foul" which REALLY helps.		it will launch debug windows which when you release them will stop at the point of your "foul" which REALLY helps.
		+	More info: http://www.pgroup.com/userforum/viewtopic.php?t=1898&postdays=0&postorder=asc&start=0&sid=719a9d9871bf16add8565a398ba548f3

	== Allocation Status ==		== Allocation Status ==