Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
P PyNEMO
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 37
    • Issues 37
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Merge requests 1
    • Merge requests 1
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Operations
    • Operations
    • Incidents
    • Environments
  • Analytics
    • Analytics
    • CI/CD
    • Repository
    • Value Stream
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Members
    • Members
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • thopri
  • PyNEMO
  • Issues
  • #59

Closed
Open
Created Apr 27, 2020 by thopri@thopriMaintainer

with a 3D child grid PyNEMO crashes if 2D boundary data is specified

Created by: thopri

At the moment PyNEMO crashes if you specify 2D data for a 3D grid. e.g. SSH or ICE with the benchmark child grid.

I am going to handle it for now with a try except to catch the error and raise an exception so that users will know a potential cause for it. (Error is a bit opaque at the mo.)

I was wondering if it was sensible to make it so PyNEMO can handle this, e.g. by slicing the surface layer of the child grid and making it 2D? would need to add warnings etc in the log but could be useful?

Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking