Differences
This shows you the differences between two versions of the page.
| Next revision | Previous revision | ||
|
samplestream:start [2024/04/18 00:37] optrix created |
samplestream:start [2024/04/24 03:02] (current) optrix |
||
|---|---|---|---|
| Line 6: | Line 6: | ||
| * Applications where you need to search for events across time-windows, | * Applications where you need to search for events across time-windows, | ||
| * When you need very reliable ' | * When you need very reliable ' | ||
| + | * When you need to correct for lag based on a measurement rather than a fixed time\\ | ||
| - | ===How It Works=== | + | ===Key Classes/ |
| - | SampleStream lets you //iterate// over a query. | + | The key classes in the library are... |
| - | SampleStream takes an AQL request, a [[window size|window size]], a [[number of samples|number of samples]] | + | [[ssintro|samplestream]], used to scan over time-frames, |
| - | Every time you ask SampleStream for the next sample of data, it returns | + | [[class_LagCorrection|LagCorrection]], used to measure |
| - | For example, if you wanted | + | [[class_LagCorrectedQuery|LagCorrectedQuery]], used to create historical queries with lag-corrected data. |
| - | The next time you ask for a sample of data, it will be //step size// seconds away from the previous sample. | ||
| - | |||
| - | This makes it quite easy to scan over a period of time. | ||
| - | |||
| - | [[Why is it different to a normal query?]] | ||
| - | |||
| - | |||
| - | |||
| - | The //window size// determines how many of seconds of data | ||
| - | |||
| - | Instead of requesting very large chunks of time, SampleStream only requests the time around the current | ||