Skip to content

Doesn't support multi-headed output architectures #12

@stephenjfox

Description

@stephenjfox

Lying somewhere between a bug and a feature enhancement, the current iteration of the nn.Module.children assumes that the layers are in a sequence (like a significantly deep convolutional network).

It does not however, consider that the children it encounters are all siblings, rather than always being parent-child relationships.

  • Given how nn.Module represents its layer relationships, crafting a solution for many cases for this could be very tricky.

Some architectures that may be negatively impacted by this:

  • U-Net
  • DenseNets (mentioned in the presentation)
  • Any network that trains on multiple outputs
    • Depending on how its modeled, these could all be considered sequential children or a nested output.

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't workingenhancementNew feature or request

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions