Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Reads intensities considerations #172

Closed
douweschulte opened this issue Jun 22, 2022 · 1 comment
Closed

Reads intensities considerations #172

douweschulte opened this issue Jun 22, 2022 · 1 comment
Labels
M-possible-scoring-change Misc: Something that can affect the scoring

Comments

@douweschulte
Copy link
Member

Right now the peaks reads scale between [1-2] this could be changed to [0-1] to allow for a broader separation between reads with highly different areas. As there are not very often datasets with Fasta/simple and peaks data at once the old argument of the peaks reads needing to have a higher score than the other reads does not really hold.
Besides this it is also interesting to think a bit better on how to normalize the scores. Now the score is absolute but there can be made some points that a normalized scoring (the best is always 1) is beneficial. Although it then has to be seen if this does not introduce too big of a problem when changing the cutoff scores in the batchfile.

@douweschulte douweschulte added the M-possible-scoring-change Misc: Something that can affect the scoring label Jun 22, 2022
douweschulte added a commit that referenced this issue Sep 27, 2022
douweschulte added a commit that referenced this issue Sep 30, 2022
@douweschulte
Copy link
Member Author

As it did not influence anything in the scores this change will be kept.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
M-possible-scoring-change Misc: Something that can affect the scoring
Projects
None yet
Development

No branches or pull requests

1 participant