Hi,
I have a weird issue with xTea, which is it gets stuck and seems to basically stop moving on at one point.
The logs just don't print anything anymore and htop shows that it's barely even running anymore, but still the process stays there for as long as i let it run, without ever properly crashing:
It seems somewhat similar to #106 but I'm using the classic short-reads version of xTea instead.
And, as shown in htop output, it usually stops at the transduction step (even though I believe there were times where it stopped at other steps).
More precisely, seemingly after the bwa index ...all_with_polymerphic_flanks.fa command, as reported by the logs:
HG00268.L1.err.txt and HG00268.L1.out.txt.
The main issue is that this problem, while happening very often, doesn't even seem to be 100% reproductible, as running many times the same BAM files led to some of them working at times ; and on the flip side, BAM files that seemed to work sometimes could not work again at later times (HG00268 is one of those examples).
Steps to maybe reproduce:
- I installed
xTea=0.1.9 through conda in its own environment in the same way as the README
- and I'm running it on BAM files from the 1KGP "1000 Genomes 30x on GRCh38" collection downloaded from e.g.
ftp://ftp.sra.ebi.ac.uk/vol1/run/ERR324/ERR3240225/HG00268.final.cram
- running xTea's main script in the following way (after conda env activation):
XTEA_DIR="$HOME/.conda/pkgs/xtea-0.1.9-hdfd78af_0/lib"
PROJECT_FOLDER="$HOME/projects/training"
REFERENCE="$PROJECT_FOLDER/data/reference/grch38/GRCh38_full_analysis_set_plus_decoy_hla.fa"
GENE_ANNOTATIONS="$PROJECT_FOLDER/supporting/gencode.v33.chr_patch_hapl_scaff.annotation.gff3"
TE_LIB="$PROJECT_FOLDER/supporting/te_lib/"
SAMPLE_IDS="$PROJECT_FOLDER/supporting/sample_ids.txt"
CRAM_PATHS="$PROJECT_FOLDER/supporting/cram_paths.txt"
WORKING_DIR="$PROJECT_FOLDER/xtea_wd/"
OUTPUT_SCRIPT="submit_jobs.sh"
~/.conda/envs/xtea/bin/xtea \
--xtea "$XTEA_DIR" \
-r "$REFERENCE" \
-g "$GENE_ANNOTATIONS" \
-l "$TE_LIB" \
-i "$SAMPLE_IDS" \
-b "$CRAM_PATHS" -x null \
-p "$WORKING_DIR" -o "$OUTPUT_SCRIPT" \
-f 5907 -y 15 -n 16 -m 64 \
> "logs/xtea/prep.out" \
2> "logs/xtea/prep.err"
- and then running them individually in each subfolder with a simple
sh, e.g. sh xtea.wd/HG00268/L1/run_xTEA_pipeline.sh > logs/xtea/HG00268.L1.out 2> logs/xtea/HG00268.L1.err
Hi,
I have a weird issue with xTea, which is it gets stuck and seems to basically stop moving on at one point.
The logs just don't print anything anymore and
htopshows that it's barely even running anymore, but still the process stays there for as long as i let it run, without ever properly crashing:It seems somewhat similar to #106 but I'm using the classic short-reads version of xTea instead.
And, as shown in
htopoutput, it usually stops at the transduction step (even though I believe there were times where it stopped at other steps).More precisely, seemingly after the
bwa index ...all_with_polymerphic_flanks.facommand, as reported by the logs:HG00268.L1.err.txt and HG00268.L1.out.txt.
The main issue is that this problem, while happening very often, doesn't even seem to be 100% reproductible, as running many times the same BAM files led to some of them working at times ; and on the flip side, BAM files that seemed to work sometimes could not work again at later times (HG00268 is one of those examples).
Steps to maybe reproduce:
xTea=0.1.9through conda in its own environment in the same way as the READMEftp://ftp.sra.ebi.ac.uk/vol1/run/ERR324/ERR3240225/HG00268.final.cramsh, e.g.sh xtea.wd/HG00268/L1/run_xTEA_pipeline.sh > logs/xtea/HG00268.L1.out 2> logs/xtea/HG00268.L1.err