Raw float64 Block — Big-Endian, No Header (.bin)
The same sixteen doubles written in network byte order, so every eight-byte group is the mirror of the little-endian twin. Decoding it with the wrong assumption produces small plausible-looking numbers rather than an error, which is why this pair exists.
| Offset | Bytes (hex) | Decodes to |
|---|---|---|
| 0 | 00 00 00 00 00 00 00 00 | 0.0 |
| 8 | 80 00 00 00 00 00 00 00 | -0.0 |
| 16 | 3f f0 00 00 00 00 00 00 | 1.0 |
| 32 | 40 09 21 fb 54 44 2d 18 | 3.141592653589793 |
| 40 | 3f b9 99 99 99 99 99 9a | 0.1 |
Specifications
- Values
- 16
- Bytes
- 128
- Byte Order
- big-endian (network order)
- Header
- none
- Pi Bytes
- 40 09 21 fb 54 44 2d 18
- Identical Values To
- the little-endian twin
Testing contract
Expected to pass- Scenario
- Read the file as big-endian doubles, then deliberately read it as little-endian and compare.
- Expected result
- The big-endian read reproduces the twin's values exactly, while the little-endian read turns pi at offset 32 into 3.207e-192 and raises no error anywhere.
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
“Raw float64 Block — Big-Endian, No Header (.bin)” is a deterministic Novus Examples fixture for Scientific data, Error handling, 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: BIN · 128 bytes. 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
- binDICOM-Shaped Stream — No Preamble, No DICM Magic (.bin)The identical element stream with the 128-byte preamble and the DICM magic stripped, which is how DICOM often arrives out of a network transfer or a database blob column. It is not a conformant Part 10 file and its content is entirely recoverable, so a reader should fall back rather than reject.
- 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 — 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.
- h5HDF5 Degenerate Shapes — Scalar, Zero-Length and Null (.h5)Five degenerate but entirely legal datasets — a rank-0 scalar, a zero-length vector, a (0, 5) array, a single-element vector and a NULL dataspace — plus an empty group. None of them is corrupt, and a reader that reports them as errors is the thing being tested.
- h5HDF5 Hard, Soft and Dangling Links (.h5)One array reachable under four names: itself, a hard link sharing its object address, a soft link resolved at access time, and a soft link pointing nowhere. A walker that counts names instead of object addresses reports four arrays and then crashes on the dangling one.
Generated by generation/scientific.py. Free for any use, no attribution required — license.