Don't error on size-zero inputs to LKJ lpdf#3347
Open
andrjohns wants to merge 1 commit into
Open
Conversation
Collaborator
Author
|
Hmm looks like there's a bit of inconsistency between the tests and the code for some of the distributions For example, the |
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.
Summary
The validation check order for inputs to
lkj_corr_cholesky_lpdfchanged since Stan 2.32, so that cholesky factors of size zero now error and reject instead of just returning 0. This breaks downstream applications which conditionally set the size to zero to remove it from the likelihood ( thermdcevR package relies on this).This PR updates the
check_cholesky_factorto allow size-zero inputsTests
Additional test added for size-zero handling
Side Effects
N/A
Release notes
lkj_corr_cholesky_lpdfreturns0instead of error with size-zero inputsChecklist
Copyright holder: Andrew Johnson
The copyright holder is typically you or your assignee, such as a university or company. By submitting this pull request, the copyright holder is agreeing to the license the submitted work under the following licenses:
- Code: BSD 3-clause (https://opensource.org/licenses/BSD-3-Clause)
- Documentation: CC-BY 4.0 (https://creativecommons.org/licenses/by/4.0/)
the basic tests are passing
./runTests.py test/unit)make test-headers)make test-math-dependencies)make doxygen)make cpplint)the code is written in idiomatic C++ and changes are documented in the doxygen
the new changes are tested