1 Reply Latest reply on Aug 25, 2014 10:38 PM by tlebay

    Coresight - Questions for programmers

    markshannon

      We have been using Coresight successfully for a little over a year and have found it to be a quick, neat tool for visualizing the data. While using it, I have noticed that two items, that if tweaked, would provide much more information to the user.

       

      1) The Coresight trend has a configuration option for adding a line to show the max, min, or average. The usefulness of these lines would be much greater if a value would be available to the user on the trend. The max/min/ave could show up when hovering on the line or on the left scale or right scale. Adding the value would decrease the need for a table below the trend to show the actual number for these calculations.

       

      2) The Coresight table has a configuration option to add the time to the table. This field displays the right most time value, a value which is already displayed in the time box (next to the NOW button). I find this field a bit pointless. To make it useful it could be altered to show the time the max occurred, or the min.

       

      I am hoping this is the right place to post this so one of the PI programmers will see it, and comment on the possibility of these small tweaks making it into production.

       

       

       

      Thank you

        • Re: Coresight - Questions for programmers
          tlebay

          Hi Mark-  This is a good place for your comments and suggestions, and thanks for sharing them.  :-)

           

          #1- We have not planned to solve this specifically but I think we will satisfy what you are looking for in a 2015 release. We are still in the planning/design stage but we have a vision to add multiple trend cursors to trends in PI Coresight.  As new trend cursors are added the value for each trace on the trend will be displayed next to the cursor.  This would include the min/max/avg values if they are currently shown on a trend and therefore would give you the numeric value you are looking for.

           

          #2- I see your point.  Should we have two time columns? One for min time and one for max time?  Also in a 2015 release we will support the work currently being developed in the PI Server to support future data. As part of this support in PI Coresight we plan to add a "reference time" cursor to the time bar.  With this time bar cursor the user will be able to control what reference time is used to show values in tables, value symbols, and gauges on the display.  The current time column seems like it will have more value at that point because it will no longer always be the end time of the display.

           

          I hope this is helpful.  This all falls into the category of future work that is still subject to change, but it is what we are planning right now.  What do you think?