Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Name of uncertainties: StdDevUncertainty vs. VarianceUncertainty vs. InverseVariance
See original GitHub issueThere is a bit of inconsistency between the names. The first (StdDevUncertainty) is somewhat abbreviated and has the “Uncertainty” suffix, the second (VarianceUncertainty) uses the full name and the suffix, while the last one (InverseVariance) uses the full name without suffix.
Since they shouldn’t be “offically released” yet we still could make the names more consistent with StdDevUncertainty (the already released one)? Maybe VarUncertainty and IVarUncertainty (or InvVarUncertainty)?
Not sure if this is actually necessary, I just noticed and wanted to ask if someone else is bothered about the naming. 😅
Issue Analytics
- State:
- Created 5 years ago
- Comments:17 (15 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
so we should provide the uncertainty (or should I say delta)?
C’mone, overwrite/clobber debate is so 2016. Moffat alpha/beta/gamma is all the rage now. 😉