I noticed that the --vcfFileIndex option does not actually seem to be used at any point during the analysis. Instead, I see that the VCF file path is being passed into savvy without any reference to the index. When using VCFs or BCFs, it seems hard coded to require a .csi index that's right next to the file in the same directory.
Can the documentation be updated to indicate this? Also, I'd be willing to help remove everything about --vcfFileIndex from the code, because right now it's being passed all the way through R into the VcfClass::setVcfObj method where it is completely unused. I also see it's in SAIGE-GENE unused in setvcfDosageMatrix. It would simplify the code if all references to --vcfFileIndex were removed, given that it isn't used.
I noticed that the
--vcfFileIndex
option does not actually seem to be used at any point during the analysis. Instead, I see that the VCF file path is being passed into savvy without any reference to the index. When using VCFs or BCFs, it seems hard coded to require a .csi index that's right next to the file in the same directory.Can the documentation be updated to indicate this? Also, I'd be willing to help remove everything about
--vcfFileIndex
from the code, because right now it's being passed all the way through R into theVcfClass::setVcfObj
method where it is completely unused. I also see it's in SAIGE-GENE unused insetvcfDosageMatrix
. It would simplify the code if all references to--vcfFileIndex
were removed, given that it isn't used.