changing the order in which arithmetic operations on conditionings were performed changed the output
rerunning the workflow with inconsequential changes could result in significantly different (and corrupted) outputs
the issue lies in how the backend passes objects around and tries to pass already-built objects back to mitigate recomputation. the general strategy to avoid this issue is to make copies of any inputs that there is any risk of mutating before operating on them.
two cases were causing unexpected behaviors:
the issue lies in how the backend passes objects around and tries to pass already-built objects back to mitigate recomputation. the general strategy to avoid this issue is to make copies of any inputs that there is any risk of mutating before operating on them.