You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have checked that this issue has not already been reported.
I have checked that this bug exists on the latest version.
Reproducible Example
The method dflowfm.setup_channels in dflowfm.py specifies
"friction_type",
"friction_value",
as allowed columns, so frictiontype and frictionvalue will be dropped silently. The routine crosssections::prepare_default_friction_and_crosssection then sets
from the function parameters and at line 99 update_data_columns_attributes then adds columns "frictiontype" and "frictionvalue" which results in two different specifications. In file crosssections.py the routine set_point_crosssections passes only the fields "frictiontype" and "frictionvalue" from the frame branches on to be merged into the user supplied cross sections.
Current behaviour
Friction values supplied by user are ignored when using setup_channels
Desired behaviour
Friction values supplied by user passed on to model when using setup_channels
Additional context
No response
The text was updated successfully, but these errors were encountered:
This might be because FMModel.physics.UniFrictType was called instead of FMModel.physics.uniffricttype (mind the casing and the extra f in the keyword). This will be resolved in #139
Version checks
Reproducible Example
The method
dflowfm.setup_channels
indflowfm.py
specifiesas allowed columns, so
frictiontype
andfrictionvalue
will be dropped silently. The routinecrosssections::prepare_default_friction_and_crosssection
then setsfrom the function parameters and at line 99
update_data_columns_attributes
then adds columns"frictiontype"
and"frictionvalue"
which results in two different specifications. In filecrosssections.py
the routineset_point_crosssections
passes only the fields"frictiontype"
and"frictionvalue"
from the framebranches
on to be merged into the user supplied cross sections.Current behaviour
Friction values supplied by user are ignored when using setup_channels
Desired behaviour
Friction values supplied by user passed on to model when using setup_channels
Additional context
No response
The text was updated successfully, but these errors were encountered: