-
Notifications
You must be signed in to change notification settings - Fork 404
Open
Description
The main problem here is the ability to use weird input schemes (mixed lengths, Datasets etc) with complex pipelines, which often await tabular data. This is for example the case with torch_geometric Data objects, and complex, non-GNN architectures receiving multiple types of "X".
see #1084 for a relevant issue.
proposed solution: metadata routing. If we can successfully route the data (e.g: an array or pandas DataFrame of torch_geometric.data.Data), it would be trivial to pass them as additional fit params, and use a collate_fn to handle stuff from there.
Metadata routing is not implemented for now in skorch NeuralNet, but it looks like it's been partailly done for LLMs?
Metadata
Metadata
Assignees
Labels
No labels