Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
DYNAMICO DYNAMICO
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 5
    • Issues 5
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Merge requests 1
    • Merge requests 1
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Operations
    • Operations
    • Metrics
    • Incidents
    • Environments
  • Packages & Registries
    • Packages & Registries
    • Package Registry
    • Container Registry
  • Analytics
    • Analytics
    • CI/CD
    • Repository
    • Value Stream
  • Wiki
    • Wiki
  • Members
    • Members
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • IPSL
    • PProjets
  • dynamico
  • DYNAMICODYNAMICO
  • Issues
  • #6

Closed
Open
Created Mar 25, 2022 by MILLOUR Ehouarn@ehouarn.millourMaintainer

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
None
Milestone
None
Assign milestone
Time tracking