Jump to content

Lindsey.Wilcox

Seeq Analytics Engineers
  • Content Count

    19
  • Joined

  • Last visited

  • Days Won

    5

Lindsey.Wilcox last won the day on April 8

Lindsey.Wilcox had the most liked content!

Community Reputation

5 Neutral

Personal Information

  • Company
    Seeq
  • Title
    Analytics Engineer

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Hi Kevin- Seeq is compatible with OData 2.0. Please let me know if you have any additional questions. Thanks, Lindsey
  2. Hi Curious George- Yes, this can be accomplished using capsules properties. Please use the following steps: 1. Here I’ve created several different conditions using Value Search on my temperature signal. Note that each of these conditions (or bins) varies in size: 2. Once I have these conditions established, I can use Formula to combine all of the conditions into one “Bins” condition, and set a property for each of the capsules in the new condition: 3. Then I can use the properties of the capsules in this Bins condition to create my Histogram: Please let me know if you have any additional questions. Thanks, Lindsey
  3. Hi- Yes, you are correct that one option to fix this is to increase the maximum duration for the Value Search. This would identify capsules of longer durations, but may compromise performance. Another option is that instead of searching for when the machine is running, use Value Search to identify when the machine is not running. Then use the .inverse() operator in Formula ($NotRunning.inverse(30d)) to identify when the process is running. This method will have less of an impact on the performance than simply extending the maximum duration of the Value Search. Lindsey
  4. This use case came up while working with a customer last week, and I thought it was worth sharing on the forum, since other users may be interested. The user I was working with was interested in creating limits for a signal. The limits would be calculated based upon the average and standard deviation of the previous 4 hours of operation; essentially the user wanted to create a rolling 4 hour boundary. We worked out the following solution: 1. Create a periodic condition for the time period that you would like to use for this rolling window. Here I created 4 hour periods: 2. Next, use signal from condition to calculate the average of the signal during each of these 4 hours periods: 3. Use signal from condition again to calculate the standard deviation of the signal during each of these 4 periods. 4. Now use Formula to calculate the upper and lower boundaries based on the average and standard deviation. Here I’m creating boundaries that are +/- 2 standard deviations. Note that the ‘.delay(4h)’ is needed to shift the boundary signals so that the PV signal is being compared to the upper and lower boundaries calculated in the previous 4 hours. 5. Once the upper and lower boundaries are identified, use Deviation Search to determine when the signal is outside of these boundaries.
  5. Hi Curious George, Yes, this is doable in Seeq by using the following steps. 1. Since you've already identified your batch runs, the first step will be to use Signal from Condition to identify the maximum value of each batch. Be sure to place the timestamp for the summary statistic at the point of the maximum value. 2. Next, use Formula to create capsules around these maximum batch values: Note that this formula creates a new condition where each capsule is centered around the batch maximum. In the screenshot, the capsules are created to start ‘6h’ before the maximum point, and end ‘6h’ after the maximum point, for a total duration of 12 hours. You can edit these times as needed for your batches. 3. Now, when I view this “Max Batch Aligned” condition in Capsule time, each of the maximum values line up at the same time point. Select Maximum alignment, if desired, to align the maximum points vertically as well: Please let me know if you have any additional questions. Thanks, Lindsey
  6. Hi Adam - did you have a chance to try the solution Julianne provided? Did it fix the issue you described?
  7. Curious George- There are a couple of ways that you can get this information. Depending how you would like to view / use the information, the following methods may be used: 1. The easiest way to get this information is to add the Duration to the Capsule Pane display: This allows you to quickly view the duration of each of your capsules. 2. If you would like to use the capsule duration in additional calculations or have the capsule duration's trended over time, the Signal from Condition tool may be used to create a new signal that reports the duration of each capsule in the condition: 3. A third option, if you would like the capsule durations presented in a table, is to use Scorecard. First, navigate to Scorecard: Then, add a Condition based metric: Please let me know if you have any additional questions. Thanks, Lindsey
  8. SeeqKing- I'm curious to know a bit more about how you have these limits configured; are you using the Boundaries Tool? Any additional information or screenshots you can provide would be helpful.
  9. Hi Aikju- To calculate the rolling sums, use the .runningSum() function in Formula. Note that you will be required to provide a condition over which to calculate the rolling sum; this could be calendar days, a production mode condition etc: Now that you have a signal calculating the rolling sum, a combination of Value Search and the .splice() function in Formula can be used to set the signal equal to 0. First, lets use Value Search to identify when the running sum is greater than zero: Before we can use the .splice() function in Formula, we need to create a 0 signal in Formula: Now, we can use the .splice() function in Formula to splice in the 0 signal whenever the Rolling Sum signal is greater than 0. Please let me know if this gets you the results that you need or if you have any additional questions. Lindsey
  10. Hi AiKju- There are a couple methods to accomplish this, both of which are summarized in our Knowledge Base. Take a look at these articles: 1. Using Boolean Signals to Replace IF Statements (https://seeq12.atlassian.net/wiki/spaces/KB/pages/379748431/Using+Boolean+Signals+to+Replace+if+Statements) 2. Using Conditions and the Splice Function to Replace IF Statements (https://seeq12.atlassian.net/wiki/spaces/KB/pages/258179210/Using+Conditions+and+the+Splice+Function+to+Replace+if+Statements) If there's any additional information you can provide about your Use Case, we may be able to provide some more specific work steps. Let me know if you have any additional questions. Lindsey
  11. Hi Curious George, This is best accomplished using the .removeOutliers() function in Formula. Navigate to Formula from the Tools menu: Apply the .removeOutliers() function to your input signal: The new signal, shown in green in the second lane, no longer contains these large spikes. Please let me know if you have any additional questions. Lindsey
  12. Hi SeeqKing- This is best achieved using the Scorecard feature, as described in the following steps. Note: Scorecard was updated in the latest release of the software. In order to perform the following steps, you must upgrade to the latest version, if you have not already done so. To upgrade, please reach out to your Seeq contact or email support@seeq.com. 1. Select Scorecard Metric from the tools menu. 2. Provide the requested information and click Execute: Type: Select 'Simple' to calculate over the display range Item to Measure: Select the input signal Statistic: Select the statistic to calculate on the input signal. Thresholds: provide Hi and Lo thresholds to be displayed as colored regions on the trend (this field is optional) 3. Display the signal and Scorecard metric in one lane by selecting the signal and metric in the details pane and then clicking "One Lane" and "One Y-axis". Please let me know if you have any additional questions. Thanks, Lindsey
  13. Gerald- I'd be interested in knowing a little bit more about your use case; any additional details you can provide would be helpful. In addition to Jon's suggestion, another idea may be to use the Scatterplot feature. Plotting your data in Scatterplot allows you to use a dimension other than time on the x-axis. Navigate to Scatterplot from the trend view: Specify the signal to display on the x-axis and the y-axis: To draw a line through the points over time, click the 'Connect' button: Please let me know if you have any additional questions Thanks, Lindsey
  14. Hi Curious George- This can be accomplished using the Histogram tool. Follow these steps to perform the analysis: 1. Create a capsule for each stage in the process. This can be done using the .toCapsules() function in Formula. This function creates a new capsule for every value change in the Compressor Stage signal. 2. Use Histogram to count the number of times in each stage. Please let me know if you have any additional questions. Lindsey
  15. Hi- This can be accomplished using a combination of Periodic Condition and Signal from Condition. 1. First, use Periodic Condition to create the hourly capsules. 2. Use Signal from Condition to calculate the hourly average. Please let me know if you have any additional questions. Thanks, Lindsey
×
×
  • Create New...