Skip to main content
Raw data records let you archive the original files that came off your cycler — untouched — inside Ionworks Studio, then link them to the processed cell measurements they produced. This gives every measurement a clear provenance trail back to its source. Raw data records live under a project, not under a specific cell instance. One raw file can feed many measurements, and one measurement can be assembled from many raw files.

When to use raw data

Use raw data records when you want to:
  • Keep the untransformed cycler export (e.g. .mpr, .res, .nda, .txt, or a Neware / Maccor / Biologic file) alongside the processed time series it was converted into.
  • Trace a measurement back to the exact file — and file version — it came from.
  • Store one source file that was split into several measurements (for example, a single test file containing formation + RPT + cycling that you uploaded as three separate measurements).
  • Combine several source files into one measurement (for example, a run that was paused and resumed, producing two export files).
If you only care about the processed data, you do not need to create raw data records — regular measurement upload is enough. Raw data is additive provenance, not a replacement for preparing data and uploading data.
Raw data records store the file as-is. They are not processed into measurements automatically — you still convert your file with ionworksdata and upload the resulting measurement separately, then attach the raw file for provenance.

Upload a raw file

Upload any file from a local path or an open binary handle. The client derives the filename from the file path or handle:
Arguments: The returned RawData object has id, project_id, name, filename, content_type, size_bytes, metadata, and timestamps.

List, get, and download

list returns a paginated response with items, count, and total. The download_url is signed and expires after a few minutes — request a fresh one each time you need to download the file.

Update and delete

name and metadata are patchable. The underlying file is immutable — to replace the bytes, delete the record and upload again.
Deleting a raw data record removes the stored file and clears any links to measurements. The linked measurements themselves are not deleted. The provenance link is many-to-many and lives on the measurement side of the SDK. Attaching is bulk and idempotent — re-attaching an already-linked file is a no-op.
To go the other direction — find every measurement that was produced from a given raw file — use list_measurements on the raw data client:
Deleting a measurement removes only its provenance links, never the raw data record or its file. Raw files are independent, project-owned assets.

End-to-end example

Upload the processed measurement, then archive the original file and link them:

Next steps

Preparing data

Convert cycler files into the Ionworks format before uploading a measurement.

Uploading data

Create cell specs, instances, and measurements via the Python API.

Measurements

Time series, properties, and file measurement types.

Projects

Group raw data, studies, and simulations by research initiative.