Skip to content
GitLab
Projects Groups Topics Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Register
  • Sign in
  • N Nemo
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributor statistics
    • Graph
    • Compare revisions
    • Locked files
  • Issues 90
    • Issues 90
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
    • Requirements
  • Merge requests 33
    • Merge requests 33
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Artifacts
    • Schedules
    • Test cases
  • Deployments
    • Deployments
    • Releases
  • Analytics
    • Analytics
    • CI/CD
    • Code review
    • Insights
    • Issue
    • Repository
  • Wiki
    • Wiki
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • NEMO WorkspaceNEMO Workspace
  • Nemo
  • Issues
  • #242
Closed
Open
Issue created May 12, 2023 by Tomas Lovato@tlovatoMaintainer

Reduce log prints of TOP boundary conditions

Context

  • Reference configuration/test case (to add, chosen or used as template)
  • Modifications of versioned files: Fortran routines (*.[Ffh]90), namelists (namelist\_*cfg), outputs settings (*.xml), ...
  • Additional dependencies

Proposal

In the time-stepping phase, the boundary condition forcing of TOP produce in the ocean.output file at every timestep the log prints for sbc, cbc, and obc boundary data read in trcb.F90.

We should limit these log write instances only the initial and final steps of the execution, as it is done e.g. in fldread.F90

IMO this should go also in %Tag 4.2.1


Edited May 12, 2023 by Tomas Lovato
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking