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
Describe the bug
Currently if torchview detects gets a list or dict as the input to forward it assumes the user will have a forward function in their model that accepts that mapping as keyword arguments or the list as a set of positional arguments. This is not always true. For instance, I often will not collate my batches and I will pass a list of dictionaries with a lot of information for how the forward pass should procede. Here is a MWE that demonstrates this:
in forward_prop it works fine and I get a nice graph like:
Additional context
I'm not sure what the correct fix for this is, but an easy fix would be to let the user pass a flag that specifies the input data should be passed in as-is without assumptions on trochview's part.
The text was updated successfully, but these errors were encountered:
Describe the bug
Currently if torchview detects gets a
list
ordict
as the input toforward
it assumes the user will have a forward function in their model that accepts that mapping as keyword arguments or the list as a set of positional arguments. This is not always true. For instance, I often will not collate my batches and I will pass a list of dictionaries with a lot of information for how the forward pass should procede. Here is a MWE that demonstrates this:To Reproduce
Expected behavior
This errors, but if I remove the
*
and**
from:in
forward_prop
it works fine and I get a nice graph like:Additional context
I'm not sure what the correct fix for this is, but an easy fix would be to let the user pass a flag that specifies the input data should be passed in as-is without assumptions on trochview's part.
The text was updated successfully, but these errors were encountered: