Changes to performance plotting script #1
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
set contam clean pointers in simple_check_1_ge.c to the correct position after processing each chunk, simplify scoring system
Rename files to more intuitive ones, easing newcomers adoption
Thanks Enze! merge check.c into query.c & add instruction for remove.c
Move configuration template out of code, fixes issue SciLifeLab#79
…description lines) for simNGS, fixes issue SciLifeLab#78
Adjusting generation of reads for simNGS, fixes issue SciLifeLab#78
…ot being sent since Pull request SciLifeLab#75
Nice, thanks Enze! fix no json output issue. see what will happen on travis
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR cannot be merged as it is, so just close it... I just wanted you to have a look at the
performance.pyscript, I've filtered the data a little bit to ease plotting ;)Here are some raw preliminary numbers in total seconds, first column is
fastq_screen, second one isFACSfor the same dataset:fastq_scr facs
(...)
2.655941 0.128
2.655941 0.004
2.655941 0.001
0.367831 0.125
0.367831 0.004
0.367831 0.004
Good news are that all numbers in right column are consistently lower than the left column. Not so good news are that the script requires some further filtering and validation, so that might be misleading at this point ;)
@arvestad might be interested in this too ;)