Closed fehrhart closed 1 year ago
Okay, well, at least I can say this is not a BridgeDb problem. It's the negative vector length that causes the problem. Furthermore, it seems to me it's deep inside Derby. We can check next week if this happens specifically with the most recent Derby version or the previous one we used. But I think you're just hit the limits of what Derby can handle...
Interesting... It should not be the size of the total file, Exonic collection is bigger and that went through. If it is variant length, there should be a script that cuts them. I observed no cut-off reports in the Missense file - but in the PTV_Missense. Maybe there is a missense variant that blocks it.
Tried the whole thing again - whole process from downloading vcf variation files from ensembl until variantCreator. Same error... Help!
Is this issue still relevant? @egonw
We do not provide these mapping files anymore.
The error message occured when using the VariantCreatorv.1.1 on the datasets Missense and PTV_Missense at the very end of process. The other datasets went through without problems (Exonic, Polyphen, PTV).
Link to tutorial: https://docs.google.com/document/d/1TxzubfLtXquBb7AZDul4E3-7e-O0I62ZnXtztguabZM/edit
Link to files involved (java scripts, config file, data files): https://drive.google.com/drive/folders/1BEdc9DBcuDQnwieDkcDR7wfRlaPb03ys
Error message: