Skip to content
GitLab
Projects Groups Topics 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
    • Contributor statistics
    • Graph
    • Compare revisions
  • Issues 27
    • Issues 27
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 3
    • Merge requests 3
  • 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

La forge institutionnelle d'INRAE étant en production depuis le 10 juin 2025, nous vous invitons à y créer vos nouveaux projets.

  • IN-WOP
  • airGRiwrmairGRiwrm
  • Issues
  • #157
Closed
Open
Issue created May 28, 2024 by Dorchies David@david.dorchiesOwner

Donor defined on gauged model node turns the node into ungauged at Calibration

The feature #92 (closed) which introduced the user defined "donor" column in GRiwrm for defining manually donor nodes for ungauged nodes does not forbid to define donor for gauged nodes. Moreveor, documentation related to feature #156 (closed) which allows to define a priori nodes other than upstream nodes propose to use this same column for forcing node sequence order at calibration when the sibling a priori node is not processed before the current node.

2 bugs are identified:

  • Gauged nodes with user defined donor are turned into ungauged node at calibration
  • The number of parameter depending on upstream/intermadiate node is not handled
Assignee
Assign to
Time tracking