Jump to content

All Activity

This stream auto-updates

  1. Today
  2. Hi Robin, 1) To answer your earlier question, to avoid the time weighted standard deviation, all you need to do is change the signal to a discrete signal and then apply the same formula: $CanWeightSignal.toDiscrete() .aggregate(stdDev(), // std deviation statistic periods(10min,1min).inside($CanProductionCapsules), // do the calc over 10 min rolling window every minute // but only for 10 minute capsules fully inside CanProduction capsules endKey() // place the calculation result at the end of the 10 minute window , 0s) // max interpolation between data points, use 0s if you want discrete result 2) To answer your most recent question, to convert your current result to a stepped signal rather than the discrete results you now have on the trend, you can use a Formula function named .toStep(). Inside the parentheses, you enter the maximum amount of interpolation, the maximum amount of time you want to draw a line connecting your calculated results. For example, the function below sets a maximum interpolation between data points of 8 hours. .toStep(8hr) Hope this helps! John
  3. Yesterday
  4. @John Cox... almost... I found a signal that indicated the production status, independent of the Can Size. This is the right trigger to calculate the STD per can I decrease the function to calculate it every 5 minutes, 30s 2 things.... can we add a (stepped) line.... and how we close the gaps... Due to calibrations, every 18 minutes or production interrupts there a gaps in the STD signal... can we fix this... ?? but many thanks for now... getting closer 😉
  5. Thanks for the reply... using the standard deviation, based on Signal from condition is a Time-Weighted STD and this will not work... It should be an event weighted Standard Deviation (each individual can) I will try your second suggestion....
  6. Last week
  7. Hello Mohammed, The answer depends on exactly what you want to remove from the signal. In some cases, you may want to do a Value Search to find the peaks you want to remove, then use the .remove() function in Seeq Formula to create the new signal with the peaks removed. In some cases, all you may need is to apply a smoothing filter (for example, agileFilter() in Seeq Formula or one of the Signal Smoothing options under the Cleanse Tools), or perhaps use removeOutliers() in Seeq Formula. The documentation below provides a great summary of the many data cleansing tools in Seeq. I hope this information is what you are looking for!
  8. I know that this is an old post but I wanted to give an update. Unfortunately there is not currently a way to pass user credentials or delete worksheets/workbooks using the URL builder functionality.
  9. There is an easy way to filter a condition to only keep capsules that are either longer or shorter than a specified duration. In formula just use one of the following function $myCondition.removelongerthan(5h) or $myCondition.removeshorterthan(5h)
  10. Hi, I need to calculate average flowrate, but for some specific case and I want to filter short capsules. Is there a possibility to filter capsules shorter than X minutes/hours?
  11. I do not have access to your original signal for testing, so my solution not handle all the unusual characteristics that may occur. But I believe the approach below will help you get going on this calculation. 1. I would first recommend you create a clean weight signal that uses the remove() function to eliminate small decreases in the weight signal due to measurement noise and equipment variation. (This first step makes step 2 work accurately, because in step 2 we will be looking for the weight to go above 2000, 3000, 4000, etc., and we don't want noise variation from say 3002 lb to 2999 lb at the next sample, to appear to be a step decrease.) Create a clean weight signal using the formula below. This should result in a weight signal that only increases during the normal rampups, but still resets to 0 when the next rampup processing begins. Note that the 1hr inside of toStep() is the maximum interpolation between data values; set this based on your preferences. 2. Create the Step Counting Signal by dividing the clean weight (step 1 result) by 1000 and using the floor function to generate an integer result. 3. For an example signal that I tested with, you can see the Step Counting Signal incrementing as each 1000 lb increment is exceeded. Depending on your final analysis goals, further calculations could of course be done to calculate/report the number of steps completed for each of your original purple capsules or to do other types of statistics.
  12. Hi Robin, I would use a Seeq formula similar to the one below, with the Can Weight signal and your existing Can Production capsules as inputs. The key functions used are aggregate(), periods(), and inside(). Note that you could also do the std deviation calculation using Signal from Condition, using a condition created in Formula with: periods(10min,1min).inside($CanProductionCapsules). $CanWeightSignal .aggregate(stdDev(), // std deviation statistic periods(10min,1min).inside($CanProductionCapsules), // do the calc over 10 min rolling window every minute // but only for 10 minute capsules fully inside CanProduction capsules endKey() // place the calculation result at the end of the 10 minute window , 0s) // max interpolation between data points, use 0s if you want discrete result Hope this helps! John
  13. I have a can line, that can handle 3 types of can sizes.... 400gr, 850gr and 900gr. I have created a capsule, based on HI / LO limites (set in Asset Framework) and the CanSetpoint Now I want to calculate the standard deviation of the can weight. These are individual measurements and the timing depends on the line speed (unknown) I want to know the 10 minutes rolling standard deviation fill weight, within a capsule. So start capsule 400gr can - xx amount of can - time 00:00:00 till 00:10:00 - STD 1 minute later: 400gr can - xx amount of can - time 00:01:00 till 00:11:00 - STD etc... Suggestions ...?
  14. Earlier
  15. Trying to count step within a capsule. What I consider steps as any step UP value change which is more than 1000 lbs. Example image attached. Any help would be appreciated.
  16. I have just install a SEEQ connector to connect Honeywell Uniformance PHD OPC Server (OPC HDA). From the seeq connector machine, I can connect to PHD OPC HDA server . I can see the new connector agent in the list on server but no connection to the PHD OPC Server. Can someone help, what could have gone wrong here? Thanks
  17. HI robin, Is there some way that identifies the end of the sub-batches or just a new unique first 7 characters for a new batch?
  18. Hi Robin, you can create a batch condition by using replace() to extract the batchnumber and toCondition() for creating the capsules for each batch: $subbatches.replace('/(\\d{1,7})NR\\d{3}/', '$1').toCondition() In the next step you can do the aggregation: $v1.aggregate(sum(), $batch.removeLongerThan(1wk), middleKey()) + $v2.aggregate(sum(), $batch.removeLongerThan(1wk), middleKey()) Regards, Thorsten
  19. The problem is that the batchnr changes everytime... and the number of sub-batches also... The first 7 char. are unique and than it can be 001 till .... 00y. And we need to capture the total per unique batch xxxxxNR001 ... xxxxxNR00y for all batches, past , present and future...
  20. Hi robin, I would start by creating a capsule that represents the entire time frame that you want to sum up the values for. If you want those two sub-batches together in the summation, you'd likely want to either do a regex value search that would capture both of those values (but not any others) or the simpler method would be to simply do a value search for each of the individual sub-batch values and then perform a "join" using composite condition to join the first one to the second. That should provide a single capsule that goes across both sub-batches. After that, you need to do your summation. The easiest method would be to use Signal from Condition to perform a sum of the green signal during the capsule created above and place that wherever you want the value to be (I'd suggest using duration as the timestamp so that you can see the statistic goes across both sub-batches). Repeat the same Signal from Condition for the purple signal as well. After that, you can use Formula with $GreenSignalFromCondition + $PurpleSignalFromCondition to complete the summation you'd like. Regards, Joe
  21. Hi Seeq.. it is possible to sum the "Product door UHT" and "Product naar Vullen\/Surgetank via NV1 klep" at the time of both sub-batches So I want to sum all bars (green and purple) where batch value 33780NR001 and 33780NR002 are true... please guide me towards a solution..
  22. Hi Adam, If you're referring to pushing data, then per the docstring (SHIFT + TAB) for spy.push, you'll need to set the column name to the ID of the Seeq signal for it to write to an existing signal: To push to an existing signal, set the column name to the Seeq ID of the item to be pushed.
  23. When running a Data Lab project.... sometimes the push command writes to an existing signal and sometimes the push command creates a new signal (with the same name as the existing signal) and writes to that. The result is duplicates. It wastes time to stay organized by switching broken formulas and deleting the duplicates. Is there a way to force the push command only to write to existing signals, never to create new signals?
  24. I am seeing a number of user authentication failures using the Users.AuthenticationFailures.Meter. We want to understand which users are failing to determine the cause. What log file can we use to determine the user name of the failures?
  25. @TeddyI'm really interested in this feature as well, could you please share the script.
  26. Hello, you can use the merge() function for this. If a tolerance value is specified all capules beginning withing that tolerance after the end of a capsule are combined. Regards, Thorsten
  27. Hello, I am trying to create a Capsule using composite condition and Union method using two individual capsules. However what I would like to do is in "Union" method ignore small gaps like <40 Seconds long gaps in between Union and call it as ONE signal capsule. Please see attached image for reference. Any help would be appreciated.
  1. Load more activity
×
×
  • Create New...