-
Notifications
You must be signed in to change notification settings - Fork 1
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
List of actions from group call 15-Oct-2024 #2255
Comments
Could you add a screenshot? I can't find that. |
OK, I've changed that on my desktop. |
Should we do that? InterPro has them as them as separate features: |
I think we shoudn't follow interPro on this one. Its clearer as single conjoined feature. |
Yes, in term of visualisation I think it makes more sense as a single feature |
InterPro / domain tracks now come before low complexity, disordered regions and most tracks from UniProt. Refs pombase/website#2255 Refs pombase/website#2203 Refs pombase/pombase-chado#1218
The InterProScan output gives no hint about this. The InterPro website only mentions Pfam-A: There is a Pfam-B file on the FTP site: This old blog post says that Pfam-B is not included in the main Pfam website so maybe it's not included in InterPro: |
Pfam-b not urgent. but useful if we can link it to the interpro to see other 'members' |
InterPro / domain tracks now come before low complexity, disordered regions and most tracks from UniProt. Refs pombase/website#2255 Refs pombase/website#2203 Refs pombase/pombase-chado#1218
We now post a message to the main window to highlight the current feature in the table of domains. Refs pombase/website#2203 Refs pombase/website#2255 Refs pombase/pombase-chado#1218
PRINTs, display features as con-joined in viewerAlso, not on the call, but I noticed that the MOBIDB said "provided by InterPRO". Probably this should say "Imported from InterPro" since that is where we get them from, but InterPro do not create them.Maybe in these cases we should be more explicit ->
e.g Provided by MOBIDB via InterPRO?
The text was updated successfully, but these errors were encountered: