Closed lkuchenb closed 3 years ago
I have the exact same output which is not the same as expected out as well.
Thank you for using our tool. We have confirmed that this was, in fact, an issue with our README which has been updated to accurately reflect the output from arcasHLA genotype when running the test case with the latest commit (8096c18). The original output that had been included in the README was from a very early private release of arcasHLA and was not updated for the subsequent public releases of the codebase which should all, at the time of writing this, produce consistent genotyping results.
Thank you all for using our tool and pointing out this important issue. I was originally mistaken (see my previous comment, with the text that has been struck through) and will try to clear up any confusion here:
The genotyping calls from releases v0.1.0 and v0.2.0 are presently inaccurate (hence failing to reproduce the proper output for the test case) due to an error resulting from a depreciated call to "git lfs" which has been addressed in the master branch by commit a7ce1bb.
Moreover, the most recent update to the README, commit eeefc2f, undoes the changes that I mentioned in my previous comment from commit 8096c18 (which, incidentally, had been misapplied to the output of the partial command rather than that of the genotype command).
We will release a new, tagged version of arcasHLA with updated requirements and various bug fixes soon.
@IoanFilip2 Is the new release underway? It would be great keep tracking this so that people using the software in their downstream piplines (such as myself) know when to update the tool.
Thanks for providing this software!
I cannot reproduce the test case as described in
README.md
. Here's how I've run arcas HLA:This is the output I get:
which mismatches on DQB1 and DRB1.
I also tested this on the master branch.