For the complete documentation index, see /llms.txt. The full corpus is available at /llms-full.txt. Most pages have a raw markdown variant; append .md to the URL or send Accept: text/markdown.

Docs  |  FAQ

FAQ

Quick answers to common questions about mappings, graphing, events, experiments, and more.

Open in full page

A mapping is a feature designed to simplify the file upload process on our platform. Essentially, it's a predefined template that helps link specific data fields seamlessly.

To upload a file using a mapping, head to Import, choose the mapping that matches your file format, and proceed with the upload.

When you upload a file, Invert will automatically suggest a mapping if it recognizes the file structure. A suggestion banner will appear above the mapping selector — click Apply mapping to accept it or dismiss it to choose manually.

If you are unsure about the mapping format, select the mapping and click Download Template .csv to use a sample format. We offer generic mappings like Timeseries Data (absolute and relative time), Run Events, and Run Data (process metadata). If you require a custom mapping please contact us through Help & Support.

Open in full page

As your run list grows, filters make it fast to isolate exactly the runs you need.

Example run list

Click Add filter and choose the run property you would like to filter by. You can include one or more values on each filter, and combine multiple filters to narrow the view further.

Open in full page

Analyses are saved as Reports. A report can hold multiple charts and tables (called plot blocks), each with its own text annotations for context and conclusions. This makes it straightforward to build a structured, shareable document directly from your data.

From the Runs page:

  1. Use filtering and grouping to select the runs you want to analyze, then click Analyze.
  2. Configure your chart — select metrics, adjust axis settings, customize the layout.
  3. Click Save Report to save the chart as a plot block in a new or existing report.

From the Reports page:

  1. Create a new report or open an existing one.
  2. Click Add Plot Block, select your runs and chart settings, then click Save Report.

Open in full page

All chart settings are accessed via the Chart button in the chart header, which opens a settings panel.

Chart Types

Switch between Line, Bar, and Scatter using the Chart type selector at the top of the Chart settings panel.

Time-series Charts (Line)

Time normalization

All time-based charts are normalized to the Run Start time, which calculates the Elapsed Run Time (ERT). Use the Time Filters section in the Chart settings panel to change the normalization basis (e.g. to a specific event like Feed Start, or to a phase like Production Start).

Zoom

X-axis drag zoom: Click and drag within the graph to zoom into a specific time window. The current bounds appear in the top right corner. Click the ✕ to reset.

X and Y axis custom ranges: Open the Chart settings panel to set precise Min / Max / Interval values for both the X and Y axes. These compose with drag-zoom so both can be active simultaneously. Overridden values are shown highlighted; use the Reset button within each axis section to revert.

Downsampling and Interpolation

To maintain a responsive interface, raw data is downsampled for line charts. Data is interpolated between time points to enable formula calculations and grouped statistical comparisons across runs with different data frequencies. Higher-resolution raw data renders as you zoom in, and is also available via data export.

Chart Splits

Use the Split by control in the Chart settings panel to choose how runs and metrics are distributed across graphs:

  • All in one — all metrics and runs on a single graph; each metric has a distinct line style, each run a unique color.
  • Split metrics — one chart per metric; run colors are consistent across charts.
  • Split runs — one chart per run or run group; metric colors are consistent across charts.
  • Separate — each metric and run combination gets its own chart.

Chart Layout

Control the number of charts per row: Auto, Full width, 2 columns, or 3 columns.

Grouping

Use Group by in the Chart settings panel to categorize runs by a metadata attribute and access statistical comparison tools. Grouped line charts display the median (50th percentile) as a solid line with a shaded band from the 16th to 84th percentiles — a distribution-agnostic representation of central tendency and spread. For normally distributed data, this band corresponds to approximately ±1 standard deviation.

Scatter Charts

Switch to scatter via the Chart type selector in the Chart settings panel. The X-axis defaults to Run ID but can be changed to any categorical or aggregated metric. The Y-axis supports any numeric value including time-series aggregations (mean, min, max, std, first, last, count), single-point properties, and calculated metrics.

When the X variable is numeric, toggle between Continuous and Categorical X-axis mode in the Chart settings panel. Enable Show statistics to overlay mean, standard deviation, standard error, and 95% confidence intervals per X category.

Bar Charts

Bar charts display aggregated metric values as bars, with the X-axis driven by a run attribute (e.g. Run ID, Strain, Condition) and the Y-axis using the same aggregations as scatter. Use Color by in the Chart settings panel to add a second grouping dimension via bar color.

Open in full page

What are Experiments?

Experiments, previously "parent runs", are a grouping of runs, typically with overlapping operations timelines used to help manage organizational complexity.

For example - a set of 12 or 24 runs that were performed in the same operational window on a Sartorius Ambr could be batched into a single Experiment. The seed flask and seed train runs can also be included in this experiment if that organizational grouping is helpful.

Note: Run data can still be compared across experiments by simply selecting the runs of interest.

