Repository navigation
Conversation
* avoid length-n allocations when evaluating the ProxGrad objective * check allocations for each objective and gradient call The old test compared one FISTA fit with 10 length-n vectors. It did not catch one extra length-n allocation in each iteration under ISTA. The test now checks that one call of smooth_objective! or smooth_fg! allocates less than one length-n vector. It also checks that a FISTA fit and an ISTA fit each allocate less than 4 length-n vectors. The scratch space holds 3. * link the scaled elastic net issue in the test comment * Bump version to 0.10.4
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
4 participants
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.
#186