Settings.paf
Qualisys Project Automation Framework settings file
| Type | object |
|---|---|
| File match |
settings.paf
Settings.paf
|
| Schema URL | https://catalog.lintel.tools/schemas/schemastore/settings-paf/latest.json |
| Source | https://raw.githubusercontent.com/qualisys/qualisys-schemas/master/paf-module.schema.json |
Validate with Lintel
npx @lintel/lintel checkA settings.paf file used by Qualisys Project Automation Framework (PAF) Modules
Properties
A human readable name that identifies the project. This name is recorded in data files and should not be changed once data collection has started as doing so will render data files useless.
Reference to the class or type name to use at the highest level in the PAF item hierarchy.
The columns section specifies the columns of the tree view in the project view. It allows the PAF file to specify multiple column setups. The idea is that the users should be able to switch between different configurations and possibly also add their own but currently only the first setup is used.
Specifies what date format to use in this project. Applies mainly to exports and column values but not to the field edit dialog. Accepted values are Iso, Little endian and Middle endian.
Specifies which token to use to separate the parts of the dates when formatting them. Accepted values are Dash, Slash, Dot and None.
Specifies what time format to use in this project. Applies mainly to exports and column values but not to the field edit dialog. Accepted values are 12-hour and 24-hour.
A regular expression that determines which files (in addition to the qtm files) that will be visible in the tree view.
This section is optional and is used when exporting to c3d file.
1 nested properties
Possible units are: mm, cm or m.
A sequence of names of fields that will be added to all types. QTM also adds a number of default fields automatically. For a list of these, see the Default Fields section.
This section contains information that the package management system uses. It is used mainly when installing packages and when creating new projects based on a package.
4 nested properties
The name of the package. Shown when creating a new project and used to keep the connection between a project and the package it was created from to, for instance, know if there is a new version of a package. This means that this value should not be changed unless strictly necessary because that will break the connection between existing projects and new versions of the package.
Two numbers separated by a period sign (e.g. 44.23), three numbers separated by period signs (e.g. 1.45.3214), or three numbers separated by a period sign and a build number separated by a plus sign (e.g. 1.3.0+188). The version of the package. Used to keep track of which version a project is based on. Visible in the about box when a project is open. Useful for debugging purposes and for knowing if the package can be upgraded.
Two or three digits separated by a period sign. The QTM version that is required for this package to work properly. Checked on install time. Must include major and minor version number and can optionally include build number too.
A sequence of names that this package has had earlier in development. This is used only when checking if a project should be upgraded and allows for packages to be renamed without losing the project upgrade path.