Skip to main content
Out of the box, Atoti Market Risk will work with a predefined file format, CSV. If you produce your data in this format, you can load and use Atoti Market Risk with no customizations needed. However, you can of course edit and configure Atoti Market Risk to work with any format or file, database source, etc. that Atoti is compatible with. Sample CSV input files are included in the source distribution. These files are loaded during testing of the MR application and provide examples of each of the file types. Download PDF version of this chapter: Atoti Market Risk Input File Formats 6.0

​
Overview of input files

The input files for Atoti Market Risk comprise the following set:

​
File name patterns

Atoti Market Risk uses glob patterns with the (*) asterisk wildcard character to identify the relevant file names for each category of input file. So you can add characters before and after the listed names, such as timestamps or ID numbers. For example, the pattern **/TradePnLs*.csv matches all CSV files with names beginning with the string “TradePnL” in any subdirectory. In this guide, the file pattern section for each of the input files specifies the glob pattern used. However, the glob prefix is omitted as it is now injected automatically. You can customize the glob patterns by setting the appropriate file-pattern property in the application.yaml file.

​
Note on AsOfDate

The files in this document that contain an AsOfDate column will rely on that AsOfDate when loaded into the Atoti Server datastores. For the files that do not specify this column (whether described in this document or not), the AsOfDate is taken from the directory structure; these files should reside in the appropriate folder (usually ./data/20xx-yy-zz/ … /*.csv).

​
Key and optional fields

For each input file, the key and optional fields are indicated in the Key and Null columns respectively.

​
Scalar and vectorized sensitivities

Sensitivities are modeled in the Trade Sensitivities store as scalar values. In other words, each row contains a single sensitivity value corresponding to a given set of tenor, maturity, and moneyness. You can load data in this same format as specified by the Sensitivities input file format page. However, you can also load sensitivity data in a vectorized format. In this case, each row of the input file contains an array of sensitivity values along with corresponding arrays of tenors, maturities, and moneyness values. With the default Atoti Market Risk configuration, these two formats can be used interchangeably. Atoti Market Risk includes a ScalarSensiTradeStoreTuplePublisher that will convert vectorized to scalar sensitivities. We recommend loading scalar sensitivities as the best option in most cases.

​
Labels and dates for pillars

For the pillar information (Tenors and Maturities), both a label and date field are available, to allow any combination of source data:
  • Pillars as labels, with no equivalent dates available in the source system
  • Pillars as dates, with no equivalent labels available in the source system
  • Pillars as both labels and dates
The dynamic re-bucketing converts the pillar information into a number of days, this is the basis on which the destination bucket is calculated. The primary cube level upon which this conversion is performed can be configured. Atoti Market Risk will attempt to use the configured converter to transform the value of the primary level into a number of days, only using the secondary level if the primary has no value. To allow the slicing and dicing of input data on source pillars, both fields are selected as levels in the cube. Examples All pillar fields are keys. Therefore 2M,N/A will be a separate fact from 2M,2019-11-05.