topic Re: the model stops itself before its stop time in FlexSim Forum

the model stops itself before its stop time

moosa — Mon, 03 Apr 2023 15:47:44 GMT

[ FlexSim 23.1.0 ]

Please find the attached model, this model stops itself before its allotted stop time.when I run with 3 independed scheduled tokens it stops at some 150000; but the same model if run with 2 scheduled tokens stops after it transverses all the rows of the assigned global table.Please note that I will have to extend this logic for 25 different tables,for now in this model I am trying with 3 tables , but i am not successful in establishing the complete logic, but the logic works well for 2 tables.TRANSPORTATION_LOGIC_rev02.fsm

Re: the model stops itself before its stop time

jason_lightfoot_adsk — Mon, 03 Apr 2023 15:51:32 GMT

rm301_row_decide sends the only token remaining to the sink at time 2563929.82 as a result of testing if x<y and evaluating to false where:

int x=token.index;
int y=Table("rm302").numRows/96-1;

Re: the model stops itself before its stop time

moosa — Mon, 03 Apr 2023 16:05:25 GMT

it is true when 2 tokens are running , but when 3 tokens are used it stops at 156,998.94 seconds, which cant be true as the model has to run until 2563838.832 seconds.

Re: the model stops itself before its stop time

jason_lightfoot_adsk — Mon, 03 Apr 2023 16:06:44 GMT

Is that a different model? Post the model you want explaining with it set up to run the relevant case.

Re: the model stops itself before its stop time

moosa — Mon, 03 Apr 2023 16:10:12 GMT

its the same model attached with 3 scheduled sources, only that i have not attached the third schedule source to the process flow block.

Re: the model stops itself before its stop time

jason_lightfoot_adsk — Mon, 03 Apr 2023 16:17:50 GMT

You have an infinite loop of zero time events.

Re: the model stops itself before its stop time

moosa — Mon, 03 Apr 2023 16:25:15 GMT

so how do i remove it ??it would be helpful if you could support me with this.

Re: the model stops itself before its stop time

jason_lightfoot_adsk — Mon, 03 Apr 2023 16:49:45 GMT

Well the delay is reading token.hour which is -25287 which evaluates to zero.

In the production time decision code, x (6) is not equal to y (108) so the token goes to exit 2.

You can place breakpoints in your code to see what's going on with the local variable values.

Re: the model stops itself before its stop time

moosa — Mon, 03 Apr 2023 18:17:02 GMT

well i did have a look over code, it works fine until I dont add more than 2 resources, but eventually i need a robust process flow which could be easily extendable.Is there any suggestion or guidance you could give me?

Re: the model stops itself before its stop time

jason_lightfoot_adsk — Mon, 03 Apr 2023 20:20:09 GMT

If you want it to be scaleable then you should probably use object process flows that relate to the presence of 3D objects (what is this model doing - how are you going to scale it?)

Re: the model stops itself before its stop time

moosa — Mon, 03 Apr 2023 20:31:07 GMT

well unfortunately object process flow is not feasible in this case, as we push one input into one list(chafers) with partition id as item.Type ,and then again pull a certain values from that list matching with a global tables (rm301,rm302,....) .In this case we shall have 22 global tables and I believe that global tables cant be parameterized and also the conditions vary a lot.

Re: the model stops itself before its stop time

jason_lightfoot_adsk — Mon, 03 Apr 2023 21:51:17 GMT

Well the fact that the processes are identical indicate to me that you should only have one definition of it and many parameterized instances. The pull from list requirement is just looked up from its own global table. If you have 22 instances (RM301-RM322) then you could use a label on each to store the table instead of calling global tables 'rm301'. But since you look to be importing to those Global Tables already, I'd have a label (called eg. 'globTable') on the M301-M322 objects that points to the correct global table data. Then you can just refer to the table using:

Table(current.globTable)[token.index+1][4]

and so this is totally parameterizable for an object process flow.

Re: the model stops itself before its stop time

moosa — Tue, 04 Apr 2023 08:18:43 GMT

well it sounds interesting , how is that we link an object to the global table? as I am not able to link them, like linking a queue RM302 to table RM302, so that I could access the whole table on the object process flow.

Re: the model stops itself before its stop time

jason_lightfoot_adsk — Tue, 04 Apr 2023 10:00:47 GMT

transportation-logic-rev02_jl.fsm

Here's an example with a new object process flow. I set a pointer to the table at reset using

current.curingTable=reftable(current.name)

but you could also just use Table(current.name) in the references for the table.

Re: the model stops itself before its stop time

moosa — Tue, 04 Apr 2023 10:16:22 GMT

thanks for this object process flow, but unfortunately I have the same output , the model stops in after 156998.94 seconds and the value of hour has value -25287, this doesnt occur when I connect 2 objects RM301 and RM302.

Re: the model stops itself before its stop time

jason_lightfoot_adsk — Tue, 04 Apr 2023 11:38:12 GMT

You set token.hour to -25287 in the activity "waiting_time_for nextchafer" since x is 131711 and y is 156998 and token.hour is set to the difference : X-Y.

This code I think assumes that the X time is in the future but in fact it's in the past resulting in the negative time.

In the "production_time" decision, Instead of testing X==Y (you should never test doubles like this) you should check if X<Y.

Also - instead of X, call it "schedProdTime" and then you can just test schedProdTime< time() instead of X and Y which don't convey any meaning.

Re: the model stops itself before its stop time

moosa — Tue, 04 Apr 2023 12:26:14 GMT

well the problem is when the time is equivalent to the scheduled time on the global table only then the pull request should be made else the task executor is to wait, if at the same instant of time we have 2 requests then the dispatcher should use the second task executor.If I use the condition X<Y then it will abruptly pull from the list which is not my motive, my target is :the list is being filled up while it is being emptied from the matching label and time from the global table.

Re: the model stops itself before its stop time

jason_lightfoot_adsk — Tue, 04 Apr 2023 12:28:34 GMT

Use a process to push to the list that is separate from the pulling process. Only push to the list when it should get on the list.

Re: the model stops itself before its stop time

moosa — Tue, 04 Apr 2023 12:45:09 GMT

well i tried doing it but was not successful, as shown ,firstly I was pushing all the items being produced into a list , then pull it back and then pushing into another list as per the requirement and then pulling it when the schedule time comes in, Tbh i am not sure you suggested something like this.Please note that the input list is producing several items at different times while the output lists is waiting for the scheduled time for the output to be delivered.

Re: the model stops itself before its stop time

jason_lightfoot_adsk — Tue, 04 Apr 2023 12:49:50 GMT

Don't do this in the object process flow instance - it's a seperate process.

You can remove the delays from your pulling process and check for producton time, since when you get to the Pull From List anything on the list is valid to be pulled.