Differences

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

--- samplestream:lcq_addquery [2024/04/24 02:11]
optrix created
+++ samplestream:lcq_addquery [2024/04/24 02:56] (current)
optrix
@@ Line 19: / Line 19: @@
 ===Usage===
-You normally add a single query for each different level of lag in your system.
+You normally add a single query for each different //level of lag// in your system.
-For example, **Machine A** is 100m away, so you query all of the points for that machine in a query with //lag// set to 100.
+This normally translates into having a distinct query for each asset - but there may be times when some assets are part of the same system and share the same amount of lag.
-**Machine B** is 50m away, so you add a query for that machine with a lag of 50.
+For example, **Machine D** is at the end of the line - we add a query for the properties on that asset, but it doesn't need any value for //lag//.
-**Machine C** is at the end of the line - you don't add a lag at all.
+**Machine C** is 50m away, so we create a query specifically for it with a //lag// of 50.
-Since you usually [[building backwards|build these queries backwards]], there's often either **no lag** or only a **small amount of lag** from the equipment at the end of the line.
+**Machine A** and **Machine B** are 100m away, so you query all of the points for both of those machines in a single query, with //lag// set to 100.
+===Choosing a Lag===
+Since you usually [[building backwards|build these queries backwards]], there's often either **no lag** or only a **small amount of lag** from the [[end asset|end asset]] found at the end of your process line. Your lag value increases as you get close to the 'start' of the process.
+The lag you choose for each query should be the [[distance|distance]] between that asset and your
+[[end asset|end asset]].

AddQuery

Differences

ARDI

Welcome Guides

User Guides

Administrative

Sever

Other

API / SDK

Scripting

Addons / Drivers

Other Media