-
Notifications
You must be signed in to change notification settings - Fork 165
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
[BUG/ISSUE] NetCDF: Index exceeds dimension bound when using Yuan processed LAI #178
Comments
Thanks for writing. The Yuan XLAI requires a further fix in HEMCO to allow for arbitrary interpolation periods. This will ship with GC 12.7.0. So you will not be able to the Yuan XLAI with 12.5.0. We are going to start benchmarking 12.7.0, but due to the holiday break, it might not be ready until sometime in January. |
Hi, HEMCO: Opening /GEOS-Chem/ExtData/HEMCO/Yuan_XLAI/v2019-03/Yuan_proc_MODIS_XLAI.025x025.2014.nc In Ncrd_2d_R4 #2: NetCDF: Index exceeds dimension bound !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! I would appreciate getting help. |
Hi @lijimdavid, thanks for writing. This will be fixed in HEMCO 3.0.0 (which will be released in GEOS-Chem 13.1.0). You can get the fix from here: geoschem/HEMCO#85. |
Thanks @yantosca, this saved my day! And I assume this is only an issue for a quarter resolution runs? And FYI, I also read others who post this problem, it seems that error always happens on the day of 12/27. --Zichong |
@zichongchen: I think it is an issue with certain data that is interpolated. It was probably noted due to the fact that the interpolation period spanned a new year boundary. We are planning on adding an integration test that spans the end-of-year so that these types of errors will be flagged earlier on in development. |
@yantosca Sounds great and thanks for letting me know. |
Hi there,
I am trying to switch to Yuan processed LAI for my 2x2.5 complexSOA_SVPOA simulation in 2013. I am using GC 12.5.0. After reading the wiki, I believe I need to do a fix to force the timestamp search algorithm work correctly. I did that and the GC compiled well. However, when I run the model, it complained the following error. I would appreciate your help.
Yours faithfully,
Fei
The text was updated successfully, but these errors were encountered: