Go to the source code of this file.
|
| None | peano4.api.taskgraph.compiler.ReportCompiledStepSequence.report_compiled_step_sequence (List["peano4.api.solversteps.Step"] steps, str title="Compiled task graph") |
| | Report the result of compiling a task graph into a linear sequence of Observers, through peano4.api.Logger() - the compiled-sequence counterpart to peano4.api.taskgraph.Graph.log_as_text()/visualise(), which report on the pre-compilation Graph/Task structure instead.
|
| |
| str | peano4.api.taskgraph.compiler.ReportCompiledStepSequence._submodel_label (submodel, access) |
| | "<name>", or "<name> [<qualifier>]" if access (one of a Step's cell_data_access/face_data_access/vertex_data_access dicts) has a Task.DataAccess qualifier on file for this submodel.
|
| |
| List[str] | peano4.api.taskgraph.compiler.ReportCompiledStepSequence._action_set_lines (step) |
| | Enumerated list of the step's action sets in invocation order, i.e.
|
| |
| None | peano4.api.taskgraph.compiler.ReportCompiledStepSequence._log_compiled_step_sequence_as_text (steps, str title) |
| |
| None | peano4.api.taskgraph.compiler.ReportCompiledStepSequence._visualise_compiled_step_sequence (steps, str title) |
| | Simplified sibling of peano4.api.taskgraph.Graph.visualise(): the same UML-state-diagram look (rounded-rectangle states, an internal-activity compartment listing "do / <name>" per action set plus "cell / <name>", "face / <name>", "vertex / <name>" per kind of mesh data the step uses, self-loops for repeating steps, initial/final pseudostates), but laid out as a single top-to-bottom chain following steps' list order, since a compiled sequence - unlike a Graph - has no dependency structure left to derive layers from; it already is the order.
|
| |