public pure function cavity_mass_thin_is_fatal(n_thin) result(is_fatal)
Is this step’s clamped-withdrawal tally a FAIL-LOUD condition?
Yes, on any count. A clamped withdrawal is one the tracked mass
source no longer matches, so from that step on the console’s
Mass Error would stop being a leak measurement while still
being printed as one — the exact failure mode the budget gate
exists to make impossible. h is nevertheless clamped first,
so the state handed to the abort path is finite and the last
printed line is meaningful.
A pure predicate, like cavity_melt_status_is_fatal, so the
suite can assert the DECISION without provoking error stop.
Nodes of different colours represent the following:
Solid arrows point from a procedure to one which it calls. Dashed
arrows point from an interface to procedures which implement that interface.
This could include the module procedures in a generic interface or the
implementation in a submodule of an interface in a parent module.
Where possible, edges connecting nodes are
given different colours to make them easier to distinguish in
large graphs.
Source Code
pure function cavity_mass_thin_is_fatal(n_thin)result(is_fatal)!! Is this step's clamped-withdrawal tally a FAIL-LOUD condition?!!!! Yes, on any count. A clamped withdrawal is one the tracked mass!! source no longer matches, so from that step on the console's!! `Mass Error` would stop being a leak measurement while still!! being printed as one — the exact failure mode the budget gate!! exists to make impossible. `h` is nevertheless clamped first,!! so the state handed to the abort path is finite and the last!! printed line is meaningful.!!!! A `pure` predicate, like `cavity_melt_status_is_fatal`, so the!! suite can assert the DECISION without provoking `error stop`.integer,intent(in)::n_thin!! `n_thin_step`.logical::is_fatalis_fatal=(n_thin>0)end function cavity_mass_thin_is_fatal