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
Currently the Jumping Knowledge module (JK) only supports homogeneous features input, that is inputs with the type signature List[Tensor]
This feature would promote JK as a potential drop-in improvement when experimenting on relevant heterogeneous tasks. I propose adding the class HeteroJK for heterogeneous inputs (for brevity's sake, I omitted comments/imports):
Modify the existing JumpingKnowledge module so that It'd also accept heterogeneous inputs, which would alter the type signature of the input to be Union[List[Tensor], Dict[str, List[Tensor]]], the return type would be changed similarly.
I'm happy to help implement either approach if this feature is a welcomed addition to PyG.
Thank you for your time and consideration.
Additional context
No response
The text was updated successfully, but these errors were encountered:
Hi,
this PR implements #9355, please do let me know if any additional
changes or documentation is needed.
Thank you
---------
Co-authored-by: rusty1s <matthias.fey@tu-dortmund.de>
🚀 The feature, motivation and pitch
Dear PyG Developers,
Currently the Jumping Knowledge module (JK) only supports homogeneous features input, that is inputs with the type signature
List[Tensor]
This feature would promote JK as a potential drop-in improvement when experimenting on relevant heterogeneous tasks. I propose adding the class
HeteroJK
for heterogeneous inputs (for brevity's sake, I omitted comments/imports):Alternatives
Modify the existing
JumpingKnowledge
module so that It'd also accept heterogeneous inputs, which would alter the type signature of the input to beUnion[List[Tensor], Dict[str, List[Tensor]]]
, the return type would be changed similarly.I'm happy to help implement either approach if this feature is a welcomed addition to PyG.
Thank you for your time and consideration.
Additional context
No response
The text was updated successfully, but these errors were encountered: