-
Notifications
You must be signed in to change notification settings - Fork 35
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Ask the use of some of the problems encountered #29
Comments
Hi there, yes something appears to be wrong. In particular, since it looks like read backed haplotypes are being generated (which means it has recorded the presence of those reads), but the counts are listed as 0 in the haplotypes file... Can you please post the full output log as a result of you running the command above? |
Thank you for your response. My bam file are processed by Tophat2,and I do not know if this has any effect on the steps behind. Then I have attached the full output log: log.txt I do not know how to do this in such cases, please forgive my ignorance. thanks, |
Thank you for posting the logs. It appears that everything except the haplotypic_counts file was generated successfully, so there may be some sort of bug with phASER. Would it be possible for you to make available to me at least the VCF and BAM for one chromosome so that I can try to reproduce the bug on my end? |
There's my file here (Include only one chromsome 18):vcf and bam thanks, |
Hi there, unfortunately the link above does not seem to work. |
sorry, it can not work for some reason. Thanks, |
I identified a bug that was occurring when the --haplo_count_blacklist argument was specified. The latest version of phASER (v0.9.9.4) should address this problem. Please try again using the updated version of phASER and let me know if you are now getting haplotypic counts. Please note, that you will also need to redownload the "hg19_haplo_count_blacklist.bed" file. |
Thank you for upgrading the phaser, i‘ve got Generate haplotypic counts. However, it seems a bit out of trouble when i run phaser_gene_ae to generate haplotype expression quantifications, the result is all zero. |
Hi there, it looks like the issue is that you have named your chromosomes e.g. "chr1", and the annotation files that are provided with phASER for convenience are named "1". I have updated all of the documentation links to include both annotation files with and without "chr" in the chromosome names, but here are the files you will need. Please re-run phASER and phaser_gene_ae with these files, and let me know if it worked. ftp://ftp.nygenome.org/sec/phaser/hg19_hla.chr.bed.gz |
@secastel Hi, could you share these files with me? I am using Tophat2 and encountering some problems as well. Thank you! |
@x811zou you can find all of the needed files (with chr in the name) on the blog post / tutorial here: https://stephanecastel.wordpress.com/2017/02/15/how-to-generate-ase-data-with-phaser/ |
Dear Stephane,
pHASER has been quite helpful for me. However, I'm trying to assess allele-specific gene expression in single-cell RNA-Seq data from human lung cancer cells and I have tried it many times,But all failed(aCount=0 and bCount=0),is there a problem with my vcf file?
vcf file:
haplotypic_counts.txt:
python phaser.py --pass_only 0 --vcf var.flt.vcf.gz --bam $bam --paired_end 1 --mapq 10 --baseq 10 --sample $bam --blacklist hg19_hla.bed --haplo_count_blacklist hg19_haplo_count_blacklist.bed --threads 6 --o ase
I do not know much about it in this respect, can you tell me where there is a problem?
thanks
The text was updated successfully, but these errors were encountered: