Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

mdu parameter settings not supported #568

Closed
BdGraaff opened this issue Oct 19, 2023 · 5 comments
Closed

mdu parameter settings not supported #568

BdGraaff opened this issue Oct 19, 2023 · 5 comments
Assignees
Labels
priority: high type: compatibility Changes needed to be compatible with the computational core

Comments

@BdGraaff
Copy link

We want to change the mdu parameters in a Jupyter notebook with D-HyDAMO.

  1. We want to change the settings for the 1Dsolver by using the following function:

fm.numerics.pure1d

This leads to the following error:
image

but we can easily acces the courant number:
image

and 2) We want to add a fixed weir file by using the following function:
fm.geometry.fixedweirfile

This leads to the following error:
image

where fm=hydrolib.core.dflowfm.mdu.models

We are using HYDROLIB version 0.2.0 and HYDROLIB-core version 0.4.1

@veenstrajelmer
Copy link
Collaborator

veenstrajelmer commented Jan 15, 2024

Hi @BdGraaff, thank you for creating this issue. I tried to reproduce your issue with this code:

from hydrolib.core.dflowfm import FMModel
fm = FMModel()
fm.numerics.pure1d = 1
fm.geometry.fixedweirfile = "aa"

The fixedweirfile fails since "aa" does not exist, but the property fixedweirfile is available in HYDROLIB-core. I have checked the 0.4.1 code and this property was also available back then. The keyword pure1d is missing and should be added. This is a simple fix and will hopefully be done in the near future. It is documented in the 1D2D manual

@RuudHurkmans
Copy link
Collaborator

Besides the keywords mentioned above, there are a few more keywords that are recommeded to set/change in the MDU but that are not included in hydrolib-core:

fm.numerics.epsmaxlev
fm.numerics.epsmaxlevm

and in geometry:

fm.geometry.storagenodefile

@priscavdsluis priscavdsluis added type: compatibility Changes needed to be compatible with the computational core priority: high labels Apr 9, 2024
@MRVermeulenDeltares
Copy link
Contributor

As we understand, the goal for this issue is:
add the following keyword:

  • fm.numerics.pure1d
  • fm.numerics.epsmaxlev
  • fm.numerics.epsmaxlevm
  • fm.geometry.storagenodefile

@veenstrajelmer & @rhutten is this correct?

@tim-vd-aardweg
Copy link
Contributor

Let's wait until #571 is implemented @MRVermeulenDeltares

@tim-vd-aardweg
Copy link
Contributor

The keywords pure1d, epsmaxlev and epsmaxlevm have been added (among with many other keywords) in #571:

model = FMModel()
    model.numerics.pure1d = 123
    model.numerics.cflmax = 12.34
    model.numerics.epsmaxlev = 12.34
    model.numerics.epsminlev = 12.34

The keywords fixedweirfile and storagenodefile were already present in HYDROLIB-core. I will therefore close this issue, but please let us know if you are having problems with these existing keywords.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
priority: high type: compatibility Changes needed to be compatible with the computational core
Projects
Status: Done
Development

No branches or pull requests

6 participants