-
Notifications
You must be signed in to change notification settings - Fork 112
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
People find the cactus header requirements + error messages confusing #8
Comments
We should investigate why tge ucsc browser places these restrictions on sequence names. It might be unnecessary an loses important information -----Original Message----- Low priority, but: The requirements that cactus has for fasta headers are somewhat confusing to users, and it's especially bad since a lot of NCBI/genbank identifiers break the requirements. We should look into making the error messages more straightforward and provide a suggested solution (replacing .'s and/or spaces with underscores, probably). We can't do much about the browser's requirements for the "." syntax, but we could look into using Reply to this email directly or view it on GitHub: |
Brian said a while back they might cause problems because mySQL uses "." as a separator between db and table. Not sure if any of the assembly hub stuff actually goes through mySQL, but maybe it goes through code that is expecting a ".table" kind of syntax. |
They quit making tables spit by chromosome years ago. We should be able to Joel Armstrong notifications@github.com writes:
|
OK, I've tested it a bit and it looks like there is no reason for that particular "ucscNames" restriction anymore. (Other than exported MAFs being hard to parse, but that isn't so bad.) Removing that will make things much better, there are so many headers with "."s in them that broke things before... |
Now that the browser works with '.' sequences, there is no need to enforce the very confusing "ucscNames" header requirements.
OK, we now ignore the "ucscNames" restriction by default, but enforce some requirements for characters that the UCSC browser still doesn't like, like "|". We should look into fixing the browser to allow "|" characters especially, since genbank sequences often have those in their identifiers. The "first word must be unique" requirement is harder to get rid of, and it follows the FASTA spec, so I think it's more understandable. |
Low priority, but: The requirements that cactus has for fasta headers are somewhat confusing to users, and it's especially bad since a lot of NCBI/genbank identifiers break the requirements. We should look into making the error messages more straightforward and provide a suggested solution (replacing .'s and/or spaces with underscores, probably).
We can't do much about the browser's requirements for the "." syntax, but we could look into using
[nameparse=full]
instead of[nameparse=darkspace]
for lastz to attempt to get rid of the "first word of a header must be unique" rule. This would make parsing the cigars difficult, though, so it may be more trouble than it's worth.The text was updated successfully, but these errors were encountered: