Jump to content

Thorsten Vogt

Super Seeqer
  • Content Count

  • Joined

  • Last visited

  • Days Won

  • Points

    690 [ Donate ]

Thorsten Vogt last won the day on August 31

Thorsten Vogt had the most liked content!

Community Reputation

67 Excellent


Personal Information

  • Company
    Werusys GmbH & Co. KG
  • Level of Seeq User
    Seeq Advanced

Recent Profile Visitors

1,208 profile views
  1. Hi Mike, by default the size of the tiles reflects the number of assets under the specific asset. In this example, as Cooling Tower 1 has more assets belonging it then Cooling Tower 2, the area of the rectange is bigger: Assets below Cooling Tower 1: Assets below Cooling Tower 2: As you may notice the shape of the rectangles for Area J and K in Cooling Tower 1 is different from the other rectangles, although the size is the same. Resizing the browser circumvents this issue and displays the rectangles all in the same shape: You can override the size of each item individually as described here: Hope this helps. Regards, Thorsten
  2. Hi Robin, as I understood you want to have the sum of the values at ~ 9 am and ~ 3 pm as the value for the batch 22091 NR. Therefore I changed the last formula of my previous post: $batch.removeLongerThan(1wk).tosamples($capsule -> { $maxFirst = $capsulesForCounter.toGroup($capsule).first().property('CounterValue') $sumOfMax = $capsulesForCounter.toGroup($capsule).reduce(0, ($r, $x) -> $r + $x.property('CounterValue')) sample($capsule.startKey(), $sumOfMax-$maxFirst) }, 1d).tostep(1wk) Regards, Thorsten
  3. Hi Robin, you may try the following way. I tried to set up an environment, that represents your data. In the first step I created a condition for each batch: As you can see the "Counter" signal is increasing after the end of the batch. Next I created capsules for the periods between every counter reset using formula. For each capsule the maximum value is stored as a property: ($counter.runningDelta() < 0).afterStart(0s).inverse().removeLongerThan(1wk).transform($c -> $c.setproperty('CounterValue', $counter.maxValue($c))) In the last step I used another formula to transfer the countervalue to a signal that is displayed across the duration of the batch: $batch.removeLongerThan(1wk).tosamples($capsule -> { $max = $capsulesForCounter.toGroup($capsule).last().property('CounterValue') sample($capsule.startKey(), $max) }, 1d).tostep(1wk) Will this work for you? Regards, Thorsten
  4. Hi Bella, you can chain the splice command multiple times: You may also have a look at this post: Hope this helps. Regards, Thorsten
  5. Hello Arnaud, the error is occuring because of the unit of the signal. I guess the unit of your signal is "t" which is converted to "t²" and "t³" for the respective parts of the formula. Therefore they cannot be used in an addition or subtraction. To get the fomula working simply convert the signal to a unitless one before calculating the polynom. The resulting signal is unitless. You can use the setUnits() function to specify a unit if you need one. Hope this helps. Regards, Thorsten
  6. Hi Vladimir, the error indicates that at least one of the conditions used in the formula does not have a maximum capsule duration defined. To get the formula working you have to specify a maximum capsule duration by using removeLongerThan(). The function takes a scalar value (e.g. 1wk) and removes all capsules longer than that duration. $A.removeLongerThan(1wk).transform( $capsule -> $BB.removeLongerThan(1wk).toGroup($capsule).first() ) You can check for a maximum duration by clicking the "i" icon next to the item in Details Pane: If the attribute is missing, the item doesn't have a maximum duration specified. This is the case if you create a condition by using a simple Value Search. Regards, Thorsten.
  7. Hi Vladimir, you may use a transform for this: $A.transform($capsule -> $BB.toGroup($capsule).first()) $A refers to condition A, $BB refers to condition BB. The formula retrieves all capsules of BB during A and returns a condition containing only the first capsule of BB: Hope this helps. Regards, Thorsten
  8. Hi Vladimir, regarding the first question: As I understand your question you want to calcuate the duration of the period when the valve is opened . You can do this by creating a "Value Search" and then using "Signal from Condition" to calculate the duration of each capsule: Regarding your second question: Create a "Periodic Condition" to create capsules for the periods you are interested in. Then create another "Signal from Condition" to count the number of "Valve open" capsules during the created Periodic Condition: Does this answer your questions? Regards, Thorsten
  9. Hi Ethan, you can try this: The formula combines two signals with the property value at start an end of the capsule. By using toStep() the samples are connected and by using within() only the portion of the signal within the condition is kept. Does this work for you? Regards, Thorsten
  10. Hi Felix, you may try this one. I have set up an example with three assets: I used the following formula to calculate the number of failed equipments: The formula iterates over each week and calculates the number of failed equipments for each capsule of the weekly condition. Therefore I am using the sign() function on the number of capsules per week, which returns 1 if capsules exists during the week and 0 if no capsules are present. The sum of these values is used for a new sample that is set at the beginning of the capsule. toStep() connects each sample using step interpolation. Regards, Thorsten
  11. Hi Theresa, you specify this in the Details Pane: Regards, Thorsten
  12. Hi Theresa, I understand the need for this. As a workaound you may put the signals that should be displayed smaller on the same lane as the signal you want to have displayed bigger with a secondary y-axis and adjusted ranges: Regards, Thorsten
  13. Hi kward, Capsule View should get you the desired output, but you you need a condition to create capsules for which you can overlay the signals. My example is for comparing daily values. You can switch the perdiodic condition to Yearly to compare the signal for different years: Regards, Thorsten
  14. Hello kward, as I understood your question, the easiest way to do this is using Capsule View, which overlays the signals for each capsule. In this example I used two signals and created a Periodic Condition for each day: By clicking "Capsule" in the top menu and selecting the capsules you are interrested in, you can compare the values during each day, as all values are are shown in relative time from the start of their capsule. Did you mean something like that? Regards, Thorsten
  15. Hi Chris, you can try to use the OData Export and some scripting in Powershell to export to CSV. Copy the "OData Sample Table Endpoint" and insert into the script below to export signal values: $credentials = Get-Credential $result =Invoke-RestMethod http://seeqserver:34216/odata.svc/Analysis_36_Export_1_7C86D848_7A39_4B5B_BB67_FA66A18CF6E4_DataSet -Credential $credentials $result | ForEach-Object { $properties = $_.content.properties [PSCustomObject]@{ Timestamp = $properties.timestamp Temperature = $properties.Cooling_Tower_1ǀExampleǀArea_AǀTemperature RH = $properties.Cooling_Tower_1ǀExampleǀArea_AǀRelative_Humidity } } | Export-Csv C:\Temp\data.csv -NoTypeInformation Another way would be using the API / SDK (https://seeq.atlassian.net/wiki/spaces/KB/pages/117027248/Seeq+APIs+and+SDKs) or Seeq Data Lab, if you have a license for this. Regards, Thorsten
  • Create New...