Fatal error(23) in Eddy Pro 3.0 with same metadata file

LI-COR Environmental Forum » Ecosystem Exchange (Eddy Covariance) » EddyPro

Fatal error(23) in Eddy Pro 3.0 with same metadata file

(5 posts) (2 voices)

Started 1 year ago by Eddy_Sarah
Latest reply from Eddy_Sarah

Tags:

Eddy_Sarah
Member

Hi,

I tried to process data with Eddy Pro 3.0, using the same project and meta data files as with Eddy Pro 2.3. Just after starting the run I get an error I do not understand:

"Invalid metadata: sonic temperature cannot be selected as a slow ambient temperaturemeasurement. If you want to use it, just select "none" in the ambient temperature, and EddyPro will automaticallyuse the sonic temperature, corrected for humidity effects, as ambient temperature.
Error detected for column n.: 7
Fatal error(23): error validating alternative metadata file.
please check entries in the "Metadata file editor" and try again.
*Program execution aborted*"

the Ambient temperatur I use is the one measured by another instrument, and I declared it that way (as I did with Eddy Pro 2.3, and here it works fine).

Any suggestions would be helpful.
Thanks

Posted 1 year ago #
FCO2
Member

Sarah these kinds of erros usually happen when your data file and metadata dont match.
We removed certain things in Eddypro 3.0 like the Data label for records option, which was present in 2.3. So it is a good idea to recreate the project and metadata in 3.0 to get rid of such errors.
A guided mode was also instroduced in 3.0 which will try to give suggestions and messages. This is the reason probably you are getting this message now. If you want to use ambinet temperature from another instrument, you should not mark the instrument as other and not as a sonic as sonic temperture is not the actual air temperature

Posted 1 year ago #
Eddy_Sarah
Member

Thanks for the answer. I recreated the project and metadata, but the problem remains the same. If I do not mark the instrument as "other", I even do not get the possibility to select the Ambient Temperature in the Dataset Selection window.

Posted 1 year ago #
FCO2
Member

Sarah
Although eddypro gives the option to enter in multiple sonic anemometers, it can handle only one anemometer at a time. So if you have have one sonic anemometer in your data set and you dont have an ambient air temperature, eddypro will use that sonic temperature and convert it into air temperature and use it for flux computations.

I understand that like in some sonic anemometers like Gills, you could connect a air temperature sensor through the analog inputs and get a temperature reading, but as of now eddypro always take any temperature reading from a sonic as a fast sonic temperature.
This was done to prevent users from mixing up air temperature and sonic temperature.
I guess for now if you have air temperature from a sonic as the scenario I mentioned above you have to mark it as other to have a successful run

Posted 1 year ago #
Eddy_Sarah
Member

Thanks for the answer.
I found the sollution by trial and error:
The error message by Eddy Pro is wrong: even though it says "ambient temperature", the problematic colum is the "ambient pressure" one. I deleted the information of the instrument measuring the ambient pressure, and now it works fine.

Thanks.

Posted 1 year ago #

RSS feed for this topic

Reply

You must log in to post.