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

Document the workflow for refreshing DOSDP patterns where CHEBI and PRO are involved #229

Open
1 task
matentzn opened this issue Mar 13, 2023 · 0 comments
Open
1 task
Assignees

Comments

@matentzn
Copy link
Contributor

matentzn commented Mar 13, 2023

CHEBI, NCBITAXON and PRO are too large to be managed easily as standard imports. To mitigate this situation, we have decided to manage these as slims which are located here:

Sometimes, a new term you are using in a DOSDP pattern is not yet in a slim. So you will have to refresh the slim first. NCBITaxon is too complicated, so for now, you have to request a refresh on the issue tracker.

Refresh PRO Slim:

Note: you will need at least 32 GB RAM for this

git clone https://github.com/obophenotype/pro_obo_slim
cd pro_obo_slim
git checkout refresh20230312 -b
# Add your terms to seed.txt, and then SORT THE FILE
sh odk.sh make all
git commit -a -m "refresh slim after adding terms for OBA"
git push --set-upstream origin refresh20230312

When this is done, make a PR. Feel free to merge it yourself (no need to ask for a review).

Refresh CHEBI Slim

git clone https://github.com/obophenotype/chebi_obo_slim
cd chebi_obo_slim
# Follow the instructions for the PRO slim from here

The full process of refreshing the DOSDP patterns:

  1. Check if new PRO / Chebi terms are not in SLIM, if they are not, add them as described above.
  2. Run sh run.sh make IMP=false MIR=false ../patterns/definitions.owl to generate a new pattern ontology component
  3. Run sh run.sh make refresh-merged to import the new terms
  4. Run sh run.sh make IMP=false MIR=false ../patterns/definitions.owl again to generate the labels correctly where new terms are concerned.

@ar-ibrahim

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