Search the Community
Showing results for tags 'treemap'.
Hello, this topic came up during a customer training. The presentation of the individual assets in the Treemap view looks strange at first glance. In the screenshot, the assets "Area J" and "Area K" are displayed as long rectangles, although all assets have the same number of sub-elements: When the size of the display pane is changed it looks better: According to your KB entry the size of the rectangles is determined by its number of assets and may be changed by the API. Is there an example for this? Regards, Thorsten
A quick question with regards to Tree Maps in SeeQ. Does the size of the cells mean anything? If it doesn’t, is it possible to link the block size to say the magnitude of meter index count? (i.e. a larger meter index count = larger cell size)
I am having some trouble getting the asset swapping and treemap functions working. I have a couple of questions: Does the asset being swapped need to be the direct parent of the signal? Does the entire asset tree structure need to be the same or only the elements of the signal that are being used in the calculation?