-
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
Create slim for public release #6
Comments
Does this sound clear? |
pre-release available for verification Navigate to: click on 'raw' (alternatively, git clone the repo) This consists of
|
Cool. We are going to have a look. I'll get back to you soon. |
Hi, Chris, I got a repot below from my colleague, Kasukawa-san. He found the terms below are not included in the OBO file: PATO:0002099 (which is a parent node of FF:0000245 and FF:0000246) Do you think these have to be added? best, |
I just made a new release of the subset
|
Hi, Kasukawa-san found FF terms that are not linked to any Phase 1 samples seem to be re-appeared. For example, FF:0000640 "Fibroblast - Aortic Adventitial, cytoplasmic fraction" |
You're right, sorry about this, thanks for checking. I was using the OWLAPI code to extract the graph closure, this appears too liberal. I will use my own code which I have vetted to do this and regenerate. On Jul 11, 2013, at 6:27 PM, hkawaji wrote:
|
… to be fully verified. Should fix issues #6
It looks fine. I will start to make it public soon. |
Fantastic! Is it OK if I send a copy to the ENCODE DCC folks? On Wed, Jul 24, 2013 at 6:04 PM, hkawaji notifications@github.com wrote:
|
Year, I am now thinking to prepare this directory: http://fantom.gsc.riken.jp/5/suppl/pre_release/ Here is the current idea of the content: https://fantom5-collaboration.gsc.riken.jp/webdav/home/kawaji/110419-FF-ontology/pre_release/ Could you please let me know your opinion (in particular, readme file). best, |
OK - I made a minor change in the ontology header. Ready to go! |
Need to check with @hkawaji - what are the criteria for being in the slim?
The text was updated successfully, but these errors were encountered: