-
Notifications
You must be signed in to change notification settings - Fork 2
Rework optimizers #139
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.
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
Draft
benikm91
wants to merge
5
commits into
dimwit-dev:main
Choose a base branch
from
benikm91:rework-optimizers
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Draft
Rework optimizers #139
Changes from all commits
Commits
Show all changes
5 commits
Select commit
Hold shift + click to select a range
7e1c382
move tensor tree related methods to separate package
marcelluethi d35ad7f
Rework optimizers
benikm91 aaf493f
Cleanup Optimizers: Remove SequenceFunction (until proven necessary),…
benikm91 4db980d
Add LearningRateSchedule to other optimizers.
benikm91 88e36b4
Remove LearningRateSchedule from dimwit (moved to deepwit)
benikm91 File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
11 changes: 11 additions & 0 deletions
11
core/src/main/scala/dimwit/optimizer/LearningRateSchedule.scala
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,11 @@ | ||
| package dimwit.optimizer | ||
|
|
||
| type LearningRateSchedule = Int => Double | ||
|
|
||
| object LearningRateSchedule: | ||
| def apply(f: Int => Double): LearningRateSchedule = f | ||
|
|
||
| private[dimwit] def from(learningRate: Double | LearningRateSchedule): LearningRateSchedule = | ||
| learningRate match | ||
| case f: LearningRateSchedule => f | ||
| case d: Double => _ => d |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don't quite understand how
IsFloatTreeis different fromFloatTree. Wouldn't it be possible to enforce theIsFloating[V]constraint there already?Uh oh!
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
FloatTree[P, V] is for a specific V.
IsFloatTree[P] marks any possible FloatTree
I can write
But then we can't use for hard-coded precision in e.g. params:
If I do
So far to the motivation. I don't know if there is a better solution :) Best I came up with.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
To make it concrete for the optimizers.
IsFloatTreewas here necessary to make the VAE example run that has hard coded Params precision. I think we should support hard coding precision.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Do we need the higher kinded type here? Maybe something like would be easier to work with?