Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Register
  • Sign in
  • airGRiwrm airGRiwrm
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 18
    • Issues 18
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 0
    • Merge requests 0
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • IN-WOP
  • airGRiwrmairGRiwrm
  • Issues
  • #54
Closed
Open
Issue created Jul 28, 2021 by Dorchies David@david.dorchiesOwner

Calibration with parameter regularisation

After HYCAR-Hydro/airgr#111 (closed), automate the regularisation in the calibration.

The main challenge is that the a priori parameters and the a priori criteria used in CreateInputsCrit_DeLavenne for one sub-catchment are only known if the a priori sub-catchment has been already calibrated. So the InputsCrit object should be created on-the-fly during the network calibration.

I propose to :

  • add an optional parameter in CreateInputsCrit.GRiwrmInputsModel for specifying the use of the DeLavenne regularisation with the Id of the sub-catchment to use as a priori parameter
  • add a call to CreateInputsCrit_DeLavenne before each sub-catchment calibration
Assignee
Assign to
Time tracking