Can someone explain Math.fmod() vs using a % operator?

Question

question

Jonathan asked Dec 01 2020 at 3:19 PM Joerg Vogel edited Dec 01 2020 at 10:57 PM

Can someone explain Math.fmod() vs using a % operator?

Working on a decision point in Flexscript I wanted to use a modulo math operator like I can within Excel. I started tinkering with this:

if (current.labels.assert("roundRobinVal", 1).value % 2) == 0) {...then do stuff...}

But no matter what I did the % did not seem to behave like I anticipated.

I then found Math.fmod() and made this:

if (Math.fmod(current.labels.assert("roundRobinVal", 1).value, 2) == 0) {...then do stuff...}

and it worked perfectly.

I am incrementing the roundRobinVal after the if().

I also don't understand the ", 1" in the latter portion of the .assert().

Software Version:

FlexSim 20.2.3

flexscript flexsim 20.2.3 math fmod

______

Cookie preferences

Your privacy is important to us and so is an optimal experience. To help us customize information and build applications, we collect data about your use of this site.

May we collect and use your data?

Learn more about the Third Party Services we use and our Privacy Statement.

Strictly necessary – required for our site to work and to provide services to you

These cookies allow us to record your preferences or login information, respond to your requests or fulfill items in your shopping cart.

YES

Improve your experience – allows us to show you what is relevant to you

These cookies enable us to provide enhanced functionality and personalization. They may be set by us or by third party providers whose services we use to deliver information and experiences tailored to you. If you do not allow these cookies, some or all of these services may not be available for you.

YES

NO

Customize your advertising – permits us to offer targeted advertising to you

These cookies collect data about you based on your activities and interests in order to show you relevant ads and to track effectiveness. By collecting this data, the ads you see will be more tailored to your interests. If you do not allow these cookies, you will experience less targeted advertising.

YES

NO

Are you sure you want a less customized experience?

We can access your data only if you select "yes" for the categories on the previous screen. This lets us tailor our marketing so that it's more relevant for you. You can change your settings at any time by visiting our privacy statement

Your experience. Your choice.

We care about your privacy. The data we collect helps us understand how you use our products, what information you might be interested in, and what we can improve to make your engagement with Autodesk more rewarding.

May we collect and use your data to tailor your experience?

Explore the benefits of a customized experience by managing your privacy settings for this site or visit our Privacy Statement to learn more about your options.

Answer 1 · 2020-12-01T17:38:44Z

Matthew Gillespie answered Dec 01 2020 at 5:38 PM

The F in fmod stands for float and doesn't round to the nearest integer like % does, for example:

3.4 % 2                  //    1
Math.fmod(3.4, 2)        //    1.4

· 1

Answer 2 · 2020-12-01T15:28:43Z

Jason Lightfoot answered Dec 01 2020 at 3:28 PM Jason Lightfoot commented Dec 01 2020 at 5:16 PM

The 1 is the initial value of the label in the assert -so the value it will take if it didn't exist.

The % operator should work exactly as fmod - can you post an example?

· 6

Jonathan commented · Dec 01 2020 at 3:32 PM

This works like I intended:

if (Math.fmod(current.labels.assert("roundRobinVal", 1).value, 2) == 0)

{newDest = current.outObjects[1];}

else

{newDest = current.outObjects[2];}

current.labels.assert("roundRobinVal", 1).value++;

This did not:

if ((current.labels.assert("roundRobinVal", 1).value % 2) == 0)

{newDest = current.outObjects[1];}

else

{newDest = current.outObjects[2];}

current.labels.assert("roundRobinVal", 1).value++;

0 ·

Jason Lightfoot ♦♦ Jonathan commented · Dec 01 2020 at 3:41 PM

I meant in a model where we can step through and see if something funky is happening, since the description you gave is perfect and should work as far as I can tell.

You could try stepping through with the debugger and put expressions in the watch list to see what everything is evaluating to.

1 ·

Jonathan Jason Lightfoot ♦♦ commented · Dec 01 2020 at 3:58 PM

I've already implemented and saved over using Math.fmod() and it's working now.

What it seemed to be doing is that the even values never evaluated to a 0 remainder with "% 2".

As far as the debugger I haven't used that yet. I'm not sure how to put in breakpoints and watch specific variables in flexsim.

0 ·

Show more comments

question