Skip to content

Variables on the velocity grid (xq, yq) show netcdf error #45

Description

@winnie-chu-aos

Hello,

I have been encountering an issue where datasets including velocity variables are not able to be combined. As a test, I ran a simulation where I output only zonal (u) and meridional (v) velocity in 3D, where u has dimensions (xq,yh) and v has dimensions (xh,yq). In the regional configuration, these dimensions are output as (xq_001,yh_002) and (xh_002,yq_001), respectively.

I get this error when the reader is working on a file near the edge of the model region (so the tile is smaller than the rest.)

[rank 000] NetCDF copy of yh_sub02 from 19930101.ocean_daily_budgets_1993_01.nc.0023
[rank 000] ERROR in NetCDF /mppnccombine-fast/mppnccombine-fast.c:71 -40 NetCDF: Index exceeds dimension bound

It works fine for all the previous coordinates

[rank 000] NetCDF copy of xh_sub01 from 19930101.ocean_daily_budgets_1993_01.nc.0023
[rank 000] NetCDF copy of yh_sub01 from 19930101.ocean_daily_budgets_1993_01.nc.0023
[rank 000] NetCDF copy of xq_sub01 from 19930101.ocean_daily_budgets_1993_01.nc.0023

but seems to get stuck at yh_sub02. I'm confused becaue this doesn't seem to be an issue for tracer points, and the dimension that it's stuck on is a tracer point, albeit one used for the velocity variables. Additionally, given the particular sub-region where the issue arises, I am wondering if the shortened dimensions of the sub-region itself has something to do with the error?

Attached below is an example of a region that works (19930101.ocean_daily_budgets_1993_01.nc.0022) and a region that does not (19930101.ocean_daily_budgets_1993_01.nc.0023).

Thank you so much for your help!

19930101.ocean_daily_budgets_1993_01.nc.zip

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions