Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

flow matching API does not match other losses #241

Open
josephdviviano opened this issue Feb 11, 2025 · 0 comments
Open

flow matching API does not match other losses #241

josephdviviano opened this issue Feb 11, 2025 · 0 comments
Assignees
@josephdviviano @hyeok9855

Comments

@josephdviviano
Copy link
Collaborator

Currently, the flow matching loss takes both intermediate or final states as two inputs. This is unlike every other loss which takes a single training object. These should be unified - splitting of intermediate or terminating states should happen in the loss itself.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@josephdviviano josephdviviano

@hyeok9855 hyeok9855

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@josephdviviano @hyeok9855