New Feature Requests

Environmental Forum Forums EddyPro New Feature Requests

This topic contains 24 replies, has 17 voices, and was last updated by  Anonymous 4 years, 5 months ago.

Viewing 15 posts - 1 through 15 (of 25 total)
  • Author
    Posts
  • #1382

    IsraelB
    Keymaster

    Please use this space to provide suggestions, improvements and additions to EddyPro.

    #1554

    Dave J
    Participant

    Is there any interest in having an EddyPro version for Mac or Linux users? Are others processing EC data on other platforms? Cast a vote for neither, Mac, or Linux.

    #1556

    Bob Evans
    Participant

    Could you please add an ATI (Applied Technologies) Sonic (especially K probe)as a sonic anemometer option?

    Thanks

    #1560

    gerardo
    Participant

    Bob, thanks for request. We’re are retrieving the necessary information to process data from the ATI probes appropriately.

    In the meanwhile, you could help us by specifying (if you know this information):

    1) Is there an option to apply/not apply the cross-wind correction to sonic temperature calculated by those anemometers?

    2) Is there any flow distortion correction applied in the firmware?

    Thanks!

    #1562

    gerardo
    Participant

    Bob wrote:

    Hi Gerardo,

    There is a shadow correction that can be toggled on/off. It corrects the flow distortion caused by the wind blowing directly along the axis of one transducer.

    There are also flow distortion corrections in the factory menu.

    Thanks,

    Bob

    Thanks a lot for the information!

    I will let you guys know how this proceeds and if we manage to include ATI anemometers already in our next release.

    Gerardo

    #1563

    hydrobot
    Participant

    In the coming years I see a Mac platform in my office, but not tomorrow.

    #1564

    hydrobot
    Participant

    I would like to see an option for a graphical display during processing. This feature is available in EdiRe. It would be nice to have an option to output a list of up to “six” selected variables. These variables would be graphically charted in separate windows. Perhaps a selection of variables from the full output vs time / record # or vs other variables.

    Cheers!!

    #1565

    IsraelB
    Keymaster

    thanks for the requests, hydrobot

    we hope to implement these requests as time and resources become available. Feature requests that improve the quality of flux computations are given the highest priority, followed by those that improve ease-of-use. Others will be implemented based on the overall interest expressed by EddyPro users, such as yourself. Please continue to provide feedback on EddyPro and share your experiences with other members of the Eddy Covariance community!

    #1566

    jgc
    Participant

    I am definitely interested in a Mac or Linux version of EddyPro (in that order), or even better, a platform independent application.

    I hope you can allocate resources to that soon. Thanks

    #1604

    TimL
    Participant

    Hi,

    I’ve been asked by a colleague to ask about including the CSAT diagnostic. The reason he gave me was that they had an intermittent fault with a CSAT at one of their sites. The covariances calculated online by the logger were contaminated and not usable but they were able to go back to the 10 Hz data, screen it using the CSAT diagnostic value and re-calculate the covariances. This saved a few months of data.

    Cheers

    Tim

    #1605

    gerardo
    Participant

    Hi Tim,

    I report here the explanation I gave you by email, for the convenience of other readers.

    The CSAT diagnostic flag – as well as any other variable – can already be used as a mask to filter out data records flagged for poor quality.

    In the “Dataset Selection” page, in the “Flags” tab, you can choose any variable available in the raw files as a flag, set a threshold value for each variable and instruct EddyPro to discard raw records for which individual values are beyond or below the defined threshold. This is a generalized concept of mask, which can be used straightforwardly with the CSAT flag, but that you may also use with other variables.

    Thanks!

    Gerardo

    #1616

    dhollinger
    Participant

    Hi –

    Thanks for the note about the Fortran 16801 error and how to avoid it by not doing the absolute limits test. Sometimes when sonics get wet or frosted they will stick on out of range values. I get a similar run termination if the data file is bad (maybe sonic out of range) when requesting uncertainty calculations. Unchecking the limits box does not work in this case (with uncertainty checked). A nice option would be a box we could check that allows the program to recover from any error (while logging the error) and continue to the next datafile. With 30-minute data files it can be very slow to discover and edit out bad files.

    Also, I also vote for the ATI sonic. Thanks for great software.

    – Dave

    #1617

    gerardo
    Participant

    Dear Dave, thanks for your post.

    Our goal is to make EddyPro able to handle any exception and skip to the next file in case of any trouble, without having you manually instruct the software to do so. Clearly, we are still not there (as you can imagine, it’s difficult to envisage and test all possible scenarios). In particular, you should be able to select any option, such as Absolute limits filters or Uncertainty calculations, without incurring in a crash.

    I would be interested in analyzing your case in more details. Would you able to send me (by email: gerardo.fratini@licor.com) the “.eddypro”, the “.metadata” and a few raw files that I can use to replicate both crashes? It shouldn’t be too complicated to spot the problem and fix it. Then, should I find solutions of general interest, I will post them here.

    As for the ATI sonics. What we need to know to include these anemometers is whether there is any specific algorithm that needs implemented to correct/calibrate wind and temperature data. Also, we would need to know the possible wind data formats (UVW? polar?) and if there is any other peculiarity. Finally, the geometrical specifications (path lengths) and time response are needed, for each ATI model.

    Note that we did not add ATI instruments so far for the simple reason that we didn’t have the opportunity to work with one. Given the interest that is arising (especially lately, with the new papers that came out on anemometer performances), we would be pleased if the community would support us adding these SATs to the list.

    Thanks a lot,

    Gerardo

    #1731

    dhollinger
    Participant

    Hi Gerardo –

    Sorry I didn’t see your post. Attached is the ATI manual. Most people who use the ATI sonic use the K probe. It would be great if you can include this in the next version.

    Thanks,

    – Dave

    #1748

    deba
    Participant

    I would be interested in an ability to run eddypro in batch mode on linux. I don’t mind using the GUI to configure in windows. I’d be happy to volunteer to help with the port (Deb Agarwal).

Viewing 15 posts - 1 through 15 (of 25 total)

You must be logged in to reply to this topic.

Comments are closed.