Editing via Uploads

The Run Data mapping allows you to edit the experiment for any run. This is recommended approach for bulk editing any run data, including Experiments.

  1. Creating the file to ingest:
  • Create a csv or excel sheet with headers "Experiment" and "Run"
  • Ensure the Run names match exactly with the runs that exist in your Invert workspace that you would like to edit, otherwise this process may result in creating new runs.
  • The Experiments do not need to exist prior to this upload, they will be created through this process. If your experiments already exist, please ensure you are using the exact name of the Experiment you intend to map the runs with.
  1. Uploading the file for ingestion
  • Navigate to the Import page
  • Select your file to import
  • Select the Run Data mapping
  • Click Start Import

Note: Some custom mappings may already incorporate experiments if the schema has been provided. If you are interested in updating an existing mapping, please reach out through Help & Support.

Editing via the Run Table

If you prefer seeing the edits in a more familiar spreadsheet format you can edit from the main run table.

  • While in the run table interface, select the runs you wish to edit
  • Ensure the Experiment column has been added to the table
  • Click Edit
  • Type in the Experiment Name.
    • If the Experiment does not already exist, it can be created through this link
  • Click Save

Editing via the Run Summary Page

Every Run can be edited individually through its summary page.

  • Click on the run name in the run table to navigate to the summary page
  • Click Edit
  • Select the Experiment name from the dropdown
    • If the Experiment does not already exist, it can be created through this link
  • Click Save

Open in full page

What is an event?

An event is a specific occurrence or milestone within your bioprocess. Users can annotate this data by creating event notes, which are distinct from timeseries data and metadata. Each event note includes details such as event type, timestamp, and optional information like event description, operator, and even image uploads. Event notes are bundled into a single event and displayed on the graph, aligned by its relative timestamp value.

How to create an event

Events are created and managed from the Events tab on the Run Summary page. Navigate to the run, open the Events tab, click Edit, then Add in the desired category. Enter the event time, type, and any optional notes or images, then save.

Image upload

You can attach an image to any event. Images appear in event tooltips on the line chart and can be viewed or downloaded from the Events tab on the Run Summary page.

How can I control which events are shown on the chart?

Event visibility is controlled from the Chart settings panel — click the Chart button in the chart header on the Analysis page. Use the Show events toggle to turn all event annotations on or off. When events are on, use the category buttons — Phases, Additions / Removals, and Observations — to show only the event types relevant to your current analysis.

Event categories and Event types

Phases

  • Growth (Start/End), Production (Start/End)

Critical Operations

  • Inoculation, Induction, Feed Start, Transfection

Additions / Removals

  • Sample, Drawdown, Foamout, Harvest, Reagent bolus

Observations

  • Observations
Open in full page

Run names tend to be long, uninformative, or overly detailed which can impact the effectiveness of your data presentation. By assigning friendly run names, you can streamline the appearance of charts and legends, enabling you to emphasize run-specific details and present your analysis with greater clarity.

To assign friendly run names using the "Group by" feature, follow these steps:

  1. Create a new property:

    Navigate to the Runs table or Library page to create a new property for your custom run names (e.g. 'Alias').

  2. Change Data Type to 'Text':

    Edit the property and set data type to 'Text'.

  3. Assign Friendly Run Names:

    Enter your desired run names into the custom property field via the Runs table.

  4. Apply 'Group By' in charts:

    On the Analysis page, select the newly created property from the 'Group By' dropdown in the Chart settings panel.

The custom text values will replace Run IDs in charts and chart legends, making it easier to identify and compare runs during analysis.

Open in full page

When runs are receiving data right now, Invert will label them with the "Live" indicator. This means that Invert has received data from the last five minutes.

You can use this to quickly find data from live runs and distinguish what's running right now from historical data.

This live indicator is separate from the run status field (Draft, In-Progress, Completed, etc.), which remains the same.

The live status will automatically appear in the run table:

Live status can be applied as a filter, to show only live runs, as shown below:

This status is visible in the analysis view as well:

Open in full page

To set up Single Sign-On (SSO) with Microsoft Azure Active Directory (Azure AD), please follow these steps:

Step 1: Register an Application in Azure AD

  1. Log in to your Azure portal.
  2. Go to Azure Active Directory → App registrations → New registration.
  3. Enter a name for the application (e.g., Invert SSO).
  4. Under Redirect URI, add the following value: https://auth.invertbio.com/login/callback
  5. Save the application.

Step 2: Collect and Share Information with Invert

Once the application is created, please provide the following details to your Invert representative so we can complete the setup on our side:

  • Application (Client) ID
  • Client Secret (you will need to generate one in the app’s Certificates & Secrets section)
  • Azure AD Domain Name (found in your Directory overview)
  • Tenant ID (optional but recommended for more reliable configuration)

Once we receive this information, we will finalize the SSO integration. After setup, your users will be able to log in to Invert using their Microsoft Azure AD credentials.