-
Notifications
You must be signed in to change notification settings - Fork 10
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Problems with reading "big" arrays (>8.1Gb) #383
Comments
@durack1 I tried running the code with latest cdms2 in cdat/label/nightly and latest libnetcdf, and was able to reproduce. $ curl https://repo.continuum.io/miniconda/Miniconda3-latest-MacOSX-x86_64.sh -o Miniconda3-latest-MacOSX-x86_64.sh $ source miniconda3/etc/profile.d/conda.sh on aims1: $ conda create -n nightly_py3.7 cdat mesalib easydev nbsphinx myproxyclient testsrunner coverage pytest "python=3.7" -c cdat/label/nightly -c conda-forge
|
@muryanto1 thanks for picking up and reproducing this issue. It'd be helpful to know whether @dnadeau4 or @doutriaux1 had worked on a fix a while ago, and if there are any open issues, branches or commits, or web documentation they can point us to for a resolution |
Thanks for documenting and reproducing this issue. I am also hitting this issue. I note that it also occurs at least as far back as CDAT2.10. |
@durack1 How was this file created? |
@jasonb5 it’s one of the CMIP6 contributed files, NCAR doesn’t use CMOR so not 100% sure what software was used to create it |
Folks, just an FYI @jasonb5 determined the issue and found a fix, and @muryanto1 has wrapped this up in the |
@durack1 great to know the issue has been resolved. Thank you all for the effort! |
@jasonb5 and @muryanto1 - Thank you! For those of us who prefer more stability than the nightly build, is this slated for a release? 8.2.x? 8.3? |
@pochedls Yes, but we do not have a time frame yet, but working on it. |
Linking PR #389, this will be available in CDAT 8.2.1. |
Describe the bug
I have hit a reproducible error where big arrays (>8.1Gb) are not read correctly, rather with a zero array (rather than real numbers) being returned. I was a little puzzled by this error, and got talking with @painter1 who also had this problem and reported it back via email in May 2019. It turns out that the issue is with arrays greater than 8.1Gb, with the original error a bug with libnetcdf versions for big variables (from @painter1's notes/emails). @dnadeau4 and @doutriaux1 may recall some of the specific details about this. I note I may not be using the latest versions of libraries below.
To Reproduce
Steps to reproduce the behavior:
cdms2-3.1.4-py37ha6f5e91_3
,libnetcdf-4.6.2-h303dfb8_1003
,netcdf-fortran-4.4.5-h0789656_1004
Expected behavior
Big arrays should be read validly, returning non-zero arrays
Desktop (please complete the following information):
The code to reproduce this:
@pochedls @muryanto1 @downiec @jasonb5 @gabdulla @gleckler1 @lee1043 ping
The text was updated successfully, but these errors were encountered: