cancel
Showing results for 
Search instead for 
Did you mean: 

Debugging Model Calculation

Former Member
0 Kudos

Hello everybody,

We are having problems in our model calculation and we need to know if its possible to debugging "the model calculation" progress ir order to investigate this issue.

Thanks in advance

Regards

Eduardo del Campo

Accepted Solutions (0)

Answers (1)

Answers (1)

0 Kudos

Hi Eduardo,

Are you getting red "Critical Alert" messages when you calculate your model, or is it just not delivering the results that you anticipated?  Do you have VBA rules in your model?

If you are making use of VBA rules, you can add message boxes to your rules in order to get some feeback on your calculation.  You'd go about it by adding lines of code like this:

MsgBox("This is a test message.")

Thanks,

-Mike

Former Member
0 Kudos

Hi Mike,

We  haven´t "Critical Alert" messages in the model. We have problems in the model calculation when one period stops calculating for example in (S1 24,5%), so this period doesn´t finish.

The model has VBA rules in Resource Drivers and Worksheets (is possible add message boxes there?).

We would like to know what is calculating the model in order to know where is just the moment when the model calculation stops.

Thanks,

Regards

Eduardo del Campo

0 Kudos

OK.  It's tough to say what's going on here without seeing the model. Here's one thing to check:

If your model is sufficiently large & the RAM on your machine is insufficient, you can use up all of the RAM, and things will basically just stall out as you've described.

Watch your ram consumption in Windows Task Manager to rule this out.  I doubt it's what's happening, but let's rule it out.

I might be able to do a Webex or Google hangout with you if you think that might be feasible & helpful.

Best,

-Mike

0 Kudos

One other possibility is that there's a circular reference in your rules.  Usually when this happens, the calculation will restart after it reaches a certain point.

I would consider putting this sort of thing in a bunch of your rules, just to debug this issue:

MsgBox("RuleName")

You can also do things like this in order to know the rule that's being run, and also what versions & periods it's running on.


MsgBox("RuleName " & ItemName(CurrentVersion) & " : " & ItemName(CurrentPeriod))

MsgBox("RuleName " & ItemName(CurrentVersion) & " : " & ItemName(CurrentPeriod)& " : " & ItemName(CurrentRespCenter))

You can do the same thing with other dimensions as well.  This sort of thing can give a lot of insight.  These message boxes clutter up the model alerts, and they can slow the calculation down a little.  You'll want to remove them at some point, but they can be super helpful with debugging.

Former Member
0 Kudos

Thanks Michael,

Im going to test with MsgBox("RuleName") via rules.

Regards