Hi,
I´m getting the message below when I run EC data (10Hz, CSAT3, Li-7200 + Li7700). Is it related to bad wind (W) values?
Thanks in advance,
Tomas
At line 1374 of file: eddypro_express_v2_main.f90
Fortran runtime error: Index '16801' of dimension 1 of array 'e2set' outside of expected range (1:16800)
At line 1374 of file: eddypro_express_v2_main.f90
Fortran runtime error: Index '16321' of dimension 1 of array 'e2set' outside of expected range (1:16320)
Hi Tomas,
I don't think the issue is with bad w values. It seems an issue with reading the file. Are your raw data text files or binary files? How long is each raw file duration 30 minutes or 12 hours or 1 day or 1 week? Also which version of EddyPro are you using?
Dear Israel,
My files are
Sorry about that,
My files are 30 minutes in ASCII format(from CardConvert, version 1.6). I´m using EddyPro 4. I´ve sucessfully run 10 data block (visits to the datalloger) varing in couple of days to 2-3 weeks (always 1/2 hour blocks in ASCII). But for 7 datablocks I´m getting those fortran messages, always with a different Index Number.
Cheers,
I think I can pinpoint the problem better if have some files to play with. As usual send me the following three files
1- Project file (.eddypro extention)
2- Metadata file (.metadata extension)
3- Raw data files (possibly one with from the block that works and one from the other block)
Send the files to envsupport@licor.com
I will let you know what I find.
After looking at the files Sonic data has too many spikes and is very noisy. The statistical routines (spike count and removal, absolute limit test etc) are removing many data points leading to the final error that you see. On Advanced Settings page on Statistical Analysis, you have the absolute limits test. This test has a check box that allows you to “Filter Out-ranged Values” (throw out). Because the sonic data has too many points that are outside the limit what’s left is not enough to proceed with the calculation. That is the error you are getting. If you un-check that box the processing will go on without an error but the calculated fluxes might be questionable. You can see in the full output file (statistical flags) which statistical tests failed.
You must log in to post.
