Skip to content
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

yali1 and yali0 gene identifiers #3

Open
2 tasks
edkerk opened this issue Oct 24, 2017 · 3 comments
Open
2 tasks

yali1 and yali0 gene identifiers #3

edkerk opened this issue Oct 24, 2017 · 3 comments

Comments

@edkerk
Copy link
Member

edkerk commented Oct 24, 2017

Instead of using the CLIB122-derived YALI0 gene identifiers, used the W29-derived YALI1 genes instead. This most likely constitutes a whole new reconstruction, to be tracked in a separate branch.

edit: instead of separate branch, @ChristianLieven has included Yali1 identifiers in the same model here.

  • evaluate of the solution above is functioning well when loading model with RAVEN and COBRA
  • identify if new Yali1 genes (absent from Yali0) code for new reactions
@ChristianLieven
Copy link
Contributor

Hi @edkerk are CLIB122-derived IDs due to a re-annotation and hence entirely different ORFs than W29-derived or would it be possible to use gene annotation to map between them?

@edkerk
Copy link
Member Author

edkerk commented Apr 13, 2018

@ChristianLieven see this supplementary table from the W29 genome paper for a mapping of CLIB122 to W29 ORFs, As you can see, some genes nicely map, while others are missing or new.

@ChristianLieven
Copy link
Contributor

Thanks @edkerk I'll take a look!

@edkerk edkerk changed the title Make separate branch with YALI1 gene associations. yali1 and yali0 gene identifiers Jun 27, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants