Open charlie9578 opened 8 months ago
@charlie9578 this is a great idea, especially if this could be achieved using existing functionality! Status code analysis are certainly an area of interest for us, but we don't have a great sense of them given data access and the wide variety of codes. It'd be great to get a sense if this is an expanded example or new feature from your perspective, which would help us determine how this could be prioritized. We're anticipating minimal internal feature development this year, just to be fully transparent.
Hi,
To mimic how a Technical Advisor would run a operational energy yield analysis (OEYAs) using SCADA data, I'd suggest the option to calculate the losses based on the 10-minute SCADA data (and potentially using events data too), rather than relying on user inputs/external sources for the losses. This is a key benefit of independent SCADA-based OEYAs, as availability is often not consistently reported.
The power curve filtering demonstrated in the 01_utils_examples and the 03_turbine_ideal_energy notebook both have some ability to achieve this aim, and so it might just be a case of demonstrating how this can be achieved in an example notebook.
Thanks, Charlie