Differences
This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision | ||
samplestream:class_lagcorrectedquery [2024/04/25 21:59] optrix |
samplestream:class_lagcorrectedquery [2024/04/25 23:46] optrix |
||
---|---|---|---|
Line 35: | Line 35: | ||
===Usage=== | ===Usage=== | ||
- | The **multiplier** is usually used to convert the time-base | + | You build up your query out of three main parts... |
- | The **shavems** option is useful if you want to simplify the data you're getting by eliminating sub-second results. This will effectively 'round up' your results so you have no more than one point per second. | + | ==Source of Lag== |
- | You build up your query out of three main parts... | + | 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]]. |
- | ==Lag Counter or Rate== | + | ==End Asset== |
- | 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. | + | 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 through |
- | ==Assets== | + | ==Assets |
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, identify all of the individual pieces you'll want to add to the query, and how much [[distance|distance]] there is between them. | ||
Line 51: | Line 51: | ||
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. | 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. | ||
- | ==End Asset== | + | ===Additional Parameters=== |
- | 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 through time]] rather than forwards, so you'll need to work from the end of your process. | + | The **multiplier** |
+ | |||
+ | The **shavems** option is useful if you want to simplify the data you're getting by eliminating sub-second results. This will effectively 'round up' | ||
===Example=== | ===Example=== | ||
[[example|See an example]] | [[example|See an example]] |