-
Notifications
You must be signed in to change notification settings - Fork 6
Description
The only way I've been able to get metadata about a measurement from within an analytic is to catch the first iteration of the Execute delegate in a conditional. Then, on the first pass of the Execute delegate I can retrieve the guid of the input and use the Hub to retrieve metadata. (Thanks for giving us access to Hub from within the analytic, team.)
If my analytic, by coincidence, starts at a time when the input is 'dead', then ECA gives me a null input. That's good most of the time, but not on the first pass. In this case I can't retrieve metadata and I need to permanently kill the portion of the analytic that is trying to use the missing data.
This situation occurs when a user establishes a large-ish array of inputs. Say the user wants to run my analytic on 50 frequency inputs. It's likely that one of the 50 inputs is temporarily down when my analytic starts up.
Can you give me access to the guids for my inputs within the UpdateSystemSettings method, or to build another analytic initialization method that gives me access to metadata about the inputs?