How to use A * when I create task executer using process flow?

Question

question

Craig DIckson asked Apr 25 2020 at 12:30 AM Matthew Gillespie edited May 12 2020 at 12:48 AM

How to use A * when I create task executer using process flow?

I defined a class of task executers using the flow item bin, and set it to use A*. But when I use process flow to create those task executers, the resulting TEs aren't in the A*. Is there a simple way to make sure they use A*? (If not, is there a complicated way? LOL)

Also I am using 20.1.1 but that's not in the pulldown below yet.

Software Version:

FlexSim 20.1.0

process flow flexsim 20.1.0 a star

______

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-04-25T05:01:51Z

Matthew Gillespie answered Apr 25 2020 at 5:01 AM Matthew Gillespie edited May 12 2020 at 12:48 AM

Here are the ways to do it currently:

1. In a custom code block after you create the person, use this code to attach the person to the A* Navigator

contextdragconnection(Model.find("AStarNavigator"), token.Person, 'A');

2. In the Create Object activity choose Create In and create the person in the A* Navigator, this will attach the person to the navigator. You might then need to move the person to where you actually want them.

3. Use the Create Person activity instead of Create Object. The Create Person activity automatically does this if there's an A* Navigator in the object. Note, however, that by adding this People activity it will also add a bunch of People groups, lists, and down behaviors to the model as well.

· 4

Craig DIckson commented · Apr 26 2020 at 5:18 PM

@Matthew Gillespie First, to be clear I am not creating people; I am creating AMRs (Automated Mobile Mobots, the generic name for what Kiva does -- basically a smarter AGV). Can I use "create person" for this? (The main reason I am using process flow to create them is because there are a couple hundred of them in the facility; I was trying to save the tedium of creating them individually in 3d, and also to allow fewer in a particular run without worrying about parking out of the way.)

When I create the AMR in the A*, the model stops with the token at that activity, and when I reset it it seems like the Create activity at the top is disabled, and I need to either replace it with a new Create activity, or restart the model.

If I use the custom code block, it almost works, except that 1.) the graphics of my AMR are gone -- all that moves is the blue collision circle and 2.) when I reset the model the created AMR is still shown in the A* list, so after a few runs I end with qith quite a number of extra non-existent AMRs. So I suppose I need a trigger to clear all traveler members from A* on reset? What would that code look like?

0 ·

Matthew Gillespie ♦♦ Craig DIckson commented · Apr 27 2020 at 8:34 PM

OK, I see. It looks like the Add a New Task Executer Flowitem option in the FlowItem Bin doesn't quite set up the new TE flowitem correctly. We'll get that fixed. If you want to fix it in your model you can run this script:

treenode bin = Model.find("Tools/FlowItemBin");
for (int i = 1; i <= bin.subnodes.length; i++) {
    treenode obj = bin.subnodes[i].first;
    if (isclasstype(obj, "TaskExecuter")) {
        assertattribute(obj, "itemtype", 0);
        rebindobjectattributes(obj);
 
        treenode resetPosition = getvarnode(obj, "resetposition");
        clearcontents(resetPosition);
        set(resetPosition, 0);
    }
}

After doing that methods 1 and 2 should work fine.

0 ·

Craig DIckson Matthew Gillespie ♦♦ commented · May 11 2020 at 5:23 PM

@Matthew Gillespie So do I run this in a custom code activity each time I run the model? Or just once in the Script console?

And whichever I do, does that mean that the new AMR task executers do go away when I reset, so I can create the correct number of them each time the model runs, which is what I was hoping to do?

Thanks!

Craig

0 ·

Show more comments

question