WARNING: THIS SITE IS A MIRROR OF GITHUB.COM / IT CANNOT LOGIN OR REGISTER ACCOUNTS / THE CONTENTS ARE PROVIDED AS-IS / THIS SITE ASSUMES NO RESPONSIBILITY FOR ANY DISPLAYED CONTENT OR LINKS / IF YOU FOUND SOMETHING MAY NOT GOOD FOR EVERYONE, CONTACT ADMIN AT ilovescratch@foxmail.com
Skip to content

Make Processor.training_step abstract. #55

@cisprague

Description

@cisprague

In contrast to Processor.validation_step – which should mostly be the same for all processors (compares rolled out trajectory to true trajectory) – Processor.training_step seems to depend more on the specific subclass of Processor. E.g., the flow matching loss can be different from the diffusion loss.

Related to this: I think we can get rid of

loss_func: nn.Module | None = None,

as, in most cases, the loss function will be specific to the subclass.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    Status

    Todo

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions