Utilities: Difference between revisions

From openpipeflow.org
Jump to navigation Jump to search
Line 21: Line 21:
* [[changeMp.f90]] - change <tt>i_Mp</tt> value in a state file.
* [[changeMp.f90]] - change <tt>i_Mp</tt> 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.
* [[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.
* [[prim2matlab.f90]] - extract data and write in a netcdf format for easy loading into Matlab or VisIt.


=== Runtime processing ===
=== Runtime processing ===

Revision as of 02:36, 13 December 2016

  • 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

Runtime processing

Non-problem-specific codes