Utilities: Difference between revisions
Jump to navigation
Jump to search
mNo edit summary |
m (→Building) |
||
| Line 10: | Line 10: | ||
> make install | > make install | ||
> make util | > make util | ||
The | > mv utilname.out ... | ||
The penultimate 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. | It is good practice to do a <tt>'make install'</tt> to generate a [[main.info]] file to keep alongside the executable. | ||
Revision as of 00:58, 3 July 2015
- Utilities are used to manipulate or analyse data, either during runtime or in the post-processing phase.
- Some of the utilities are non-specific to pipe flow, e.g. code for the GMRES algorithm.
- Almost all modifications can/should be made via a utility, rather than altering the core code (i.e. avoid editing the contents of the program/ directory wherever possible).
- Utilities are kept in utils/.
Building
To build, in Makefile, set UTIL = utilname (omitting the .f90 extension), then type
> make > make install > make util > mv utilname.out ...
The penultimate command creates utilname.out.
It is good practice to do a 'make install' to generate a main.info file to keep alongside the executable.
Pre/post-processing
- 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.
Runtime processing
- runtime.f90 - Processing template.
- newton.f90 - Newton-Krylov.
Non-problem-specific codes
- GMRESm.f90, arnoldi.f - Krylov-subspace methods.
- NewtonHook.f90 - Newton-hookstep method.