DICOM-Shaped Part 10 File — Implicit VR, Synthetic Phantom (.bin)
The same synthetic phantom written with the implicit-VR transfer syntax, where element types never appear on the wire and a reader must consult a data dictionary to know that Rows is a 16-bit integer. The file meta group stays explicit VR, which is the mixed-mode detail parsers most often miss. Every identifier is invented: the patient name is SYNTHETIC^PHANTOM, the instance UIDs sit under the unregistered 2.25 UUID arc, and the pixels are a generated pattern. There is no protected health information here and nothing in the file refers to a real person, device or study.
| Element | Explicit VR file | This file |
|---|---|---|
| (0008,0060) Modality | tag + 'CS' + 2-byte length + value | tag + 4-byte length + value |
| (0028,0010) Rows | tag + 'US' + 2-byte length + value | tag + 4-byte length + value |
| (7FE0,0010) PixelData | tag + 'OW' + 2 reserved + 4-byte length | tag + 4-byte length |
| File meta group | explicit VR | explicit VR — always, regardless of the dataset |
Specifications
- Transfer Syntax
- 1.2.840.10008.1.2
- Transfer Syntax Name
- Implicit VR Little Endian
- Dataset Element Layout
- tag + 4-byte length, no VR on the wire
- Meta Group Layout
- explicit VR, as the standard requires
- Requires Data Dictionary
- true
- Rows
- 32
- Columns
- 32
- Same Image As
- the explicit-VR file
- Contains PHI
- false
Testing contract
Expected to pass- Scenario
- Read the transfer syntax from the explicit-VR meta group, then switch to implicit-VR parsing for the dataset.
- Expected result
- The meta group parses as explicit VR and reports 1.2.840.10008.1.2, after which the dataset decodes with 4-byte lengths and yields the same pixel array as the explicit-VR file.
What is a .bin file?
A .bin file is a generic binary blob with no specific format — raw bytes whose meaning depends entirely on the producing application (firmware images, memory dumps, serialized payloads). The extension signals only 'not text.'
How to use this file
Use an example .bin file to test binary/hex viewers, file-type sniffing, octet-stream handling, and download pipelines that must not corrupt arbitrary bytes.
How to use this file for testing
“DICOM-Shaped Part 10 File — Implicit VR, Synthetic Phantom (.bin)” is a deterministic Novus Examples fixture for Scientific data, Serialization testing. Citation catalogs (BibTeX, RIS), chemistry structures (MDL Molfile, PDB), and gridded binary data (NetCDF, FITS) — for testing reference managers, molecule viewers, and scientific-data loaders.
Documented properties for this file: 32 rows · 32 columns. Compare results against paired or grouped companions on this page when present (clean↔damaged, searchable↔scanned, or format twins) so scores stay reproducible across runs.
Download the file once, keep the path stable in CI or local scripts, and treat the spec table as the contract: dimensions, seeds, field lists, and roles are intentional. Corrupt or invalid samples are labelled as such — expect parsers to fail loudly rather than silently accept them.
Scientific fixtures are small, valid, and fully synthetic — no real organism, patient, sample, or observation. Point your parser or loader at the file and check it reads the documented records, variables, or headers; binary formats ship a readable twin or metadata listing for comparison.
Related files
- fitsFITS BINTABLE — Typed Columns with TUNIT (.fits)A FITS binary table with four typed columns, big-endian numerics packed with no inter-field padding and TUNIT declaring milli-jansky on the two flux columns. It is the fixture for a table reader that has to build a row struct from TFORM codes rather than guess widths.
- fitsFITS BLANK — Undefined Integer Pixels (.fits)Integer FITS images mark undefined pixels with the BLANK keyword, and BLANK is compared against the stored value before BZERO and BSCALE are applied. Scale first and the four undefined pixels turn into a perfectly plausible zero, which is the ordering bug this file exists to expose.
- fitsFITS Header-Only — Valid File With No Pixels (.fits)A completely valid FITS file consisting of one 2880-byte header block and no data unit, which the standard permits whenever NAXIS is 0. It separates readers that model the data array as optional from readers that treat 'no pixels' as corruption.
- fitsFITS Image — BITPIX 16 with BZERO Unsigned Trick (.fits)FITS has no unsigned 16-bit type, so unsigned data is stored signed with BZERO = 32768 and recovered as BZERO + BSCALE * stored. Every stored value in this image is negative, so a reader that ignores the scaling returns an entirely negative frame while parsing the file perfectly.
- fitsFITS Image — BITPIX 8 Unsigned Bytes (.fits)The baseline rung of the BITPIX ladder: a 24x16 synthetic star field stored as unsigned bytes, the one integer width FITS holds without a BZERO shift. Every image in this family carries the same scene so a decoder can be scored across data types.
- fitsFITS Image — float32 with NaN and Inf Pixels (.fits)Single-precision FITS pixels including two NaNs, which is the only way the standard marks undefined data for floating BITPIX, plus one +Inf. Statistics computed without NaN-aware reductions come back as NaN for the entire frame.
Generated by generation/scientific.py. Free for any use, no attribution required — license.