Jump to content
  • To Search the Seeq Knowledgebase:


Search the Community

Showing results for tags 'periodic condition'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


  • Community Technical Forums
    • Tips & Tricks
    • General Seeq Discussions
    • Seeq Data Lab
    • Seeq Developer Club
    • Seeq Admin Forum
    • Feature Requests


  • Community Calendar


  • Seeq FAQs
  • Online Manual
    • General Information


  • Published
  • Code
  • Media

Find results in...

Find results that contain...

Date Created

  • Start


Last Updated

  • Start


Filter by number of...


  • Start





Level of Seeq User

Found 14 results

  1. For reporting purposes, I want to calculate statistics based on the most recent period(capsule) and display that along with the periods immediately preceding it. This can be done in Organizer using the custom date range by creating a Periodic Condition and selecting the capsule closest to or offset by one from the end. The same date ranges or capsules relative to now can be created in Seeq Workbench as well. Organizer: Workbench: We create the same condition as the above Organizer in Workbench by following the methods below. The first method defines how to create conditions for current and previous conditions for years, days, weeks, shifts. The second method includes an extra step that is necessary for current and previous months and quarters since the exact duration of these periods can vary based on the number of days each month. Method 1 - when the length of time in each period is definitive (e.g. year, week, day, shift). This example shows how to create conditions for "Current Week" and "Previous Week" 1. Create a Periodic Condition for "Weekly" using the Periodic Condition tool. 2. Create a Condition around the current time ("Now") using Formula --> condition(1min, capsule(now() - 1min, now())) 3. Use the Composite Condition tool to create a condition for "Current Week" when the Periodic Condition "Weekly" touches the tiny capsule at "Now". 4. Use Formula to create a condition for the "Previous Week" --> $currentWeek.beforeStart(7d) Method 2 - when the length of time in each period is variable (e.g. month, quarter). This example creates a condition for "Current Month" and "Previous Month" 1. Create a Periodic Condition for "Monthly" using the Periodic Condition tool. 2. Create a Condition around the current time ("Now") using Formula --> condition(1min, capsule(now() - 1min, now())) 3. Use the Composite Condition tool to create a condition for "Current Month" when the Periodic Condition "Monthly" touches the tiny capsule at "Now". 4. Use Formula to create a Condition for the last day of the last period (in this case "Last Day of the Last Month") $currentMonth.beforeStart(1d) 5. Use the Composite Condition tool to create a condition for the "Previous Month" when the Periodic Condition "Monthly" touches the "Last Day of Last Month". Content Verified DEC2023
  2. How can i create a time based condition for a time interval that isnt in the periodic condition tool? In this case i want to calculate a statistic for my signal (an average or max) every 15 minutes. How can i do this?
  3. Hi all, I am based in the UK and wanted to define shift pattern that changes with time zones. I have created a condition for a 12 hour shifts that are on days for 2 consecutive days and then on nights for 2 consecutive nights. [Each shift will have 4 working days (2 days and 2 nights and 4 days off] Consider 4 shifts in this shift pattern, namely: Shift 1, Shift 2, Shift 3, Shift 4. The shift starts at 8am and ends at 20:00. After which the next shift starts at 20:00 and ends at 8:00 I am using the following formula: In the next step, I am defining my Night Shift using below formula: And then I am defining my Days Shift using below formula: After this, I combined, the days and night condition: $days.union($n) Then I defined my first shift: Shift A: I then moved the next shift by 2 days, Shift B: And then used this shift to define next one and so on, by moving each shift by 2 days from previous one. The issue I am having is that the shift is not aligned with daylight saving. Please help, I referred guide from, but doesn't work for this shift pattern
  4. Background: Seeq has functions in Formula to remove outliers based on different algorithms, but sometimes it is desired to identify and remove outliers that falls outside of the interquartile range. Solution: The approach we can take to solve this data cleansing problem in Seeq is to determine the periods over which we want to calculate the quartiles, calculate new signals from the 25th and 75th percentiles during each of those periods, identify deviations from those percentiles, and remove data outside of the IQR from our original signal. 1. The first step is to decide what type of periods you would like to use to calculate your percentiles. Some periodic choices might include: hourly, daily, or a rolling window of 24 hours each hour. Other choices could be the current production run, the time since the equipment was last maintained, etc. In this example we will use an hourly periodic condition in our quartile calculations. 2. Next, use the signal from condition tool to calculate the 25th percentile during each of the capsules defined above. 3. Use the same method to calculate the 75th percentile during each of the capsules defined above. 4. Use Seeq's Formula tool to calculate the IQR. $UpperQ - $LowerQ 5. Now use Formula to calculate the upper and lower limits as for outlier removal as: $upperQ + n*$IQR (where n is a scalar multiplier, 1.5 in this example) $lowerQ - n*$IQR 6. Search for deviations from the Upper and Lower limits using Deviation Search. 7. Then use Formula to remove data during the identified outlier capsules. $signal.remove($outliers)
  5. a. Add the property of the day of the year to the daily condition. 1. From Tools>>Identify select Periodic Condition >> Daily and click execute. The daily condition automatically includes the properties of the Day of the week, month and the day of the year. 2. From the Capsules pane select the required properties. b. Add the property if the week of the year to the weekly condition. 1. Use the following Formula to create a weekly condition with the property of the week of the year. round(timesince(years(),1week).tostep() + 1).toCondition('Week') 2. From the Capsules pane select the Week property.
  6. Hello Everyone, I hope you are doing well. I need some help with creating a function. I have multiple conditions that I have created that tell me if the equipment is stopped, lag, standby, or other attributes. I want to be able to be able to: ADD Durations for when equipment is stopped and in lag OR when the equipment is stopped or standby. ADD Durations for when equipment is stopped but not in lag or standby. The example variables are in hours. Stopped ($i5) Standby($i6) Lag ($i) I would appreciate the help.
  7. Need to clarify the difference between a "calendar month" (per an actual calendar) and a "normalized month" (365/12) Example screenshots: 1. I set the time window to 1 month, starting January 1st at 12:00am. It ends January 31st at 10:00am. This is a "normalized month" 2. I do an integral over months, UTC-12:00. It resets on the 1st of each month at 6:00am. This is a "calendar month". 3. If I manually type in "6 months," it is 1/1/2020 12:01am to 7/1/2020 1:01pm. However if I manually type in "26 weeks" it is automatically converted by Seeq to "6 months" and it is 1/1/2020 12:01am to 7/1/2020 1:01am. The length of the 6 months is different! Here's the real kicker: I manually type in 6 weeks and it is automatically converted by Seeq to "6 months". I then manually type in "6 months". The time scale doesn't change, it still ends at 7/1/2020 1:01am. So the length of the "6 months" that I entered depends on the previous state of the chart. Same thing happens for a year. One year is 365 days (or 366 days for a leap year). It is not 52 weeks * 7 days = 364 days. It would greatly help us to get these time frames resolved. Contracts and accounting run on true calendar months and years. 3 How long is six months.pdf 1 Normalized Month.pdf 2 Calendar Month.pdf
  8. Summary There are many use cases where the user wants to do an aggregation over a periodic time frame, but only include certain values. Examples abound: for cement calculate the average daily clinker production only when the kiln is running, for biotech pharma the standard deviation of dissolved oxygen only when the batch is running, etc. Here our user is looking into equipment reliability for compressors. She wants to calculate the average daily compressor power to examine its performance over time. Steps 1. Add the signal into Seeq. 2. Use the 'Periodic Condition' or 'Formula' Tool to add a condition for days. This doesn't have to be days, it can be any arbitrary time, but it is usually periodic in nature. To use a custom periodic Condition, consider using the periods() function. For example to do this for days, the formula is: periods(1day) As an example, to change this to 5-minute time periods the formula is: periods(5min) Here are how the days and statistics in the Capsule Pane look for her: 3. Find only the desired values to be used in the aggregate (e.g. Average) statistic. From the values in the Capsule Pane she sees that the average compressor powers results are too low. This is because all the time when the compressor was OFF, near 0, are included in this calculation. She wants to only include times when the compressor is running because that will provide a true picture of how much energy is going into the equipment - and can indicate potential problems. To do this, she creates a 'Value Search' for times to include in this calculation, in this case when the Compressor is ON or > 0.5kW. 4. Create a new signal to only have values *within* the 'Compressor ON' condition. Use the aptly named 'within' function in the 'Formula' Tool. Notice how the resulting Signal in the bottom lane only has values within the 'Compressor ON' condition. Now she can use this because all those 0's that were causing the time-weighted Average to be low... are now gone. 5. Examine the resulting statistical values. She now sees that the calculations are correct and can use this resulting 'Compressor Power only when ON' Signal in other calculations using 'Signal from Condition', 'Scorecard Metric', and other Seeq Tools! Example using 'Signal from Condition' tool to calculate Average daily Compressor power when ON Content Verified APRIL2023
  9. FAQ: I would like to create a condition for the summer season that runs from May 1 - September 30, but when I use the Periodic Condition tool to create a monthly condition and select the months May-September, I get individual monthly capsules rather than one capsule for the entire summer. Is there a better way to do this using Seeq's tools? Solution 1 - Using Seeq Point & Click Tools: 1. Use the Periodic Condition tool to create a condition for May. 2. Use the Periodic Condition tool to create a condition for September. 3. Use the Composite Condition tool (join operator, inclusive of A, inclusive of B) to create a new condition that spans from the beginning of May to the end of September. Solution 2 - Using Seeq Formula: 1. Create a monthly Periodic Condition selecting all of you "summer months". Note that while it looks like one long capsule at the top of the display pane, it is actually 5 adjacent monthly capsules. You can confirm this by looking at the capsules pane in the bottom right hand corner of the application. 2. Use Seeq Formula and the merge() function to merge adjacent capsules. The appropriate syntax for merging adjacent capsules can be found by searching the word "merge" in the search documentation bar within Seeq Formula and scrolling to the example to "merge overlapping AND adjacent capsules". Note now in the capsules pane there are still the individual capsules for summer months, but there is a new green capsule that spans the entire summer as defined in this problem statement.
  10. The timing of Periodic Condition capsules is tied to the time zone selected by the user when specifying the Periodic Condition. The user should pay close attention to this selection as it can have significant impact on calculated results. Suppose the user is creating a daily periodic condition as shown below: In this case, the user has specified US/Eastern time zone for the daily capsules when setting up the Periodic Condition We can see in the capsules pane in the screenshot below that these capsules start at 12am in the Eastern time zone, which is the "worksheet time zone" the user is currently using for the trend display (evidenced by the "EST" to the right of the timestamps just below the trend). NOTE: the worksheet time zone changes the display of the timestamps, but it doesn't change the actual timestamps of the daily capsules. Now, suppose the user wants to do a daily average or totalization based on this daily condition, but the calculations are for equipment or a manufacturing site that is in the US Central time zone (or some other time zone). Because the daily capsules start at 12am Eastern time, the calculated results would be inaccurate for daily results involving equipment in the US Central time zone, as we would be aggregating the daily results starting at 11pm Central time. The selection of the appropriate time zone always depends on the specific objectives of each analysis, but in this specific case the user may want to set up the Periodic Condition specifying US/Central for the time zone, so that daily aggregations are from 12am-12am Central time. Selecting the correct time zone is also important because it affects edge cases like daylight savings. Selecting a time zone that honors DST will produce the 25 or 23h capsule on the proper adjustment day. Similar time zone comments apply when working with capsules representing other periodic time periods (weeks, months, years, etc.), as well as for recurring crew shifts - where the user should specify the time zone carefully based on the objectives, manufacturing site, equipment location, etc. Content Verified DEC2023
  11. I have a Boolean signal and would like to count the number of events over a specified time period. How can this be accomplished in Seeq? Thanks, Sam
  12. Overview: This example explores two methods for assessing equipment operating conditions per unit of time (i.e. total operating hours per week in this example) using the Signal from Condition tool and Histogram. The Signal from Condition approach creates a new signal using an equation or statistical function. The Histogram approach transforms a signal into a "value" domain, plotting the distribution of values over a period of time. For these examples, we will use “Compressor Power (Area A)” from the Seeq demo data and asset framework, which has routine ON/OFF operating cycles. The objective in this example is to create Derived Data signals to indicate when a compressor is running and calculate operating hours per week. Workflow: 1. Add target signal -- in this analysis we will use Compressor Power (Area A). 2. Complete a Value Search to determine when the equipment is running. In this example, I searched the compressor power signal for when it is above 5 kW which indicates it is running. 3. Using Periodic Condition, create a Weekly Signal. 4. Create a new signal Compressor Run Hours Per Week using Signal from Condition Tool. 5. Customize the Signal from Condition as a Bar Graph -- click the Customize button in the Details Pane and select the Bar Chart Icon under the Samples column. Each bar represents the total operating hours of the compressor each week. 6. Histogram Aggregated by Calendar Week- In this example, we have created a Histogram, Avg Compressor Run Hours per Week, which calculates the average value of the derived-signal, Compressor Run Hours per Week, aggregated by calendar week (Week of Year). Content Verified DEC2023
  13. Currently I am using the Periodic Condition to be able to view average capacities hourly, however I'd like to know if there is a way to obtain these averages every minute. What I am are trying to achieve here is to be able to see the average capacities every minute of our tags and if at the same time this data could be portrayed as a signal so that we can compare the averages with our original signal in one single lane if both are possible together. Thanks again.
  • Create New...