Closed yaseminbridges closed 1 year ago
Hi @yaseminbridges we made a lot of updates to the code base and we have a new release with updated docs for setup and running. The updates include support for both v1 and v2 phenopackets.
I believe, however, that the issue may be caused by an invalid URI in your input phenopacket since the stack trace indicates that the error originates in java.base/java.nio.file.Path.of(Path.java:199)
.
Can you please re-test with the new version and let me know if the issue persists?
Thanks, Daniel
Hi @ielis, yes you are completely right, it was due to an invalid URI in the input phenopacket! I didn't realise this was the issue as I was providing the path to the VCF in the CLI so I thought it would get ignored in the phenopacket.
Thanks, Yasemin
Hello,
I wondered if there would be support for phenopackets v2. Currently when I try and run LIRICAL with a v2 phenopacket I get this error:
If not it may be useful if you could make the input check for phenopackets less strict.
Thanks,
Yasemin