Jump to content

InterruptStep


LizMB

Recommended Posts

I'm having trouble at the interruption step. Yes, I have looked at InterruptibleOperator, InterruptingServerWithMultipleCapacity, InterruptingAcrossMultipleServers. Despite all of that, I still cant figure it out.

Model.thumb.png.26a69f6395d21d4d031151796e15bb4a.png

What I want to happen:

Worker1 carries both entites and drops at respective servers (A/B PICK) and doesn't leave until processed. 

WorkerA/B stops whatever its doing (though it does not stop if transporting) and is siezed when Worker1 brings the entity to A/B PICK. 

Worker1 moves on and WorkerA/B does what it needs to.

 

Here's the deal in WorkerA/B areas:

The worker stays with an entity at serverA/B. Th worker can be interrupted at that process and go to A/BPICK to process the newer entity. The worker can't work on that newer entity right now because there is already an entity in serverA/B. So the newer entity waits at A/BPICK. 

At the gluing servers, the workers only have to get the entity into the processing state, but after that can go grab an entity waiting at A/BPICK and start it at serverA/B.

Once the gluing process is done, it should be a priority to stop working at serverA/B and go take the entity at end of the gluing server to the sink. Then goes back to working at serverA/B.

And the cycle continues. 

 

Here's a youtube video of what happens:

 

 

Here's my add-on processes. I'm only concerned with A path because I can figure out B from A. 

1.png.efdf75f2da5997ba455e7b6f609c93a6.png

 

 

2.thumb.png.35fab0ed34534700aedd31837c265121.png

 

 

3.png.95851e1226171f49dc98d706ffcb9a06.png

 

4.png.b57bdfb8bfbcdcd8e40acb43b2d1bf39.png

^ The idea was to turn the EntA at one of processes that are interrupted to yellow to symbolize the interruption of that entity^

5.png.4533eb810f0ffbf45aba58820a4eb6b9.png

 

ModelForQuestionCOPY4FORUM.spfx

Link to comment
Share on other sites

×
×
  • Create New...