-
Notifications
You must be signed in to change notification settings - Fork 31
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
Mark istrans as inactive #658
Merged
Merged
Conversation
This file contains 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
Pull Request Test Coverage Report for Build 10827927966Details
💛 - Coveralls |
mhauru
requested changes
Sep 11, 2024
One may equally mark many others, but from the linked issue I saw this was
differentiated and we might as well not (and other tools mark as non
differentiable already)
…On Wed, Sep 11, 2024 at 12:50 PM Markus Hauru ***@***.***> wrote:
***@***.**** commented on this pull request.
------------------------------
In ext/DynamicPPLEnzymeCoreExt.jl
<#658 (comment)>
:
> @@ -10,4 +10,6 @@ end
@inline EnzymeCore.EnzymeRules.inactive_type(::Type{<:DynamicPPL.SamplingContext}) = true
***@***.*** EnzymeCore.EnzymeRules.inactive_noinl(::typeof(DynamicPPL.istrans), args...) = nothing
Cool, thanks. Is there a particular reason why marking this one manually
has having 0 grad is significant, or is it the case that we might equally
mark many other functions, and this one just came up in
EnzymeAD/Enzyme.jl#1807
<EnzymeAD/Enzyme.jl#1807>?
—
Reply to this email directly, view it on GitHub
<#658 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAJTUXFS2UQECWMT7DNICE3ZWBYDXAVCNFSM6AAAAABOBJI23CVHI2DSMVQWIX3LMV43YUDVNRWFEZLROVSXG5CSMV3GSZLXHMZDEOJXHEZTAOJUHE>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
mhauru
approved these changes
Sep 12, 2024
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.
Thanks @wsmoses!
Can this get a patch release?
…On Thu, Sep 12, 2024, 6:02 AM Markus Hauru ***@***.***> wrote:
Merged #658 <#658> into
master.
—
Reply to this email directly, view it on GitHub
<#658 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAJTUXD6FFLBKAWILEXGGI3ZWFRC3AVCNFSM6AAAAABOBJI23CVHI2DSMVQWIX3LMV45UABCJFZXG5LFIV3GK3TUJZXXI2LGNFRWC5DJN5XDWMJUGIZTAMJQGQZTOMY>
.
You are receiving this because you modified the open/close state.Message
ID: ***@***.***>
|
Looking into it. A major PR (#575) has been merged into master since the last release, will probably rather make sure that everything is in order with that, and make a breaking release that would include this too. |
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.
Purely a performance optimization