# Div by zero errors in new nightly

**URL:** https://mworks.discourse.group/t/div-by-zero-errors-in-new-nightly/510
**Category:** Support
**Created:** [July 9, 2015, 1:55pm UTC](https://mworks.discourse.group/t/div-by-zero-errors-in-new-nightly/510 "2015-07-09T13:55:05Z")
**Posts on this page:** 4
**Page:** 1

<div class="post-metadata">

### Author: ![cstawarz](https://yyz1.discourse-cdn.com/flex031/user_avatar/mworks.discourse.group/cstawarz/32/3_2.png) [@cstawarz](https://mworks.discourse.group/u/cstawarz)
#### Post date: [July 9, 2015, 1:55pm UTC](https://mworks.discourse.group/t/div-by-zero-errors-in-new-nightly/510/1 "2015-07-09T13:55:05Z")

</div>

Hi Chris,

I just upgraded our test machines to a new nightly (old: 140512, new: today’s).

I now get these new errors in the console, for the same experiment code:

00:00:05: Loaded wav file (/var/folders/cy/74p2fr416js2y2mbv2bwtgz40000gp/T/MWorks/Experiment Cache/\_Users\_histed\_ExperimentXML-git\_HoldAndDetectConstant\_HoldAndDetectConstant8/tmp/…/wavs/noiseBlob.wav; format=4353, size=960, freq=96000  
00:00:05: ERROR: Division by zero  
00:00:05: ERROR: Division by zero  
00:00:05: ERROR: Division by zero  
00:00:05: ERROR: Division by zero  
00:00:05: Experiment successfully loaded, using protocol: JuiceOnHoldProtocol  
00:00:05: Received new codec, updating variable registry.

I did some digging around on tender and found this:  
[http://help.mworks-project.org/discussions/problems/94-load-time-errors-in-conditional-statements-and-transitions](http://help.mworks-project.org/discussions/problems/94-load-time-errors-in-conditional-statements-and-transitions)

Is that a likely source of the errors? Or might it be coming from somewhere else?  
I don’t know how to debug where these errors are coming from. It’s suboptimal for us where technicians are sometimes running the machines to have them ignore errors on every experiment load, but we can do this.

thanks,  
Mark

---

<div class="post-metadata">

### Author: ![cstawarz](https://yyz1.discourse-cdn.com/flex031/user_avatar/mworks.discourse.group/cstawarz/32/3_2.png) [@cstawarz](https://mworks.discourse.group/u/cstawarz)
#### Post date: [July 9, 2015, 2:04pm UTC](https://mworks.discourse.group/t/div-by-zero-errors-in-new-nightly/510/2 "2015-07-09T14:04:09Z")

</div>

Hi Mark,

There should be some way to eliminate the errors. If you send me a copy of your experiment, I’ll figure out where they’re coming from and how to get rid of them.

Cheers,  
Chris

---

<div class="post-metadata">

### Author: ![cstawarz](https://yyz1.discourse-cdn.com/flex031/user_avatar/mworks.discourse.group/cstawarz/32/3_2.png) [@cstawarz](https://mworks.discourse.group/u/cstawarz)
#### Post date: [July 14, 2015, 3:12pm UTC](https://mworks.discourse.group/t/div-by-zero-errors-in-new-nightly/510/3 "2015-07-14T15:12:35Z")

</div>

Hi Chris,

I thought you might have some immediate ideas, but I was able to zero in on the problem pretty quickly.

There are some assignments in my experiment along the lines of

And as you’ve noted before those are evaluated at load time with the default value of var2, which was zero. Changing the default to 1 fixed the errors. There are no consequences for the experiment because var2 is always set to a value via a prior action before the division action is executed.

Thanks,  
Mark

---

<div class="post-metadata">

### Author: ![cstawarz](https://yyz1.discourse-cdn.com/flex031/user_avatar/mworks.discourse.group/cstawarz/32/3_2.png) [@cstawarz](https://mworks.discourse.group/u/cstawarz)
#### Post date: [July 19, 2022, 10:38pm UTC](https://mworks.discourse.group/t/div-by-zero-errors-in-new-nightly/510/4 "2022-07-19T22:38:48Z")

</div>


