Other useful scripts - Revision history

import>Jss43: /* scratchrestart.pl */

2009-10-01T13:38:34Z

scratchrestart.pl

← Older revision		Revision as of 13:38, 1 October 2009
Line 3:		Line 3:
	= scratchrestart.pl =		= scratchrestart.pl =

	A common issue is running over quota on the clusters, due to each calculation generating a large file (e.g. CPMD RESTART files). [[Media:~~scratchrestart~~.txt \| scratchrestart.pl]] attempts to solve this by searching recursively through the directory tree (from the working directory) and moving all files matching a regular expression to a scratch disk, leaving behind a symbolic link to the file's new location and leaving all other files untouched. Warning: you will be asked for confirmation only once.		A common issue is running over quota on the clusters, due to each calculation generating a large file (e.g. CPMD RESTART files). [[Media:scratchrestart2.txt \| scratchrestart.pl]] attempts to solve this by searching recursively through the directory tree (from the working directory) and moving all files matching a regular expression to a scratch disk, leaving behind a symbolic link to the file's new location and leaving all other files untouched. Warning: you will be asked for confirmation only once.

	<pre>		<pre>

import>Jss43 at 14:49, 15 July 2009

2009-07-15T14:49:48Z

← Older revision		Revision as of 14:49, 15 July 2009
Line 21:		Line 21:
	= testcode =		= testcode =

	~~[http://www-alavi.ch.cam.ac.uk/tools/testcode-r10684.tar testcode]~~ Test that code at least reproduces previous results by running a set of test calculations and comparing to "benchmarks": useful to test for regressions, compilation issues and optimisations~~. Requires a script that analyses output of the calculations. Integrated with subversion (but this is not required)~~. The Alavi group use this for automated nightly testing of their software and during development work.		Test that code at least reproduces previous results by running a set of test calculations and comparing to "benchmarks": useful to test for regressions, compilation issues and optimisations. The Alavi group use this for automated nightly testing of their software and during development work.

	Features:		Features:
	* Flexible job specification, so that a few jobs or job categories can be tested at a time, allowing for both quick tests when developing a small area of the code and a more comprehensive set of tests.		* Flexible job specification, so that a few jobs or job categories can be tested at a time, allowing for both quick tests when developing a small area of the code and a more comprehensive set of tests.
	* Multiple tests in the same job directory.		* Multiple tests in the same job directory.
	* Ability to test more than one codebase in one test suite. This is not particularly appropriate for very disparate codes~~: see the benchmarks section for further details~~.		* Ability to test more than one codebase in one test suite. This is not particularly appropriate for very disparate codes.
	* Easy to adapt: all the configuration is given in a simple syntax in config files.		* Easy to adapt: all the configuration is given in a simple syntax in config files.
	* Can produce benchmarks for future comparisons.		* Can produce benchmarks for future comparisons.
⚫	* Can be used in conjunction with checktest.py ~~(not yet released)~~ and cron to regularly ~~check~~ an ~~svn~~ repository ~~code~~.
	* Can run the test jobs either locally or by submission to a cluster.		* Can run the test jobs either locally or by submission to a cluster.
		⚫	* Can be used in conjunction with checktest.py and cron to regularly checkout a code from a version control repository, compile and then test it.

	See the ~~README file~~ for more information.		See the documentation for more information.

			Available for download from [http://www.cmth.ph.ic.ac.uk/people/j.spencer/code.php].

	= Memory Manager =		= Memory Manager =
Line 38:		Line 40:
	Fortran module to log and check memory allocations. The debugging mode prints out all memory log activities. Outputs the peak memory usage and information about the largest arrays.		Fortran module to log and check memory allocations. The debugging mode prints out all memory log activities. Outputs the peak memory usage and information about the largest arrays.

	[[Media:MemoryManagement.F90.txt \| source code]].

	[http://www-alavi.ch.cam.ac.uk/tools/MemoryManagement.tar tarball] containing the source and an example program. After downloading and extracting, compile and run using:
	<pre>		<pre>
	jss43@keiko:~/testmem> make
	jss43@keiko:~/testmem> ./testmem.x		jss43@keiko:~/testmem> ./testmem.x

Line 70:		Line 68:
	Goodbye.		Goodbye.
	</pre>		</pre>

			Available for download from [http://www.cmth.ph.ic.ac.uk/people/j.spencer/code.php].

import>Jss43: /* testcode */ updated tarball released

2008-08-10T22:00:26Z

testcode: updated tarball released

← Older revision		Revision as of 22:00, 10 August 2008
Line 21:		Line 21:
	= testcode =		= testcode =

	[http://www-alavi.ch.cam.ac.uk/tools/testcode-~~r10123~~.tar testcode] Test that code at least reproduces previous results by running a set of test calculations and comparing to "benchmarks": useful to test for regressions, compilation issues and optimisations. Requires a script that analyses output of the calculations. Integrated with subversion (but this is not required). The Alavi group use this for automated nightly testing of their software and during development work.		[http://www-alavi.ch.cam.ac.uk/tools/testcode-r10684.tar testcode] Test that code at least reproduces previous results by running a set of test calculations and comparing to "benchmarks": useful to test for regressions, compilation issues and optimisations. Requires a script that analyses output of the calculations. Integrated with subversion (but this is not required). The Alavi group use this for automated nightly testing of their software and during development work.

	Features:		Features:

import>Jss43 at 11:24, 24 July 2008

2008-07-24T11:24:25Z

@@ Line 1: / Line 1: @@
-A place to share non-research specific scripts that could be useful to others.
+A place to share non-research specific code that could be useful to others.
 = scratchrestart.pl =
@@ Line 33: / Line 33: @@
 See the README file for more information.

import>Cen1001: Other useful scipts moved to Other useful scripts

2008-07-16T07:04:54Z

Other useful scipts moved to Other useful scripts

← Older revision	Revision as of 07:04, 16 July 2008
(No difference)

import>Jss43: /* testcode */ update to r10123

2008-07-15T15:10:21Z

testcode: update to r10123

← Older revision		Revision as of 15:10, 15 July 2008
Line 21:		Line 21:
	= testcode =		= testcode =

	[http://www-alavi.ch.cam.ac.uk/tools/testcode-~~r9746~~.tar testcode] Test that code at least reproduces previous results by running a set of test calculations and comparing to "benchmarks": useful to test for regressions, compilation issues and optimisations. Requires a script that analyses output of the calculations. Integrated with subversion (but this is not required). The Alavi group use this for automated nightly testing of their software and during development work.		[http://www-alavi.ch.cam.ac.uk/tools/testcode-r10123.tar testcode] Test that code at least reproduces previous results by running a set of test calculations and comparing to "benchmarks": useful to test for regressions, compilation issues and optimisations. Requires a script that analyses output of the calculations. Integrated with subversion (but this is not required). The Alavi group use this for automated nightly testing of their software and during development work.

	Features:		Features:
Line 30:		Line 30:
	* Can produce benchmarks for future comparisons.		* Can produce benchmarks for future comparisons.
	* Can be used in conjunction with checktest.py (not yet released) and cron to regularly check an svn repository code.		* Can be used in conjunction with checktest.py (not yet released) and cron to regularly check an svn repository code.
			* Can run the test jobs either locally or by submission to a cluster.

	See the README file for more information.		See the README file for more information.

import>Jss43: /* testcode */ point to latest version of testcode and feature update.

2008-06-24T10:34:21Z

testcode: point to latest version of testcode and feature update.

← Older revision		Revision as of 10:34, 24 June 2008
Line 21:		Line 21:
	= testcode =		= testcode =

	[http://www-alavi.ch.cam.ac.uk/tools/testcode-~~r9408~~.tar testcode] Test that code at least reproduces previous results by running a set of test calculations and comparing to "benchmarks": useful to test for regressions, compilation issues and optimisations. Requires a script that analyses output of the calculations. Integrated with subversion (but this is not required). The Alavi group use this for automated nightly testing of their software and during development work.		[http://www-alavi.ch.cam.ac.uk/tools/testcode-r9746.tar testcode] Test that code at least reproduces previous results by running a set of test calculations and comparing to "benchmarks": useful to test for regressions, compilation issues and optimisations. Requires a script that analyses output of the calculations. Integrated with subversion (but this is not required). The Alavi group use this for automated nightly testing of their software and during development work.

	Features:		Features:
	* Flexible job specification, so that a few jobs or job categories can be tested at a time, allowing for both quick tests when developing a small area of the code and a more comprehensive set of tests.		* Flexible job specification, so that a few jobs or job categories can be tested at a time, allowing for both quick tests when developing a small area of the code and a more comprehensive set of tests.
			* Multiple tests in the same job directory.
	* Ability to test more than one codebase in one test suite. This is not particularly appropriate for very disparate codes: see the benchmarks section for further details.		* Ability to test more than one codebase in one test suite. This is not particularly appropriate for very disparate codes: see the benchmarks section for further details.
	* Easy to adapt: all the configuration is given in a simple syntax in config files.		* Easy to adapt: all the configuration is given in a simple syntax in config files.

import>Jss43: /* testcode */

2008-06-05T15:13:21Z

testcode

← Older revision		Revision as of 15:13, 5 June 2008
Line 21:		Line 21:
	= testcode =		= testcode =

	[http://www-alavi.ch.cam.ac.uk/tools/testcode.tar testcode] Test that code at least reproduces previous results by running a set of test calculations and comparing to "benchmarks": useful to test for regressions, compilation issues and optimisations. Requires a script that analyses output of the calculations. Integrated with subversion (but this is not required). The Alavi group use this for automated nightly testing of their software and during development work.		[http://www-alavi.ch.cam.ac.uk/tools/testcode-r9408.tar testcode] Test that code at least reproduces previous results by running a set of test calculations and comparing to "benchmarks": useful to test for regressions, compilation issues and optimisations. Requires a script that analyses output of the calculations. Integrated with subversion (but this is not required). The Alavi group use this for automated nightly testing of their software and during development work.

	Features:		Features:

import>Jss43: /* testcode */

2008-05-16T14:29:10Z

testcode

← Older revision		Revision as of 14:29, 16 May 2008
Line 28:		Line 28:
	* Easy to adapt: all the configuration is given in a simple syntax in config files.		* Easy to adapt: all the configuration is given in a simple syntax in config files.
	* Can produce benchmarks for future comparisons.		* Can produce benchmarks for future comparisons.
	* Can be used in conjunction with checktest.py (not ~~released~~ yet) and cron to regularly check an svn repository code.		* Can be used in conjunction with checktest.py (not yet released) and cron to regularly check an svn repository code.

	See the README file for more information.		See the README file for more information.

import>Jss43 at 14:28, 16 May 2008

2008-05-16T14:28:50Z

← Older revision		Revision as of 14:28, 16 May 2008
Line 18:		Line 18:

	This is used for moving files to /storage on tardis: you will need to change the value of the $scratch variable to be the name of your scratch disk.		This is used for moving files to /storage on tardis: you will need to change the value of the $scratch variable to be the name of your scratch disk.

			= testcode =

			[http://www-alavi.ch.cam.ac.uk/tools/testcode.tar testcode] Test that code at least reproduces previous results by running a set of test calculations and comparing to "benchmarks": useful to test for regressions, compilation issues and optimisations. Requires a script that analyses output of the calculations. Integrated with subversion (but this is not required). The Alavi group use this for automated nightly testing of their software and during development work.

			Features:
			* Flexible job specification, so that a few jobs or job categories can be tested at a time, allowing for both quick tests when developing a small area of the code and a more comprehensive set of tests.
			* Ability to test more than one codebase in one test suite. This is not particularly appropriate for very disparate codes: see the benchmarks section for further details.
			* Easy to adapt: all the configuration is given in a simple syntax in config files.
			* Can produce benchmarks for future comparisons.
			* Can be used in conjunction with checktest.py (not released yet) and cron to regularly check an svn repository code.

			See the README file for more information.