Closed mostafa-ti closed 1 year ago
Make sure you have enough memory on your server (e.g. upward of 60 gigabytes). Colab will not be enough.
Make sure you have enough memory on your server (e.g. upward of 60 gigabytes). Colab will not be enough.
Thanks for the reply. But this is from the official tutorial, which ran on the free version of colab. I just re-run it, but on the pro version of colab so probably the issue shouldn't be related to the amount of memory.
Sigkill 9 (the issue you're having) usually means a memory problem. From my experience, kb count with a cDNA+intron index can cause out of memory problems frequently because the index is so large. Is the behavior reproducible (e.g. does it always run on colab free-tier but crash on colab pro?)?
This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 5 days
Describe the issue I ran
kb count
command from this tutorial: https://www.kallistobus.tools/tutorials/kb_velocity/python/kb_velocity/#pre-processingWhat is the exact command that was run? %%time !kb count --h5ad -i index.idx -g t2g.txt -x 10xv2 -o SRR6470906 \ -c1 spliced_t2c.txt -c2 unspliced_t2c.txt --workflow lamanno --filter bustools -t 2 \ SRR6470906_S1_L001_R1_001.fastq.gz \ SRR6470906_S1_L001_R2_001.fastq.gz \ SRR6470906_S1_L002_R1_001.fastq.gz \ SRR6470906_S1_L002_R2_001.fastq.gz
kb count ... I run the command on my google colab pro account
Command output (with
--verbose
flag)