discuss propto with double vs. autodiff variables in User's Guide
Open
Nobody has claimed this yet.
enhancement
- Dominant language
- TeX
- Stars
- 43
- Forks
- 133
- Avg merge
- 11h 32m
- Merged PRs (30d)
- 4
Description
Summary:
In the User's Guide chapter on efficiency, we should discuss the tradeoff between evaluating propto=true with double and autodiff variables.
Description:
The issue is that
propto=truerequires us to compute autodiff in order to drop normalizing constant calculations (we drop ones that aren't autodiff vars)propto=falserequires computation of normalizing constants overdouble, but no autodiff
For double input, either of these can be faster depending on how expensive the normalizing constants are to compute
Current Version:
v2.32
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the User's Guide chapter on efficiency and locate the discussion of propto=true and propto=false for double and autodiff variables. Add the requested tradeoff discussion, explaining when each approach may be faster, and verify the rendered documentation and relevant source changes.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- tex
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100