Skip to content
GitLab
    • Explore Projects Groups Topics Snippets
Projects Groups Topics Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Register
  • Sign in
  • evalhyd-cpp evalhyd-cpp
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributor statistics
    • Graph
    • Compare revisions
  • Issues 3
    • Issues 3
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 1
    • Merge requests 1
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Package Registry
    • Terraform modules
  • Monitor
    • Monitor
    • Metrics
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar

En prévision de l'arrivée de la forge institutionnelle INRAE, nous vous invitons à créer vos nouveaux projets sur la forge MIA.

  • HYCAR-HydroHYCAR-Hydro
  • evalhydevalhyd
  • evalhyd-cppevalhyd-cpp
  • Issues
  • #8
Something went wrong while setting issue due date.
Closed
Open
Issue created 1 year ago by Thibault Hallouin@thibault.hallouinOwner
  • New related issue

  • New related issue

bug when using calendar years instead of hydrological years for bootstrap

Closed

bug when using calendar years instead of hydrological years for bootstrap

It is expected that when using the bootstrapping functionality, the user will provide series of complete hydrological years (e.g. period of three years from 2001-10-01 until 2004-09-30 in the northern hemisphere), it is not enforced, and complete calendar years can be provided (e.g. period of three years from 2001-01-01 until 2003-12-31).

However, in practice, there is a bug, because in the first case 2004-2001=3 (so all three years are sampled), but in the second case 2003-2001=2 (so only two years are sampled). This is a special case when the series starts on 1st of January, as soon as the series starts on 2nd of January the problem disappears.

In evalhyd, when using calendar years, it fails an internal check and raises an error (see https://gitlab.irstea.fr/HYCAR-Hydro/evalhyd/evalhyd-cpp/-/blob/86f1e26a5884cdf3548f44fbb33a5e90e15f5257/include/evalhyd/detail/uncertainty.hpp#L112-L119).

Edited 1 year ago

    Tasks

    0

    No tasks are currently assigned. Use tasks to break down this issue into smaller parts.

    Linked items
    0

    Link issues together to show that they're related. Learn more.

    Activity


    • Thibault Hallouin added BUG label 1 year ago

      added BUG label

    • Thibault Hallouin mentioned in commit 805e4a6a 1 year ago

      mentioned in commit 805e4a6a

    • Thibault Hallouin changed the description 1 year ago

      changed the description

    • Thibault Hallouin closed via commit 805e4a6a 1 year ago

      closed via commit 805e4a6a

    • Thibault Hallouin mentioned in commit 1d815c68 1 year ago

      mentioned in commit 1d815c68

    • Thibault Hallouin closed via merge request !6 (merged) 1 year ago

      closed via merge request !6 (merged)

    Please register or sign in to reply
    0 Assignees
    None
    Assign to
    Labels
    0
    None
    0
    None
      Assign labels
    • Manage project labels

    Milestone
    No milestone
    None
    Due date
    None
    None
    None
    Time tracking
    No estimate or time spent
    Confidentiality
    Not confidential
    Not confidential

    You are going to turn on confidentiality. Only project members with at least the Reporter role, the author, and assignees can view or be notified about this issue.

    Lock issue
    Unlocked
    0
    0 Participants
    Reference:

    Menu

    Explore Projects Groups Topics Snippets