Retrieving measurement property fails when Result Name is present in Selector String

[mdwhitten]

This line and the equivalent in LabVIEW both fail when a selector string is passed into this function referring to a specific named result:

rfic-reference-design-libraries-csharp/Source/SA/RFmx NR/RFmxNR.cs

Line 444 in 6a5dc3c

nr.ComponentCarrier.GetNumberOfComponentCarriers(selectorString, out int numComponentCarriers);

This is a problem for any personality and any measurement where we use this method of determining how large the array should be before fetching.

For C#, we can probably just ignore the selector string input for the function. Otherwise, for both the solution would be to strip out the result string from the selector string.

[sean-moore3]

For C#, we can probably just ignore the selector string input for the function. Otherwise, for both the solution would be to strip out the result string from the selector string.

I don't think we can do that since the user might have multiple signals

[sean-moore3]

I think we have an overarching question here as to whether this is an RFmx bug or not. I can see how specifying a signal::result:: implies i want the signal instance used for the measurement when that information likely isn't stored.

[sean-moore3]

Proposed solutions:

1. Remove result name from selector string. Pro - no interface changes. Con - May cause errors if user re-configures signal before fetching results
2. Use a list to fetch and append results for each carrier until RFmx throws an exception/error. Pro - immunity to cons in option 1. Con - Clunky
3. Force the user to pass StandardConfiguration struct to fetch functions. Pro - Easy, Con - What if user changes settings before calling fetches? Interface change.