You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
What's the problem this feature will solve?
When indexing into a column of an NTTable subfield (i.e. the second index), I need to know exactly which index my desired object is at.
Describe the solution you'd like
While this is possible to manage on the user end by getting the PV in python code and identifying the index that way, it would be nice if it were possible to add a logical statement to the second subfield straight in designer. In my mind it would look something like pva:MY_PV/subfield1/subfield2==indexIWant. I could also see a solution using syntax similar to the calc plugin. I defer to your all's expertise!
The text was updated successfully, but these errors were encountered:
Hi Yekta, sure:
I have an NTTable containing information about klystron anomalies with 2 columns, "station" and "anomaly_state". If I want to get the anomaly state of a particular station, I need to find the index of that station in the "station" column, and append that to the pv, so I end up with something like:
What's the problem this feature will solve?
When indexing into a column of an NTTable subfield (i.e. the second index), I need to know exactly which index my desired object is at.
Describe the solution you'd like
While this is possible to manage on the user end by getting the PV in python code and identifying the index that way, it would be nice if it were possible to add a logical statement to the second subfield straight in designer. In my mind it would look something like pva:MY_PV/subfield1/subfield2==indexIWant. I could also see a solution using syntax similar to the calc plugin. I defer to your all's expertise!
The text was updated successfully, but these errors were encountered: