You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Since these categories are derived from a mutable file level_one_terms.txt, these IDs will have to be dynamically assigned during each data conversion "build," which will inextricably tie the term lookup file to the BP modules file. For example, if the "cellular process" GO term is dropped from level_one_terms.txt then another "other" term might inherit its ID. Or if another term is added, the ID of its "other" category term may change from OTHER:0002 to OTHER:0003 or something else.
Handled (AFAIK) in d1960bd. The dataflow works like:
The level_one_terms.txt file is parsed in mint_other_terms.py to create a JSON lookup with an OTHER: term minted for each level 1 term. The "other biological process" term is also added.
This JSON is then input into organize_bp_modules_from_slim.py so that the correct OTHER: IDs are used.
The ibd_modules_organized.json and level_one_terms.json files are then used to create go_term_info.json.
Currently, the plan is to make up term IDs for the "other" categories. Ex:
Since these categories are derived from a mutable file level_one_terms.txt, these IDs will have to be dynamically assigned during each data conversion "build," which will inextricably tie the term lookup file to the BP modules file. For example, if the "cellular process" GO term is dropped from
level_one_terms.txt
then another "other" term might inherit its ID. Or if another term is added, the ID of its "other" category term may change fromOTHER:0002
toOTHER:0003
or something else.Tagging @tmushayahama
The text was updated successfully, but these errors were encountered: