In milestone v3.0, the report will depend on the designed vector type being known -- either ssAAV or scAAV. Currently, the input field vector_type allows a third option, "unspecified".
Consider a heuristic to convert "unspecified" to ss or sc based on the contents of the processed data, just before reporting:
Majority frequency of "full" subtypes with ssAAV vs. scAAV polarities/strandedness
Median read length -- we expect ssAAV to be around 4.7 kilobases and scAAV around half that; consider a cutoff around 2.5kb if the majority-frequency heuristic isn't enough.
Alternatively, just remove the "unspecified" option from the vector_type field if we expect users to always know the designed vector type and heuristic auto-detection is either unhelpful or unreliable.
In milestone v3.0, the report will depend on the designed vector type being known -- either ssAAV or scAAV. Currently, the input field
vector_typeallows a third option, "unspecified".Consider a heuristic to convert "unspecified" to ss or sc based on the contents of the processed data, just before reporting:
Alternatively, just remove the "unspecified" option from the vector_type field if we expect users to always know the designed vector type and heuristic auto-detection is either unhelpful or unreliable.