The following Quiver cards are supported in derived series logic:
Quiver cards that do not output time series are supported; however, they will not update dynamically. Whatever value the card resolves to at the time of creation will be fixed in the derived series logic.
If you receive an error for multiple root objects in the dialog, your analysis likely started from a sensor object type and used two different individual objects for comparison. For example, you may have pulled and compared the sensor objects Inlet pressure and Outlet pressure from the sensor object type instead of the Machine 1 root object type. To create a derived series, you will need to start from the root object instance.
Review the requirements for setting up a derived series to learn why derived series must be generated from the perspective of a root object.
Yes. The logic and calculations are templatized so results can be calculated from the perspective of any bound object with the same object type. Review the section on storing derived series in the Ontology, and notice that the same codex template is applied to different Machine objects or sensor objects.
The derived series RID is for the Quiver resource that holds the resource name, description, and other metadata. The codex template RID listed on the Derived series management page is a reference to the template logic used when the derived series data is calculated at runtime. Review the section on storing derived series in the Ontology for more details.
To reference a specific version of logic, your TSP value should look like the following:
{"templateRid":"ri.codex-emu.main.template.8da5f759-4b...","templateVersion":"0.0.x"}
Since derived series are calculated at read time, the derived series will show any updates to the input series that are available. For example, any change to the input series that are visible in Quiver will also be reflected in the derived series.
Yes, derived series can be nested and used to calculate another derived series. You can use the derived series in the same way you would use a raw time series. Make sure to follow the derived series creation requirements so that the new derived series functions as expected.
Derived series offer the advantage of immediate logic updates without consuming pipeline resources. Applications that render the derived series (usually a Quiver analysis or a Quiver dashboard embedded in an application) will calculate the derived series using the updated templated logic.
Yes! A TSP can have a mix of values which are either a series ID for (non-derived) time series or Codex template RIDs for derived series. This is typically used with a sensor object type. If your TSP is backed by multiple syncs and contains derived series, your Codex template RID for the derived series should not be in the qualified series ID format.