schug 1.14.0

Keep track of genes, transcripts and exons from different sources

Schug

Schug :stew: is a service that gather data about genes, transcripts and exons from multiple sources and merge the information. Clinical Genomics Stockholm is currently maintaining an instance of Schug which can be used for downloading data. Here is the REST API with relevant endpoints.

Test the app using Docker

You can test Schug on your local computer using Docker. Make sure you have Docker installed and type the following commands in a terminal window:

git clone https://github.com/Clinical-Genomics/schug
cd schug
docker compose up

Then the app endpoints should be listed available at the following address http://localhost:8000/docs

The command to stop the demo is docker compose down.

Installation (development)

Make sure poetry is installed

git clone https://github.com/Clinical-Genomics/schug
cd schug
poetry install
schug serve --reload

Go to http://localhost:8000/docs and check out the API.

Ready-to-use endpoints

Once having set up an instance of Schug, you can use the following endpoints:

• /genes/ensembl_genes/

  Downloads genes from Ensembl in text format. Specify a genome build by using the parameters 37 or 38.

  Usage: curl -X 'GET' 'http://0.0.0.0:8000/genes/ensembl_genes/?build=38' > ensembl_genes_38.txt

• /transcripts/ensembl_transcripts/

  Downloads gene transcripts from Ensembl in text format. Specify a genome build by using the parameters 37 or 38.

  Usage: curl -X 'GET' 'http://0.0.0.0:8000/transcripts/ensembl_transcripts/?build=38' > ensembl_transcripts_38.txt

• /exons/ensembl_exons/

  Downloads gene exons from Ensembl in text format. Specify a genome build by using the parameters 37 or 38.

  Usage: curl -X 'GET' 'http://0.0.0.0:8000/exons/ensembl_exons/?build=38' > ensembl_exons_38.txt

Issues While Downloading Genes, Transcripts, or Exons

You might encounter errors while downloading genes, transcripts, or exons, such as the following error:

httpx.RemoteProtocolError: peer closed connection without sending complete message body (incomplete chunked read)

This error often occurs when the external service prematurely closes the connection during data streaming. To address this issue, you can try increasing the max_tries parameter in your request, which otherwise defaults to 5. Increasing the number of retries can help handle intermittent network issues or temporary interruptions from the service.

Here’s an example of how to modify the request:

curl -X 'GET' 'http://0.0.0.0:8000/exons/ensembl_exons/?build=37&max_retries=10' > ensembl_exons_37.txt`

What is left to do?

The basic structure is outlined and implemented, however there are many details left to implement before this can be used. Some of the basic endpoints are in place but these need to be extended according to the needs of the users. Also the gene information needs to be completed, this will be done in a similar fashion as in Scout.