Assign Operators by Code

Question

question

Bryan Suharik asked Dec 12 2016 at 5:29 PM Bryan Suharik answered Dec 13 2016 at 5:31 AM

Assign Operators by Code

Hello,

I have a model that uses a GUI to build the entire model. Because of this, i need quite a bit of flexibility. First, I have the model build processes based on how many the user defines. I also ask the user to choose how many operators the model will have. Based on how many are chosen, the model builds the operators.

I need to assign these operators to all the processors and have the number of processors for the process dependent on item from a global table lookup.

//Builds the operators
for (int ops=1; ops<=MTs; ops++) { 
    createinstance(node("taskexecuters/Operator", library()), model()); 
    treenode Mechanic = last(model());
    setloc(Mechanic, ops,-10,0); 
    setname(Mechanic, concat("Mechanic", numtostring(ops,0,0)));
}

Then I have all the processors built and need the above operators Center attached to all the processors, but only some operators are called depending on the item type in that process.

createinstance(node("/fixedresources/Processor", library), model());
 
treenode bayrepair = last(model());
setname(bayrepair, "BayRepair");
setloc(bayrepair, 0, y, 0);
 
contextdragconnection(Checkin, bayrepair, "A"); 
string ProcessTime =
    "treenode current =ownerobject(c); treenode item = parnode(1); return gettablenum(\"ProcessTimes\",getitemtype(item),2);"; 
setvarstr(bayrepair, "cycletime", ProcessTime);
setvarnum(bayrepair, "nrofprocessoperators", gettablenum("ProcessTimes", getitemtype(item), 3));
contextdragconnection(mechanic, bayrepair, "S");

Basically, via code, I need to assign all the operators in the model to all the processors, but only some operators are called for work depending on the item type that is formatted from the global table.

Thanks for the help! I'm a bit new to this programming and FlexSim, but hope to be able to give help soon!

Software Version:

FlexSim 16.0.6

code operators process operators assignment autobuild

· 1

______

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 · 2016-12-13T05:31:56Z

Bryan Suharik answered Dec 13 2016 at 5:31 AM

I figured it out on combining the string and loop num. Also, using the dispatcher to conduct the tasks helped!

for (int p = 1; p<=MTs;p=p+1)

{

string bayn = numtostring(p,0,0);

string bayn2 = concat("/Mechanic ",bayn);

contextdragconnection(Dispatch,node(bayn2,model()),"A");

}

for (int q = 1; q<=BAYNUMBER;q=q+1)

{

string disbay = numtostring(q,0,0);

string disbay2 = concat("/Repair Bay ", disbay);

contextdragconnection(Dispatch, node(disbay2,model()), "S");

}

Answer 2 · 2016-12-12T22:58:34Z

Joerg Vogel answered Dec 12 2016 at 10:58 PM Ben Wilson commented Dec 12 2016 at 11:38 PM

hmm, you should use names for variable's with more than one character. Some characters are functions or operators in the source code of Flexsim's engine. In really young versions of Flexsim there exited the operator "o". I don't know if the operator has got a function or it is still in use.

Then you should give names to objects with unique names. In the creation of your mechanics you give them all the same name. You can concatenate the name with a number string op_name = concat("Mechanic",numtostring(o,0,0));// "o" should still be named different.

If you call more than one operator to assist a processor you connect the centerport connection to a dispatcher and connect the operators from the dispatcher to them by an object connection "a". A fixed resource can only call directly one operator by a center port connection. And the call isn't linked to the name of the operator. It is linked to a pointer, which is unique to each object in the model even if the name is the same. If you like you can test it on your own. You can set a flowitem to be the selected object so() and write in the script console pf(tonum(so())); If you open an output console and execute the script console the number you see in the output console is different for each different item you select as so().

@Bryan Suharik

· 3

Matt Long commented · Dec 12 2016 at 11:32 PM

You don't have to worry about writing variables that may have been functions or "special" values used by the engine. Once you declare a variable, it overrides whatever that character or word used to mean. You can see this often with c, i, count which are commonly used as variables but which also have special meaning when used in certain ways.

1 ·

Ben Wilson ♦♦ Matt Long commented · Dec 12 2016 at 11:38 PM

Though you can still have problems if you declare a Global Macro with the same name as a variable used elsewhere, so caution in your naming collisions is still warranted.

1 ·

Bryan Suharik commented · Dec 12 2016 at 11:11 PM

Will do, thanks for the tip!

0 ·

question