this is for holding javascript data
Jennifer Shelton edited implementation.tex
over 8 years ago
Commit id: 98679910dec79b668efbd922f658092895e5c1ab
deletions | additions
diff --git a/implementation.tex b/implementation.tex
index 6ab655d..a1d37db 100644
--- a/implementation.tex
+++ b/implementation.tex
...
Inconsistent or unwrapped sequence lines, spaces in headers and missing or non-standard new lines are considered non-fatal errors. If they are detected the decision is made to reformat as requested, report the issue to the analyst and continue the workflow.
The script also automatically adjusts to run the minimal number of steps sufficient to fix and report format issues. If it is included in the set of QC steps then wrapping is the first format issue tested because while repairing FASTA wrapping both headers and new lines can be corrected. New lines are given priority after wrapping because while repairing new lines it is also trivial to repair headers. Finally, headers are evaluated for format issues. If
a an early test returns a format issue and launches a reformatting that automatically repairs any remaining format issues
it is Fasta-O-Matic still
important to test tests for
the remaining any additional format
errors. errors in the original file. The analyst should be made aware of any unexpected format issues in case they indicate an unexpected issue with the data.