Network Node errors

Question

question

Lou Keller asked Jul 12, '16 Matthew Gillespie edited Jul 14, '16

Network Node errors

One of my major limiting factors in technical support is the deciphering of cryptic error messages. In the attached model for example, there is a series of error messages that aren't explicitly intuitive to me. Because the model uses 5 different Patient Tracks keyed to different ESIs, the errors are repeated for each track which simultaneously makes life both simpler and more complex. Here are the 7, simultaneous errors...

time: 18.645993 exception: Exception Caught in NetworkNode::getSplinePos(int port, double perc, double * returnloc) object: /NN12

time: 18.645993 exception: Exception Caught in NetworkNode::getPlaceOffset(treenode traveler, treenode reqnode, int port, double* returnarray) object: /NN12

time: 18.645993 exception: Exception Caught in NetworkNavigator::navigateToObject(treenode traveler, treenode destination, double endspeed) object: /DefaultNetworkNavigator

time: 18.645993 exception: Exception Caught in TaskExecuter::beginTask(treenode task) object: /ESI Level 3_ID1

time: 18.645993 exception: Exception Caught in TaskExecuter::finishTask(treenode task) object: /ESI Level 3_ID1

time: 18.645993 exception: Exception Caught in TaskExecuter::onTimerEvent(treenode involved, int code, char *datastr) object: /ESI Level 3_ID1

time: 18.645993 exception: Exception Caught in ObjectFunction237__project_library_FlexSimObject_behaviour_eventfunctions_OnTimerEvent object: /ESI Level 3_ID1 i: /ESI Level 3_ID1>variables/activetasksequence/ts1/task1 class: /ESI Level 3_ID1

The bottom line is that I suspect some, if not all, of the problems may be the result of the user either working in the Tree with little if any knowledge of its purpose or function, or manipulating various object characteristics as a matter of simple curiosity. Whatever the case, their immediate question is, "why aren't there any arrivals in the model?" What I need is a simple explanation of the errors and what generated them so I can repair the model, educate the user and get on with equally important items.

Software Version:

FlexSim HC 5.0.12

flexsim hc network node error messages tree default network navigator

· 2

5 |100000

Attachments: Up to 12 attachments (including images) can be used with a maximum of 23.8 MiB each and 47.7 MiB total.

Matthew Gillespie ♦♦ commented · Jul 12, 2016 at 04:02 PM

Can you attach the model? If the model is confidential you can make the question private.

Those error messages aren't very helpful if you can't look at the model. You'd need to look at what is happening in the model at time 18.64. Otherwise all I can infer is that the first patient is trying to travel on a network node and can't for some reason.

0 ·

Lou Keller commented · Jul 12, 2016 at 04:07 PM

You are absolutely right! My error. Here you are: crmhedver5-lou.fsm

0 ·

crmhedver5-lou.fsm (3.2 MiB)

Answer 1 · 2016-07-12T19:17:08Z

Matthew Gillespie answered Jul 12, '16 Matthew Gillespie commented Jul 13, '16

You're seeing this issue because there are two Default Network Navigators in your model. It looks like you somehow moved the original one into the tools folder which caused the model to create a new one in the model when it couldn't find the original.

Here is some code that will merge the two navigators together, just run this in a script window and then reset and run:

treenode original = node("Tools/DefaultNetworkNavigator", model());
treenode duplicate = node("DefaultNetworkNavigator", model());

treenode one = getvarnode(duplicate, "nodemembers");
treenode two = getvarnode(original, "nodemembers");

while (content(one) > 0)
	transfernode(first(one), two);
	
one = getvarnode(duplicate, "travelmembers");
two = getvarnode(original, "travelmembers");

while (content(one) > 0)
	transfernode(first(one), two);
	
destroyobject(duplicate);
transfernode(original, model());

· 3

5 |100000

Attachments: Up to 12 attachments (including images) can be used with a maximum of 23.8 MiB each and 47.7 MiB total.

Matthew Gillespie ♦♦ commented · Jul 13, 2016 at 06:12 PM

@Lou Keller I had to update the script since the first one didn't fix the issue completely.

0 ·

Lou Keller commented · Jul 13, 2016 at 06:17 PM

Is what's now posted the most current version?

0 ·

Matthew Gillespie ♦♦ Lou Keller commented · Jul 13, 2016 at 06:19 PM

Yes.

0 ·

question