Find files, editable templates and browser test targets by what you need to make or test. Explore complete business kits for connected records, templates and expected results.
Page 98 of 221; 24 results per page.
Eight levels of nested groups, each holding a dataset whose values equal its own depth. Any tree walk that caps recursion depth or flattens names silently loses the lower levels, and the depth-valued arrays make that immediately visible.
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.
The CF NetCDF grid expressed with HDF5's own dimension-scale mechanism, so each axis of the 3-D array points at a real coordinate dataset through DIMENSION_LIST references. It lets a reader be tested on scale resolution instead of on filename conventions.
A three-group HDF5 file laid out the way a real bench run is (raw arrays, a processed derivative that names its source in a derived_from attribute, and a metadata group) with units on every dataset. It is the walk-the-tree fixture: a reader has to recurse rather than assume a flat namespace.
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.
Twelve datasets, one per numeric HDF5 type, each holding the extreme values of that type including the uint64 and int64 limits that do not survive a trip through a double. It is the fixture that exposes a reader which widens everything to float64 on the way in.
Fixed-width byte strings, variable-length UTF-8 strings and UTF-8 attribute text in one file, including Greek, CJK and combining diacritics. HDF5 hands fixed-width strings back as padded bytes and variable-length ones as decoded text, and conflating the two is where string handling usually breaks.
Four measured quantities where the uncertainty lives in dataset attributes rather than a parallel column, with the coverage factor spelled out so k=1 and k=2 values cannot be confused. It is the fixture for a pipeline that must propagate uncertainty it read from metadata.
A small HDF5 file with a compound 'employees' dataset and a numeric 'readings' grid: the hierarchical format used across science and ML. For testing h5py/HDF5 readers and conversion.
A CSV with no header row, for testing parsers that must infer or be told the column names.
Synthetic FHIR Claim resource for healthcare billing parser tests, not a real patient.
Fictional insurance eligibility check response for prior-auth workflow tests.
Synthetic lab result rows for clinical data warehouse import tests.
Sample HL7 v2 ORM order message with PID and OBR segments: fictional patient and order ids.
Synthetic patient demographics CSV for EHR import and de-identification pipeline tests.
Synthetic e-prescription JSON for pharmacy routing and validation tests.
SAMPLE procedure code list with fees for medical billing calculator tests.
A heap profile measuring bytes still live at the sample point, not bytes ever allocated, which is why its shape differs from the allocation profile of the same process. 620 MB retained across five sites, with an unbounded session cache at the top.
A Helm v2 Chart.yaml with two conditional subchart dependencies, semver range constraints, a kubeVersion constraint, maintainers and annotations. Every repository and URL is example.invalid, so nothing resolves anywhere real.
The defaults half of a Helm values pair: nested maps, an empty map and an empty list, a list of env entries, and quoted booleans that must survive as strings. Pairs with the production overrides fixture for deep-merge testing.
The overrides half of a Helm values pair, built to exercise all three merge behaviours at once: maps merge key by key, the env list replaces the defaults wholesale, and an explicit null deletes the inherited podAnnotations map.
The values.schema.json that validates the paired Helm values files: a 2020-12 JSON Schema with $defs, $ref, enums, quantity patterns, and additionalProperties: false on nested objects. Validates the defaults and rejects a values file with an unknown image key.
An HL7 v2.5 ADT^A01 patient-admission message: pipe/caret-delimited segments (MSH, EVN, PID, PV1, allergies, diagnosis). A fixture for testing healthcare integration engines and HL7 parsers. The patient is fictional.
Short synthetic HL7 v2 ADT-A03 message: fictional SAMPLE demographics for parser tests.
We use Google Analytics and show ads via Adsterra. Non-essential cookies and ad scripts run only after you allow the matching categories. See our cookie policy.
