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
@Mindyporterfield and @senaarpinar are finalizing a tool for generating GlyGen CSV files for glycomics data. Please review the following ticket (especially the second half with the mandatory columns and the assumptions) and let us know if you agree or have alternative suggestions.
The expression part is undefined and will be ignored for now. There is also an issue with the relationship between the two expressions. Each row represents a glycosylation event. The protein expression has nothing to do with a row. Its rather the "sum" of all rows with the protein + the abundance of the non-glycosylated version. For the glycan expression its not sure what this means. If its the abundance of a certain glycan it again has nothing to do with an individual row but rather is the sum of all occurrences of this glycan on all sites. If its something like 20% of the glycans on this site are this glycan we have two problems. I am not sure how the user can enter this with lots of overhead and we have this kind of information often in the form of (20% high mannose and 80% complex Nglycans). But these would not have a GlyTouCan ID.
The last point raises the question how to deal with this type of data? Its even "less" than a composition. Its just a glycan type.
@Mindyporterfield and @senaarpinar are finalizing a tool for generating GlyGen CSV files for glycomics data. Please review the following ticket (especially the second half with the mandatory columns and the assumptions) and let us know if you agree or have alternative suggestions.
This is based on the CSV file definition you provided a while ago:
https://gwu0.sharepoint.com/:w:/r/sites/GlyGenTeam-GRP/_layouts/15/Doc.aspx?sourcedoc=%7B27A34C21-ADB9-4D85-A96D-4B7EB40A103A%7D&file=Mindy%20paper%20curation.docx&action=default&mobileredirect=true
The text was updated successfully, but these errors were encountered: