Unchained Labs instrument integration

Unchained Labs workflows span protein concentration, buffer exchange, stability and particle characterization. Lunatic, Big Tuna, Uncle, Aunty, Stunner and Hound produce different experimental evidence. Connect them through sample provenance and explicit analysis context so a scientist can follow both the preparation and the observations made about the material.

Choose your instrument software

Choose the source software and evidence.

These are connection routes to configure using the documented source output. Check the installed version, licensed options and export settings in the linked platform docs; the listing does not install an acquisition driver or a universal parser.

Identify the exported analysis, not just the instrument name.

Lunatic report layouts and Big Tuna data exports answer different questions. Uncle and Aunty experiments need the chosen analysis mode and experimental conditions. Stunner can combine concentration and scattering observations, while Hound evidence can involve images and spectra. Confirm the installed software’s output rather than assuming all reports from the same manufacturer share a schema.

Keep the complete export and any native experiment, image or spectrum evidence required for interpretation. Select the reported values that support the receiving workflow. A compact report can be a useful mapping input without representing every acquisition channel or every detail of the experiment.

Follow material changes and preserve distinct result types.

Buffer exchange or another preparation can change the material being characterized. Keep input and output sample identities and the preparation run connecting them. A later concentration or stability result should reference the material actually measured, rather than being attached indiscriminately to the original stock sample.

Concentration, scattering, transition temperatures and particle observations have different meanings. Retain the assay or method context, units and selected analysis parameters provided by the source. Do not combine them into one generic ‘quality’ value or treat similarly named temperature results from different methods as automatically equivalent.

Compare conditions with their supporting evidence.

For a formulation or stability comparison, define the sample set and conditions before collecting summaries. Keep storage or treatment context with the material records, and preserve the source experiment behind each observation. Identify missing results and excluded analyses so the comparison does not silently use a different population for each metric.

Use representative exports from every analysis mode in scope. Test re-exporting the same experiment and introducing a revised evaluation separately. If an export layout or analysis mode changes, require the mapping to recognize the change rather than accepting a plausible number from an unexpected column.

Example: compare material before and after buffer exchange

The preparation relationship explains why the subsequent measurements belong to different material states.

Input sample
Retain the original material identity and its concentration measurement.
Preparation
Link the Big Tuna run and available process evidence to the output sample.
Characterization
Attach the output sample’s concentration or stability analysis with its method and source revision.

Use these relationships as a mapping example for your own templates. The receiving fields and record grain remain configurable through normal Seal Scripts and APIs.

Configure the collection and mapping for your site.

For local exports, use a completed-file handoff on the instrument workstation or another approved site computer. Seal IoT collects the file and uploads it to the chosen Seal destination over outbound HTTPS. Keep source files until delivery and mapping have been verified.

A Seal Script can validate the expected layout, resolve source identities and write selected typed fields. Keep the original export as File content. Acquisition and vendor analysis remain in the source application; configure and verify any separately supported dispatch operation on its own terms.

Follow the on-site equipment setup instructions, then use the source-specific guide above to test the actual export and mapping. For a result exchange with an existing LIMS, also define that system’s supported receiving operation and sample identifiers.

Test the configured workflow with known evidence.

  1. Trace a prepared output sample back to its input and confirm measurements are attached to the correct material state.
  2. Compare selected concentration, stability or particle results with their source method and reported units.
  3. Test an excluded result and a changed analysis export without losing the original experiment evidence.

Keep the test outcome with the configuration and repeat the relevant checks when software, reports, analysis settings or destination fields change.

Discuss your Unchained Labs workflow with a representative export, the installed software version and the records you want to connect.