Skip to main content

Cancer Omics Drug Experiment Response Dataset

There is a recent explosion of deep learning algorithms that to tackle the computational problem of predicting drug treatment outcome from baseline molecular measurements. To support this,we have built a benchmark dataset that harmonizes diverse datasets to better assess algorithm performance.

This package collects diverse sets of paired molecular datasets with corresponding drug sensitivity data. All data here is reprocessed and standardized so it can be easily used as a benchmark dataset for the This repository leverages existing datasets to collect the data required for deep learning model development. Since each deep learning model requires distinct data capabilities, the goal of this repository is to collect and format all data into a schema that can be leveraged for existing models.

Coderdata Motivation

The goal of this repository is two-fold: First, it aims to collate and standardize the data for the broader community. This requires running a series of scripts to build and append to a standardized data model. Second, it has a series of scripts that pull from the data model to create model-specific data files that can be run by the data infrastructure.

Data access

For the access to the latest version of CoderData, please visit our documentation site which provides access to Figshare and instructions for using the Python package to download the data.

Data format

All coderdata files are in text format - either comma delimited or tab delimited (depending on data type). Each dataset can be evaluated individually according to the CoderData schema that is maintained in LinkML and can be udpated via a commit to the repository. For more details, please see the schema description.

Building a local version

The build process can be found in our coderbuild directory. Here you can follow the instructions to build your own local copy of the data on your machine.

Adding a new dataset

We have standardized the build (coderbuild) process so an additional dataset can be built locally or as part of the next version of coder. Here are the steps to follow:

  1. First visit the coderbuild directory and ensure you can build a local copy of CoderData.

  2. Checkout this repository and create a subdirectory of the coderbuild directory with your own build files.

  3. Develop your scripts to build the data files according to our LinkML Schema. This will require collecting the following metadata:

  • entrez gene identifiers (or you can use the genes.csv file
  • sample information such as species and model system type
  • drug name that can be searched on PubChem

You can validate each file by using the linkML validator together with our schema file.

You can use the following scripts as part of your build process:

  1. Wrap your scripts in standard shell scripts with the following names and arguments:
shell script arguments description
build_samples.sh [latest_samples] Latest version of samples generated by coderbuild
build_omics.sh [gene file] [samplefile] This includes the genes.csv that was generated in the original build as well as the sample file generated above.
build_drugs.sh [drugfile1,drugfile2,...] This includes a comma-delimited list of all drugs files generated from previous build
build_exp.sh [samplfile ] [drugfile] sample file and drug file generated by previous scripts
  1. Put the Docker container file inside the Docker directory with the name Dockerfile.[datasetname].

  2. Run build_all.py from the root directory, which should now add in your Dockerfile in the mix and call the scripts in your Docker container to build the files.

Metadata

Release files for coderdata 2.4.0

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for coderdata 2.4.0
File Size Uploaded Provenance Actions
coderdata-2.4.0.tar.gz 25.5 kB Without provenance Details for coderdata-2.4.0.tar.gz

Built distribution (wheel)

Table of built distributions (wheels) for coderdata 2.4.0
File Interpreter ABI Platform Actions
coderdata-2.4.0-py3-none-any.whl Python 3 none any Details for coderdata-2.4.0-py3-none-any.whl

Total release size: 54.1 kB

Release files / coderdata-2.4.0.tar.gz

Download URL coderdata-2.4.0.tar.gz
Size 25.5 kB
Tags Source
SHA-256 checksum
How to use checksums
de99234858ad8251df693c990b2858393f3488d5f57bb632a51ffcc215b2550c
BLAKE2b-256 checksum
How to use checksums
80f387b953ab85e51f7dc20c5c2555689fcc639370f33af36bd28e5899ce31ad
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via Hatch/1.18.1 {"ci":null,"cpu":"arm64","distro":{"name":"macOS","version":"27.2"},"implementation":{"name":"CPython","version":"3.14.8"},"installer":{"name":"hatch","version":"1.18.1"},"openssl_version":"OpenSSL 4.0.3 29 Sep 2026","python":"3.14.8","system":{"name":"Darwin","release":"27.2.0"}} HTTPX2/2.13.1

Release files / coderdata-2.4.0-py3-none-any.whl

Download URL coderdata-2.4.0-py3-none-any.whl
Size 28.6 kB
Tags Python 3
SHA-256 checksum
How to use checksums
730a82982408d89659bef9b566f671ab7c4294b7689d45b609780a8785d960e9
BLAKE2b-256 checksum
How to use checksums
a6c2b8b143bd4fdf938e2584b5215536f8760e372d5bb8e1e68d52d32d2a0409
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via Hatch/1.18.1 {"ci":null,"cpu":"arm64","distro":{"name":"macOS","version":"27.2"},"implementation":{"name":"CPython","version":"3.14.8"},"installer":{"name":"hatch","version":"1.18.1"},"openssl_version":"OpenSSL 4.0.3 29 Sep 2026","python":"3.14.8","system":{"name":"Darwin","release":"27.2.0"}} HTTPX2/2.13.1

Security for coderdata 2.4.0

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

No provenance found

None of the files in this release were uploaded with provenance metadata.

A note on package security

PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.

To learn more about protecting yourself from malicious actors, visit our package security documentation.

Release history Release notifications | RSS feed

This release

2.4.0 This release

2 release files No provenance

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page