Flow123d  DF_patch_fe_data_tables-65e7202
Input Classes

Overview of assembly process

We assume that the input data of the program can be represented by a tree. The leave nodes of the tree contain actual data and has one of the 'scalar' types represented by the classes in Input::Type namespace : Bool, Integer, Double, String, and FileName. The branching nodes of the input tree can be either of type Array or type Record (or Abstract). Classes derived from Input::Type::TypeBase only describes structure of the input tree which is independent of actual format of the input data. All nodes of tree allows definition of input attributes, which are optional for every node. Base attributes are defined in Input::Type::Attributes, special attributes of Flow123D in FlowAttributes. These structures contain common attributes, user can define other else.

Instances of the classes from the Input::Type namespace form a declaration-tree that is later used by a reader of the particular file format (currently we support YAML and JSON through the Input::ReaderToStorage reader) to interpret the input data, check its structure, possibly use default values and put the raw data into an intermediate storage-tree formed be Input:Storage classes.

Finally, the data are accessible through accessors Input::Record, Input::Array, and Input::AbstractRecord. These accessors holds pointers into declaration tree as well as into the data storage tree and provides unified access to the data.

Furthermore, the declaration-tree can output itself provided a basic documentation of the input data structure, that is consistent with the actual state.

Here is simple scheme of information exchange between classes:

Practical usage

In order to use input interface you have to create declaration-tree, namely Selection, Record, and Abstract types has to be declared by specification of its keys. We suggest to have a static method that returns Input::Type::Record for ever class which is initialized from input interface. Example of usage follows:

class Mesh {
using namespace Input::Type;
return Record("Mesh", "Full description of computational mesh.")
.declare_key("mesh_name", String(), Default::optional(),"Optional name of the mesh")
.declare_key("mesh_file", FileName::input(), Default("mesh.msh"), "Principial mesh input file")
.declare_key("materials_to_remove", Array(Integer()), "Removes elements with material ID that appears in this list.")
.close();
}
: name( input.val<string>("mesh_name") )
{
string fname = input.val<FilePath>("mesh_file");
boundary = new Boundary( input.val<Input::Record>("boundary") );
std::vector<int> ids_to_remove;
input.val<Input::Array>("materials_to_remove").copy_to( ids_to_remove );
}
}
Dedicated class for storing path to input and output files.
Definition: file_path.hh:54
Accessor to input data conforming to declared Array.
Definition: accessors.hh:566
Accessor to the data with type Type::Record.
Definition: accessors.hh:291
const Ret val(const string &key) const
Record type proxy class.
Definition: type_record.hh:182
Definition: mesh.h:362
Boundary boundary(uint edge_idx) const override
Definition: mesh.cc:328
friend class Boundary
Definition: mesh.h:692
Mesh()
Definition: mesh.cc:239
static const Input::Type::Record & get_input_type()
Definition: mesh.cc:213

The accessor for the root Input::Record is provided by the reader class ( ReaderToStorage.get_root_interface<>() )