Closed dustine32 closed 6 years ago
Yes, looks right to me.
I figured out a big part of what was wrong here, which was a lack of proper triple-matching used to find existing MF-enabled_by-GP triples. The resulting pathway now shows connected edges from ATR to ABL1 through ATM, though the remaining ATM (with MF protein binding) is still unconnected to ATR:
Not totally sure why yet since I do have logic that connects to multiple target MF's per source. I'll have to dig further.
Think I fixed remaining issue with latest commit. I separated out the declaration of entities (GP, MF) before circling back through the pathway spreadsheet and adding the regulation relations. This way, at time of looking for all matching ENTITY B's for a connection, all entities would exist. You can see the full ATR-ATM-ABL1 connections here:
From Paul's (@thomaspd) email:
"The main issue remaining is to handle the one:many issue. For example, there’s probably only one relationship in SIGNOR where, say, where ATR directly positively regulates ATM. But there are many different activities of ATM where ATM regulates different downstream activities (BRCA1, CHEK2, MDM2, etc.). This means the Noctua model will need to connect ATR activity to ALL of the different ATM activities with directly positively regulates relations. Right now ATR’s activity is only connected to one of the ATM activities (the one where it’s acting on MDM2)."
I think this is what we want? Note: the two ATM nodes connected to ABL1 are for two different activities (protein kinase activity and protein binding).