Print Witness Calculated with airSlate SignNow

Print witness calculated

very warm welcome to everybody who has logged in to this second of two paths webinars the first one materials are already available and therefore I do not propose to go through any other material I talked about last time a request just to remind you please to keep your phones muted so that we do not get any sound leakage to spoil the feedback sound that you will hear in the next half hour so I in turn to talk through about five small demonstration models showing various aspects of paths and pseudo paths and I'll finish off doing a quick look at some paths in virtual reality in witness 14 okay the first model I have opened is a model that we did see somewhat of something over last time around and it is using paths and in the previous example I showed the way they use the walk time function to allow the time along the path to vary depending upon the length of the path which can be very convenient especially if you are stretching your paths to lay them out on top of a CAD background however there are times when it is safer for us to set the travel time along paths and explicitly either in witness itself or more likely from Excel so in the case in point I have my path w3 and if I double-click on to it I can see that my path Traverse time rather than using the walk time function uses a variable VR m1 to m2 TT standing for travel time and I set that information case in model initialized actions to 5 time units normally this would be a value reading from Excel for maximum flexibility on the path I have got actions on entry where I record the time when the part arrives on the path and at the end of the path I record the time now - a time when the part arrived to give me the travel time along the path so this is an independent verification that the values are put in are being used correctly and it's always useful when testing your models to have some form of independent checking to make sure it's doing what you believe it should do so if I set mine water running I can see my label walking along the path and I can see the travel time are set in moderniser actions is five minutes here's a time when the Labour Party mence on a path journey and this is a time being updated every time our labor and parts or leave the path so in this case I can extend my path length and I can continue running and I still have the same trouble time okay very simple but very convenient uncertainly with a quieting model I do I choose to have the toggle time set explicitly from data in Excel but tickly if I'm trying to establish the tack time for operators moving around a small cell of machines second model I'm going to show you is to do with changing variable speed along paths will not save the previous one and in this model I have a path which has called walkway and the travel time along the path is using a witness function want I've created myself many of you will be familiar with the built-in functions and witness but hopefully more experience of you will have been able to create and use your own private functions if I look at my path again I'm doing my checking so this when the part arrives on the path I write the time in this case to an attribute on the part and when I leave the path I check the time and print out on the displayed variable so I can see how long the part took traveling along the path if I say my model running I have two part types going along here one which is effectively moving empty a lot quicker than one that is moving full and you can see looking at the variable to the top right at the time along the path varies between seven and 18 time units depending on the part I'm going along if I take a look in the function it is quite a simple function it looks at another attribute which in this case is a string attribute which is set against the part I set that in actions on crater the part or potentially I could set it at the beginning of the operation in or buffer etc so in this case the the path interrogate the part is arrives and if the attribute is thought it gives it a fixed cycle time of 18 time units and if it's empty it uses a quicker travel time of 7 units these values are hard-coded here just for simplicity but you can imagine them being read from a variable array if you have a lot of data that you're entering through Excel close that down if I look at my part very quickly double-click on it on here I am simply randomly sampling every time I create a part that determine whether it's going to be a a loaded a full or empty part and I changed the pen color accordingly so that we have a red and a green part in our model which always aids visual inspection understanding so very simple again but it just shows that we can manipulate our times in a way that we choose fit simply by using a function so that is for a path explicit path element I can do something quite similar on pseudo paths so I shall open another model which is pseudo path there will speed along pseudo paths in this case I have two parts and let me just set them all running and we can see that we have red parts leaving machine one which are moving quickly and we have green parts leaving machine two which are moving rather more slowly and we can see my check time just as I've done in the other models is being time stamping like parts as they join the path and I'm checking the D elapsed time as they leave the path arriving machine 3 and we can see that time as part 8 minutes or 8 tie means for our faster-moving red parts and 32 tongue means for our slow-moving green parts this information is set bras on the path because of course you don't have an explicit path but in model options paths actions on entry to the path my time stamp onto a real attribute a R stands for actual be real which is the naming convention we tend to use to improve clarity and our models and then actions on leave I display a variable a real variable the time now - a time when apart joined the paths to give me my hand shaker back the travel time is a function as you saw before function travel time so let's have a look in that and in this case I'm simply taking the walk time function the default one that we've used and we saw in the previous webinar and I'm either dividing it by 2 or doubling it depending on which part type it is thing to remember is a walk time is derived from dividing the path length in pixels by the walk rate we could easily change the path length by dragging our paths or dragging my machine to a new position to give myself a longer path distance if I wanted to change my walk rate however it's slightly different if I go to model options and paths we can see the walk rate is set as a 1 we can go into this box and type in whatever value we wish but that of course involves us directly interacting in the box walk rate is one of those errors in witness that only evaluates at the beginning of the model run there are several places in witness where is considered potentially dangerous to allow values to be changed whilst the model is running and this is of those so in general we would have to set this up at the beginning of our model run however there is a way around it and it's worth sharing this with you because it could be quite useful not only here for setting the walk writing paths but also in other aspects of witness I'm going to go to user actions model user actions and in here I have a command a set info command which is going to be used to change the walk rate from the current value of 1 to a value of 2 and again I don't have to use a hard-coded number here this could be a verily you read into a variable which is an interpreted within this command let me run it first of all so if I click OK on here and press the execute user actions button and then go back into model options paths we can see the walk rate is now 2 and if I run my model you remember the times here were 8 and 32 and if I run the model on now we can see the times are now changed they've been halved because I walk rate is twice as fast as it previously was so I can change my walk rate at any point in the model burn if I wish to do so using this set info command set info uses the witness library file or list file for its source of information if I go to file save us and rather than saving our model as a model file I save it as a like list file or a model library file and click Save well I've already got one but I'll save it again and then if I look in my Explorer just-just screen I can see I have a library file or a list file so I'll open that in notepad and this is a complete text listing of my witness model it contains all the definition of elements all the display information and all the detailed information rules cycle times breakdowns etc I want to move down to find and how to know where this is I'm just going to type in the word options to take me to where I want to get and down here I come to the options and we can see the indenting is in fact the way we navigate our way through this block of text so I need to find myself at the base level to display then I go to options then I work down to find the information I want the walk rate and this is a thing I'm going to change and then at the end of this process I need to extract myself so I need to do end options and end display and if I go back into the model user actions you can see not to command that so we have Astrid set info hazard is a function so the arguments are contained in brackets it is a string function so we have quotation marks at each end and index keeps the command it goes in to find the display part in the list file which you don't have to save out incidentally it will go and find it where he displayed it out to show what was going on the backslash n is effectively could a newline and by by using the backslash n symbol I can compress everything onto a single line of executable code so it goes the display part event Ilan's then drops down to walk rate set it to the value I've chosen and then extracts out to it so a set infer command is very useful we can do to change things like cycle times quantities of machines whole host of other things as well so it's very powerful but you have to be very careful to have the syntax right if I was to miss that semi we'll make it a comma or make it a colon it will not execute correctly so you have to be careful but it does give us a modest huge power in this example and model initialize actions I have another set info command to restore the walk rate back to one so if I were to begin my model and start it over again and go take a look in model options paths I can see my walk rate has been set back to one okay the next model I'm going to move on fairly quickly to because we're about a quarter of an hour through and I wanted some time for any questions later on yes I'm going to open the model sudo path travel time function in this model I've got an Argan asset e running I've got four machines and parts are moving from one machine to other in turn along sudo paths the attribute that you can see displayed with x if I slow it down a bit say got my chance of seeing it I'll go to step mode so we can see the attribute that has the time for each leg of the journey written on to it I do timestamp my part 1 arrives in the model so I can work out the total length of time it spends in a system which effective is a sum of these three legs of traveling but rather than use the built-in walk time function which some people may be a little wary of because it's not something I can get into and see very easily I've done my own homemade version if I look at my machine on actions on finish I am going to calculate the journey time for the next leg using my function FN calc moved into that I'm going to pass four properties the x-coordinate of my first machine and then the y-coordinate my first machine then the X cord and my second machine and the y-coordinate of my second machine in all of these witness machines on the screen I have exact the same code the only thing is different is the machine name so a machine to a machine before and my source machine will be m4 and my destination machine will be m3 here my source machine is m3 my destination is m2 because the calculation I'm going to do is the same no matter where I go it makes sense to extract that information into a standard witness function I'm passing four values across and I therefore need to have four locations to put that information where it can be worked upon so I'm passing the x1y1 x2y2 coordinates into this a function and now then that creates some local variables I bring them into existence at this point in the model I use them only within this function and what I'll leave this function those variables are ceased to exist I then have a number of calculations I do the end of which is the transfer time for the next leg of the operation and that value is returned back into my machine into here where it is stored as the attribute journey time the machine that pushes apart onward using the path and because it's sudo paths they go to model options paths the journey time is whatever is written on the attribute of the part so the gates calculated at each machine will have a unique value and that is then used for the travel time of the next leg one thing that I can show you which is quite useful is the debugging facility which is available in witness so I've ticked the debugger box I click OK and now I'm going to set my model running off step it forward and when Machine one complete cycling it goes into actions on finish in execute this code and we can then take a look at what's going on inside this code so I'm calculating the X distance from m1 to m4 and it doesn't matter to me whether it's a positive or negative number because I could be going left to right or right to left what I need to know is the absolute distance in pixels that we've traveled I can see that my machine and one if I hover over the cursor and we look in the top window here is around about eighty six and twenty five and we can see those of the values have being passed across if I look at Machine m4 again the coordinates around about 680 ish 294 and we can see those are also being passed across I can then step through here either by this button or basing the f8 key to step through and it calculates and we can see now the difference between those values so between 88 and 688 not surprisingly 600 and the difference between my two Y values is also calculated 264 in this case I'm going to convert that to meters because of my speed I know is in meters per second commit so I am going to divide that pixels by my mapping factor which in this case is 8 the map in factor setting model options coordinates will go there briefly want us I finished it through here but that gives me a conversion from the distance in pixels to a distance in meters for both in wax and why I then apply Pythagoras's theorem to get the diagonal distance and I convert it to time by dividing by my speeds in this case is five meters per minute around the value down so I can display it on the screen without having a lot of digits shown as my pants progress through I at the end of it I have got my transfer time calculated which is shown here sixteen point three nine time units so if I press run one more time there has my value sixteen point three nine so debugging if you haven't seen it before is really useful in stepping through blocks of code to see how effectively it's working so read my model again through the three machines with their individual tile times calculated through that function and the some aggregates 231 point five five minutes I stopped my model and I move my machine a lot closer and I can continue running on and we can now see our revised travel time once this is all passed through is down to nineteen point nine five minutes so simply by moving my elements around I can change my travel time so hopefully there's something in there beyond just paths which will be of interest to email okay two more models I want to show you quickly before I and classical any questions the first one is office movement and this is one of the standard models on the West installation so you can go and look at this one you can get at it through the go-to view make sure your start page is enabled and then through the sample models you can find it in here office movement Ahmad close the start page this model has got a number of paths which is the white background that are linked together to find a network of roots for parts to travel through the model generally parts have to travel more than one path to get their destination in the models we saw before with our operator moving along between machine one and machine to I always had a machine between adjacent paths in this case you can see probably we don't have that we have paths butting up two paths so the first parts arrive and they come along a pathway which is past zero zero one and it ends at this point here I don't have another path path the zero zero five taking my parts on to their destination equally there's a path here which links this first path down to a location the end and then finally another path so if I need to link paths together you cannot go to path display and link a path to a path if I were to double-click onto this path detail we can see that the source is the office entrance which is this buffer and the destination is something called node two if I go to this path and look at the properties and that links node two to my office cue register this path here links between node 1 and node 2 and then the path beyond links between node 1 and its destination the node is a physical witness element which is placed there as as a placeholder it can be a part which is in this case or it could be a buffer or a machine so you can see here my paths module as well as on my paths I have a particle node 1 which is simply passive it doesn't do anything it's simply there to act as a bridging base between my papers so by using these nodal and n elements parts of machines to act as nodes then you can find a way of linking a succession of paths together with that have to go through any intermediate physical elements like a machine so if you want to build a path that's the way to do it final thing I'm going to show you is I'm going to open another copy of witness which is witness 14 which is out very soon now so you have but to do this you although the other models that I've shown you will be available for download shortly until you have witness 14 you will not be able to open and run this one but this is a paths model that we saw some time ago I simply put a kink into my long path that's walking from machine to machine to setting the model running and we can see our past going along there we can see our labor changes direction so he's always traveling in the direction it's facing and if I go to model quick 3d I'm going to build myself a 3d world very simple world here I've got a checkerboard floor and change the floor but carpeting on it to make it look better I can build walls around it I can put it inside the building I can do pretty much everything I want but this is the basic starting point and if I remind model I can see you can see that the man is travelling assuming a bit around the route he is actually walking we have leg movement and swinging arms when the man gets onto the track between M 1 and M 2 just step forward we can see he's actually walking with a part up in the air in his hands and he's not swinging his arms so it starts to make virtuality a lot more lifelike than we previously had if I go to my path in 2d and I want to open my toolbar for paths so I go to view toolbars paths having selected this path I can go to the information dialog and this is a path I built up in the previous webinar so you'll have seen this much so far but what I'm now going to do is add some heightened so my person first of all go straight then he goes round a corner and on the third segment I'm going to say he goes up one unit in height it doesn't have to be a whole number I can use decimals then round the top and then coming down the other side here I'll have him going back down payment in height if I click OK there and I do a quick 3d so if I remember model now we can see that our person will now he's going up in the air over whatever obstruction is in the way and back down so again we can add height into our paths without walking people and we have people holding parts so that's what's coming in witness 14 there's a few more refinements to going before its effect further releases of public but we're getting pretty close to being ready to go with it okay I've talked for about half an hour to put a little longer they intended to but if I could invite any questions if it haven't already been sent in alternatively who send them then we will deal with an answer them after the WebEx is complete it's time to draw us to close I thank you for your attention I hope you got something out of it if there's any feedback you can give us afterwards to help us know how the presentation went what you'd like to see different in terms of content and also execution sound quality in which court etcetera please feed that back to us and we'll try and make things better and better and better by the way thank you guys for attention I hope you have a good day and I hope look forward to doing the WebEx again sometime in the relatively near future goodbye