November 12, 2012 at 1:57 pm #1409
EddyPro interprets (and skips) some data files as being empty even though they contain a full half-hourly dataset at 10Hz. Nothing obvious to me distinguishes the skipped files from the other ones that the software processes without complaints.
Attached is an example of an allegedly empty file and the associated metadata.
Thanks in advance for your help,
CaroleNovember 13, 2012 at 10:30 am #1652
I was able to process the file you attached without problems, using your .metadata file and default settings. EddyPro correctly imported 18000 data records and calculated fluxes.
This makes me think that there is some settings in your .eddypro file that instruct EddyPro to filter out data records under certain circumstances (e.g. wind data or gas concentration beyond some thresholds). Please post the “.eddypro” file that caused the problem you described, so that I can use it and see if I can replicate the problem. Also, it could be useful if you could post also a raw file that is processed correctly by the software.
PS: Note that “empty” in EddyPro can also mean that no “valid record” is found in the file.November 15, 2012 at 12:41 pm #1653
thanks for your comment which alerted me to the fact that a diagnostic flag was set by error. I’ve now succesfully processed the data.
Thanks again for your help!
CaroleNovember 20, 2012 at 12:38 pm #1658
I’m running into the same problem again but with a different set of data files. Would you mind taking a look at the attached files? There aren’t any flags set as far as I can tell.
Thanks a lot
CaroleNovember 20, 2012 at 1:10 pm #1659
the problem is the metadata file. The first column is a “non-numeric” data column, because it contains non-numeric characters such as ” and :.
This column must be thus labeled as “non numeric” by setting “No” in the “Numeric” field of the Raw File Description table in the Metadata File Editor.
You probably thought that, because you instructed EddyPro to ignore that column, you didn’t need to specify that it is not numeric. Well, this is not the case: a non-numeric column must be identified even if it is ignored. The reason is that the software uses two different routines for importing purely numeric files, and files with at least one non-numeric column, no matter if it is ignored or not.
By modifying the metadata in this way I was able to process the .dat file without problems. Note that I used the just released EddyPro version 4.1.
As usual, please let us know if you have success processing your data.
GerardoNovember 20, 2012 at 1:49 pm #1660
thank you so much for being so responsive. I went away for lunch after posting my question and now that I’m back I’m ready to roll.
Changing the column type to non-numeric did solve my problem.
CaroleNovember 20, 2012 at 2:34 pm #1661
Non c’è di che! 😉
Glad to hear it worked. If you didn’t yet, I’d suggest you to switch to ver. 4.1!
You must be logged in to reply to this topic.