Jump to content

Joe Reckamp

Seeq Team
  • Content Count

  • Joined

  • Last visited

  • Days Won


Joe Reckamp last won the day on May 3

Joe Reckamp had the most liked content!

Community Reputation

48 Excellent

Personal Information

  • Company
    Seeq Corporation
  • Title
    Analytics Engineer
  • Level of Seeq User
    Seeq Advanced

Recent Profile Visitors

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

  1. Hi Pat, You will need to make sure that the maximum interpolation is less than the data being removed or else the data will be interpolated through the gaps. You can set the maximum interpolation in the formula as well by adding a .setmaxinterpolation(<time>) at the end.
  2. Many batch customers want to track cycle times of batches. Histograms are a great way to aggregate and visualize the cycle times for continuous improvement. The data set involved includes a Batch ID (typically a string signal, but could also be a capsule with a Batch ID property) and optionally a signal for splitting up the batch such as a unit procedure, operation, phase, or step. In order to prepare the data for the histogram, we need to convert these signals into capsules with the appropriate Batch ID and operation as properties on each capsule. This can be done in the followi
  3. Hi Stephanie, Currently, you cannot use Scorecard Metrics as a threshold, but you could create the same calculated metric using Signal from Condition and use that result as the threshold for the other metric. Once you have the signal created, you can use the following button to toggle from a value input to a signal input for the threshold:
  4. Hi Julian, The first formula ($signal.toCondition()) will create a capsule the length of each time frame between step changes. From there, you can use Signal from Condition to calculate the "Total Duration" statistic for each of the capsules created (use the result of the formula for both the condition of interest and bounding condition).
  5. Hi Julian, This Formula should do the trick: $signal.toCondition() Note, if you want just the time point where the change occurs, you could add another argument to shorten the time duration of each capsule: $signal.toCondition().afterstart(1s)
  6. This can now be done a lot simpler by just doing the following command: spy.search('<URL>') or as an example: spy.search('https://explore.seeq.com/workbook/741F06AE-62D6-4729-A4C3-8C9CC701A2A1/worksheet/DFAC6933-A68F-4EEB-8C57-C34956F3F238')
  7. For those Formula-savvy users, a one Formula approach to this would be as follows where you would define your percentage of the capsule in the first line: $percent = 10%.tosignal().resample(1s) $condition.transform($capsule ->{ $movetime = $capsule.duration()*$percent.toScalars($capsule).first() capsule($capsule.startKey(),$capsule.startKey()+$movetime)})
  8. Hi John, The capsule shows in progress because when the next month starts, it will jump to the next month, meaning that the capsule will continuously be moving. I think what you want is to use the following formula which will create a 1 year long capsule starting each month. periods(1y, 1mo)
  9. Hi Mattheus, You can do this by using the move (v49+) or delay (<=v48) function. For example, your equation would be: ($signal.move(5s)+$signal.move(10s)+$signal.move(60s))/3
  10. Hi Devin, In version R50, there are some additional features for Scatter Plot coming out including adding labels to the scatter plot that will show the values and timestamp next to it:
  11. Hi Sivaji, Sorry for another "you probably need to upgrade" response to your question, but if you look through the Knowledge Base on Scatter Plot (https://seeq.atlassian.net/wiki/spaces/KB/pages/153518135/Scatter+Plot), you'll see that a lot of these capabilities have been added. For example, starting in version 46, you can color by fixed date ranges, allowing more coloring options by time as you mention. The workaround on your version I believe would be to make each year its own condition using Custom Condition or something like that (one condition would be only the year of 2019, an
  12. Hi Sivaji, This is not possible in version 45, but is available starting in version 48: https://seeq.atlassian.net/wiki/spaces/KB/pages/736035141/What+s+New+in+R22.0.48
  13. Hi Aleksander, The totalize function requires the totalization to be bounded by a capsule because otherwise it has no idea how far back in history to go. For instance, if you want to view the most recent day worth of data, does it have to go back through the entire history of your data signal (maybe 10+ years worth of data) to perform the calculation on? Therefore, the condition you give it will "bound" that calculation to a certain period of time so that Seeq knows when to start and stop that calculation. If I'm understanding correctly, I think you would want to "bound" the calculat
  14. You can only set the priority color based on conditions so you would need to create a condition off the signal. For example, you may do a Value Search to find when a capsule longer than a certain time length is found. In this case, you will first need to perform the totalized or summation using Signal from Condition and then you can do a Value Search on that signal.
  15. Hi Sivaji, You could do this in a couple different ways by turning the duration of the condition into a signal. One method would be to use Signal from Condition to calculate the duration of each capsule in the condition and then performing a sum on that signal for the Treemap statistic: Since you have to place the duration at a timestamp of each capsule, it means that if the "end" timestamp were selected as in the above example, the whole capsule would be counted even though half of the capsule may be off the edge of the time selected in the display. If this is an issue, I
  • Create New...