pal_finder: improve reporting of specific errors associated with SRR Fastq read headers #82
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
…script associated with SRR Fastq read headers.
…s from Pal_finder log file.
…he errors connected to Fastq read headers.
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.
PR which updates the wrapper script within the
pal_findertool, to detect and report specific errors which are associated with SRR Fastq read headers (though they could potentially affect other non-Illumina-style Fastq files).SRR read headers take the form:
and so far seem to result in failures of the Pal_finder script to complete, leaving messages in the Pal_finder log of the form:
and
The PR updates the final error message to include more information in either of these cases.