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

Admin message

Gitlab has been updated. More info.

  • IPSLIPSL
  • Projets
  • dynamico
  • DYNAMICODYNAMICO
  • Issues
  • #6

Better control over reading input start file with XIOS

Note that if one has

xios_output = false

in run.def , when loading the start file the following error will be generated:

In file "field_impl.hpp", function "void xios::CField::getData(xios::CArray &) const [with int N = 3]",  line 50 -> Impossible to access field data, the field [ id = ps_start ] does not have read access.

Even though the start file is there and contains the field... It seems one must have

xios_output = true

So perhaps this flag should be considered obsolete and removed? Or some more control and explicit error message be given to the user?

Assignee
Assign to
Time tracking