Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision 		Previous revision
samplestream:example [2024/04/25 23:33]
optrix 		samplestream:example [2024/04/25 23:50] (current)
optrix
Line 3: Line 3:
 {{cupcakelag.png}} {{cupcakelag.png}}
  
-In this case, we're going to ask for both the **oven temperature** and **final colour** on a cupcake-making machine. These two pieces of equipment are 50m apart from one-another. We want the values synchronised with the conveyor system, compensating for the lag between the two components.+In this case, we're going to ask for both the **oven temperature** and **final colour** on a cupcake-making machine. These two pieces of equipment are 50m apart from one-another.  
 + 
 +===Example Chart=== 
 + 
 +This is what a chart of our temperature and colour values looks like at the moment. Thanks to the distance between the two components, there's a significant amount of lag between the readings from the //oven// compared to the readings from the //inspection station//. 
 + 
 +{{linechartbakerynormal.png}} 
 + 
 +If we wanted to report on cupcake quality and get insight into //why// the quality was low, we can make this much clearer by compensating for the lag.
  
 ===Identify Key Elements=== ===Identify Key Elements===
  
-First, we determine the [[source|source of our lag]]. This is the **conveyor speed**, which is a **rate of change**.+First, we determine the [[source|source of our lag]]. The real source is //distance//. To compensate for the distance between our assets, we need either a //counter// or a //rate// that reflects the distance moved by our conveyor. 
 + 
 +The **speed of the conveyor** is perfect for this - it's a rate of //distance// over //time//.
  
 Next, we determine our [[end asset|end asset]]. In this case, the last asset in the system is the **Inspection Section**. Next, we determine our [[end asset|end asset]]. In this case, the last asset in the system is the **Inspection Section**.
  
-Finally, we want to measure our [[distance|distances]]. The distance between the Oven and the Inspection Station is **50m**.+Finally, we want to measure our [[distance|distances]] between each asset and our end asset. From the diagram at the top of the page, we can see that the distance between the Oven and the Inspection Station is **50m**.
  
 ===The Code=== ===The Code===
Line 48: Line 58:
 We then send a request for the last hour of data. We then send a request for the last hour of data.
  
------+===The Results===
  
 In our results, we get the following... In our results, we get the following...
Line 60: Line 70:
 |6.0|62%|131.6| |6.0|62%|131.6|
  
-You'll notice that you don't have a //time// index anymore in the resulting dataframe. Instead, you've got a total amount of whatever you're measuring as a //rate// or //total// (in this case, it's meters).+You'll notice that you don't have a //time// index anymore in the resulting dataframe. Instead, you've got a total amount of the [[source|source of lag]] seen (in this case, it's meters of conveyor-belt).
  
 ===What It Means=== ===What It Means===
  
-Originally, a chart of our values looked like this... +Reading our original chart, people may //suspect// that there's a direct relationship between the two dips, but it requires technical knowledge and very clean data to be confident.
- +
-{{linechartbakerynormal.png}} +
- +
-Reading it, people may //suspect// that there's a direct relationship between the two dips, but it requires technical knowledge and very clean data to be confident.+
  
 But after lag compensation, our chart looks like this... But after lag compensation, our chart looks like this...

ARDI

Welcome Guides

User Guides

Administrative

Sever
Other

API / SDK

Scripting

Addons / Drivers

Other Media