Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • airGRiwrm airGRiwrm
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 13
    • Issues 13
    • 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
  • #4

Closed
Open
Created May 25, 2020 by Dorchies David@david.dorchiesOwner

Overriding airGR CreateInputsModel, RunOptions and RunModel

Instead of running CreateInputsModel and RunOptions inside the SD RunModel (see: https://gitlab.irstea.fr/in-wop/griwrm/-/blob/3a1003f6ff49e3b36542bdd763c8efe5814e1a05/R/RunModelGriwrm.R#L101). Launch RunOptions once and store all options in a list of sub-basins in order to get a RunModel and Calibration more coherent with the airGR interface.

Use S3 class methods as proposed in HYCAR-Hydro/airgr#14 (comment 20100) for overriding airGR function depending of the class object used as first argument of the function.

Edited May 26, 2020 by Dorchies David
Assignee
Assign to
Time tracking