Jump to content
  • To Search the Seeq Knowledgebase:

    button_seeq-knowledgebase.png.ec0acc75c6f5b14c9e2e09a6e4fc8d12.png.4643472239090d47c54cbcd358bd485f.png

Search the Community

Showing results for tags 'periodic condition'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • Community Technical Forums
    • General Seeq Discussions
    • Seeq Admin Forum
    • Training Resources
    • Product Suggestions
    • Seeq Data Lab
  • Community News
    • Seeq Blog Posts
    • News Articles
    • Press Releases
    • Upcoming Events
    • Resources

Categories

  • Seeq FAQs
  • Online Manual
    • General Information

Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


About Me


Company


Title


Level of Seeq User

Found 14 results

  1. 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)
  2. 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.
  3. 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.
  4. FAQ: For reporting purposes, I want to calculate statistics based on the current period to date and display that next to the periods immediately preceding it. This is easy to do using the custom date range tool in Organizer Topic (Creating a Periodic Condition and the grabbing the capsule closest to or offset by 1 from the end). Is there a way to create these same date ranges relevant to the current time in Seeq Workbench? Solution: We can create identical conditions in Seeq 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".
  5. 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
  6. 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!
  7. 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.
  8. I have created a daily condition in Seeq using the Periodic Condition tool. Why don't the capsules start at midnight? For example, in the screenshot below the "Daily" capsules start at 11:00PM (see the Capsules pane) instead of midnight (12:00AM). This results when the user interface (UI) time zone does not match that of the Seeq Server. In this example the Seeq Server time zone is US/Eastern but the UI time zone is US/Central. To make the UI time zone match, the user can click on the UI time zone link (noted by the red box in the screenshot: trend display, x-axis, right of timestamp): The user can then set the "Always use:" option to US/Eastern (in this example the Seeq Server is on US/Eastern) as shown here: The daily capsules now start at midnight:
  9. 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
  10. Overview: This technique example explores two methods for assessing equipment operating conditions per unit of time (i.e. total operating hours per week in this example) using Signal from Conditions (Presented as a Bar Graph) and Histogram. The Signal from Condition approach transforms a condition into a new signal using an equation or statistical function (in this case we will use an equation and the “TotalDuration” function). The approach using the Histogram tool allows transforming a signal into a "value" domain. For example, for a given segment of time, plot the distribution of values. 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. The signals are then presented in two formats - bar graph and histogram. Applications: Similar types of duration analysis of signals from conditions can add value for Seeq users in comparative analysis for batch processes, calculating and monitoring equipment operating hours and tracking target operating envelope deviations. Workflow: 1. Add target signal --Find and add the 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. This will be used in our Signal from condition Calculation 4. Create a Signal from Condition. Create a new signal Compressor Run Hours Per Week using Signal from Condition Tool. 5. Plot the Signal from Condition as a Bar Graph -- in order to show the derived signal for Compressor Run Hours Per Week as a bar graph, simply click the Customize button in the Details Pane and select the Bar Chart Icon under the Samples column. The result is shown below. Each bar represents the total operating hours of the compressor each week. 6. Histogram Aggregated by Calendar Week- The Histogram Tool can also be used to generate a similar graphical analysis for Compressor Run Hours per Week. However, this tool is currently applicable for performing statistical functions on signals. 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). The Bar Graph and Histogram are shown on the same display below.
  11. 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.
  12. Rolling averages are frequently used in Seeq to smooth signals. Calculating a rolling average requires creating a Periodic Condition and then applying the Signal from Condition tool to aggregate the signal of interest over the bounding periodic condition. Sometimes, we want to calculate a rolling statistic over a time frame not listed in the Periodic Condition tool (anything < hours). To create a periodic condition for periods of time not offered in the tool, the Seeq formula tool can be used with the periods() function. For example, a 15 minute periodic condition can be created by entering "periods(15 min)" into the Seeq formula tool.
  13. Hello, This might be a simple question but have not been ale to find help anywhere (Being a beginner). I would like to know how to calculate hourly avg trend of a signal which is one sec interval. What I am thinking is: Suppose signal is = $a a) Create value search for hourly capsules? b) Taking avg of during those capsules using formula search? However I would like the time range for this hourly avg to be dependent on time slider. Which means that sliding time should update the trend. Any help (Formula snippets) would be appreciated.
  14. Is Seeq able to create the graph below? Note that the left-hand side plots the yearly average, while the right-hand side plots the monthly average. Ideally I would like this all displayed on one graph. Currently, our only workaround is to create 2 separate graphs (one for the yearly averages and one for the monthly averages) and display them side by side.
×
×
  • Create New...