Evaluator API Schema#
Evaluator request#
Key |
Value type - Required/Optional |
Description: Value options |
Example |
|---|---|---|---|
|
|
Type of readout that is requested from the Predictor: [“point”,”track”, “interaction_matrix”]. |
“readout”: “track” |
|
|
Each object must contain the following keys: |
“prediction_tasks”: [ |
|
|
Unique identifier for each prediction task object. |
“name”: “model_prediction” |
|
|
Prediction type you want predicted: [” |
“type”: “expression” |
|
|
What cell type you want predicted for |
“cell_type”: “K562” |
|
|
What species you want predicted for |
“species”: “homo_sapiens” |
|
|
How would you like the predictions scaled upon return (if at all): [“linear”, “log”]. |
“scale” : “linear” |
|
|
Upstream flanking sequences to add to each sequence in |
“upstream_seq”: “AATTA” |
|
|
Downstream flanking sequences to add to each sequence in |
“downstream_seq”: “CCCAAAA” |
|
|
A collection of key-value pairs (strings). Keys are unique sequence ID keys – any characters |
“sequences”: { |
|
|
A collection of key-value pairs, where the keys should be identical to sequence ID keys and values are arrays with the start and end region you want predictions for, within the provided sequence context. Start and end are 0 indexed and inclusive, respectively (e.g. [0,1] is the first two bases). |
“prediction_ranges”: { |
Notes#
keys in
sequencesmust be unique or will be overwritten during the reading inall indexing is 0 based
to minimize any bias from the predictors we suggested randomizing your sequences so that there is no dependency on the order
Evaluator Output File Specifications#
All evaluation metrics are saved into a single tab-separated file: evaluation_summary_[evaluator_name].csv
The evaluator_name is constructed automatically in config.py by appending the container’s build timestamp (from Apptainer’s /.singularity.d/labels.json) to the evaluator’s base name. The format is {EvaluatorName}_{YYYYMMDD-HHMMSS}_{TZ}. In development mode (outside a container), _dev is appended instead. This follows the same convention as predictor_name (see Predictor API Schema).
The file uses append mode, so multiple evaluation runs against different Predictors accumulate in the same file. The description column distinguishes between different metric types (e.g. per-task correlation vs. cell-type specificity).
Column |
Data Type |
Description |
Example |
|---|---|---|---|
|
|
The unique, automatically versioned identifier for the evaluator module. |
|
|
|
Human-readable description of what is being measured. For per-task correlations, this identifies the task (e.g. |
|
|
|
The |
|
|
|
UTC timestamp in |
|
|
|
The evaluation metric used. |
|
|
|
The computed metric value. Set to |
|
|
|
Serialized prediction task metadata (excluding the |
|
The codebase for the Agarwal MPRA Joint Library Evaluator can be found on GitHub and serves as a reference for implementing custom metric calculations.