Uncertain
nshipster.com
Uncertain
1–10 of 101 posts
Re: Uncertain<T>
#2Always enjoy mattt’s work. Looks like a great library.
Re: Uncertain<T>
#3Does this handle covariance between different variables? For example, the location of the object your measuring your distance to presumably also has some error in it's position, which may be correlated with your position (if, for example, if it comes from another GPS operating at a similar time).
Certainly a univarient model in the type system could be useful, but it would be extra powerful (and more correct) if it could handle covariance.
Re: Uncertain<T>
#4[flagged]
Re: Uncertain<T>
#5[flagged]
I don't think inference is part of this at all, frequentist or otherwise.
It's not part of the type system, it's just the giry monad as a library.
Re: Uncertain<T>
#6[flagged]
> And why does it need to be part of the type system?
As presented in the article, it is indeed just a library.
Re: Uncertain<T>
#7[flagged]
> What if I want Bayesian?
Bayes is mentioned on page 46.
> And why does it need to be part of the type system? It could be just a library.
It is a library that defines a type.
It is not a new type system, or an extension to any particularly complicated type system.
> Am I missing something?
Did you read it?
https://www.microsoft.com/en-us/research/wp-content/uploads/...
Re: Uncertain<T>
#8A small note, but GPS is only well-approximated by a circular uncertainty in specific conditions, usually open sky and long-time fixes. The full uncertainty model is much more complicated, hence the profusion of ways to measure error. This becomes important in many of the same situations that would lead you to stop treating the fix as a point location in the first place. To give a concrete example, autonomous vehicles will encounter situations where localization uncertainty is dominated by non-circular multipath effects.
If you go down this road far enough you eventually end up reinventing particle filters and similar.
Re: Uncertain<T>
#9[flagged]
It was chosen to be implemented as a generic type in this design because the way that uncertainty "pollutes" underlying values maps well onto monads which were expressed through generics in this case.
Re: Uncertain<T>
#10Arguably Uncertain should be the default, and you should have to annotate a type as certain T when you are really certain. ;)