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
Whilst I'm working on the CI pipeline for the WJ model, I've noticed we have a lot of redundant parentheses in our gene associations. Some examples are below
R_RC02241
((WBGene00020264 or WBGene00022646 or WBGene00044631) or (WBGene00010339 or WBGene00011543) or (WBGene00016934 or WBGene00007446 or WBGene00013995)) or WBGene00017888
R_rnasynth_m
((WBGene00009658 or WBGene00011791 or WBGene00012528) and WBGene00001596 and WBGene00014115) and (WBGene00012999 and WBGene00008781 and WBGene00000123 and WBGene00016140 and WBGene00004411 and WBGene00017300 and WBGene00013680)
Whilst this makes no difference to the actual way genes are handled, it is potentially something we should tidy up at some point.
The text was updated successfully, but these errors were encountered:
I totally agree... I guest most of it is coming from the merging process. We should make clear rules for the future how this is used. I prefer to have the AND only for multiprotein complexes and not for lumped/nested reactions. If their are alternative multimers we can have parentheses llike (A AND B) OR (A AND C).
Whilst I'm working on the CI pipeline for the WJ model, I've noticed we have a lot of redundant parentheses in our gene associations. Some examples are below
R_RC02241
((WBGene00020264 or WBGene00022646 or WBGene00044631) or (WBGene00010339 or WBGene00011543) or (WBGene00016934 or WBGene00007446 or WBGene00013995)) or WBGene00017888
R_rnasynth_m
((WBGene00009658 or WBGene00011791 or WBGene00012528) and WBGene00001596 and WBGene00014115) and (WBGene00012999 and WBGene00008781 and WBGene00000123 and WBGene00016140 and WBGene00004411 and WBGene00017300 and WBGene00013680)
Whilst this makes no difference to the actual way genes are handled, it is potentially something we should tidy up at some point.
The text was updated successfully, but these errors were encountered: