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
For this example I have selected the packets received at a single node, under 4 different interface configurations and with 5 repetitions.
The IDE infers that the series should be "interfaceType" and group should be "replication"
If I remove the "replication" grouping, I expect only 4 bars like the following:
However it won't accept no grouping, giving the error: "Please set both the Groups and Series properties in the dialog - or neither, for automatic setup."
Is this the designed behaviour?
Instead I have to group by "name" or some other parameter that they all share which seems counter intuitive.
Alternatively, I could put the interfaceType as the grouping, but then I have to put some other "universal" parameter in the Series field:
The text was updated successfully, but these errors were encountered:
Your expectation (the middle screenshot) is entirely reasonable, and it should probably work that way.
I think there were some technical reasons for why the current behavior emerged (having to put a universal attribute into the "other" field).
For this example I have selected the packets received at a single node, under 4 different interface configurations and with 5 repetitions.
The IDE infers that the series should be "interfaceType" and group should be "replication"
If I remove the "replication" grouping, I expect only 4 bars like the following:
However it won't accept no grouping, giving the error: "Please set both the Groups and Series properties in the dialog - or neither, for automatic setup."
Is this the designed behaviour?
Instead I have to group by "name" or some other parameter that they all share which seems counter intuitive.
Alternatively, I could put the interfaceType as the grouping, but then I have to put some other "universal" parameter in the Series field:
The text was updated successfully, but these errors were encountered: