You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Creating Projection objects is actually somewhat annoying -- especially for AlignmentRecord. We should create "standard projections" for commonly-used schemas, which are named and described in an appropriate way, that can be used and combined rather than simply creating a new custom projection for every use of a Parquet file.
E.g. is there a projection for when you only need the names and metadata about reads? for when you need the full alignment? For when you do (or don't) care about the mate- (or paired-end-) fields?
The text was updated successfully, but these errors were encountered:
tdanford
changed the title
Create a simplified 'vocabulary' for creating Projections
Create a simplified vocabulary for naming projections.
Oct 14, 2014
Creating Projection objects is actually somewhat annoying -- especially for
AlignmentRecord
. We should create "standard projections" for commonly-used schemas, which are named and described in an appropriate way, that can be used and combined rather than simply creating a new custom projection for every use of a Parquet file.E.g. is there a projection for when you only need the names and metadata about reads? for when you need the full alignment? For when you do (or don't) care about the mate- (or paired-end-) fields?
The text was updated successfully, but these errors were encountered: