Skip to main content

Overview

Baseline models generate synthetic gene expression data from metadata alone. You describe the biological conditions—tissue type, disease state, perturbations, cell type, etc.—and the model generates realistic expression profiles matching those conditions. This is the most common use case: generating synthetic data for conditions where real data may be scarce or unavailable.

Available Models

  • gem-1-bulk: Bulk RNA-seq baseline model
  • gem-1-sc: Single-cell RNA-seq baseline model

Creating a Query

The structure of the query required by the API is specific to each model. Use get_example_query() to get a correctly structured example for your chosen model.
The query consists of:
  1. sampling_strategy: The prediction mode that controls how expression data is generated:
    • “sample generation”: Generates realistic-looking synthetic data with measurement error (bulk only)
    • “mean estimation”: Provides stable mean estimates of expression levels (bulk and single-cell)
  2. inputs: A list of biological conditions to generate data for
Each input contains metadata (describing the biological sample) and num_samples (how many samples to generate).

Making a Prediction

Once your query is ready, send it to the API to generate gene expression data:
The result is a list containing two data frames: metadata and expression.

Single-Cell Example

Single-cell models only support "mean estimation" mode.

Query Parameters

In addition to metadata, queries support several optional parameters that control the generation process.

sampling_strategy (character, required)

Controls the type of prediction the model generates. This parameter is required in all queries. Available modes:
  • “sample generation”: The model generates realistic-looking synthetic data that captures measurement error. This mode is useful when you want data that mimics real experimental measurements. (Bulk only)
  • “mean estimation”: The model creates a distribution capturing biological heterogeneity consistent with the supplied metadata, then returns the mean of that distribution. This mode is useful when you want a stable estimate of expected expression levels. (Bulk and single-cell)

total_count (integer, optional)

Library size used when converting predicted log CPM back to raw counts. Higher values scale counts up proportionally.
  • Default: 10,000,000 for bulk; 10,000 for single-cell

deterministic_latents (logical, optional)

If TRUE, the model uses the mean of each latent distribution (p(z|metadata)) instead of sampling. This removes randomness from latent sampling and produces deterministic outputs for the same inputs.
  • Default: FALSE (sampling is enabled)

seed (integer, optional)

Random seed for reproducibility when using stochastic sampling.

Combining Parameters

You can combine multiple parameters in a single query:

Valid Metadata Keys

The input metadata is a list of lists. Here is the full list of valid metadata keys:

Biological

  • age_years
  • cell_line_ontology_id
  • cell_type_ontology_id
  • developmental_stage
  • disease_ontology_id
  • ethnicity
  • genotype
  • race
  • sample_type (“cell line”, “organoid”, “other”, “primary cells”, “primary tissue”, “xenograft”)
  • sex (“male”, “female”)
  • tissue_ontology_id

Perturbational

  • perturbation_dose (number and unit separated by a space, e.g., “10 um”)
  • perturbation_ontology_id
  • perturbation_time (number and unit separated by a space, e.g., “24 hours”)
  • perturbation_type (“coculture”, “compound”, “control”, “crispr”, “genetic”, “infection”, “other”, “overexpression”, “peptide or biologic”, “shrna”, “sirna”)

Technical

Valid Metadata Values

The following are the valid values or expected formats for selected metadata keys: We highly recommend using the EMBL-EBI Ontology Lookup Service to find valid IDs for your metadata. Models have a limited acceptable range of metadata input values. If you provide a value that is not in the acceptable range, the API will return an error.

Modifying Query Inputs

You can customize the query inputs to fit your specific research needs:

Working with Results

You may want to process the data in chunks or save it for later use: