The following image corresponds to fluid problemtype, but its structure is commonly used in most problemtypes. In red, the physical nature of the problem is defined. In blue, discretization and numerical parameters are specified.
However, time settings are not following the stated convention. Total interval is a physical parameter, but it's not possible to modify it. Instead of this, there are a Start and End times (physical) under Solution parameters (discretization), mixed together with Delta time (dicrete).
Looking at the Kratos implementation, thing are managed more consistently: Start and End time are owned by the AnalysisStage (physical problem) while DeltaTime is owned by the Solver (discrete problem).
The following image corresponds to fluid problemtype, but its structure is commonly used in most problemtypes. In red, the physical nature of the problem is defined. In blue, discretization and numerical parameters are specified.
However, time settings are not following the stated convention.
Totalinterval is a physical parameter, but it's not possible to modify it. Instead of this, there are aStartandEndtimes (physical) underSolutionparameters (discretization), mixed together withDelta time(dicrete).Looking at the Kratos implementation, thing are managed more consistently:
StartandEndtime are owned by theAnalysisStage(physical problem) whileDeltaTimeis owned by theSolver(discrete problem).