The Datastore Historical worker calculates the historical magnitude of a security's reaction to changes in underlying factors, creating a new datastore with the result of the calculations.
The Datastore Historical worker must receive specific parameters in order to execute properly. When parameters are not set correctly it may cause the worker to not work as expected. This worker parameters is separated in the following tabs: Input, Output and Advanced.
The Input tab contains parameters which are consumed by the worker, in order to execute it's calculations.
Set the research workspace of the portfolio using Fixed Workspace variant. The default is using the current workspace.
1.3 Property Selection
The property selection section contains the properties that will be included in the datastore.
Select whether the volatility will be calculated or not using Boolean variants. The calculation returns options which can be chosen from the following items: Security and Portfolio.
Select whether the VaR will be calculated or not using Boolean variants. The calculation returns options which can be chosen from the following items: Security and Portfolio.
Select whether the CVaR will be calculated or not using Boolean variants. The calculation returns options which can be chosen from the following items: Security and Portfolio.
1.3.4 Stress Test
Select whether the Stress Test will be calculated or not using Boolean variants. The calculation returns options which can be chosen from the following items: Security and Portfolio.
Select whether the Portfolio BVaR will be calculated or not using Boolean variants.
1.3.5 Max Drawdown
Select whether the Portfolio Max Drawndown will be calculated or not using Boolean variants.
The Output tab contains parameters that defines the worker execution results, and how it will be provided to downstream workers.
Set the workspace in which the output datastore will be saved on the platform using Fixed Workspace. Default setting is the workspace of the input portfolio.
Select if the output datastore will be saved on the platform or be a transient one (temporary during workflow execution), through the following options: Transient or Create. The default is a transient datastore.
The Advanced tab contains the header suffix and the set of parameters that will be used in the calculations.
3.1 Header Suffix
Number of business days used to calculate the covariance for the primitive risk factors using Number variants, the default is 252.
3.3 Exponential Decay
Weighting factor determining the rate at which "older" data enter into the calculation. The default is 0.94.
Sampling represents the frequency that historical prices and rates (spreads) are collected in order to compute the invariant risk factors. In order to sample daily, use 1. In order to sample weekly (non-overlapping), pass 5. For various combinations between horizon and sampling click here. The default is 1-day sampling.
Determines the Horizon for calculation. The horizon parameter produces a range of outcomes for each security via their underlying factors across specific date range. The default is 1-day Forecast.
Determines the confidence level for calculation. The confidence interval produces a range of values with a defined probability that the value of a parameter lies within it. For example: if the confidence interval is 95% and the number of simulations is 10,000, we use only the first 5%, or 500 samples. The default is 95%.
Once the worker finishes it's executions succesfully, it will return a result object containing the datastore to the workflow, which can be used by upstream workers. Below you can see an example of the datastore result object hierarchy.
- Datastore (datastore)
- ID (string)
- Name (string)
- Date (date)
- Tags (list of strings)
- Data (list of lists)
The Data component is composed of the columns common to all datastores, attributes and aggregations, including the selected properties columns. The possible columns added to the datastore are listed below.