# Alarming incorrect computation in Flux / Juno?

**URL:** <https://discourse.julialang.org/t/alarming-incorrect-computation-in-flux-juno/33017>\
**Category:** Machine Learning\
**Created:** [January 6, 2020, 5:27am UTC](https://discourse.julialang.org/t/alarming-incorrect-computation-in-flux-juno/33017 "2020-01-06T05:27:17Z")\
**Posts on this page:** 1\
**Showing post:** 6

<div class="post-metadata">

**Author:** ![jaynick](https://avatars.discourse-cdn.com/v4/letter/j/71c47a/32.png) [@jaynick](https://discourse.julialang.org/u/jaynick)\
**Post date:** [January 7, 2020, 5:46am UTC](https://discourse.julialang.org/t/alarming-incorrect-computation-in-flux-juno/33017/6 "2020-01-07T05:46:16Z")

</div>

I posted about this at  
[https://discourse.julialang.org/t/seriously-incorrect-computation-in-juno-repl/33050](https://discourse.julialang.org/t/seriously-incorrect-computation-in-juno-repl/33050)  
because it seems (to me) to be a problem in Juno, maybe.

---

_[View the full topic](https://discourse.julialang.org/t/alarming-incorrect-computation-in-flux-juno/33017)._