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
Doing this effectively moves the reldepth calculation from inside the GOTerm class to its own module
Description
The GOTerm data member, reldepth, which is the depth of a GOTerm if optional relationships are loaded as well as the required is_a edges. It only appears on a GOTerm if optional relationships are loaded.
The issue with GOTerm having a reldepth data member is that its value was calculated using all of the optional relationships, if optional relationships are requested, even if the researcher is only working with the part_of relationship.
The GODag is designed to parse the go-basic.obo and either read or not read optional relationships.
The partner class, GoSubDag is designed to use specific relationships (None, All, or Some) specified by the researcher and takes the GODag as an input argument.
This change makes the reldepth calculation independent of other tasks, like parsing the go-basic.obo or using a subset of the GODag through GoSubDag or calculating semantic similarity values between two GO terms using Wang's semantic similarity. It also allows the researcher to have depth calculated using a subset of optional relationships.
The text was updated successfully, but these errors were encountered:
Sumary
Description
The GOTerm data member, reldepth, which is the depth of a GOTerm if optional relationships are loaded as well as the required is_a edges. It only appears on a GOTerm if optional relationships are loaded.
The issue with GOTerm having a reldepth data member is that its value was calculated using all of the optional relationships, if optional relationships are requested, even if the researcher is only working with the part_of relationship.
The GODag is designed to parse the go-basic.obo and either read or not read optional relationships.
The partner class, GoSubDag is designed to use specific relationships (None, All, or Some) specified by the researcher and takes the GODag as an input argument.
Usage
To get reldepth value now, do this:
Benefits
This change makes the reldepth calculation independent of other tasks, like parsing the go-basic.obo or using a subset of the GODag through GoSubDag or calculating semantic similarity values between two GO terms using Wang's semantic similarity. It also allows the researcher to have depth calculated using a subset of optional relationships.
The text was updated successfully, but these errors were encountered: