[DRAFT] Implement C optimal discretisation strategy to reduce gradient variance in error budgeting feature#266
Draft
adlantz wants to merge 2 commits into
Draft
[DRAFT] Implement C optimal discretisation strategy to reduce gradient variance in error budgeting feature#266adlantz wants to merge 2 commits into
adlantz wants to merge 2 commits into
Conversation
|
|
Collaborator
|
@adlantz let me know when I should start reviewing this PR. Ideally, it should be out of draft and with CI passing, but I am fine doing a pre-review if you need one :) |
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Opening this PR as a draft just to track changes. As of 5/29 all work is local and hasn't been committed to this fork.
🔗 Closed Issues
Link any issues closed or comments addressed by this PR.
"Closes #X" will close issue X automatically when the PR is merged.
📝 Description
Add any additional description required to understand the PR.
Cite related issues, PRs, or comments as needed.
🚦 Status
If anything still needs to be done before this PR can be merged, track it here.
🛠️ Future Work
Focused PRs are good!
Create and link issues for any follow-up work needed.
➕️ Additional Information
Anything that doesn't fit into a category above.
🧾 Release Note
If this PR will be squash-merged, draft the final one-line commit message here.
Otherwise, describe your rebase strategy or how you plan to maintain clean commits.