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
Thanks for your earlier replies. Really enjoying this software. One thing I have noticed is that outputs seem biased towards returning top results for proteins that have longer sequence lengths. It also appears that there is a filter for sequence length available. What solutions/workflows have you found to be most useful for eliminating this bias, i.e. what cutoffs to use, which proteins to eliminate from index, etc. Thanks in advance.
The text was updated successfully, but these errors were encountered:
Can you share an example of this behavior please? I would like to reproduce the issue locally. Currently, if same hits were identified, the shorter ones gets higher score because Folddisco applies length-based penalty in scoring.
Thanks for your earlier replies. Really enjoying this software. One thing I have noticed is that outputs seem biased towards returning top results for proteins that have longer sequence lengths. It also appears that there is a filter for sequence length available. What solutions/workflows have you found to be most useful for eliminating this bias, i.e. what cutoffs to use, which proteins to eliminate from index, etc. Thanks in advance.
The text was updated successfully, but these errors were encountered: