Bayden Smith

When displaying the condition names via labels onto an analysis trend, the text for the name is now wrapping across multiple lines and over the top of other labels.  It never used to do this as the entire condition name used to appear in a single line.  Signal name labels are displayed correctly though.

I used to screen shot these analysis trends to highlight issues with our process or show the performance but now with this change it is hard for anyone to understand what each condition is representing on the analysis.

This change seemed to occur over a weekend back in mid march where it was fine in the morning but had changed by the afternoon.  It is still like this and occurs regardless of which web browser I am using.  The version of Seeq we use is R58.8.10-v202403072038.

Is this something that others have issues with and if so is there a setting somewhere that may fix this issue (I cannot find anything).

Below is an example of what I am seeing now and how it used to look:

Thanks John,

That is perfect and gives me exactly what I am after.

I was already making them toStep() so I wouldn't get a join the dots line, but was unaware of the '30d' part of that formula.

Regards,

Bayden

I am trying to do analysis of various process variables against their setpoints.  I do this by trending the various variables along with setpoints.  Some have calculations to determine differences or sometimes multiple setpoints are needing to be added to get a final setpoint.  When I add the setpoint signals, some will not display unless they have changed in the viewing window due to the infrequent data points.

I can increase the maximum interpolation but this still only works if there is a change in the viewing window (but does give me the line back to the previous change).

Since each setpoint can change multiple times a day or remain constant for weeks at a time this makes this difficult to use reliably.  I can always use a fixed value but then I will need to change it when the setpoint changes and is not workable on a live trend.  I can replace invalid values with another one which works, but this is the same issue as using a fixed value in that it will not necessarily be the correct value for a live trend.

Is there anyway to get around this limitation?