Jump to content

Thorsten Vogt

Members
  • Content Count

    23
  • Joined

  • Last visited

  • Days Won

    1
  • Points

    4 [ Donate ]

Thorsten Vogt last won the day on July 7

Thorsten Vogt had the most liked content!

Community Reputation

1 Neutral

1 Follower

Recent Profile Visitors

290 profile views
  1. Hi, you can get the start and end value the following way: 1. Import data from CSV and create a capsule for complete range of data by doing a simple Value Search: 2. In order to get only the first and the last value of the imported data create another two capsules that represent a small interval just after start and just before end of the capsule created in step 1. 3. Use the "Signal from Condition" tool to calculate the start and end values: You could also skip step 2 and use the capsule created in step 1 inside step 3 as the bounding condition. But then you have to specify a maximum duration of the capsule which may decrease performance. Regards, Thorsten
  2. Hi Jitesh, you could do a simple Value Search to get a batch whenever the Compressor stage does not match "OFF". The duration of the resulting batches is displayed in the capsules window: By using signal from condition you can calculate the total duration of each batch: In case you want a new batch starting with each value change you can use toCondition(): Hope this helps. Regards, Thorsten
  3. Hi Drew, in order to see the numeric values you must change the visualization to "Scorecard". The values are then displayed in a table. Regards, Thorsten
  4. Hi Drew, if I understand the problem correctly, you want the current value to be displayed. As far as I know it is not possible to display the last value in the chart all the time. But you can get an overwiew of the last values of your signals by creating some Scorecard Metrics that display the current value at the end of the display range. These values are being updated if the Auto Update setting is active: Hope this helps. Regards, Thorsten
  5. Hi Jitesh, you can achieve this by filtering the values with the filter() function: $stage.toCapsules().filter($x -> $x.getProperty("Value") != "OFF") You should think of using toCondition() instead of using toCapsules(), as toCapsules() generates a capsule for each interval between recorded points even if the value stays the same. You can see this in the Capsules window of your screenshot. By using toCondition() you will get only one capsule per change of value: $stage.toCondition() If you want to filter the results of toCondition() you have to specify a maximum duration for the capsules before using filter(): $stage.toCondition().setMaximumDuration(1wk).filter($x -> $x.getProperty("Value") != "OFF") Regards, Thorsten
  6. Hi Kevin, you can resample the continuos signal with the timestamps of the discrete one: $continous.resample($discrete) This will create a new signal with interpolated values. Exporting the values with original timestamps should give you the desired results. Regards, Thorsten
  7. Hi Ruben, you can do it by using this formula. The formula gets the values for the last eight hours, picks the last sample and gets its key (timestamp). Based on that timestamp the condition of the previous 24 hours is build. You can also use pick(-1) instead of last(). You should keep in mind that the capsule itself is uncertain because of the use of now(). Regards, Thorsten
  8. Hi Chris, I was able to achive this by using Property Transforms on the specific datasources: https://seeq12.atlassian.net/wiki/spaces/KB/pages/127009211/Connector+Property+Transforms But I think you have to be careful with this setting as you can easily define a possibly wrong setting for your data items. In my case, the interpolation value for the data item was preserved, although I removed the transformation. Regards, Thorsten
  9. Hello, creating comments in View-Only mode seems not to be possible, the "New Comment" button is missing in the Comments area.
  10. 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
  11. In case of the reference profile I don't have a use case.But I would like to know if this uncertainty resulting in using now() is a problem for predicting a signal into the future? In my case I have a signal that depends on two other signals. In Seeq example data I created a demo that creates a model of the "Temperature" signal by using "Wet Bulb" and "Relative Humidity". To get predicted values for the forecast of 5 days I take the values of the humidity for the last 24hs and repeat it the next 5 days. I then use the values of Wet Bulb from the last 24hs and repeat them also over the next 5 days with rising them by 1°C per day: The prediction for the temperature signal is build upon this two signals:
  12. Hello Ben, does "uncertain" in this context mean the values could change because of getting the data dynamically by using now()? If I change the code from my example above without using now() and changing to a fixed capsule the visualization changes (2. lane): Is there any way to get around this issue? Regards, Thorsten
  13. Hi Ruben, maybe you can use a rolling training window in the following way. For this demo I want to create a reference profile for the Compressor Power when the stage of the compressor is != OFF. The rolling training window shall be the last 7 days as you said. 1. Add the data to the display pane 2. Create a new signal for the compressor power, that takes the data of the last 7 days and moves this data to some fixed date range (e.g. 01/01/2019): 3. Repeat this step for compressor stage signal: 4. Create a condition that identifies the times when the compressor is on during training window: Your display now should look like this when you move to 01/01/2019: 5. Create a condition that identifies the times when the compressor is on (NOT during training). We will use this for the reference profile to be applied to: 6. Create the reference profile based on the training window. I had to shorten the training window by two minutes at end due to an error message ( Training window for reference table must be certain at 'captureReferenceSlice',). The result looks like this: To simulate a change of time you can modify the formulas for the training data like this You can see that the shape of the profile changes: I am not sure if this workaround may cause problems in some situations, as it seems the error message in step 6 is thrown because there is no sample at the end of the training window. Therefore this solutions has to be adjusted to your needs. Regards, Thorsten
  14. Hi Ruben, yes, you can export the data to Excel from your workbench analysis: Include Summary Data adds a worksheet to the Excel file containing statistics of your signals and capsules, Include Signal Samples adds a worksheet with the samples for each signal in the display range. More information can be found here: https://seeq12.atlassian.net/wiki/spaces/KB/pages/494436371/Export+Data+to+Excel+File Regards, Thorsten
×
×
  • Create New...