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
*mod_args.get(etype,()) and **mod_kwargs.get(etype,{}) in HeteroGraphConv's forward need to be changed to *mod_args.get((stype, etype, dtype),()) and **mod_kwargs.get((stype, etype, dtype),{})
Motivation
For heterogeneous graphs, the parameters of a homogeneous graph cannot be determined only by etype, for example, if there are two kinds of edges (node1,edge1,node1) and (node2,edge1,node1).
The text was updated successfully, but these errors were encountered:
Thanks for filing the issue. Is there a reason for not defining separate edge types (e.g. edge1 and edge2) when the source nodes are of different types in this example? Are there any special considerations to keep in mind?
Yes, I know there are ways to avoid this problem, but I think as a framework itself, there should be no assumptions about the user's source data schema. @rudongyu
Thanks for further elaboration. I see your point. We’ve added it to our backlog to get prioritized over other feature requests in our roadmap. You are also appreciated to contribute to DGL to get it supported, thanks!
🚀 Feature
*mod_args.get(etype,()) and **mod_kwargs.get(etype,{}) in HeteroGraphConv's forward need to be changed to *mod_args.get((stype, etype, dtype),()) and **mod_kwargs.get((stype, etype, dtype),{})
Motivation
For heterogeneous graphs, the parameters of a homogeneous graph cannot be determined only by etype, for example, if there are two kinds of edges (node1,edge1,node1) and (node2,edge1,node1).
The text was updated successfully, but these errors were encountered: