Utilities: Difference between revisions

Revision as of 01:01, 15 August 2014

Almost all changes can/should be made via a utility, rather than altering the core code in the program/ directory.
Utilities are kept in utils/

To build, in Makefile, set UTIL = utilname (omitting the .f90 extension), then type

> make
> make install
> make util

The last command creates utilname.out.

It is good practice to do a 'make install' to generate a main.info file to keep alongside the executable.

main.info - Record of settings at compiletime
ic.f90 - Pre/Post-processing template.
describe_state.f90 - check time/parameters; see also main.info for outputs.
changeMp.f90 - change i_Mp value in a state file.
change_Mp_alpha.f90 - make copies of a state, or extract modes, dependent on changes in length or azimuthal symmetry.
prim2matlab.f90 - convert to matlab/visit-readable netcdf.

@@ Line 1: / Line 1: @@
-Utilities are kept in <tt>utils/</tt>
+* Almost all changes can/should be made via a utility, '''rather than altering the core code''' in the <tt>program/</tt> directory.
+* Utilities are kept in <tt>utils/</tt>
-To build, in <tt>Makefile</tt>, set <tt>UTIL = utilname</tt> (omitting the <tt>.f90</tt> extension), then type <tt>'make util'</tt> which builds <tt>utilname.out</tt>.
+=== Building ===
+To build, in <tt>Makefile</tt>, set <tt>UTIL = utilname</tt> (omitting the <tt>.f90</tt> extension), then type
+ > make
+ > make install
+ > make util
+The last command creates <tt>utilname.out</tt>.
 It is good practice to do a <tt>'make install'</tt> to generate a [[main.info]] file to keep alongside the executable.