Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision | |||
|
samplestream:class_lagcorrectedquery [2024/04/25 23:20] optrix |
samplestream:class_lagcorrectedquery [2024/04/25 23:46] (current) optrix |
||
|---|---|---|---|
| Line 37: | Line 37: | ||
| You build up your query out of three main parts... | You build up your query out of three main parts... | ||
| - | ==Lag Counter or Rate== | + | ==Source of Lag== |
| - | First, you need a number that can be used to measure the lag. This might be a distance, a flow-rate, a speed or some other **counter** or **rate** that can be used to see how much of a //thing// (other than time) has passed. This is called the [[source|source of lag]]. | + | First, you need a number that can be used to compensate for lag. This might be a distance, a flow-rate, a speed or some other **counter** or **rate** that can be used to see how much of a //thing// (other than time) has passed. This is called the [[source|source of lag]]. |
| - | ==Assets== | + | ==End Asset== |
| - | Next, identify all of the individual pieces | + | Next, you' |
| - | For example, if a conveyor moves through three different temperature sensors, you'd identify them and measure how far away they are from one-another. | + | ==Assets |
| - | ==End Asset== | + | Next, identify all of the individual pieces you'll want to add to the query, and how much [[distance|distance]] there is between them. |
| - | Next, you'll choose an [[End Asset|end asset]]. This is usually the //last// part of your system. This is because the class only searches [[building backwards|backwards | + | For example, if a conveyor moves through |
| ===Additional Parameters=== | ===Additional Parameters=== | ||