This page describes the binary format for an InterOp file. The formats are broken down into two parts: (1) the header, which is written first, a single time for the file and (2) n-Records, which are written next, many times composing the rest of the file.
An InterOp file may have several versions of the format. This is important because certain values may not be populated in the model. For example, for the CorrectedInt InterOp file, the signal to noise attribute is only populated for version 2 of the format. This parser does not support all versions of the InterOp files, namely versions that were supported by the GA platform.
In 2017, we introduced the concept of "by-cycle" InterOp files, where every InterOp has a separate file for every cycle of data for which the file is produced. Each file has its own header and set of n-Records, but is otherwise similar to before.
The documentation for the model notes when an attribute is only populated by a specific version of the format.
- Corrected Intensity v2
- Corrected Intensity v3
- Corrected Intensity v4
- Error v3
- Error v4
- Error v5
- Error v6
- Extended Tile Version 1
- Extended Tile Version 2
- Extended Tile Version 3
- Extraction Version 2
- Extraction Version 3
- Image Version 1
- Image Version 2
- Image Version 3
- Index Version 1
- Index Version 2
- Phasing Version 1
- Phasing Version 2
- Q-Metrics Version 4
- Q-Metrics Version 5
- Q-Metrics Version 6
- Q-Metrics Version 7
- Tile Version 2
- Tile Version 3
- Collapsed Q-Metrics Version 2 (BaseSpace)
- Collapsed Q-Metrics Version 3 (BaseSpace)
- Collapsed Q-Metrics Version 4 (BaseSpace)
- Collapsed Q-Metrics Version 5 (BaseSpace)
- Collapsed Q-Metrics Version 6 (BaseSpace)
- Summary Run Version 1
The following are binary formats used only for testing purposes and are not officially supported: