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
wondering about reading/writing multiple proteoforms. Does a proteoform have to be completely on a single line? if not, is there a line length (like fasta). Does each proteoform have to start with a specific character to know when the thing begins, like ">"?
Excellent question, I've wondered the same thing. I don't believe that the standard addresses this, right? I've always imagined a file with a single ProForma Term on each line, but the idea of a FASTA-like setup is interesting. Would provide a place for metadata ... but honestly, I'm not sure that there would be that much to say about specific proteoforms.
FASTQ files are never split at 60 characters, so there is precedent for requiring no line breaks. But if we're going to call it a ProForma FASTA file, we should allow line breaks.
my 2 cents: One should allow line breaks if we expect people to manually edit these files. Given the specific set of modifications that users might want, I assume this will be the case. That being said, should we allow tags to be broken across 2 lines? That seems messy, but parsers wouldn't really care as we'd just mash everything together
Despite the mess, I think we should allow tags to be broken across lines. Mashing together worked for all sorts of potatoes last week, so it should work for us here.
Activity
rfellers commentedon Feb 21, 2018
Excellent question, I've wondered the same thing. I don't believe that the standard addresses this, right? I've always imagined a file with a single ProForma Term on each line, but the idea of a FASTA-like setup is interesting. Would provide a place for metadata ... but honestly, I'm not sure that there would be that much to say about specific proteoforms.
[-]proteoform lists and line lengths[/-][+]Proteoform lists and line lengths[/+]acesnik commentedon Apr 4, 2018
This is being discussed here, too: topdownproteomics/ProteoformNomenclatureStandard#11
Personally, I'm in favor of FASTA-like setup to allow specifying metadata (accessions, ontologies).
acesnik commentedon Sep 9, 2018
Should we allow the files to be split at 60 characters per line? That could be pretty strange if tags get split in the middle.
Examples:
PROTEOFORMPROTEOFORMPROTEOFORMPROTEOFORMPROTEOFORMPROT[Phospho]EOFORMROTEOFORMPROTEOFORMPROTEOFORMPROTEOFORMPROTEOFORMPROT[mass:79.98]EOFORMacesnik commentedon Nov 25, 2018
FASTQ files are never split at 60 characters, so there is precedent for requiring no line breaks. But if we're going to call it a ProForma FASTA file, we should allow line breaks.
rfellers commentedon Nov 26, 2018
my 2 cents: One should allow line breaks if we expect people to manually edit these files. Given the specific set of modifications that users might want, I assume this will be the case. That being said, should we allow tags to be broken across 2 lines? That seems messy, but parsers wouldn't really care as we'd just mash everything together
acesnik commentedon Nov 26, 2018
Despite the mess, I think we should allow tags to be broken across lines. Mashing together worked for all sorts of potatoes last week, so it should work for us here.