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 132 of 221; 24 results per page.
Short deterministic loop waveform 039 in the music-loops-stems set, tuned for repeatable trimming, gain, loop, and export checks. Stable P8 artifact p8-audio-214.
Short deterministic loop waveform 040 in the music-loops-stems set, tuned for repeatable trimming, gain, loop, and export checks. Stable P8 artifact p8-audio-215.
A mutual non-disclosure agreement as a formatted PDF with numbered clauses and a signature block: a realistic legal-document fixture for testing PDF text extraction, clause parsing, and document classification.
A fictional mutual NDA as DOCX: template twin of the PDF. Not legal advice; SAMPLE content for document tooling.
PDF twin of the SAMPLE mutual NDA template, for PDF text extraction and template pipelines.
A MySQL-flavour SQL dump with backtick-quoted identifiers and engine options, for testing SQL importers.
A token-classification dataset in JSON Lines: 16 tokenized sentences with aligned BIO tags for person, organisation, and location entities. All names, companies, and places are fictional. A fixture for NER model training and sequence-labelling tooling.
Six distinct NaN bit patterns (quiet, signalling, signed and payload-carrying) stored as float64. They are all NaN and none equals another, so any code that deduplicates, sorts or hashes them by value is doing something undefined and this array proves it.
The six NaN bit patterns broken into sign bit, quiet bit and payload so the difference between a quiet and a signalling NaN is a column rather than folklore. It is the reference for testing whether a serializer preserves NaN payloads or normalises them all to one canonical pattern.
A counterpart to the rest of the catalog's forms: it omits novalidate, so the browser's own constraint UI blocks submission and shows the bubble. Use it to tell native enforcement apart from script-driven validation in the same harness.
Fillable SAMPLE mutual NDA shell (not legal advice) for legal-form tooling tests.
Parties, term, and signature fields for testing legal-form parsers. Sample contract text, not legal advice.
Precomputed DCG/nDCG values for ranking metric unit tests.
A newline-delimited JSON (NDJSON) stream of event records, for testing streaming JSON parsers.
Fieldsets nested three levels deep, each carrying a legend, so a grouping algorithm has to compose several group names rather than take the nearest one. Includes a radio group nested inside a titled section.
Intentionally corrupt. A second form element opens inside the first, which HTML forbids. Browsers drop the inner tag and attach its controls to the outer form, while many static parsers report two forms - so the same file yields a different field list depending on who reads it.
One submission in both shapes: the flat name and value pairs a browser sends, and the nested object a framework builds from them. The expected output for the bracket-notation form shipped alongside it.
Control names in bracket notation - customer[name], customer[address][city], items[0][sku] - that many server frameworks explode into nested objects. The file is the reference case for a parser that has to rebuild the graph from flat name and value pairs.
One variable that hides absent data three different ways at once: two _FillValue cells, one legacy missing_value cell and one raw NaN, with valid_min and valid_max also declared. Averaging the raw array without honouring all three gives roughly -60 K instead of a real mean.
The same 4x5x6 temperature grid written in the 64-bit offset variant of NetCDF-3, whose only visible difference from the classic file is the fourth magic byte and the width of the header offsets. Use it to check that format sniffing looks at the version byte instead of stopping at the 'CDF' signature.
A NetCDF-3 classic file holding a 4x5x6 air-temperature field with full CF-1.8 coordinate metadata: standard names, axis attributes, units on every variable, and a declared _FillValue. Use it to check that a reader attaches units and coordinates to the array rather than returning bare numbers.
A NetCDF-3 (classic) file holding a small CF-convention gridded temperature field over latitude, longitude, and time, with named dimensions and units, for testing NetCDF readers like netCDF4 and xarray.
Four physical quantities on one shared (time, station) grid, each with its own CF units string including the dimensionless '1' and the UDUNITS 'm s-1' spelling. It is the fixture for a unit-aware layer that has to keep four different unit systems straight in a single file.
The same temperature field stored as int16 and recovered through the CF packing attributes scale_factor and add_offset. This is the failure that parses cleanly and is silently wrong: a reader that ignores the attributes returns values around -2000 instead of 260-292 K.
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.
