Closed CodyRamirez closed 4 years ago
Update: I was able to get pVACfuse to run successfully on a few set of patients. However, a large portion of patients are still failing with the above error even though fusion results exist.
If it works for some I would just assume that there are no agfusion results processable by pVACfuse for those other samples. The warning message may simply be an oversight from the addition of agfusion.
I'm looking at the LYM001_tumor.AGFusion_outdir
directory and there are only two predicted fusions, none of which have a _protein.fa
file. Therefore, there are no predicted fusions that can be processed by pVACfuse. I have noticed before that not all fusions will produce this file but it's not clear to me why that is. Either way, we need to improve the warning message to differentiate it from Integrate NEO.
Describe the bug pVACfuse does not recognize that I am passing it agfusion results which it request a directory path. Instead pVAcfuse reads it in as a .bedpe file which it tries to convert to a tsv file, which is then empty obviously. Then because the file is empty, it immediately fails out.
To Reproduce What is the pVACtools command you ran? Please also attach any input files that can be used to reproduce this problem.
Log Output
Output File If your bug is related to the contents of an output file, please paste the output file here.
Expected behavior I expect pVACfuse to recognize that I am giving it a directory of agfusion results.