Skip to content
Novus Examples
npy656 B

NumPy .npy — complex128 Spectrum (.npy)

The real FFT of a 64-sample sine stored as complex128, where each element is an interleaved pair of doubles rather than two separate planes. Readers without a complex type usually flatten it, which doubles the reported length and shifts the peak bin.

Preview — schema + first 9 rowsnpy
FieldValue
dtypecomplex128
descr in header<c16
shape(33,)
fortran_orderFalse
elements33
Bytes per element16 (two float64s, real then imaginary)
Layoutinterleaved, NOT two separate planes
Peak bin4
|peak|31.531319
A reader that treats complex128 as pairs of unrelated doubles doubles the element count.

Specifications

Dtype
complex128
Elements
33
Bytes Per Element
16
Layout
interleaved real, imaginary
Source
rfft of a 64-sample sine
Descr
<c16

Testing contract

Expected to pass
Scenario
Load the array and locate the bin with the largest magnitude, checking the reported element count.
Expected result
The array holds 33 complex elements of 16 bytes each and the magnitude peaks at bin 4; a flattening reader reports 66 real elements instead.

What is a .npy file?

NPY is NumPy's native binary format for a single array. A short header records the dtype, shape, and memory order, followed by the raw array bytes, so an array round-trips exactly without any text parsing. It is the standard way to persist embeddings, tensors, and numeric matrices in the Python data stack.

How to use this file

Use an example .npy to test array loaders (numpy.load), tensor and embedding pipelines, and converters between .npy, JSON, and columnar formats like Parquet.

How to use this file for testing

“NumPy .npy — complex128 Spectrum (.npy)” 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: NPY · 656 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.

Generated by generation/scientific.py. Free for any use, no attribution required — license.