Diablo was first created in 2007 by Jason Hicken, and has since then been maintained by the CFD group.
Diablo has its own folder within Jetstream. It does not need to be compiled ("make" command) by itself.
Diablo should be ready to use once Jetstream is compiled.
Running
Before starting, ensure that there is one grid.g (or according to one's personalised naming convention) and one grid.con file in the directory. Also ensure that the parameters within the input.param (or alternate name) file are correct. Lists of parameters may be found in the user's manual and on this page. The true list is likely a union of those two sets. This input file should be in the same directory.
Type "jetstream_x86_64 >& screen" to run Jetstream (replacing the first half with a renamed executable if necessary). The executable will produce the following files:
screen - displays the standard output of Jetstream.
results.q - the extension signifies a solution file.
results.his - the extension signifies a convergence history file (general; containing Newton--Krylov iteration number, runtime, residuals, etc.)
results.solv - the extension signifies a convergence history file (detailed; containing FGMRES iterations)
Other files may be produced depending on whether one performed a flowsolve or a full optimisation, and whether one ran it on a local machine or on a cluster.
Restarting
To restart, one must have the results files (results.his, results.q, results.solv, etc.) from a previous run.
Set the parameter "restart" to ".true." and "use_frstrm" to ".false.", then re-run Diablo or resubmit the slip to the computing cluster.
HPACF/SciNet
There is a standard submit script for running cases on HPACF or SciNet. It's best to obtain a template from someone in the lab because different versions of Jetstream require different commands to be included.
Parameters
Check here for description of Diablo/Jetstream parameters
Overview
Diablo was first created in 2007 by Jason Hicken, and has since then been maintained by the CFD group.Diablo has its own folder within Jetstream. It does not need to be compiled ("make" command) by itself.
Table of Contents
Operation
Diablo should be ready to use once Jetstream is compiled.Running
Before starting, ensure that there is one grid.g (or according to one's personalised naming convention) and one grid.con file in the directory. Also ensure that the parameters within the input.param (or alternate name) file are correct. Lists of parameters may be found in the user's manual and on this page. The true list is likely a union of those two sets. This input file should be in the same directory.Type "jetstream_x86_64 >& screen" to run Jetstream (replacing the first half with a renamed executable if necessary). The executable will produce the following files:
screen - displays the standard output of Jetstream.
results.q - the extension signifies a solution file.
results.his - the extension signifies a convergence history file (general; containing Newton--Krylov iteration number, runtime, residuals, etc.)
results.solv - the extension signifies a convergence history file (detailed; containing FGMRES iterations)
Other files may be produced depending on whether one performed a flowsolve or a full optimisation, and whether one ran it on a local machine or on a cluster.
Restarting
To restart, one must have the results files (results.his, results.q, results.solv, etc.) from a previous run.Set the parameter "restart" to ".true." and "use_frstrm" to ".false.", then re-run Diablo or resubmit the slip to the computing cluster.
HPACF/SciNet
There is a standard submit script for running cases on HPACF or SciNet. It's best to obtain a template from someone in the lab because different versions of Jetstream require different commands to be included.Parameters
Check here for description of Diablo/Jetstream parametersSupplementary Materials