You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
While the percentile threshold was correctly applied, I found that affinity seemed not to be cut off:
I was therefore wondering if I was understanding the parameters correctly.
Thank you very much.
Chen
The text was updated successfully, but these errors were encountered:
Thanks for reporting this, Chen. This is happening because only one quantity can be filtered, so your affinity threshold is being ignored. The library API (Class1PresentationPredictor.predict_sequences) makes this clear but I agree in the commandline tool this is super confusing. I am changing this now to have different semantics for the commandline tool and to apply all the filters you specify. The fix will go into the next release.
Drop the --results-best flag to mhcflurry-predict-scan. Apply all the
threshold filters specified rather than just one of them. Closes#219.
The rationale for this potentially breaking change is that this it is
closer to user expectations.
Dear author,
I was running mhcflurry using:
mhcflurry-predict-scan test.fasta --peptide-lengths 8-11 --alleles HLA-A0101 --threshold-affinity 500 --threshold-affinity-percentile 2.0 --out ./test.csv
While the percentile threshold was correctly applied, I found that affinity seemed not to be cut off:
I was therefore wondering if I was understanding the parameters correctly.
Thank you very much.
Chen
The text was updated successfully, but these errors were encountered: