Lanner Group WITNESS Hints & Tips Service summary

Page 1 of 13
Author: Lanner Group Customer Support Centre
WITNESS Hints & Tips
Version 3.5
14/06/01
Lanner Group WITNESS Hints & Tips Service summary
Page 2 of 13
Author: Lanner Group Customer Support Centre
Overview
How to use this document:
This document will be sent by e-mail to all maintained WITNESS customers who
wish to receive it. The mail will be sent out periodically with a selection of hints &
tips to help you use your WITNESS system more effectively. Each issue more tips
will be added and the contents list will be updated. To remove yourself from the
list of people who receive this mail please reply to this e-mail with the text
REMOVE in the subject field.
To search for a tip relating to a particular area then you can use the Find option
from the Tools menu.
The Whats New section in this document will contain a brief summary of new
tips in this issue.
In the body of detail for each tips there will be a reference to the Tip number on
our Web site www.lanner.com if the tip is included there in the Support page.
Where there is an example model for the tip you can download this from the Web.
You may need to Register for on-line support which can be done from the
support page. We will mail you back with the User name and Password. The
address direct to the relevant tip is given. Clicking on this will take you directly to
the tip on the Web.
Whats New
New tips this issue:
Tip 3.021: Property Actions for all elements.
Tip 3.022: In-place editing of path display.
Tip 3.023: The use of model buttons in WITNESS 2001.
Tip 3.024: How to record the run time for your model.
Tip 3.025: Buffered Metafile drawing.
There is also a direct reference to the tip on the Web where relevant. See above
for details.
Lanner Group WITNESS Hints & Tips Service summary
Page 3 of 13
Author: Lanner Group Customer Support Centre
Overview................................................................................................................................................2
Whats New.......................................................................................................................................2
Modelling tips.......................................................................................................................................4
Tip 3.001: Labour moves a batch of parts...........................................................................4
Tip 3.002: Different cycle times on machines. ...................................................................4
Tip 3.003: Customer tip: Documenting Part Routes in Excel. ......................................5
Tip 3.004: How to model a machine which processes parts in batches where the
batch size may vary......................................................................................................................5
Tip 3.005: How to model a machine which can setup after its cycle.........................5
Tip 3.006: Randomly select between two identical machines / activities with a
50/50 chance of selecting either one.....................................................................................6
Tip 3.007: Fixed maintenance schedule for machines. ...................................................6
Tip 3.008: How to move windows when you can not see the title bar. ....................7
Tip 3.009: How to load a model when you open WITNESS . ........................................7
Tip 3.010: How to stop your model running when all jobs are finished...................7
Tip 3.011: An assembly operation requiring different quantity of material............8
Tip 3.012: Customer tip: Excel Link Advice. .......................................................................8
Tip 3.013: Changing the name of an element based on a value read from Excel.9
Tip 3.014: Different setup time for each cycle of a multi-cycle machine / task of
a multi task activity. .....................................................................................................................9
Tip 3.015: How to rewind a read file......................................................................................9
Tip 3.016: The use of the MATCH rule...................................................................................9
Tip 3.017: The use of WITNESS system variables..........................................................10
Tip 3.018: How to create a message box that gives a message such as
"Simulation is finished "............................................................................................................10
Tip 3.019: Moving a batch to queue / buffer. ...................................................................11
Tip 3.020: How to easily get the total Work in Progress or Total Number
Shipped for all parts or entities in your model.................................................................11
Tip 3.021: Property Actions for all elements.....................................................................11
Tip 3.022: In-place editing of path display. ......................................................................12
Tip 3.023: The use of model buttons in WITNESS 2001. .............................................12
Tip 3.024: How to record the run time for your model. ................................................13
Tip 3.025: Buffered Metafile drawing...................................................................................13
Lanner Group WITNESS Hints & Tips Service summary
Page 4 of 13
Author: Lanner Group Customer Support Centre
Modelling tips
Tip 3.001: Labour moves a batch of parts.
This is Hint #67 on our Web site.
http://www.lanner.com/Secure/Tips/hint67.html An example model can be
downloaded from the Web.
This model shows how one or more labour can be made to move a batch of parts.
The machine Shelf is a batch machine with a batch quantity of 10. One Man1 is
required to load the parts into the machine. This is achieved by the rule
IF NPARTS (StageTable) = 10
MATCH/ANY Core out of StageTable With Man1 Using Path #(1)
AND Core out of StageTable Using Path #(9)
ELSE
Wait
ENDIF
Two Man2 are required to unload the machine. This is achieved using the output
rule
IF NAVAIL (Man2) = 2 AND NPARTS (ELEMENT) = 10 AND M = 1
PUSH to OutBuffer With Man2#(2) Using Path
ELSEIF NPARTS (ELEMENT) < 10
PUSH to OutBuffer Using Path
ELSE
Wait
ENDIF
The check in the output rule is necessary to prevent the parts moving without the
labour if the labour is not free.
In Model / Options on the Paths tab the "Enable Labour Walk To Idle" and "Enable
Labour Walk To Move Parts" options have been checked. Also the "Pseudo Path
Traverse Time" has been set to PATHLENGTH (ELEMENT) / 10.0. This ensures the
traverse time is proportional to the distance between elements (in this case divide
by 10 is a speed up factor).
Tip 3.002: Different cycle times on machines.
This is Hint #2 on our Web site. http://www.lanner.com/Secure/Tips/hint2.html
An example model can be downloaded from the Web.
Parts have different cycle times on machines as shown below.
Machine
Mach001 Mach002
Part001 9.247 9.739
Part002 8.728 8.685
Rather than using if statements each time a part enters a machine, use a variable
and an attribute to reference the cycle time.
Lanner Group WITNESS Hints & Tips Service summary
Page 5 of 13
Author: Lanner Group Customer Support Centre
Tip 3.003: Customer tip: Documenting Part Routes in Excel.
This is Hint #71 on our Web site.
http://www.lanner.com/Secure/Tips/hint71.html An example model can be
downloaded from the Web.
This tip was supplied by a customer. The customer wanted to document part
routing detail from his model. There is no WITNESS utility which does this
directly. What the customer did was to write an Excel macro which searches the
library file and extracts part routing information. This is then written to the Excel
sheet. The model, library file and Excel workbook are supplied.
If any customer have any similar utility which they would like to share then
please send them in.
Tip 3.004: How to model a machine which processes parts in
batches where the batch size may vary.
This is Hint #70 on our Web site.
http://www.lanner.com/Secure/Tips/hint70.html An example model can be
downloaded from the Web.
This model shows how you may set up a machine which can process batches of
parts where the batch quantity varies between part types. This could be a
requirement in manufacturing where the batch size may be dependant on a
certain feature of the parts. This may apply in process industries too.
The model achieves this with a simple example. The parts are created with a
random pen number between the value of 1 and 6. In this example the batch size
required is the same as the pen number. In actions on input to STORE001 a check
is made to see if a batch of the part entering the buffer is now available for
processing. If here is a batch then the attribute Readytogo is set to the value 1
for the part entering. The input rule for STORE001 ensures that a batch is pulled
from the buffer. The first part to be pulled is the part with Readytogo set to 1.
The second part of the input rule
MATCH/CONDITION (PEN = ELEMENT:PEN) STORE001 #(PEN - 1)
ensures that the remainder of the batch is taken.
In reality the batch size for each part type may be referenced in a variable array.
Part type may be defined by a user defined attribute.
Tip 3.005: How to model a machine which can setup after its
cycle.
This is Hint #69 on our Web site.
http://www.lanner.com/Secure/Tips/hint69.html An example model can be
downloaded from the Web.
WITNESS machines can only setup before they cycle. In many real modelling
situations setups may occur after a machine has cycled. The model shows how
this can be achieved. This is done by making the machine a multi-cycle machine.
The first cycle is the normal cycle of the machine. The second cycle is a dummy
cycle with a cycle time of zero. The setup will be checked before every cycle, so in
Lanner Group WITNESS Hints & Tips Service summary
Page 6 of 13
Author: Lanner Group Customer Support Centre
this case the setup is triggered by value change of the variable setmachine. This
is checked and changed at the end of the first cycle. In the model the setup will
occur for every part. You could change the condition here to reflect reality for
your model. The finish quantity for cycle 1 is 2 and the output quantity is 1. This
creates a second part at the end of the cycle. The actions on finish of cycle 1
change the second part to type dummy. The output rule pushes the original part
to ship. You would push the part to the next stage in your process here. The
dummy part stays at the machine for the setup and the dummy part is used for
the setup and cycle 2. In this way the original part leaves the machine at the end
of the first cycle and the setup then occurs.
Tip 3.006: Randomly select between two identical machines
/ activities with a 50/ 50 chance of selecting either one.
This is Hint #1 on our Web site. http://www.lanner.com/Secure/Tips/hint1.html
An example model can be downloaded from the Web.
Random selection between two identical machines / activities with a 50/50
chance of selecting either one. If the machine / activity selected is busy, select
the other one (if available). Both machines / activities will be utilised equally over
time. Note that the machine / activity dummy is used to pull the parts / entities
from the buffer / queue and an attribute x is set in actions on finish. This is where
the 50/50 sample is taken. This ensures that if both machines / activities are
unavailable then the sample will not be taken again. This is a more accurate
model since x will not change for any specific part / entity.
Tip 3.007: Fixed maintenance schedule for machines.
This is Hint #3 on our Web site. http://www.lanner.com/Secure/Tips/hint3.html
An example model can be downloaded from the Web.
The following is a method for modeling a predetermined preventative and fixed
maintenance schedule for a work area with several machines of the same type
(defined in WITNESS as a machine element with a quantity > 1). For example,
you may have 5 milling machines of the same type on which you want to perform
preventative maintenance. The idea is to perform preventative maintenance
individually, on a weekly basis, so they will not all be out of service during a busy
production period.
In WITNESS, the standard method for modeling a fixed preventative maintenance
schedule for a machine involves adding a breakdown activity to the detail of the
machine, setting the Breakdown Mode to Available Time, and entering a value for
Time Between Failures and for Repair Time. Unfortunately, if you have a quantity
of greater than one for this machine, ALL of the machines will breakdown at the
same time.
The solution offered here is to use Forced Breakdown and Repair functions (new
in WITNESS 8.0) to force each of the machines of a given type first to breakdown
at a particular system time, then to repair at a later time.
System time values when each machine is scheduled to start and finish its
preventative maintenance period are read into the variable SCHEDULE from the
read file DOWNSCHD in Model/Initialize Actions. The Actual data file is
DOWNSCHD.TXT and is shown in the table below. This schedule is repeated every
36 hours. Two dummy machines and a dummy part are used to check the
variable SCHEDULE every 2 hours.
Oven
Lanner Group WITNESS Hints & Tips Service summary
Page 7 of 13
Author: Lanner Group Customer Support Centre
Time 1 2 3 4 5 6 7 8 9
Down 2 6 10 14 18 22 26 30 34
Up 4 8 12 16 20 24 28 32 36
Tip 3.008: How to move windows when you can not see the
title bar.
This is Hint #72 on our Web site.
http://www.lanner.com/Secure/Tips/hint72.html
Sometimes you may find that the title bar of your windows cannot be seen so that
you can not move that window. The window can be moved using some standard
functionality of windows applications. You can use the keyboard to reposition the
window.
Make the required window active. Use Alt and - to select the system menu for
that window Select M to Move. The cursor keys can then be used to position the
window.
Note also that Alt and spacebar can be used to reposition the currently selected
application.
Tip 3.009: How to load a model when you open WI TNESS .
This is Hint #73 on our Web site.
http://www.lanner.com/Secure/Tips/hint73.html
By default, WITNESS will load startup.mod when you open WITNESS from the
start menus. You may wish to create a shortcut to load your own startup model or
a project model. This can be done by creating a shortcut to WITNESS first. This
can be done by right-clicking on witness.exe from windows explorer and selecting
"create shortcut". This shortcut can then be dragged on to your desktop to create
a shortcut there. To specify the model to open you should add a second
parameter which must be the model name including its path. This parameter
should be in double quotes. If there is a space in the folder name you will need to
download the latest upgrade which allows spaces in the model folder name. The
full command line will look something like this -
"C:\Witness 2000\witness.exe" "C:\My models\Mystartup.mod"
Tip 3.010: How to stop your model running when all j obs are
finished.
This is Hint #74 on our Web site.
http://www.lanner.com/Secure/Tips/hint74.html An example model can be
downloaded from the Web.
When running your model you may not know how long you need to run it. You
may be investigating how options may affect the time to process a certain
number of jobs. This model shows one way in which this can be achieved. The
variable totalWIP is updated in actions on create and actions on leave for the
jobs. In actions on leave there is a check to see if this value is zero. If totalWIP is
zero then the STOP action is used to stop the model run. Note also that the string
variable message is set and the OPENWIN action used to display a message.
Please note that this method assumes that there will always be jobs in the system
until the last one is complete.
Lanner Group WITNESS Hints & Tips Service summary
Page 8 of 13
Author: Lanner Group Customer Support Centre
Tip 3.011: An assembly operation requiring different quantity
of material.
This is Hint #7 on our Web site. http://www.lanner.com/Secure/Tips/hint7.html
An example model can be downloaded from the Web.
The main objective of this example is to show you an applicable example on how
to combine Sequence rules with Name and Integer variables. This example will
also review some tips on how to use Read files, variable input quantity for
assembly machines, and elements with multiple quantities.
The following description will describe the system layout as well as giving you
some additional information on the basic operation of the plant.
Five different parts or materials are assumed to be always available at the
beginning of this model. Whenever needed, a feeder station pulls these parts into
the system. The goal of this station will be to replenish a material storage area,
located right before an assembly machine. The feeder station contains five
different machines. Each one of these machines is dedicated to one specific
material and has a different cycle time (1, 2, 3, 4, 5 minutes for feeders 1
through 5, respectively). The material storage area contains five groups of
buffers, one for each type of material. The number of buffers for each group
varies between two and four: three for the group of buffers for materials one and
five, four for the groups of buffers for materials two and four, and two for the
group of buffers for material three.
As the different materials are being sorted into their respective buffers, the
assembly machine should be ready to start the assembly of the first combination
of materials. The assembly machine in this model could be an automated machine
that can assemble parts based on a combination of various materials and
quantities. If needed, this machine is also capable of running a combination more
than once before switching combinations. The data for this machine should be
contained in an external file so that the modeler can experiment with the
production schedule. The external file should contain at least the following
information: The name of the buffer group from where the parts should be
retrieved, the number of parts to be taken from each buffer group, and the
number of consecutive assemblies to be performed before switching
combinations. Assume that the cycle time for each assembly combination is 10
minutes. Once an assembly operation has taken place, the finished part should
leave the system and a counter for each type of assembly operation should be
kept.
Tip 3.012: Customer tip: Excel Link Advice.
This is Hint #75 on our Web site.
http://www.lanner.com/Secure/Tips/hint75.html
This tip was supplied by a customer. There are many things that can affect the
performance of linkage between WITNESS and Excel. Operating system, Memory,
Other applications running can all change the robustness and operation of the
link.
One user has reported the following two tips that may help :
i) Disabling the Analysis Toolpak in the Excel Add-ins menu prevented a lock up
on his system
ii) Opening Excel before running WITNESS. This user found that this was
necessary on his machine if he wanted to run an Excel linked WITNESS model
immediately after booting up.
Thanks to our customer for this advice.
Lanner Group WITNESS Hints & Tips Service summary
Page 9 of 13
Author: Lanner Group Customer Support Centre
Tip 3.013: Changing the name of an element based on a
value read from Excel.
This is Hint #76 on our Web site.
http://www.lanner.com/Secure/Tips/hint76.html An example model can be
downloaded from the Web.
This functionality was requested twice in the same week by customers. In the
model it is achieved by constructing a string 'wclstr' containing the commands to
change the name of Store001 to the value read from the Excel sheet. These
commands are then run as a SETINFO call from the initialise actions of the
variable 'Storename'. The capacity of the buffer / queue is also set in these
actions based on the value read from the Excel sheet. Beware! Once you have run
the model you should not save it since the SETINFO WCL call will not work with
the buffer / queue name changed from its initial value.
Tip 3.014: Different setup time for each cycle of a multi- cycle
machine / task of a multi task activity.
This is Hint #77 on our Web site.
http://www.lanner.com/Secure/Tips/hint77.html An example model can be
downloaded from the Web.
The model shows how you can model a different setup times for each cycle of a
multi-cycle machine / task of a multi task activity. To create a setup at each stage
in the process the setup is triggered by 'Value Change' where the value chosen is
'CYCLE (ELEMENT)'. The system variable ELEMENT is Process (1) in this case. The
function CYCLE returns the number of the current cycle. There are 3 cycles at
Process so this is guaranteed to change at each cycle. The setup time is detailed
as SetTime (CYCLE (ELEMENT)) which takes the appropriate value from the array
SetTime. Run the model and the messages in the interact box give confirmation
of the start and end time of each setup.
Tip 3.015: How to rewind a read file.
This is Hint #78 on our Web site.
http://www.lanner.com/Secure/Tips/hint78.html
In your model you may want to close a file if, for example, you need to read the
values in two different places. The CLOSE action applies to write files only. There
is no inbuilt function which will rewind a read file. What you could do is to use the
SETFILE function. The parameter for this is the file's actual name. You should
make this the same as the name already specified on the machine's detail. In this
way the file's actual name remains the same and the read file is rewound. The
next read statement will read the first line.
Tip 3.016: The use of the MATCH rule.
This is Hint #79 on our Web site.
http://www.lanner.com/Secure/Tips/hint79.html An example model can be
downloaded from the Web.
This tip was presented at the UK User Group on 15
th
May 2001.
Lanner Group WITNESS Hints & Tips Service summary
Page 10 of 13
Author: Lanner Group Customer Support Centre
The MATCH rule in WITNESS is extremely powerful. The on-line help system
describes how you can use this to input a matched set of parts/entities and/or
labour/resource units to a machine/activity, or as a labour/resource rule to match
labour/resource units for a job at that element. One useful feature of the rule is
that nothing will move until all components required to satisfy the rule are
available. They will then all move together. Please note the importance of the
'Output option' for Store1. This is set to 'Any' which ensures that any job
satisfying the rule can be taken.
In the model you can select from the drop down list which MATCH rule to use. The
five on offer are those given as examples in the on-line help system. The rule
currently selected is displayed on the 'Main View' window.
The choice of rule makes use of the new dialog functionality in WITNESS 2000.
This is run from initialise actions and can also be run at any time by stopping the
model and running User Actions. The options available are described within the
help system.
Tip 3.017: The use of WI TNESS system variables.
This is Hint #80 on our Web site.
http://www.lanner.com/Secure/Tips/hint80.html An example model can be
downloaded from the Web.
This tip was presented at the UK User Group on 15
th
May 2001.
Within WITNESS there are a number of system variables which can be very useful
in modelling. Note that when you use these variables from actions within a
function they will always refer to the element that is calling the function.
ELEMENT - This name variable will return the name of the current element. If the
element is of quantity greater than one the index will be included. So in actions
on finish of an element "process01" of quantity 3 ELEMENT will return process01
(2) in any actions or rules within the second instance of process01.
N - This integer variable returns the index of the current element. So, if you have
a machine / activity "process01" of quantity 3, N will return the index number of
the current element.
M - This is an integer variable that holds the item number within a lot or batch.
This can be useful within actions on finish or the output rule of a production
machine / split activity. Each part / entity could have different actions applied or
a different output rule applied.
I - This is an integer variable that holds the index of the current vehicle.
VTYPE - This name variable holds the name of the current vehicle or NONE if no
vehicle is present.
TIME - This is a real variable that returns the current simulation time.
The example model makes use of all of these system variables apart from VTYPE.
Tip 3.018: How to create a message box that gives a
message such as "Simulation is finished ".
This is Hint #81 on our Web site.
http://www.lanner.com/Secure/Tips/hint81.html An example model can be
downloaded from the Web.
The function MSGDLG shows a message but the user must click a button. To have
a message only display a string variable on a window and set the value of this
and use the OPENWIN action to show the message. An alternative is to use the
Lanner Group WITNESS Hints & Tips Service summary
Page 11 of 13
Author: Lanner Group Customer Support Centre
PRINT action to display a message in the interact box. In the model look in
actions on leave for Job. This contains examples of all three options. Note the use
of OPENWIN and OPENBOX
Tip 3.019: Moving a batch to queue / buffer.
This is Hint #82 on our Web site.
http://www.lanner.com/Secure/Tips/hint82.html An example model can be
downloaded from the Web.
You may have a situation in your model such that when a buffer / queue has less
than 10 parts /entities. You may want to replenish such that of 100 parts /
entities are in the buffer / queue. The best way to do this is to use a control
variable 'trigger' whose value can be set to '1' in actions out of the queue / buffer.
This will then trigger a dummy batch machine / activity to pull parts / entities in.
You should ensure that 'trigger' is reset to zero when the batch has been moved.
In the model 'Replenish' takes the batch to replenish 'JobQueue'. The part file is
used to initialise JobQueue at time zero.
Tip 3.020: How to easily get the total Work in Progress or
Total Number Shipped for all parts or entities in your model.
This is Hint #31 on our Web site.
http://www.lanner.com/Secure/Tips/hint31.html An example model can be
downloaded from the Web.
This tip was presented at the UK User Group on 15
th
May 2001.
The module here shows how you can get the total number of entities / parts
shipped or their total work in progress. The functions Total.Throughput,
Total.CurrentWIP and Total.AveWIP make use of the functions ELTCOUNT,
ELTNAME and ELTTYPE. They loop though all elements in the model and check if
the part type is the one required (part / entity in this case). If the element is of
the required type then the statistic is taken and summed. To use these functions
you should use Total.Throughput, Total.CurrentWIP and Total.AveWIP in your
actions. In this module parts / entities are the selected type but you could apply
the same principle to other element types and use the relevant WITNESS
functions. To test the functions open your model and then open total.mdl. Run
our model and then run an immediate action such as "PRINT Total.Throughput
()". The total number of parts / entities shipped will be printed in the interact box.
Tip 3.021: Property Actions for all elements.
This is Hint #83 on our Web site.
http://www.lanner.com/Secure/Tips/hint83.html An example model can be
downloaded from the Web.
In WITNESS 2001 you now have the option to have property actions on all
element types. Property actions from a designer element are executed when ever
you create from that designer element. What this means is that you can write a
dialog within these to prompt the user to configure this element when creating
from a designer element.
In the model the property actions prompt you to configure the capacity of the
Lanner Group WITNESS Hints & Tips Service summary
Page 12 of 13
Author: Lanner Group Customer Support Centre
buffer.
Tip 3.022: I n- place editing of path display.
This is Hint #84 on our Web site.
http://www.lanner.com/Secure/Tips/hint84.html
With WITNESS 2001 you have the ability to display paths for conveyors, power
and free conveyors and tracks. This allows you greater control over the display of
these elements. You can display a path which moves around a corner.
You have the option to change the display of a path directly on screen "In Place
Editing".
When in Graphical Edit mode : Select the path on screen, by clicking on any part
of it. Handles will appear to denote the ends of each section, and Arrows appear
between the ends, indicating the direction of flow.
The entire Path display will be moved , if you hold down the mouse and drag the
display. By Pressing CTRL, whilst hovering over an end, "handle", the individual
point can be re-located, If you Press CTRL and click over a direction handle, the
path is split at that point. The New End can then be moved as described above.
Curved paths can be created by the use of multiple short line sections.
Tip 3.023: The use of model buttons in WI TNESS 2001.
This is Hint #85 on our Web site.
http://www.lanner.com/Secure/Tips/hint85.html An example model can be
downloaded from the Web.
WITNESS 2001 now includes the ability to add Model toolbars. Model toolbars
contain actions specific to your model and hence are saved as part of the model
.MOD file and are not available when you load a new model. WITNESS toolbars
contain the standard buttons which were available in previous releases of
WITNESS. Buttons from WITNESS toolbars may be added to Model toolbars by
dragging and dropping them on from the Commands tab on the Customise dialog
but those from Model toolbars may not be added to WITNESS toolbars.
"WITNESS toolbar" settings are stored in the registry and will be restored
whenever you reload WITNESS, regardless of the model.
"Model Toolbar" settings are saved with the model, and are available only when
that particular model is loaded by you or you target user.
The model Maintmenu3 is based around Maintenance.mod which is supplied in
the WITNESS demo folder. The model has a Model toolbar 'User Control Centre'
with two static buttons 'Close' and 'Open', two standard buttons 'Close Window 1'
and 'Open Window 1' and two WITNESS buttons 'Run' and 'Stop'. The name of the
button is what appears as you hover the mouse over the button. The prompt
appears when you press <shift> F1 and then click on the button. The text of the
static buttons is that displayed on the button on the toolbar. For standard buttons
you may also select an icon and you may enter an action which will be run when
the button is pressed. In the model the buttons open / close window 1.
The WITNESS buttons 'Run' and 'Stop' are added to the toolbar by dragging these
from the Command tab in the Customize dialog.
Lanner Group WITNESS Hints & Tips Service summary
Page 13 of 13
Author: Lanner Group Customer Support Centre
Tip 3.024: How to record the run time for your model.
This is Hint #86 on our Web site.
http://www.lanner.com/Secure/Tips/hint86.html An example model can be
downloaded from the Web.
You may wish to get an accurate figure for the actual time it takes WITNESS to
run to run model. The WCL commands TIME_START and TIME_END enable you to
do this. In the WCL file Runtime.wcl TIME_START signals the start of the
recording interval. TIME_END signals the end of the recording interval. The
resulting time, in seconds is written to the file results.dat. To run the example
save Runtime.wcl to the WITNESS demo folder and open it from WITNESS. In the
file you will see the length of time that WITNESS has taken to run BELLS.MOD for
50000 time units. Note that the model is loaded before the batch starts to exclude
model load time from the result.
LOAD BELLS.MOD
TIME_START
BATCH TIME, 50000
TIME_END
Tip 3.025: Buffered Metafile drawing.
This is Hint #87 on our Web site.
http://www.lanner.com/Secure/Tips/hint87.html
WITNESS 2001 offers options for drawing complex drawings more efficiently.
On the Model Options dialog the "Buffered metafile drawing" option allows you to
specify that .emfs (usually imported .dxf files or clipart) should be drawn as
single bitmaps. The product will automatically create internal bitmaps for all .emf
shapes , at the greatest resolution in-use. The product will then draw the bitmap
instead of the .emf, when refreshing the screen in run-mode.
This is particularly effective when you have imported a complex CAD drawing, for
use as a backdrop in your model.
From the menus select Model / Options and check the "Buffered Metafile Drawing"
option. When you have this option selected you will find that the update of the
display of your model in run mode may improve significantly. WITNESS converts
the .emf to a bitmap which can be updated much more quickly for complex
drawings. If your drawing has a background then the "Buffered Metafiles Drawn
Transparent" option may improve the display update further.
You should however be aware that although drawing complex .emfs as Bitmaps
can be significantly faster, simple drawings that cover a large area, are mode
efficiently drawn as .emfs.
Currently this is a global option and applies to all .emf drawing in the model. You
should evaluate its effectiveness, having considered the total balance of the use
of emfs across the entire model.