ࡱ>   gypkur  !"#$%&'()*+,-./0123456789:;<=>?@abcdefghijklmnopqrstuvwxyz[\]^_`abcdefhijklmnopqrstuvwxyz{|}~root entry f !workbookq" summaryinformation(documentsummaryinformation8*_ \ploretta ba=l  !"#$%&'()*+,-./0123456789 thisworkbook=;k+"8x@"1arial1arial1arial1arial1$arial1 arial1arial1arial1arial1arial10arial unicode ms10arial unicode ms1 arial1& courier new1 arial1arial1 arial1arial1arial1qtahoma1qtahoma1qtahoma1qtahoma1qtahoma1qtahoma1qtahoma1qtahoma1qtahoma1qtahoma1 arial1h8cambria1,8calibri18calibri18calibri1calibri1calibri1<calibri1>calibri1?calibri14calibri14calibri1 calibri1 calibri1arial1calibri1calibri1 calibri1calibri"$"#,##0;\-"$"#,##0"$"#,##0;[red]\-"$"#,##0"$"#,##0.00;\-"$"#,##0.00#"$"#,##0.00;[red]\-"$"#,##0.005*0_-"$"* #,##0_-;\-"$"* #,##0_-;_-"$"* "-"_-;_-@_-,)'_-* #,##0_-;\-* #,##0_-;_-* "-"_-;_-@_-=,8_-"$"* #,##0.00_-;\-"$"* #,##0.00_-;_-"$"* "-"??_-;_-@_-4+/_-* #,##0.00_-;\-* #,##0.00_-;_-* "-"??_-;_-@_-"$"#,##0_);\("$"#,##0\)!"$"#,##0_);[red]\("$"#,##0\)""$"#,##0.00_);\("$"#,##0.00\)'""$"#,##0.00_);[red]\("$"#,##0.00\)72_("$"* #,##0_);_("$"* \(#,##0\);_("$"* "-"_);_(@_).)_(* #,##0_);_(* \(#,##0\);_(* "-"_);_(@_)?:_("$"* #,##0.00_);_("$"* \(#,##0.00\);_("$"* "-"??_);_(@_)61_(* #,##0.00_);_(* \(#,##0.00\);_(* "-"??_);_(@_) 0.000"yes";"yes";"no""true";"true";"false""on";"on";"off"],[$ -2]\ #,##0.00_);[red]\([$ -2]\ #,##0.00\) 0.0000                0  0  0  0  0  0  0  0  0  0  0  0  /  /  /  /  /  /  /  /  /  /  /  /  $  (   * ff + ) , * -  #   p ! p "  "  &   ) ` %  ,    '    . a> +        h+  @+  @*      a a +  #  $@ @  d@ @ *  d@ @   ,@ @  ! ! !p  @   "p@ @ * "p " "p  !p)   h)  @)  "  "x  !x) !p) !p) "0@@ "0@ "0@ "p@ @ + "0  `@@ )  `@ )  ` @ )   h  !x a  "0@ @  h  h        (  ( ( "t@ @ * !t) "x  h !x) !p@ @ * !p !p@@ ) !p@ ) !p @ ) a! a! a!) !p@ @ +  `@ @ * a )  "p@ @ * "0@ @ "0@ "0@  "p@ @ + !   a! a a!  t@ @ *  0@ @   |@ @    8@ @      a ||y"}-}= 00_)}a}2 00_)[$ -}a}3 00_)?[$ -}a}4 00_)23[$ -}-}5 00_)}a}1 a00_)[$ -}a}( 00_)[$ -}a}9 e00_)[$ -}}7 ??v00_)̙[$ -##0.5678  }}; ???00_)[$ -???##0.???5678 ??? ???}}) }00_)[$ -##0.5678  }a}8 }00_)[$ -}}* 00_)[$ -???##0.???5678 ??? ???}-}? 00_)}x}:00_)[$???## ???5 ???}-}/ 00_)}u}> 00_)[$## }a}" 00_)[$}a} 00_)ef[$}a} 00_)l[$}a} 00_)23[$}a}# 00_)[$}a} 00_)ef[$}a} 00_)l[$}a} 00_)23[$}a}$ 00_)[$}a} 00_)ef[$}a} 00_)l[$}a} 00_)23[$}a}% 00_)[$}a} 00_)ef[$}a} 00_)l[$}a} 00_)23[$}a}& 00_)[$}a} 00_)ef[$}a} 00_)l[$}a}  00_)23[$}a}' 00_) [$}a} 00_)ef [$}a} 00_)l [$}a}! 00_)23 [$ 20% - accent1m 20% - accent1 ef % 20% - accent2m" 20% - accent2 ef % 20% - accent3m& 20% - accent3 ef % 20% - accent4m* 20% - accent4 ef % 20% - accent5m. 20% - accent5 ef % 20% - accent6m2 20% - accent6  ef % 40% - accent1m 40% - accent1 l % 40% - accent2m# 40% - accent2 l湸 % 40% - accent3m' 40% - accent3 l % 40% - accent4m+ 40% - accent4 l % 40% - accent5m/ 40% - accent5 l % 40% - accent6m3 40% - accent6  lմ % 60% - accent1m 60% - accent1 23 % 60% - accent2m$ 60% - accent2 23ٗ % 60% - accent3m( 60% - accent3 23֚ % 60% - accent4m, 60% - accent4 23 % 60% - accent5m0 60% - accent5 23 %! 60% - accent6m4 60% - accent6  23 % "accent1aaccent1 o % #accent2a!accent2 pm % $accent3a%accent3 y % %accent4a)accent4 d % &accent5a-accent5 k % 'accent6a1accent6  f %(bad9bad  %) calculation calculation  }% * check cell check cell  %????????? ???+ comma,( comma [0]-&currency.. currency [0]/explanatory textg5explanatory text %0 : followed hyperlink 1good;good  a%2 heading 1g heading 1 i}%o3 heading 2g heading 2 i}%?4 heading 3g heading 3 i}%235 heading 49 heading 4 i}%6( hyperlink 7inputuinput ̙ ??v% 8 linked cellk linked cell }% 9neutralaneutral  e%"normal :noteb note   ;outputwoutput  ???%????????? ???<$percent =title1title i}% >totalmtotal %oo? warning text? warning text %xtablestylemedium9pivotstylelight16`Ʒ instructionsc command indexunits of speed a ao =b *barl sblck rbldg brk bsavm1bsav variables |c caow cao variables ")colb tcset {ct cv da di 3do wdo2 es oesav fllw 2fog f-i ijbar ls ppaus pb _pde a/pe z@ped uplbm ҏpoly pr rmsb "rmse d4road ,rsa { rt , sign 6` sl sobj 3 sout u spcw @ stcw gx tdo tree v [ vc . wg665           !" #$%&'(#) *+ , - ./0 12 3453 a@@   xnthis workbook is designed to help the user generate scenario definition code for the stisim driving simulator.zimportant note: the default settings in excel are such that when you save a file that includes hyperlinks to other files,the file in a different location that where it was originally created. to avoid this, please do the following (in excel) before saving the file:tips are provided by means of comments that are inserted in cells. cells that have comments have a little red triangle in the top right corner, like this:;to read the comment in a cell, just move the mouse over it.`to use the worksheet associated with a particular command, fill in values in the coloured cells.green cells must be filled in.@yellow cells are optional (e.g., parameters 9-24 for command a).bthen copy them to the windoze clipboard (ctl-c), and paste them into your sdl file editor (ctl-v).notes:r1. the initial values provided for all distances and parameters are taken from examples in the stisim help files.d2. i recommend that you do not save over this copy of the workbook.fif you want to save your work, i suggest that you save as, and rename.e3. if you want to strip out the tabs in the commands copied from this workbook, copy them into word,7when you are ready to begin writing commands, go to the command index page. file name: written by:"bruce weaver, bweaver@lakeheadu.ca*click on a command to go to its worksheet.:a - vehicle ahead of driver, approaching in the other lanepaus  pause a simulation runao - analog outputpb - police officer shows up5b - blank the roadway display screen for x.xx secondspde - previously defined event barl - construction zone barrelspe - police officer goes away9blck - display blocks or rectangles on the display screenped - pedestrianbldg - display a building plbm  playback markerbrk  activate the brake pedalpoly - 2 dimensional polygons4bsav - begin saving dynamic data for the output filepr - play recording(c - add curvature to the roadway displayrmsb - begin taking rms datacao - continuous analog outputrmse - end taking rms datacolb  collision block!road - display a specific roadwaycset - set crash parameters0rsa - change the current road surface attributes%ct - cross traffic in an intersectionrt - reaction time "cv - control vehicle automaticallysign - display a roadway sign2da - add a divided attention symbol to the display#sl - display a traffic signal lightdi - digital input eventsobj - add a static objectdo - digital output eventsout  serial output%do2  digital output (extended) eventspcw - speed control warninges - end simulation runstcw - steer control warning3esav - end saving dynamic data for the output file tdo - triggered digital output fllw  follow a lead vehicle,tree - display trees on the side of the road!fog - add a patch of fog to scene,v - vehicle ahead of driver in driver's lane#i - display a roadway intersection vc - vertical curvature jbar - jersey barrier wg - wind gusts ls - change the speed limitmain help file for sdl)instructions on how to use this worksheetunits of speed worksheet<conversion table: km/hr and ft/sec (from google calculator)km/hrft/seccalculator: km/hr to ft/sec enter km/hr:result in ft/sec:calculator: ft/sec to km/hr enter ft/sec:result in km/hr:note:>to convert 55 km/hr to feet per second, do a google search on:!55 km per hour in feet per second;to convert 48 ft/sec to km per hour, do a google search on:!48 feet per second in km per hourback to commands command name:a description:approaching vehiclevehicle index numbers help file:c:\stisim\help\sdleventa.htmrandon selection of parametersdistance-1 parameter no.parameter valuepvalnotesspeed of av in ft/s/distance from driver (ft) when av first appears+lateral lane position of av wrt centre line*1~8vehicle model numberclosure time (s)*0lateral distance (ft) that av will move, with respect to its current lateral position (positive to the interactive vehicle s right).tnew speed (ft/s), that the av will be traveling at the end of the transition period.ethe amount of time, in seconds, over which the transition will occur. command line:,sit is a very good idea to include comments in your scenario defintion (text) files.9lines that being with "-1", as shown above, are comments.ao analog outputc:\stisim\help\sdleventao.htmeanalog channel on which the voltage will be output from the computer.6voltage that will be output on the specified channel. !duration flag. 0=time, 1=distance)duration that the voltage will be output.vflag specifying if initial values should be displayed when the board is initialized or when the simulation run begins.bblank the screenc:\stisim\help\sdleventb.htm#blanking time, measured in seconds.barlroadway barrelsc:\stisim\help\sdleventbarl.htmklongitudinal distance (ft) that the lane marker is away from the driver when the lane marker first appears.no longer used.elateral position, in feet, from the roadway s dividing line to bottom left corner of the lane marker.-barrel model number (see help file for list). audio crash effect (range: 0-3).c:\stisim\sounds\thud.wavslane marker crash sound file. if parameter 11 is set to 2, a sound file is played. volume control, 0 to 10.blckblocksc:\stisim\help\sdleventblck.htmrlongitudinal distance (ft) that the block is away from the driver when it appears.lthe longitudinal position (ft) of the front upper left hand corner of the block with respect to parameter 1.lthe physical lateral position (ft) of the front upper left hand corner of the block that will be displayed. gthe physical vertical position (ft) of the upper left hand corner of the block that will be displayed. ithe physical lateral width, in feet, of the block that will be displayed.bthe physical height, in feet, of the block that will be displayed.nthe physical longitudinal depth, in feet, of the block that will be displayed.othe color that the block will be displayed in. (see assignsimcolors help file.)bldg buildings description dimensionsdisplay a buildingb1cafe 30 x 35 x 20c:\stisim\help\sdleventbldg.htmb2convenience store 20 x 20 x 15b3 coffee house 40 x 40 x 20b4 gas station 65 x 105 x 25b5 grocery store 95 x 80 x 20b6 hotdog stand 15 x 35 x 15_the longitudinal distance (ft) that the building is away from the driver when it first appears.b7 legal office 60 x 60 x 20blateral position, in feet, from the roadway s dividing line to bottom left corner of the building.b8 burger joint 50 x 50 x 20g5building model index.b9government building 50 x 30 x 208heading angle (counter clockwise rotation, in degrees). b10 generic storeb12b13 30 x 30 x 15b14b15g1general building 100 x 65 x 50g2 85 x 45 x 50g3 40 x 70 x 80 attention:g4 75 x 60 x 809used to generate the pulldown list for parameter 3 above. 50 x 55 x 80g6 80 x 120 x 80g7 25 x 35 x 95g8 35 x 75 x 80g9480 x 380 x 20g10120 x 120 x 100g11 50 x 55 x 65g12 130 x 75 x 20g13 130 x 75 x 40h1househ2h3h4h5h6h7h8h9h10h11h12h13h14h15h16s1 skyscrapers2s3s4s5s6s7s8s9s10s11s12s13s14s15s16s17u1barnu2 water tank< u3shedu4large warehouseu5small warehousebrkbrakec:\stisim\help\sdleventbrk.htm>percentage of brake input to use (0=none, 100 = full braking).6type of threshold where the braking ends (range: 0-3).%magnitude of the brake on threshold. bsavbegin block savec:\stisim\help\sdleventbsav.htm&save data option (0=distance, 1=time).save increment.calvindata block title.1, 6, 4, 18, 19[up to 44 comma-separated numbers (1-44) that represent the data variables you wish to save.value5elapsed time since the beginning of the run (seconds)1driver s longitudinal acceleration (feet/second),driver s lateral acceleration (feet/second)- driver s longitudinal velocity (feet/second)'driver s lateral velocity (feet/second)^total longitudinal distance that the driver has traveled since the beginning of the run (feet)gdriver s lateral lane position with respect to the roadway dividing line, positive to the right (feet).kvehicle curvature (curved path the vehicle is following based on the driver's steering and speed) (1/foot)."current roadway curvature (1/foot)6vehicle heading angle (degrees). see comment for more.$steering wheel angle input (degrees)sfor simple dynamics: longitudinal acceleration due to the throttle (feet/second )ofor advanced dynamics: throttle input (0 to 1, with 0 being no throttle input and 1 being full throttle input)qfor simple dynamics: longitudinal acceleration due to the brakes (feet/second )2for advanced dynamics: brake pedal force (pounds)lcurrent traffic signal light position: 0=no light; 1=green; 2=yellow; 3=red+horn indicator, 0 if horn button is pressed5left turn signal indicator, 0 if turn indicator is on6right turn signal indicator, 0 if turn indicator is on`running compilation of the crashes that the driver has been involved in. (see comment for more).0roadway traffic data. see comment for more info.xtime code for systems that are using a horita time code stamper. (see comment for more.))head tracker data. see comment for more.data marker flag.+driver's longitudinal velocity (miles/hour)!vehicle yaw rate (radians/second)current transmission gearsteering input counts.throttle input counts. braking input counts.scene viewing angle in degrees.total pitching angletotal rolling angle$steering wheel rate (radians/second)1value of the pan scene to the left input button. 1value of the pan scene to the right input button.bminimum time to collision (seconds) between the driver and all vehicles in the driver s direction.sminimum range (feet) between the driver and all vehicles in the driver s direction.hminimum time to collision (seconds) between the driver and all vehicles opposing the driver s direction.yminimum range (feet) between the driver and all vehicles opposing the driver s direction.gcomputer system time stamp in hours, minutes, seconds and milliseconds.?drivers response time (seconds) to any divided attention tasks.ftotal inertial heading angle (radians). ignores resetting of the driver to the main road when turning.abyte that contains the current state of all of the input buttons.dcurrent status of the digital input port on the secondary i/o card. !current speed limit (feet/second)ccurvec:\stisim\help\sdleventc.htmrlongitudinal distance (ft) that the curve is away from the driver when it appears.|entry spiral length in feet. an entry spiral is a transition section of roadway from a straight section of road to a curve. cthe longitudinal length, in feet, of the curved section of roadway.yexit spiral length in feet. an exit spiral is a transition section of roadway from a curve to a straight section of road.constant roadway curvature (1 over the radius of curvature, 1/foot) that will be used when displaying the curved roadway section.&roadway super elevation: (0=no, 1=yes)lcurve's super elevation or cross-slope measured in percent grade (100 * ft/ft). negative value helps driver.caocontinuous analog outputc:\stisim\help\sdleventcao.htmbsimulation variables that will be output on the specified channel.1gain that will be applied to the output channel. joverall minimum time to collision (ttc) for the current simulation frame. 7overall minimum range for the current simulation frame.zdriver's head yaw angle (degrees). this is only available if you are using a head tracker.? driver s response to the most recent divided attention symbol.mdriver s response time (seconds) to the most recent divided attention symbol.colbcollision blockc:\stisim\help\sdleventcolb.htmnthe longitudinal distance that the center of the block is away from the driver when it is initially activated.wlateral position, in feet, from the roadway s dividing line to the center of the block.:longitudinal (down the road) length of the block, in feet.3lateral (side to side) width of the block, in feet."collision block sound effect file.(lines that being with "-1" are comments.csetset crash parametersc:\stisim\help\sdleventcset.htmcrash sound flag (0-7).jinitial position of the vehicle with respect to the roadway s dividing line, positive to the right (feet).hdistance off the edge of the road where a crash occurs, positive to the right (feet). blank = no change.xbuffer distance after an accident has occurred before another accident can occur (feet).ct cross trafficc:\stisim\help\sdleventct.htmqlongitudinal distance, in feet, that the cross traffic vehicle is away from the driver when it initially appears.,cross traffic display options. values: 1-5.kthe initial lateral position, in feet, that the crossing vehicle is away from the roadway s dividing line. econstant velocity, in feet/second, for the cross traffic vehicle. (used only if p2 is set to 4 or 5.)r7the direction the vehicle is coming from (default = r).*2~8;-56the vehicle model index for the cross traffic vehicle.0intelligent vehicle flag: 0=dumb, 1=intelligent.cvcontrol vehiclec:\stisim\help\sdleventcv.htmhthe speed, in feet/second, that the vehicle will be traveling. if set to 0, driver controls accelerator.bflag giving the driver control of the steering wheel (0, 1, or 2).dadivided attentionc:\stisim\help\sdleventda.htm'divided attention display symbol (1-8).divided attention action (0-3).nvolume control if the "daerror.wav" file is played. values range from 0 to 10.di digital inputc:\stisim\help\sdleventdi.htmla number that corresponds to the expected correct response for the di event.dodigital outputc:\stisim\help\sdleventdo.htmdnumber that sets the specified pin s outputs to high (1) or low (0).do2digital output (extended)c:\stisim\help\sdleventdo2.htm;port number that the specified values will be sent out on. |16.byte value that will be output on register a. &3-byte value that will be output on register b.^255,byte value that will be output on re< gister cesend simulation runc:\stisim\help\sdleventes.htm3time (in seconds) when the simulation run will end.esavend block save!no parameters for this command. fllwfollow lead vehiclec:\stisim\help\sdleventfllw.htm*10mthe initial speed, in feet/second, of the lead vehicle that will be followed.blongitudinal distance (ft)that the lead vehicle is away from the driver when it initially appears.gthe lateral lane position, in feet, of the center of the lead vehicle wrt the roadway s dividing line. 8lead vehicle model type number (see vehicles help file).<time delay (in seconds) before the sine wave input kicks in.)gain on the lead vehicle s speed profile.olength of time (in seconds) that the vehicle following task will be displayed. c:\stisim\data\speedprofile.singname and location of a file that contains the sinusoidal input profile.oflag that specifies whether to save the raw data to the stisim drive data file.warning distance (in feet). fog fog effectsc:\stisim\help\sdleventfog.htm^longitudinal distance (ft) that the fog is away from the driver when it first becomes visible.ddistance, in feet, that the driver will be able to see into the fog.4the longitudinal length, in feet, of the fog event. i intersectionc:\stisim\help\sdleventi.htm6type of intersection (0=full; 1=branch r; 2=branch l).vdistance offset (ft) that is added to the event on distance to specify exact location.(turns allowed (0=none; 1=any; 2=r; 3=l).<type of crosswalk to display in the drivers direction (0-4).btype of crosswalk to display in the cross traffic direction (0-4)..correct turn direction (0=straight; 1=r; 2=l).wauditory file (.wav format) that is played in case of wrong turn. (optional parameter.)jbarjersey barrierc:\stisim\help\sdleventjbar.htm^distance (ft) that the front of the barrier is away from the driver when it initially appears._lateral position (ft) of the front of the barrier with respect to the roadway s dividing line. ^lateral position (ft) of the rear of the barrier with respect to the roadway s dividing line. 8length, in feet, of the barrier that will be displayed. etype of jersey barrier to display (1-9). see help file for pictures.ls limit speedc:\stisim\help\sdleventls.htmdthe maximum speed, in miles/hour, that the driver may legally drive.ythe distance (ft)that the event is away from the driver when the event initially occurs. pauspause simulation runc:\stisim\help\sdleventpaus.htmlpause duration (s). if 0, experimenter must restart (alt-p, or play button).pbpolice officer - beginc:\stisim\help\sdleventpb.htmvdelta speed (ft/s) that is used when computing whether or not the driver is speeding. pdepreviously defined eventc:\stisim\help\sdleventpde.htm vehahead.pdename of event file.*0~45+paramters 2-9 are passed to the event file.=what gets passed depends on what event it is being passed to.0see the help file sdleventpde.htm for more info.pepolice officer end/exitc:\stisim\help\sdleventpe.htmped pedestrianc:\stisim\help\sdleventped.htm`distance (ft) that the pedestrian is away from the driver when the pedestrian initially appears.lcollision time (s) when the pedestrian first begins to walk across the road.>pedestrian walking speed (ft/s). if 0, ped is standing still.xinitial pedestrian lateral position, in feet, with respect to the roadway dividing line.2direction pedestrian is coming from (b, f, l, r). 5pedestrian model number (see help file for pictures).plbmplayback markerc:\stisim\help\sdleventplbm.htmpolypolygonsc:\stisim\help\sdleventpoly.htmcthe longitudinal distance, in feet, of the polygon s first vertex. fthe physical lateral position, in feet, of the polygon s first vertex.hthe physical vertical position, in feet, of the polygon s first vertex. 1the plane in which the polygon will be displayed.the polygon color. c:\stisim\data\testpolyscn.pol0ascii text file that contains the polygon data. 3flag for roadway object versus screen-based object.dduration, in seconds, that a screen based polygon will be displayed. c:\stisim\data\textures\num9.gifgcomplete name of any texture map that will be displayed on the polygon.6display system that the polygon will be displayed on. prplay recordingc:\stisim\help\sdleventpr.htmlname of the file that contains the message to be played, including the path.vthe playback flag: 0=do not hold; 1 = hold subsequent events until recording finished.evolume control when playing back the file. values range from 0 to 10.rmsbbegin taking rms datac:\stisim\help\sdleventrmsb.htmbthis parameter is no longer used, but is still required. set to 0.!curve to right with 2 pedestrians.rms data block with its own individual title. rmseend taking rms datac:\stisim\help\sdleventrmse.htmroadroad parametersc:\stisim\help\sdleventroad.htm%width, in feet, of each roadway lane.ftotal number of lanes that will be displayed for the desired roadway. 'total number of right hand side lanes. .roadway s dividing line striping option (0-7).ndistance (ft)from the edge of the roadway to the inside edge of the edge line.7length, in feet, of the stripes that will be displayed.vdistance, in feet, between the end of one stripe and the beginning of the next stripe.-width, in feet, of the lane division markers.lwidth, in feet, of the edge lines, if they will be displayed on the roadway.@transition length, in feet, to change from previous road event. vcross-slope for the right hand side travel lanes, in percent grade (100 * feet/feet). 0cross-slope for the left hand side travel lanes.,cross-slope of the right hand side shoulder.0width, in feet, of the right hand side shoulder.*cross-slope of the left hand side shoulder/width, in feet, of the left hand side shoulder.'slope of the right hand side foreslope.1width, in feet, of the right hand side foreslope.&slope of the left hand side foreslope.0width, in feet, of the left hand side foreslope.&width, in feet, of the center median. ucolor value or file containing the texture map used for displaying the roadway lanes.bif p22 = texture map, then p23 = width of the texture map in feet.fcolor value or file containing the texture map that will be used for displaying the roadway shoulders.bif p24 = texture map, then p25 = width of the texture map in feet.gcolor value or file containing the texture map that will be used for displaying the roadway foreslopes.bif p26 = texture map, then p27 = width of the texture map in feet.[color value or file containing the texture map that will be used for displaying the ground.bif p28 = texture map, then p29 = width of the texture map in feet.ccolor value or file containing the texture map that will be used for displaying the roadway median.bif p30 = texture map, then p31 = width of the texture map in feet.rsaroad surface attributesc:\stisim\help\sdleventrsa.htm?lane number(s) that will have their surface attribute changed. 1ten times the surface s coefficient of friction. rt reaction timec:\stisim\help\sdleventrt.htm5turn image off with: 0-time (s), or 1- distance (ft).kduration of the image in either seconds or feet based on parameter 2 above.data\miscellaneous\rtstop.3dspname of the image file (must be located within the stisim drive root directory).signdisplay roadway signc:\stisim\help\sdle<ventsign.htm@type of sign that will be displayed (1-16, or 100 for own sign).udistance (ft) that the sign is away from the driver when the sign initially appears. !c:\stisim\data\signs\rgtcrv30.3ds5specialty parameters for any signs that require them.sign source: 0=usa, 1=europe.>sign location: 0=driver's side of road; 1=other side of road.(sign heading rotation value, in degrees.sl"signal light (i.e., traffic light)c:\stisim\help\sdleventsl.htm^distance, in feet, that the signal is away from the driver when the signal initially appears. ]time (s) that the driver is away from a green traffic light signal when it changes to yellow.3time, in seconds, that the yellow light remains on.0time, in seconds, that the red light remains on.0initial light setting: 0=green, 1=yellow, 2=red.cdistance from the traffic signal location to the "true" limit line.bsignal light type (1=corner post; 2=15' overhang; 3=25' overhang).'signal light sequence: 1=usa, 2=europe.apost location: 0=behind intersection, 1=in front of intersection.sobjadd a static objectc:\stisim\help\sdleventsobj.htmsdistance (ft) that the static object is away from the driver when it first appears.blateral position (ft) from the roadway s dividing line to bottom left corner of the static object.jheight, in feet, from the ground to the origin of the static object model.jrotation angle, in degrees, of the static object about its vertical axis. grotation angle, in degrees, of the static object about its pitch axis. erotation angle, in degrees, of the static object about its roll axis.c:\stisim\data\signs\rcurve.3dsifile name (including path) of the model file defining the static object. sout serial outputc:\stisim\help\sdleventsout.htm@i have not written a fully developed worksheet for this command.<i may do so in the future, if it is one that we find useful.spcwspeed control warningc:\stisim\help\sdleventspcw.htmcspeed control: 0=off, 1=one warning, 2=warning until speed reduced./speed (ft/s) that triggers the warning message.volume control (0-10).stcwsteer control warningc:\stisim\help\sdleventstcw.htmqthe time, in seconds, of the interval when the driver's steering will be checked.[number of times the driver can "fail" the steering criteria before they automatically pass.zthe passing rms value for the driver's lane deviation (in ft) during the testing interval.ethe passing rms value for the driver's steering rate response (in deg/s) during the testing interval."volume control for warning (0-10).tdotriggered digital outputc:\stisim\help\sdleventtdo.htmqcontrol byte that tells stisim drive what event(s) will trigger a digital output.tsets the bit on register b that the triggered output pulse will be transmitted with.qduration of the minimum output pulse that will be sent over the digital i/o pin. treeroadside treesc:\stisim\help\sdleventtree.htm@maximum number of trees that will be displayed at any one time. <no longer used but has been left for backward compatibility.*1~18+type of tree that will be displayed (1-18).jminimum lateral distance from the roadway dividing line to the trees (ft).dmaximum lateral distance from the roadway dividing line to the tree.&side of road: 0=both, 1=left, 2=right.list of tree typesrandom number selectionvvehicle ahead in driver's lanec:\stisim\help\sdleventv.htm/30/the speed, in feet/second, of the new vehicle. qdistance (ft) that the vehicle is away from the driver when it initially appears.xlateral lane position (ft) of the center of the vehicle wrt the roadway s dividing line.5if decelerating: 0=no brake lights, 1 = brake lights.vehicle model type number.cclosure time (s) between the driver s vehicle and the vehicle you are controlling. (can be + or -.)/12vlateral distance (ft) that the new vehicle will move wrt its current lateral position.*30xnew speed (ft/s) that the vehicle will be traveling at the end of the transition period.6time, in seconds, that the transition will occur over.vcvertical curvaturec:\stisim\help\sdleventvc.htmdthe longitudinal length of the vertical curvature, measured in feet.}rate of change of the grade with distance along the vertical curve, measured in (percent grade/feet) (100 * feet/feet)/feet. wg wind gustsc:\stisim\help\sdleventwg.htm!steering wheel gain, in radians. throttle controller gain. crun length multiplier--the total time that the gust will remain on.^it contains hyperlinks to the stisim helpfiles, which must be stored in folder c:\stisim\help.6 :o ]those hyperlinks will become relative, even if they were entered as absolute. this means that things will get all fouled up if you store %d lnclick on tools->options->general->web options->files. once there, uncheck the 4 $box next to: "update links on save." " kafter you have filled in all the necessary green or yellow cells, you must highlight all of the blue cells,` dkthat way, you will not lose the original examples. (see above for the note about hyperlinks before saving.)f [uthen search for ^w (i.e., white space), and replace with nothing, or one blank space.1you must not tamper with the building codes shown )stisim driving simulator programming toollast modified:stisim programming tool.xls5in columns r to t of this worksheet, because they are= @bncaeafg h9 jw kv kalfwmm>o6pylrjtuxq}xxhyz?[[\o\\5\`!]r]]] ^m5_`ce%sg hh l7nwpr*tcv?@yz{|+} ~рiԃe o h v ?lƎ@m8e<iʝ`ijs!*& x qzůqzw`ccb  %pn  dmbp?_*+%&?'?(?)?mlexmark e210o odxxletterpriv''''222222222p dlcourier newh"dx??&u} }  }  i %  ;      , ,    @      b cccccccc b cccccccc     d dd cccccc   a         0z(("! " # $  !a !e "a " "ae #a~ #v@#a $af <*&(  ~  <nxpp?v z]4@ny  nu+6yo3dskwt: h<ibw: notice the little red triangle in the top right corner of this cell.<0h  michel bdarde>@heje 7xyk  command index page.'command index'!a1 sheet1ggd  'e  dmbp?_*+%&?'?(?)?mlexmark e210o odxxletterpriv''''222222222p dlcourier newh"dx??&u} 2      a g g g g g g g g g g g g g! g" g# g$ g% g& g' g( g) g* g+ g, g- g. g/ g0 g1 g2 g3 g4 g5 h6 g7 g8 g9 g: g; g< g= g> g? g@ ga gb gc gd ge gf gg gh< (    b xpp?i`]4@ w΢w;g)r) } <~note: the worksheet for this command is not yet developed, because it has 44 parameters, and i thought i would wait to see if it is a command we are actually going to use. this command is also quite easy to use: you simply list the parameter numbers (separated with commas) of the items you want to output to the serial port (in the order you want them to go). bw, 14-sep-2004 < )| }bw>@ 7yk ;a - vehicle ahead of driver, approaching in the other lanea!b1zyk ao - analog outputao!b1yk 6b - blank the roadway display screen for x.xx secondsb!b1zyk !barl - construction zone barrelsbarl!b1yk :blck - display blocks or rectangles on the display screenblck!b1nyk bldg - display a building bldg!b1tyk brk  activate the brake pedalbrk!b1 yk 5bsav - begin saving dynamic data for the output filebsav!b1 yk )c - add curvature to the roadway display'c'!b1t yk cao - continuous analog outputcao!b1f yk colb  collision blockcolb!b1p yk cset - set crash parameterscset!b1yk &ct - cross traffic in an intersectionct!b1zyk #cv - control vehicle automaticallycv!b1yk 3da - add a divided attention symbol to the displayda!b1fyk di - digital input eventdi!b1hyk do - digital output eventdo!b1yk &do2  digital output (extended) event 'do2'!b1dyk es - end simulation runes!b1yk 4esav - end saving dynamic data for the output file esav!b1ryk fllw  follow a lead vehiclefllw!b1zyk "fog - add a patch of fog to scenefog!b1zyk $i - display a roadway intersection i!b1fyk jbar - jersey barrier jbar!b1lyk ls - change the speed limitls!b1tyk paus  pause a simulation runpaus!b1yk *instructions on how to use this worksheetinstructions!a1nyk pb - police officer shows uppb!b1tyk pde - previously defined eventpde!b1pyk pe - police officer goes awaype!b1xyk ped - pedestrianped!b1fyk plbm  playback markerplbm!b1tyk poly - 2 dimensional polygonspoly!b1\ yk pr - play recordingpr!b1r yk rmsb - begin taking rms datarmsb!b1n yk rmse - end taking rms datarmse!b1| yk "road - display a specific roadwayroad!b1 yk 1rsa - change the current road surface attributesrsa!b1\yk rt - reaction time rt!b1tyk sign - display a roadway signsign!b1|yk $sl - display a traffic signal lightsl!b1nyk sobj - add a static objectsobj!b1byk sout  serial outputsout!b1ryk spcw - speed control warningspcw!b1yk units of speed worksheet'units of speed'!a1ryk stcw - steer control warningstcw!b1vyk  tdo - triggered digital output tdo!b1yk -tree - display trees on the side of the roadtree!b1yk -v - vehicle ahead of driver in driver's lanev!b1fyk vc - vertical curvature vc!b1vyk wg - wind gusts wg!b1yk main help file for sdlyk x../../../../stisim/help/sdl.htmyx;h,]ą'c sheet2ggd  j4  dmbp?_*+%&?'?(?)?mlexmark e210o odxxletterpriv''''222222222p dlcourier newh"dx??&u}  } m}      ai ij ik al~ j?j&:û)? am~ kt@j(yu?~ j? an%ltxz:r@ d&:û)?~ j>@md w;@~ ji@m4f@~ jt@mtxz:r@ ao~ jv@mdzxt@ ap~ kt@~ jy@ minv@ aq% lsu@ d(yu?~ j[@ m=]y@~ j^@ md w[@ ar s t u v w *<w .<w *   w>@ w"w 7pyk back to commands'command index'!a3ryk back to commands'command index'!b30,warning!warning!cdo not enter data here--there is a formula in this cell. enter a speed in km/hr in the green cell.jthere is a formula in this cell. please enter data in the green cell only. mb,warning!warning!ddo not enter data here--there is a formula in this cell. enter a speed in ft/sec in the green cell.jthere is a formula in this cell. please enter data in the green cell only. mb  sheet3ggd  '08  dmbp?_*+%&?'?(?)?mlexmark e210o odxxletterpriv''''222222222p dlcourier newh"dx??&u} u} } } } i} } } } } } } } } } } } } } } } } } } } } } } } } } } } } !!} ""} ##} $$} %%} &&} ''} ((} ))} **} ++} ,,} --} ..} //} 00} 11} 22} 33} 44} 55'6666666666 6 6 6 6 6666666666666666666 nx oyp nz [q \rrrrrr n] ^ _rrrrnq n`~ sy@t uv wa:x  $ comment for d@ -- d@bp'$comment for a -- approaching vehiclehyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyy5 zb zc[ wa xd xex \fbyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyy5u?s4@t wa]? d@^4@(* la ,by ygbyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyy5u@s@@t wa]@(  l^@@( y yhbyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyy5 u@s t wa ]@(  ^(  y yib yyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyy5~ u@ sj t wa ]@(  ^`( *1~8 y ykb yyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyy5 _@s$@ t wa ]@(  ^$@(  y ylb yyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyy5~ `@ sm t wa ]@(  ^h( *0 y ynb yyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyy5 `@s4@ t wa ]@( ^4@( y yob yyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyy5a @s@t wa] @(^@(y ypbyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyy5_"@b@t wa]"@(^@(y ylbyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyy5`$@bt wa]$@(^(y ynbyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyy5`&@b4@t wa]&@(^4@(y yobyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyy5a(@b@t wa](@(^@(y ypbyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyy5~ _*@ bt wa]*@(^@(y ylbyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyy5~ `,@ bt wa],@(^@(y ynbyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyy5~ `.@ bt wa].@(^@(y yobyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyy5~ a0@ bt wa]0@(^@(y ypbyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyy5~ _1@ bt wa]1@(^@(y ylbyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyy5~ `2@ bt wa]2@(^ @(y ynbyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyy5~ `3@ bt wa]3@(^@(y yobyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyy5~ a4@ bt wa]4@(^$@(y ypbyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyy5~ _5@ bt wa]5@(^(@(y ylbyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyy5~ `6@ bt wa]6@(^@(y ynbyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyy5~ `7@ bt wa]7@(^0@(y yobyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyy5~ a8@ bt wa]8@(^@( y ypbyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyy5cntw]^yyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyy5dl&rr& 6!6"6%6&6 nq n6 dy@  da $b er6 e@  da $ba er6 e4@ da $b er6 e@@ da $b er6 e d a $ b er6 ea  d a $ b*1~8 er6 e$@  d a $ b er6 ep  d a $ b*0 er6 e4@  d a $ b er6 e@  da $b er6 e@  da $b er6 e  da $b er6 e4@  da $b er6 e@  da $b er6 e@ ! da $b er6 !e@ # da $b "er6 #e@ % da $b $er6 %e@ ' da $b &er6 'e@ ) da $b (er6 )e@ + da $b *er6 +e@ - da $b ,er6 -e@ / da $b .er6 /e@ 1 da $b 0er6 1e@ 3 da $b 2er6 3e @ 5 da $b 4er6 5f@ da $bl!qqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqq5 "gw"g %ar%g %s&q &tpvp& t  5q0 (     bЂ xpp?i  ]4@Ђ  liihgi </bw: the speed, in feet/second, of the approaching vehicle. you may also reference the approaching vehicle s speed with respect to the driver s speed by using a * in front of this parameter. if a * symbol appears as the first character in the parameter specification, the program will take the value of parameter 1 and add it to the current speed of the driver s vehicle and use this as the vehicle s speed. <  b( xpp?i ]4@( yd@bterDZl u<vbw: the longitudinal distance, in feet, that the vehicle is away from the driver when the vehicle initially appears. <u  b xpp?i ]4@ :acab|yȻ <bw: the lateral lane position, in feet, of the center of the vehicle with respect to the roadway s dividing line. you may also reference the vehicle s position with respect to the driver s position by using a * in front of this parameter. if a * symbol appears as the first character in the parameter, the program will take the value of parameter 3 and add it to the current lateral position of the driver s vehicle and use this as the vehicle s lateral position. <y  bЃ xpp? i -]4@Ѓ@ Ѯe!bg)9(  <-bw: vehicle model type number {vehicles}. you may assign the vehicle type using stisim drive s random parameter selection capabilities. for example, *1~8 means to select randomly one of vehicles 1-8. see help file c:\stisim\help\randomparams.htm for random selection examples.<f  b( xpp? itx]4@( /qj w+hmjh <s bw: closure time, in seconds, between the driver s vehicle and the vehicle you are controlling, this can be both positive and negative depending on the action that is desired. positive indicates that the two vehicles are getting closer to one another, negative indicates that the vehicles are getting farther apart. specifying the closure time so that the event acts as you intended is not an easy task. since the closure times are irrespective of the locations of the 2 vehicles, you can add an additional attribute to the closure time parameter that tells stisim drive to only activate the closure time if the new vehicle is in front of or behind the driver s vehicle. if the closure time parameter ends with an f, the action will only be activated when the new vehicle is in front of the driver s vehicle and the closure time criteria is met (e.g. 10f would mean only in front of the driver s vehicle and within 10 seconds and closing). placing a b at the end of the closure time parameter, instructs stisim drive to only take action when the new vehicle is behind the driver s vehicle. if neither a f or a b appears, stisim drive will activate when ever the closure time criteria is met. <  b xpp? i ]4@ m+d2mܞk x<bw: lateral distance that the vehicle will move, with respect to its current lateral position, in feet, positive to the interactive vehicle s right. like parameter 3 above, you may use the * symbol at the beginning of the parameter specification in order to reference the new lateral position of the vehicle with that of the driver s vehicle. <;x  bЄ xpp? i]4@Є` *l:$!x! `<bw: new speed, in feet/second, that the vehicle will be traveling at the end of the transition period. since you will be specifying a transition time, the program will perform a linear transition from the vehicle s speed when the transition begins until it reaches the specified speed at the end of the transition period. if you specify a speed that is slower than the current vehicle speed, then the vehicle will decelerate during the transition period. as with parameter 1 above, you may use the * symbol at the beginning of the parameter specification to reference the new speed to the driver s vehicle. <, `  b( xpp? ii]4@( kݬmf']e j<kbw: the amount of time, in seconds, over which the transition will occur. <\j  b xpp?i>]4 @  m (nc^d@r+ɫ l<mbw: distance (in feet) driver's vehicle has travelled when the event begins.<al  bЅ xpp?i]4 @Ѕ 6l?oՠ6 a< bw: display a vehicle approaching the driver from the other direction. if the driver s vehicle comes in contact with this new vehicle, the crash sound effect will be played (if active), and a collision will be added to the driver s collision total. vehicles that are displayed using the a event can be controlled and setup to do specific user defined actions based on speed and lane changing. these vehicles have a reasonable amount of intelligence and will stop at traffic lights and stop signs and will try to avoid colliding with vehicles in front of them. they will not automatically change lanes or steer to avoid collisions. note: if you will be controlling additional vehicle actions (parameters 5-24), then all vehicle intelligence will be turned off (the vehicle will pass through other vehicles, and will not stop at signal lights and stop signs) as long as additional vehicle motions remain. once all of the vehicle motions have been completed, the vehicle will revert back to an intelligent vehicle and will begin paying attention to other vehicles and traffic control devices. the reason for this is that you are specifically requesting the vehicle to do something and if it tries to avoid colliding with other vehicles or stopping at stop signs and signal lights, then this may affect what you have requested the vehicle to do. <_a  b( xpp?i$]4 @(  rwoj* <comment & command line: highlight the blue cells, then copy (ctl-c) and paste (ctl-v) into your sdl file. if you want the command without the comment, copy only the last line (with a box around it).<rive  b xpp?iix]4 @@ 7twnaq&j <s bw: closure time, in seconds, between the driver s vehicle and the vehicle you are controlling, this can be both positive and negative depending on the action that is desired. positive indicates that the two vehicles are getting closer to one another, negative indicates that the vehicles are getting farther apart. specifying the closure time so that the event acts as you intended is not an easy task. since the closure times are irrespective of the locations of the 2 vehicles, you can add an additional attribute to the closure time parameter that tells stisim drive to only activate the closure time if the new vehicle is in front of or behind the driver s vehicle. if the closure time parameter ends with an f, the action will only be activated when the new vehicle is in front of the driver s vehicle and the closure time criteria is met (e.g. 10f would mean only in front of the driver s vehicle and within 10 seconds and closing). placing a b at the end of the closure time parameter, instructs stisim drive to only take action when the new vehicle is behind the driver s vehicle. if neither a f or a b appears, stisim drive will activate when ever the closure time criteria is met. <  bІ xpp?ii ]4 @І ;`j=h x<bw: lateral distance that the vehicle will move, with respect to its current lateral position, in feet, positive to the interactive vehicle s right. like parameter 3 above, you may use the * symbol at the beginning of the parameter specification in order to reference the new lateral position of the vehicle with that of the driver s vehicle. <  x  b( xpp?ii]4@( ]}+&d.w2 `<bw: new speed, in feet/second, that the vehicle will be traveling at the end of the transition period. since you will be specifying a transition time, the program will perform a linear transition from the vehicle s speed when the transition begins until it reaches the specified speed at the end of the transition period. if you specify a speed that is slower than the current vehicle speed, then the vehicle will decelerate during the transition period. as with parameter 1 above, you may use the * symbol at the beginning of the parameter specification to reference the new speed to the driver s vehicle. < , `  b xpp?ii ti]4@` 4gof{^ j<kbw: the amount of time, in seconds, over which the transition will occur. <\j  bЇ xpp?iix]4@Ї rr͠8j>Ö <s bw: closure time, in seconds, between the driver s vehicle and the vehicle you are controlling, this can be both positive and negative depending on the action that is desired. positive indicates that the two vehicles are getting closer to one another, negative indicates that the vehicles are getting farther apart. specifying the closure time so that the event acts as you intended is not an easy task. since the closure times are irrespective of the locations of the 2 vehicles, you can add an additional attribute to the closure time parameter that tells stisim drive to only activate the closure time if the new vehicle is in front of or behind the driver s vehicle. if the closure time parameter ends with an f, the action will only be activated when the new vehicle is in front of the driver s vehicle and the closure time criteria is met (e.g. 10f would mean only in front of the driver s vehicle and within 10 seconds and closing). placing a b at the end of the closure time parameter, instructs stisim drive to only take action when the new vehicle is behind the driver s vehicle. if neither a f or a b appears, stisim drive will activate when ever the closure time criteria is met. <  b( xpp?ii ]4@(  w,l>d+atr x<bw: lateral distance that the vehicle will move, with respect to its current lateral position, in feet, positive to the interactive vehicle s right. like parameter 3 above, you may use the * symbol at the beginning of the parameter specification in order to reference the new lateral position of the vehicle with that of the driver s vehicle. <;x  b( xpp?ii#]4@( uxmcm  `<bw: new speed, in feet/second, that the vehicle will be traveling at the end of the transition period. since you will be specifying a transition time, the program will perform a linear transition from the vehicle s speed when the transition begins until it reaches the specified speed at the end of the transition period. if you specify a speed that is slower than the current vehicle speed, then the vehicle will decelerate during the transition period. as with parameter 1 above, you may use the * symbol at the beginning of the parameter specification to reference the new speed to the driver s vehicle. <, `  b xpp?ii t i]4@ vl gb_ j<kbw: the amount of time, in seconds, over which the transition will occur. <\j  bЋ xpp?'i1'#]4@Ћ@ qqyak*o6=>4 <bw: this is the last cell to highlight if you are copying the example given in the stisim help files. do not copy the comma in the next column.< ' @ michel bdardl michel bdardl michel bdardl michel bdardl  michel bdardl  michel bdardl  michel bdardl  michel bdardl  michel bdardl michel bdardl michel bdardl michel bdardl michel bdardl michel bdardl michel bdardl michel bdardl michel bdardl michel bdardl michel bdardl michel bdardl michel bdardl michel bdardl michel bdardl michel bdardl michel bdardl michel bdardl  michel bdardl bwc>@heje a 02""" 7 yk c:\stisim\help\sdleventa.htmyk ../../appdata/local/microsoft/windows/stisim/help/sdleventa.htmyx;h,]ą'cyk vehicle index numbersyk ../../appdata/local/microsoft/windows/stisim/help/sdlvehicles.htmyx;h,]ą'cyk randon selection of parametersyk ../../appdata/local/microsoft/windows/stisim/help/randomparams.htmyx;h,]ą'cp""yk back to commands'command index'!a3yk vehicle index numbersyk h../../../../stisim/help/sdlvehicles.htmyx;h,]ą'c yk randon selection of parametersyk j../../../../stisim/help/randomparams.htmyx;h,]ą'cyk c:\stisim\help\sdleventa.htmyk d../../../../stisim/help/sdleventa.htmyx;h,]ą'cu<\ distance from start of course(distance measured in feet)et parameter 1ithe speed, in feet/second, of the approaching vehicle. see comment in cell to the left for more details./t parameter 2pthe longitudinal distance, in feet, that the vehicle is away from the driver when the vehicle initially appears.q parameter 3the lateral lane position, in feet, of the center of the vehicle with respect to the roadway s dividing line. see comment in cell to the left for more details.al  4. vehicle model number\range: 1 to 57 random selection possible see comment in cell to the left for more details. e j 21. closure timeclosure time (seconds) between the driver s vehicle and the vehicle you are controlling. see comment in cell to the left for more details.o  22. lateral distancelateral distance (feet) that the vehicle will move, with respect to its current lateral position. see comment in cell to the left for more details.to 23. new speednew speed (ft/s) that the vehicle will be traveling at the end of the transition period. see comment in cell to the left for more details.e ta 24. transition time (s)fthe amount of time, in seconds, over which the transition will occur. d.sei 5. closure timeclosure time (seconds) between the driver s vehicle and the vehicle you are controlling. see comment in cell to the left for more details.  6. lateral distancelateral distance (feet) that the vehicle will move, with respect to its current lateral position. see comment in cell to the left for more details.to  7. new speednew speed (ft/s) that the vehicle will be traveling at the end of the transition period. see comment in cell to the left for more details.e ta  8. transition time (s)fthe amount of time, in seconds, over which the transition will occur. d.sei 9. closure timeclosure time (seconds) between the driver s vehicle and the vehicle you are controlling. see comment in cell to the left for more details. 10. lateral distancelateral distance (feet) that the vehicle will move, with respect to its current lateral position. see comment in cell to the left for more details.rl 11. new speednew speed (ft/s) that the vehicle will be traveling at the end of the transition period. see comment in cell to the left for more details.e ta 12. transition time (s)fthe amount of time, in seconds, over which the transition will occur. d.sej 13. closure timeclosure time (seconds) between the driver s vehicle and the vehicle you are controlling. see comment in cell to the left for more details. 14. lateral distancelateral distance (feet) that the vehicle will move, with respect to its current lateral position. see comment in cell to the left for more details.to 15. new speednew speed (ft/s) that the vehicle will be traveling at the end of the transition period. see comment in cell to the left for more details.e ta 16. transition time (s)fthe amount of time, in seconds, over which the transition will occur. d.sej 17. closure timeclosure time (seconds) between the driver s vehicle and the vehicle you are controlling. see comment in cell to the left for more details. 18. lateral distancelateral distance (feet) that the vehicle will move, with respect to its current lateral position. see comment in cell to the left for more details.to 19. new speednew speed (ft/s) that the vehicle will be traveling at the end of the transition period. see comment in cell to the left for more details.e ta 20. transition time (s)fthe amount of time, in seconds, over which the transition will occur. d.se comment & command linehighlight the blue cells, then copy (ctl-c) and paste (ctl-v) into your sdl file. if you want the command without the comment, copy only the last line (with a box around it).om  sheet4ggdggh/h  q  dmbp?_*+%&?'?(?)?"??&u} i} } q} } $}       !"#$%&'()*+,-./0123456789:;<=>?@abcdefghijklmnopqrstuvwxyz[\]^_`abcdefghijklmnopqrstuvwxz{|}~} } } } } } } }       nx oup nz v n] w n`~ s@@t uuv~ w:x@y $ comment for d@ -- d@bp"comment for ao -- analog outputyyyyyyyyyyy zb zc[ wa xd xex \fyyyyyyyyc?s@t wa]? d6^@  da $by yxyyyyyyyyc@s@t wa]@ d6^@  da $by yyyyyyyyyy c@s t wa ]@ d 6 ^  d a $ b y yz yyyyyyyy c@s$@ t wa ]@ d 6 ^$@  d a $ b y y{ yyyyyyyy~ c@ st wa ]@ d 6 ^@  d a $ b y y| yyyyyyyy c" tyyyyyyyyyyyyy u nq h6 d@@  da $b er6 e  da $bao er6 e@ da $b er6 e@ da $b er6 e d a $ b er6 e$@  d a $ b er6 f@ d a $ bu qqqqqqqqqqqqqu gwiuuu arg su t* h&&&0." 0 t  q@ (    bЍ xpp?ik]4@Ѝ` $[~g8@? <bw: sends a discrete analog output to some external piece of equipment. the ao, cao, do, do2, sout and tdo events are the only way you can control external equipment during a simulation run. the ao event allows you to output specific voltages to any active output channel. the voltage range on any individual channel is set based on the hardware specification (usually using dip switches on the board or through software provided by the hardware manufacturer). currently the simulator only supports hardware from measurementcomputing. refer to the additional i/o hardware section for further details about the types of output cards that are supported. systems equipped with an active steering system have a digital to analog (d/a) card in them, however, an additional card is needed in order to use the ao, cao, do, do2 and tdo events. the first d/a card is used to control the steering system, speedometer and tachometer (speedometer and tachometer are optional), and then the second card is used to handle any additional input and output (i/o) requirements that a user may have. if you have a system that does not use the active steering system, then you would install a single d/a card and use that for your additional i/o. you will need to refer to the hardware s documentation for specifics on voltage range, pin assignments and other details of the board. this event is used if you want to send a specific voltage at a specific point in the scenario, for example, to turn on a recorder or set a gauge. if you want to send continuous simulation variables out to an external computer, you should use the cao event. since you can use both the ao and cao in the same scenario, the cao event takes precedence over the ao event. this is because both events require you to specify the channel where the voltage will be output, and if both an active ao event and a cao event specify the same output channel, one of them must have priority. since the cao is outputting a steady stream of data, it is given priority. <|&  b( xpp?ui&]4@( ooeu l<mbw: distance (in feet) driver's vehicle has travelled when the event begins.<al  b xpp?ui/ <]4@` wbk,jvy <bw: analog channel on which the voltage will be output from the computer. refer to the output board's documentation for channel numbers and pin diagrams for determining the output pins and their grounds. <  bЎ xpp?ui ]4@Ў 0ñfz<%{# x<bw: voltage that will be output on the specified channel. possible values can vary from channel to channel and you can generally modify the output range using either dip switches on the card or with installation software provided by the board s manufacturer, or both. in some cases, the board may have a fixed voltage ranges for each channel. <x  b( xpp?ui ' x]4@(  qbxl n<obw: duration flag. possible values are: 0. time 1. distance <_n  b xpp?u i ]4@ 6n!i@i@ <bw: duration that the voltage will be output. when this duration has been exceeded, the voltage on the specified channel will be reset to 0. <  bЏ xpp?u i`<]4@Џ sc/d <bw: flag specifying if initial values should be displayed when the board is initialized or when the simulation run begins. this flag only effects the system when the starting distance of the ao event is 0, otherwise it will have no effect on the ao event. the flag values are: 0. wait until the start of the run to output analog signal 1. outputs the analog signal when the board initializes <s  b( xpp? i]4@(@ {qrtbՍeg <comment & command line: highlight the blue cells, then copy (ctl-c) and paste (ctl-v) into your sdl file. if you want the command without the comment, copy only the last line (with a box around it).<rive michel bdard  michel bdard  michel bdard  michel bdard   michel bdard   michel bdard   michel bdard   michel bdard >@heje 7yk c:\stisim\help\sdleventao.htmyk ../../appdata/local/microsoft/windows/stisim/help/sdleventao.htmyx;h,]ą'cpyk back to commands'command index'!a4yk c:\stisim\help\sdleventao.htmyk f../../../../stisim/help/sdleventao.htmyx;h,]ą'c6\ distance from start of course(distance measured in feet)etn 3. duration flagerror0. time 1. distanceyou must enter either 0 or 1.01y 7 5. timing of initial valueserror0. wait until start of run 1. output signal when board initializes this flag only effects the system when the starting distance of the ao event is 0, otherwise it will have no effect on the ao event. you must enter either 0 or 1. 01a   parameter 1analog channel on which the voltage will be output from the computer. refer to the output board's documentation for channel numbers and pin diagrams for determining the output pins and their grounds. n e  parameter 2ivoltage that will be output on the specified channel. see comment in cell to the left for more details. f c parameter 4duration that the voltage will be output. when this duration has been exceeded, the voltage on the specified channel will be reset to 0. grs   comment & command linehighlight the blue cells, then copy (ctl-c) and paste (ctl-v) into your sdl file. if you want the command without the comment, copy only the last line (with a box around it).un.   sheet5ggdggh'h   s  dmbp?_*+%&?'?(?)?"??&u} u} } q} } } } }                 nx o}p nz ~ n]  n n`~ sy@t uv wa:x $ comment for d@ -- d@bp$!comment for b -- blank the screen yyy zb zc[ wa xd xex \fu?s4@t wa]? d6^4@  da $by ytyyyyy nq h6 dy@  da $b er6 e @  da $bb er6 f4@ da $b j qqqqq gw i arg s t &* &h& t  xp`(    b xpp?i ]4@  nd![cb, <bw: blank the screen for a given amount of time. when this event is activated the simulation will continue to run as normal, the only difference is that the roadway display screen will be black, and will remain black until the specified time has elapsed. the blanking time should be based on the frame time for the simulation. the minimum blanking time would be 1/(simulation frame time). the desired simulation frame time is set in the configuration s graphics tab dialog box. <  b xpp?uiq]4@  r6gd^v(q l<mbw: distance (in feet) driver's vehicle has travelled when the event begins.<al  bp xpp?ui @]4@p f=]hm (<)bw: blanking time, measured in seconds. <(  b xpp?i 0 ]4@ ;/}lb77 <comment & command line: highlight the blue cells, then copy (ctl-c) and paste (ctl-v) into your sdl file. if you want the command without the comment, copy only the last line (with a box around it).<rive michel bdard  michel bdard  michel bdard   michel bdard >@heje   7 yk c:\stisim\help\sdleventb.htmyk ../../appdata/local/microsoft/windows/stisim/help/sdleventb.htmyx;h,]ą'cp yk back to commands'command index'!a5yk c:\stisim\help\sdleventb.htmyk d../../../../stisim/help/sdleventb.htmyx;h,]ą'ci\ distance from start of course(distance measured in feet)etm blanking timemeasured in seconds.meur comment & command linehighlight the blue cells, then copy (ctl-c) and paste (ctl-v) into your sdl file. if you want the command without the comment, copy only the last line (with a box around it).ee  sheet6ggdggh'h  g4i  dmbp?_*+%&?'?(?)?mlexmark e210o odxxletterpriv''''222222222p dlcourier newh"dx??&u} u} } q} } } m} } } } } } } } } } } } } } } } } } } } } } } } } } 5                      q  q    nx op nz  n] n n`~ s@t uv wa:x $ comment for d@ -- d@bp&#comment for barl -- roadway barrels<yyyyyyyyyyyyyyyyyyyyyyyyyyy zb zc[ wa xd xex \f6yyyyyyyyyyyyyyyyyyyyyyyyk?s@@t wa]?( l^@@(* la ,by y6yyyyyyyyyyyyyyyyyyyyyyyyk@st wa]@(^( y y6yyyyyyyyyyyyyyyyyyyyyyyy k@s t wa ]@(  ^(  y y6 yyyyyyyyyyyyyyyyyyyyyyyy k@s t wa ]@(  ^(  y y6 yyyyyyyyyyyyyyyyyyyyyyyy k@s t wa ]@(  ^(  y y6 yyyyyyyyyyyyyyyyyyyyyyyy k@s t wa ]@(  ^(  y y6 yyyyyyyyyyyyyyyyyyyyyyyy k@s t wa ]@(  ^( y y6 yyyyyyyyyyyyyyyyyyyyyyyyk @st wa] @(^(y y6yyyyyyyyyyyyyyyyyyyyyyyyk"@st wa]"@(^(y y6yyyyyyyyyyyyyyyyyyyyyyyyk$@s?t wa]$@(^?(y y6yyyyyyyyyyyyyyyyyyyyyyyyk&@s@t wa]&@(^@(y y6yyyyyyyyyyyyyyyyyyyyyyyy~ k(@ st wa](@(^x(c:\stisim\sounds\thud.wavy y6yyyyyyyyyyyyyyyyyyyyyyyyk*@s$@t wa]*@(^$@(y y6yyyyyyyyyyyyyyyyyyyyyyyyfttyyyyyyyyyyyyyyyyyyyyyyyyyyyyy nqh6d@  da $b er6ea  da $bbarl er6e@@  da $b er6 e  da $b  er6 e  d a $ b  er6 e  d a $ b er6e  d a $ b er6e  d a $ b er6e  d a $ b er6e  da $b er6e  da $b er6e?  da $b er6e@  da $b er6e  da $bc:\stisim\sounds\thud.wav er6f$@ da $bv gwi arg s t8 && &jm & t  `(    b xpp?*i| ]4@` nte$~f''>g a<bbw: display a construction barrel or other lane marker in the roadway display scene. typically, temporary roadway construction zones use some type of a raised marker to alert the driver that some of the lanes ahead of them will be closed. in stisim drive you would use a series of barl events to display the construction zone. highway cones can also be used to mark off the boundaries of handling courses such as the consumer union lane change course. there are several different roadway markers to choose from and you can optionally set it up so that if the driver hits a lane marker, stisim drive can issue a collision. since stisim drive uses 3d models of the roadway markers, the dimensions that were specified in previous versions of the program are no longer used, so there are multiple parameters that will just be set to 0. <a  b xpp?ri3]4@ kd*j4<] l<mbw: distance (in feet) driver's vehicle has travelled when the event begins.<al  bp xpp?ri  ]4@p  xj2 y<zbw: the longitudinal distance, in feet, that the lane marker is away from the driver when the lane marker first appears. <<y  b xpp?ri ]4@ * i@s7tl $<%bw: no longer used. please enter 0.<$  b xpp?ri]4@ 9pkcc4 j<bw: lateral position, in feet, from the roadway s dividing line to bottom left corner of the lane marker. <j  bp xpp?ri ]4@p@ db5@xmАold <bw: barrel model index: 1. barrel 1 (or as the geometric design engineers call them, drum 1): 2. tube (vertical post): 3. cone 1: 4. barrel 2 (drum 2): 5. cone 2: 6. placard (type ii baracade): <  b xpp?ri]4@ jspfl x/ <bw: this parameter specifies any audio crash effect that will be played when the driver collides with the lane marker. the possible values for this parameter are: 0. do not generate a collision effect 1. generate a normal collision (based on current setting) 2. play audio file specified by parameter 12 3. no collision effect is used, but the barrel is knocked over no matter what effect is used, colliding with the barrel will always be counted as a collision in the overall stisim drive data. <|   b xpp?ri]4@ 0m@i4 h<ibw: lane marker crash sound file. if parameter 11 is set to 2, rather than generating a collision (as specified by the crash options), a sound file is played. this option could be used to play a "thud" sound if a lane marker was hit. this would alert the driver that the marker was hit, but would not stop the simulation drive. <h   bp xpp?ri]4 @p` fibv9 <bw: volume control, 0 to 10. <   b xpp?ri ]4 @ *숢co, $<%bw: no longer used. please enter 0.<$   b xpp?r i ]4 @  ilaoj $<%bw: no longer used. please enter 0.<$   bp xpp?r i ]4 @p ld-g= $<%bw: no longer used. please enter 0.<$   b xpp?r i ]4 @ ̇v oy $<%bw: no longer used. please enter 0.<$  b xpp?r i]4@@ cgb5ow7 $<%bw: no longer used. please enter 0.<$  bp xpp?r i]4@p ?`}g! $<%bw: no longer used. please enter 0.<$  b xpp?i]4@ 83o^3i <comment & command line: highlight the blue cells, then copy (ctl-c) and paste (ctl-v) into your sdl file. if you want the command without the comment, copy only the last line (with a box around it).<rive michel bdard  michel bdard  michel bdard  michel bdard  michel bdard  michel bdard  michel bdard  michel bdard   michel bdard  michel bdard  michel bdard  michel bdard  michel bdard  michel bdard  michel bdard  michel bdard >@hejea 3 7yk  c:\stisim\help\sdleventbarl.htmyk ../../appdata/local/microsoft/windows/stisim/help/sdleventbarl.htmyx;h,]ą'cpyk back to commands'command index'!a6yk  c:\stisim\help\sdleventbarl.htmyk j../../../../stisim/help/sdleventbarl.htmyx;h,]ą'cr\ distance from start of course(distance measured in feet)et 10. barrel model indexerror!i1. barrel/drum 1 2. tube (vertical post) 3. cone 1 4. barrel/drum 2 5. cone 2 6. placard/type 2 barricade)please enter a number in the range shown.h 11. audio crash effecterror!x0. no audio effect 1. normal audio effect 2. use audio file named in parmeter 12 3. no audio, but barrel is knocked over)please enter a number in the range shown.'z 13. volume controlerror! range 0-10'please enter a number between 0 and 10.udle  parameter 1uthe longitudinal distance, in feet, that the lane marker is away from the driver when the lane marker first appears. s ocx parameter 2error!no longer used. set equal to 0. this parameter must be set to 0. d wx parameter 3error!no longer used. set equal to 0. this parameter must be set to 0. d w x parameter 4error!no longer used. set equal to 0. this parameter must be set to 0. d w x parameter 5error!no longer used. set equal to 0. this parameter must be set to 0. d w x parameter 6error!no longer used. set equal to 0. this parameter must be set to 0. d w x parameter 7error!no longer used. set equal to 0. this parameter must be set to 0. d w x parameter 8error!no longer used. set equal to 0. this parameter must be set to 0. d w parameter 9flateral position, in feet, from the roadway s dividing line to bottom left corner of the lane marker. brj 12. crash sound file1see comment in cell to the left for more details.h  comment & command linehighlight the blue cells, then copy (ctl-c) and paste (ctl-v) into your sdl file. if you want the command without the comment, copy only the last line (with a box around it).kr sheet7ggdggh'h  t  dmbp?_*+%&?'?(?)?"??&u} u} } q} } } } } } } } } } } } } } } } } } } 5     qq nx op nz  n] n n`~ s@t uv wa:x $ comment for d@ -- d@bpcomment for blck -- blocks(yyyyyyyyyyyyyyyyy zb zc[ wa xd xex \f"yyyyyyyyyyyyyyk?s@@t wa]?(l^@@(* la ,by y"yyyyyyyyyyyyyyk@st wa]@(^( y y"yyyyyyyyyyyyyy k@sd t wa ]@(  ^d(  y y" yyyyyyyyyyyyyy k@s4@ t wa ]@(  ^4@(  y y" yyyyyyyyyyyyyy k@s>@ t wa ]@(  ^>@(  y y" yyyyyyyyyyyyyy k@s4@ t wa ]@(  ^4@(  y y" yyyyyyyyyyyyyy k@sy@ t wa ]@(  ^y@( y y" yyyyyyyyyyyyyyk @s?t wa] @(^?(y y"yyyyyyyyyyyyyy2ttyyyyyyyyyyyyyyyyyyy nqh6d@  da $b er6ea  da $bblck er6e@@  da $b er6 e  da $b  er6 ed  d a $ b  er6 e4@  d a $ b er6e>@  d a $ b er6e4@  d a $ b er6ey@  d a $ b er6f? da $bv gwi arg s t.s && &6 & t lp 4(    bp xpp?i ]4@p '(iu/h <bw: display a 3-d block or 2-d rectangle in the roadway display. the block is transformed so that as the driver approaches it, the block is in perspective. when looking at the parameter definitions, refer to the figure at the end of the blck discussion for a graphical definition of the various parameters. this event has remained in order to keep the sdl backward compatible, however because modeling programs can create much better looking block models, the usefulness of this event has diminished. furthermore, the blck event only allows the blocks to be color shaded and does not support texture mapping the block. to add simple 2d texture mapped rectangles (and other shapes for that matter), use the poly event. even with these limitations, the blck event occasionally comes in handy. <  b xpp?ri3]4@@  mf%[= l<mbw: distance (in feet) driver's vehicle has travelled when the event begins.<al  b xpp?ri  ]4@ $]my|e r<sbw: the longitudinal distance, in feet, that the block is away from the driver when the block initially appears. <r  bp xpp?ri k]4@p ;pyde7,oi <bw: the longitudinal position, in feet, of the front upper left hand corner of the block with respect to parameter 1. this parameter is an offset with respect to parameter 1. because of the way the program sorts things and displays them on the screen, if you are trying to display a block on top of another block, you must make the upper left corner for both blocks be the same, and then offset one of the boxes using this parameter. normally this parameter is zero. <  b xpp?ri i]4@` .g}to9勳{ <ubw: the physical lateral position, in feet, of the front upper left hand corner of the block that will be displayed. this is with respect to the roadway s dividing line. <  b xpp?r ie ]4@ cevo\v9׽s <bw: the physical vertical position, in feet, of the upper left hand corner of the block that will be displayed. this is with respect to the ground. this should always be positive. <<  bp xpp?r i f ]4@p` s?8lœ$q n<obw: the physical lateral width, in feet, of the block that will be displayed. <_n  b xpp?r i ]4@ k+>bqb g<hbw: the physical height, in feet, of the block that will be displayed. <bg   b xpp?r i ]4 @  r,"ng<0a)p s<tbw: the physical longitudinal depth, in feet, of the block that will be displayed. <ys   bp xpp?r i]4 @p @\o=8h  <abw: the color that the block will be displayed in. the valid colors are defined using the "set simulation colors" and "assign simulation colors" options, found in the "options" menu. you may assign the block a random color by using stisim drive s random parameter selection capabilities. <r    b xpp?i]4 @ mt kmen4 <comment & command line: highlight the blue cells, then copy (ctl-c) and paste (ctl-v) into your sdl file. if you want the command without the comment, copy only the last line (with a box around it).<rive michel bdard  michel bdard  michel bdard  michel bdard   michel bdard   michel bdard   michel bdard   michel bdard  michel bdard  michel bdard  michel bdard >@heje 7yk  c:\stisim\help\sdleventblck.htmyk ../../appdata/local/microsoft/windows/stisim/help/sdleventblck.htmyx;h,]ą'cpyk back to commands'command index'!a7yk  c:\stisim\help\sdleventblck.htmyk j../../../../stisim/help/sdleventblck.htmyx;h,]ą'cn \ distance from start of course(distance measured in feet)et parameter 1mthe longitudinal distance, in feet, that the block is away from the driver when the block initially appears. .s parameter 2the longitudinal position, in feet, of the front upper left hand corner of the block with respect to parameter 1. see comment in cell to the left for more details.t{ parameter 3the physical lateral position, in feet, of the front upper left hand corner of the block that will be displayed. this is with respect to the roadway s dividing line. .y  parameter 4the physical vertical position, in feet, of the upper left hand corner of the block that will be displayed. this is with respect to the ground. this should always be positive. a  y parameter 5jthe physical lateral width, in feet, of the block that will be displayed. octh r parameter 6cthe physical height, in feet, of the block that will be displayed.   ~ parameter 7othe physical longitudinal depth, in feet, of the block that will be displayed.    parameter 8the color that the block will be displayed in. the valid colors are defined using the "set simulation colors" and "assign simulation colors" options, found in the "options" menu. see comment in cell to the left for more details.i  comment & command linehighlight the blue cells, then copy (ctl-c) and paste (ctl-v) into your sdl file. if you want the command without the comment, copy only the last line (with a box around it).n ll sheet8ggdggh'h  c>\4  dmbp?_*+%&?'?(?)?mlexmark e210o odxxletterpriv''''222222222p dlcourier newh"dx??&u} i} } } } } } i} ic   q  qhhh nx oo a a a nz     n]         n`~ s@t    uuv wa:x $ comment for d@ -- d@bp)&comment for bldg -- display a buildingyyyyyyyyy    zb zc[ wa xd xex \fyyyyyy   c?s@@t wa]? d6^@@  da $by yyyyyyy   c@sd@t wa]@ d6^d@  da $by yyyyyyy   ~ c@ s t wa ]@ d 6 ^x  d a $ bg5 y y yyyyyy    c@sf@ t wa ]@ d 6 ^f@  d a $ b y y yyyyyy   " ttyyyyyyyyyyy  u nq n6 d@  da $b er6 ea  da $bbldg er6 e@@ da $b er6 ed@ da $b er6 e d a $ bg5 er6 ff@ d a $ b    v q q qu gwg   u   u   u    ull cccccccccc    ll cccccccccc    mm cccccccccc             arg s   q t                  d>lpft*p&4l444dlb***pb*** !"#$%&'()*+,-./0123456789:;<=>?   ! ! " " # # $ $ % % & & ' ' ( ( ) ) * * + + , , - - . . / / 0 0 1 1 2 2 3 3 4 4 5 5 6 6 7 7 8 8 9 9 : : ; ; < < = = > > ? ?dl@ab @ @ a  a  b  b  (    c (     b xpp?]4@` te9lnnt^o f<gbw: this is an event that allows you to display a predefined building in the display scene. buildings are used to create cities or towns in the scenario. in previous versions of the software, buildings were created using multiple block commands. this is no longer necessary because you can use predefined 3d building models. <f  b xpp?ji]4@ ج$8;b8z9 l<mbw: distance (in feet) driver's vehicle has travelled when the event begins.<al  bp xpp?ji ]4@p  !*^aq`> <bw: the longitudinal distance, in feet, that the building is away from the driver when the building first appears. when specifying this parameter it is important to take into account the length of the building because the building's reference point is in the center of the building. therefore for long buildings such as the block of offices, the corner closest to the driver as the driver approaches will be closer than the distance specified by this parameter. <a  b xpp?ji> <]4@ hj]=l[. g<bw: lateral position, in feet, from the roadway s dividing line to bottom left corner of the building. <g  bp xpp?ji<]4@p wh{|? <c bw: building model index. this works a little bit differently than in version i of the simulator. in version i there where a total of 13 buildings that could be selected, however there was no rhyme or reason for their numbering and new buildings had to be added to the end. now there are numerous buildings in the following categories: business buildings (b) general buildings (g) houses (h) skyscrapers (s) utility (u) using categories will allow buildings to easily be added in the future without screwing up the existing numbering because they will simply be added to the end of a category. this means that scenarios should not require any changes when new buildings are added. however because of the category system, a building must now be specified using both the category designator (letter in parenthesis in the hyperlinks above) and the building number (e.g. b4, g10, bingo, etc.). for version i scenarios, the software will reassign the version i building numbers to a similar new building, however the building sizing might be off a bit. you may also assign a random building (from within a single category) using stisim drive s random parameter selection capabilities. <w  bpp xpp?j i |]4@pp@ $3@jd <bw: heading angle (counter clockwise rotation, in degrees). this allows you to rotate the building about its z axis (up and down) in order to give the building a different look. for example you could put a building at a 45 degree angle on a corner in order to give the corner a different look. the rotation is with respect to the normal building position with stisim drive. one slight caveat, some of the buildings do not have backs on them (yes they are facades) and if rotated may not look very good. <^   bp xpp? i@]4@p +tż*b?i. l <comment & command line: highlight the blue cells, then copy (ctl-c) and paste (ctl-v) into your sdl file. if you want the command without the comment, copy only the last line (with a box around it).<rive michel bdard  michel bdard  michel bdard  michel bdard   michel bdard   michel bdard   michel bdard >@heje 7pyk back to commands'command index'!a8yk  c:\stisim\help\sdleventbldg.htmyk ../../appdata/local/microsoft/windows/stisim/help/sdleventbldg.htmyx;h,]ą'cyk  c:\stisim\help\sdleventbldg.htmyk j../../../../stisim/help/sdleventbldg.htmyx;h,]ą'c<\ distance from start of course(distance measured in feet)et parameter 1the longitudinal distance, in feet, that the building is away from the driver when the building first appears. see comment in cell to the left for more details.hm parameter 2clateral position, in feet, from the roadway s dividing line to bottom left corner of the building. et parameter 4jheading angle (counter clockwise rotation, in degrees). see comment in cell to the left for more details.ie   3. building codeerror!%see list of codes in columns q and r.7you must select a building code from the pulldown list. %b  comment & command linehighlight the blue cells, then copy (ctl-c) and paste (ctl-v) into your sdl file. if you want the command without the comment, copy only the last line (with a box around it)..  3. building codeerror!%see list of codes in columns r and s.7you must select a building code from the pulldown list. th%b  sheet9ggdggh'h   )u  dmbp?_*+%&?'?(?)?"??&u} i} q} } } } } } } } }            q      nx o p nz  n]   n`~ s@t uuv wa:x $ comment for d@ -- d@bpcomment for brk -- brakeyyyyyyy zb zc[ wa xd xex \fyyyy c?sy@t wa]? d6^y@  da $by yyyyy c@st wa]@ d6^  da $by yyyyy  c@s@ t wa ]@ d 6 ^@  d a $ b y y yyyy  ttyyyyyyyyy  u nq h6 d@  da $b er6 e  da $bbrk er6 ey@ da $b er6 e da $b er6 f@ d a $ b u u ar g su tuu gwnun og(dt&,&z" 0 " g  $x(  $ $ br xpp?fi k]4@r uxsdfw} b(<cbw: this event allows you to place an event into your simulation scenario that controls the brake pedal input. this event is generally used in connection with the rsa event to put the driver into a situation where the vehicle begins to spin, thus forcing the driver to correct the problem using a steering input. one of the problems with an event like this is determining when the brakes will be released, therefore several options have been included so that you can customize the braking as much as possible. in any braking case, if the brakes are applied long enough so that the vehicle comes to a complete stop, then the brakes will automatically be released and control given back to the driver. note: this event only pertains to systems using the simple dynamics and will have no affect on systems using the advanced dynamics. <( vb $ br xpp?i]4@r  "@) o l<mbw: distance (in feet) driver's vehicle has travelled when the event begins.<al $ br xpp?i0 ]4@r 8nhiz p<qbw: percentage of brake input to use. range = 0 to 100. 0 = no braking at all 100 = full braking input <p $ b(s xpp?i]4@(s qjh@_. <bw: type of threshold where the braking ends: 0. time 1. distance 2. absolute velocity (when the velocity drops below a set velocity 3. relative velocity (when the velocity drops by the specified amount) <. $ bs xpp?i-]4@s@ ΃yf.7@heje 7pyk back to commands'command index'!a9yk c:\stisim\help\sdleventbrk.htmyk ../../appdata/local/microsoft/windows/stisim/help/sdleventbrk.htmyx;h,]ą'cyk c:\stisim\help\sdleventbrk.htmyk h../../../../stisim/help/sdleventbrk.htmyx;h,]ą'ce braking percentageerror6range: 0 to 100 0 = no braking 100 = full braking&you must enter a number from 0 to 100.//d threshold type when braking endserror=0. time 1. distance 2. absolute velocity 3. relative velocity)you must enter a number in the range 0-3.e/\ distance from start of course(distance measured in feet)ole g magnitude of break on thresholdsee comment for parameter 3.e   comment & command linehighlight the blue cells, then copy (ctl-c) and paste (ctl-v) into your sdl file. if you want the command without the comment, copy only the last line (with a box around it).e  sheet10ggdggh'h   y  dmbp?_*+%&?'?(?)?"??&u} i} } q} } } } } } } } } } } (}    q   nx op nz  n]   n`~ s@t uuv wa:x5 $ comment for d@ -- d@bp'$comment for bsav -- begin block saveyyyyyyyyy zb zc[ wa xd xex \fyyyyyy c?st wa]? d6^  da $by yyyyyyy c@sy@t wa]@ d6^y@  da $by yyyyyyy ~ c@ s t wa ]@ d 6 ^  d a $ b calvin y y yyyyyy ~ c@ s t wa ]@ d 6 ^n  d a $ b1, 6, 4, 18, 19 y y yyyyyy " ttyyyyyyyyyyy  u nq h6 d@  da $b er6 ea  da $bbsav er6 e da $b er6 ey@ da $b er6 e d a $ b calvin er6 f`n d a $ b1, 6, 4, 18, 19 uu arg su t gwi$z,&,&~& 0 w  9((  ( ( bu xpp?i  ]4@u  u؆n.u9k <bw: begin saving data that will be stored in the stisim drive output data file that is created at the completion of the simulation run. this option combined with the esav event allows you to save a block of data at any time during the simulation run. specifying the bsav event tells the program to begin collecting the data, to stop collecting data, you must use the esav option, or use a new bsav event. you will specify what data is collected based on a list of possible variables, and these variables can be changed from one data block to the next. the data that is stored will be saved in fixed length fields that will make it easier to pull the data into a spreadsheet or other analysis packages. you can also use the datareduction program (in the tools folder, generally c:\stisim\tools) that comes with stisim drive to assist you will reducing blocks of data saved using the bsav event. < ( bu xpp?i]4@u awg#a&q l<mbw: distance (in feet) driver's vehicle has travelled when the event begins.<al ( b(v xpp?fi v]4@(v idȥc <wbw: save data options. to specify the save data option, set parameter 1 to one of the following: 0. save data based on how far the vehicle has traveled since the last time the program saved an increment of data. if you use this option, the save increment is entered in feet. the vehicle may actually travel farther then the specified amount before the data is saved. this is because the distance the vehicle travels is based on the speed of the vehicle and the frame time for the simulation run. as soon as the save increment has been exceeded the program will save the data. 1. save data based on the number of seconds that have elapsed since the last time the program saved an increment of data. if you use this option, the save increment is entered in seconds. for best results, try to make this number be an integer increment of the frames per second parameter specified in the configuration s graphics tabbed dialog window. < ( bv xpp?i <]4@v@  ;k6 4<5bw: the save increment. as was discussed above, if you are using parameter 1 set to a value of 0, then you will enter this parameter in the units of feet. if you have parameter 1 set to a value of 1, then this parameter will be in seconds. because of round off errors and blown simulation frames there is potential slippage in the timing increment. for this reason you may wish to subtract a small fraction off of the time increment. for example, if you would like the data to be saved every .1 second, you may want to specify the save increment as .099 or .0995. < 4 ( bv xpp?i ok]4@v jjcm k*( <bw: this is a string variable that allows you to mark a particular data block with its own individual title. this parameter is intended to help you with your data reduction needs. labeling a block of data with a descriptive name makes it easy to search through the data that was collected and find the block of data that you are trying to find. this is especially true if you are randomizing your scenarios by creating pde files that you then shuffle around to offset ordering effects. < ( b(w xpp? i kk]4@(w ^tve@0 :(<;bw: up to 44 comma-separated numbers (1-44) that represent the data variables you wish to save. you specify the data that will be collected by listing the variable numbers that correspond to the variables you would like to save. the list of variables that may be collected is shown in worksheet bsav variables. <()i7: ( bw xpp? i ]4@w` 6qqbenq`v7dm <comment & command line: highlight the blue cells, then copy (ctl-c) and paste (ctl-v) into your sdl file. if you want the command without the comment, copy only the last line (with a box around it).<rive michel bdard  michel bdard  michel bdard  michel bdard   michel bdard   michel bdard   michel bdard >@heje 7yk  c:\stisim\help\sdleventbsav.htmyk ../../appdata/local/microsoft/windows/stisim/help/sdleventbsav.htmyx;h,]ą'cryk back to commands'command index'!a10yk  c:\stisim\help\sdleventbsav.htmyk j../../../../stisim/help/sdleventbsav.htmyx;h,]ą'ci\ distance from start of course(distance measured in feet)et 1. save data optionserror!n0. save data based on distance 1. save data based on time see comment in cell to the left for more details.please enter 0 or 1.vt 2. save incrementwfeet (if p1 = 0) seconds (if p1 = 1) see comment in cell to the left for more details.thle parameter 4comma-separated numbers (1-44) that represent the variables you wish to save. see worksheet "bsav variables" for descriptions of the 44 variables.  f 3. data block titleerror!)string variable to label a block of data.ouis  comment & command linehighlight the blue cells, then copy (ctl-c) and paste (ctl-v) into your sdl file. if you want the command without the comment, copy only the last line (with a box around it).  sheet11ggdggh'h   /u;ad  dmbp?_*+%&?'?(?)?mlexmark e210o odxxletterpriv''''222222222p dlcourier newh"dx??&u} $ r} ^s/      p q~ r? s~ r@ s~ r@ s~ r@ s ~ r@ s!~ r@ s"~ r@ s#~ r @ s$~ r"@ s%~ r$@ t&~ r&@ s'~ r(@ s(~ r(@ s)~ r*@ s*~ r*@ s+~ r,@ s,~ r.@ s-~ r0@ s.~ r1@ s/~ r2@ t0~ r3@ s1~ r4@ s2~ r5@ s3~ r6@ s4~ r7@ s5~ r8@ s6~ r9@ s7~ r:@ s8~ r;@ s9~ r<@ s:~ r=@ s;dl !"#$%&'()*+,-.~ r>@ s<~ !r?@ !s=~ "r@@ "s>~ #r@@ #s?~ $ra@ $s@~ %ra@ %sa~ &rb@ &sb~ 'rb@ 'sc~ (rc@ (sd~ )rc@ )se~ *rd@ *sf~ +rd@ +sg~ ,re@ ,sh~ -re@ -si~ .rf@ .sj"p ,8 (  , , by xpp? i0]4@y w4o;؀  <abw: this value will always be in the general range of + or  90 degrees. this is because when a driver performs a right or left hand turn, the software moves the driver back to the main road. for the inertial value of heading angle (composite value that includes turns), see parameter 41.<u d , bpy xpp?x]4@py@ ѓ!yuj\=z <bw: the accidents have the following numbers: 1 - vehicle collisions 2 - off road collisions 3 - collisions with pedestrians for example, if the current number shown for this parameter is 10, then on the next line of the stisim drive data file, this parameter has changed to 13, then an accident occurred and it was a collision with a pedestrian (13-10=3 therefore a pedestrian was run over). < , by xpp?p ]4@y ba 6 jͿ~ }(<bw: for each vehicle that is in the roadway display, this parameter will save the following data: vehicle identification number difference in longitudinal speed between the driver s vehicle and the roadway vehicle (feet/second) longitudinal position of the roadway vehicle with respect to the driver s vehicle (feet) lateral position of the roadway vehicle with respect to the roadway s dividing line (feet) there is a slight problem when saving this particular data. this option will save data for every other roadway vehicle that is being displayed and as vehicles drop out of the display, their data will no longer be collected. this can cause shifting in the data file because as one vehicle drops out, all of the subsequent columns move over. for this reason we recommend that if you will be collecting other vehicle data, you always make 19 the last variable in the variable list. <( l{}  , b(z xpp?i(z]4@(z z~d=m\'hlqm <bw: this allows you to place the time code from the stamper hardware into the data file and onto a video tape so that your data can be correlated. check with sti for more details on this hardware option. the format for the time display is: hh:mm:ss:ff where hh is the hours, mm the minutes, ss the seconds, and ff is the video frames (1-30). for information on the video setup, refer to the video portion of the hardware configuration discussion. <  , bz xpp?i'-]4@z` 1ɖio2 a<bbw: this is only available if you are using a head mounted display with a head tracker and will provide the heads orientation: head pitch ( up and down motion, in degrees, positive up) head roll (tilt left and right, in degrees, positive to the right) head yaw (turning side to side, in degrees, positive to the right) <a , bz xpp?i -]4@z "jˈ3 <bw: if this is set and you simultaneously press the alt-m keyboard combination the marker will increment by 1. this allows you to view the driver and then mark the data file if you see something that you may want to check later. <c  , b({ xpp?i!]4@({` } %onqi{m <bw: actual raw steering wheel input directly from the steering wheel. this variable is only available on systems that use the simple dynamics. <  , b{ xpp?i"]4@{ khoa? <bw: actual raw throttle input directly from the throttle pedal. this variable is only available on systems that use the simple dynamics. <|   , b{ xpp?i#]4 @{  "bzk0ߑ7 <bw: actual raw braking input directly from the brake pedal. this variable is only available on systems that use the simple dynamics. <r   , b(| xpp?i0i]4 @(| ;b@abersy; ^<_bw: this only applies to single monitor and head mounted display systems and not to systems with a wide field of view. this parameter is the current viewing angle of the center display with 0 being straight ahead and positive values mean the view is looking to the right. the view angle can be changed by pressing the f1 (left) and f2 (right) keys on the keyboard (5 degree increments), or by simultaneously activating the horn and left or right turn signal indicator. in this case the view angle will change at 90 degree increments and only allows the angle to get to a value of plus or minus 90 degrees. <? ^   , b| xpp?i$]4 @| w$cnb&c]k` s<tbw: total pitching angle, includes both ground slope and vehicle motion (radians) <s   , b| xpp? i%<]4 @|@ n' l@c~- q<rbw: total rolling angle, includes both ground slope and vehicle motion (radians) <{q 0s  , b(} xpp?"i']4 @(} j(@0if <bw: this is set to a value of 1 if the driver selected to have the driver s view rotate 90 degrees to the left, otherwise it will be 0. <g , b} xpp?#i)]4@} y cy@ <bw: this is set to a value of 1 if the driver selected to have the driver s view rotate 90 degrees to the right, otherwise it will be 0. <m , b} xpp?$ip+]4@}` il7/@_l(gd <kbw: note: in order to save variables 35-38, the collect time to collision data option must be activated. you can set this option in the configuration s other tabbed dialog window. <y  , b(~ xpp?%ip,]4@(~ >8ުc)Üt <kbw: note: in order to save variables 35-38, the collect time to collision data option must be activated. you can set this option in the configuration s other tabbed dialog window. <y  , b~ xpp?&ip-]4@~  />!\m8s <kbw: note: in order to save variables 35-38, the collect time to collision data option must be activated. you can set this option in the configuration s other tabbed dialog window. <y  , b~ xpp?'ip.]4@~ s*fjcӶ <kbw: note: in order to save variables 35-38, the collect time to collision data option must be activated. you can set this option in the configuration s other tabbed dialog window. <y  , b( xpp?(i .]4@(  k3qތx  <bw: computer system time stamp in hours, minutes, seconds and milliseconds. this allows the simulator data to be time synchronized with other computers. < , b xpp?)i/]4@@ ws =nԬ&| k<lbw: note: need to ask ted rosenthal if rt can be measured with finer resolution (e.g., for ior scenarios).<k , b xpp?+ip3]4@ 1 ?qn"dӸ <bw: byte that contains the current state of all of the input buttons. to get a particular buttons status, you will need to perform a logical and between this value and the button assignment value that was specified in the simulator configuration. <@s , b( xpp?$p4]4@(  5ڦy|o w9 < bw: current status of the digital input port on the secondary i/o card. the input port allows for 12 bits of information (4096 values) and will require a logical and operation in order to look at the individual bits. the secondary i/o card is an optional board and does not come as standard equipment on any simulator system. review the hardware section for more information on this option. the 12 bit number is as follows: register cl: register a: bits: {12 11 10 9} {8 7 6 5 4 3 2 1} < sow bw bw bw bw bw bw bw bw  bw  bw   bw ! bw # bw $bw %bw &bw 'bw (bw )bw *bw ,bw -bw >@ a 7 sheet12ggd    dmbp?_*+%&?'?(?)?mlexmark e210o odxxletterpriv''''222222222p dlcourier newh"dx??&u} u} i} q} } } } } } } } } } } } } } } } } 5     q nx okp nz l n] m n n`~ s@t uv wa:x  $ comment for d@ -- d@bpcomment for c -- curve$yyyyyyyyyyyyyyy zb zc[ wa xd xex \fyyyyyyyyyyyyk?s@@t wa]?( l^@@(*  la ,by ynyyyyyyyyyyyyk@sy@t wa]@(^y@( y yoyyyyyyyyyyyy k@s@@ t wa ]@(  ^@@(  y yp yyyyyyyyyyyy k@sy@ t wa ]@(  ^y@(  y yq yyyyyyyyyyyy k@u? t wa ]@(  v{gzd?(  y yr yyyyyyyyyyyy~ k@ bt wa ]@(  ^@(  y ys yyyyyyyyyyyy~ k@ bt wa ]@(  ^@( y yt yyyyyyyyyyyy.ttw]^yyyyyyyyyyyyyy nqh6d@  da $b er6e@  da $bc er6e@@  da $b er6 ey@  da $b  er6 e@@  d a $ b  er6 ey@  d a $ b er6e{gzd?  d a $ b er6e@  d a $ b er6f@ d a $ b arg s t gwi* h&* &2&   0(  0 0 b xpp?i x]4@ rnjd/  <bw: display a constant radius horizontal curve in the roadway display. this event describes the roadway that will appear on the display screen. positive values of curvature will display the curve to the right and negative values display curves to the left. each curve is limited to a total of 180 degrees (curve length multiplied by the curvature) and curves that are specified greater than 180 degrees will cause a warning to be displayed and will be ignored. there is a very important limitation that you must abide by when using the roadway curvature event: note: you must make sure that the previous curvature has been completely negotiated before you begin displaying a new curve. <  0 bp xpp?i]4@p \h[ l<mbw: distance (in feet) driver's vehicle has travelled when the event begins.<al 0 b xpp?i ]4@@ ́f߂d, <bw: the longitudinal distance, in feet, that the beginning of the curve is away from the driver when the curve first appears. <i 0 b xpp?i6 k]4@ 3y1l)?  <3bw: entry spiral length in feet. an entry spiral is a transition section of roadway from a straight section of road to a curve. the spiral will linearly change the roadway curvature from zero (straight) to the curvature of the curve (parameter 5) over the spiral length. spirals are used on real roads to ease the driver s transition into curves. note: the spirals must be specified in whole numbers of feet. <q 0 bp xpp?i i]4@p  wq"nb2- h<ibw: the longitudinal length, in feet, of the curved section of roadway. <sh 0 b xpp? i-]4@`  v)wxl <+bw: exit spiral length in feet. an exit spiral is a transition section of roadway from a curve to a straight section of road. the spiral will linearly change the roadway curvature from curvature of the curve (parameter 5) to zero (straight) over the spiral length. spirals are used on real roads to ease the driver s transition out of curves. note: the spirals must be specified in whole numbers of feet. <y 0 b xpp? i ]4@  exgj.| o <bw: constant roadway curvature (1 over the radius of curvature, 1/foot) that will be used when displaying the curved roadway section. a positive curvature means that the roadway will curve to the right while a negative value of curvatures means the roadway will curve to the left. <d 0 bp xpp? im]4@p  ˭~b0r^(g 8<bw: this optional parameter is a flag for enabling and disabling roadway super elevation. set this parameter to one of the following: 0. no super elevation 1. use super elevation super elevation is the cross-slope of the roadway driving lanes while you are in a curve. in general the roadway lanes have a slope to them that is defined using the cross-slope parameter in the road event. what this parameter does is allows you to override the cross-slope parameter and allows you to specify a new cross-slope for the curve. the magnitude of the cross-slope is specified with parameter 7. this is an optional parameter and is not required. you should also note that the shoulder and foreslopes are not affected by super elevation. <8! } _}q/  0 b xpp? i]4 @  0moeؿ1y  <bw: curve's super elevation or cross-slope measured in percent grade (100 * ft/ft). a negative value causes the travel lanes of the roadway to be banked with the curve (this helps the driver). note: parameter is optional.<  ;  0 b xpp?i]4 @  ^btdbc@heje 7 yk c:\stisim\help\sdleventc.htmyk ../../appdata/local/microsoft/windows/stisim/help/sdleventc.htmyx;h,]ą'cryk back to commands'command index'!a11yk c:\stisim\help\sdleventc.htmyk d../../../../stisim/help/sdleventc.htmyx;h,]ą'c \ distance from start of course(distance measured in feet)et parameter 1zthe longitudinal distance, in feet, that the beginning of the curve is away from the driver when the curve first appears. ep parameter 2qentry spiral length in feet. see comment in cell to the left for more details.iv ws parameter 3dthe longitudinal length, in feet, of the curved section of roadway. etls } parameter 4nexit spiral length in feet. see comment in cell to the left for more details.   parameter 5constant roadway curvature (1 over the radius of curvature, 1/foot) that will be used when displaying the curved roadway section. see comment in cell to the left for more details.d  p6 -- optionalerror!roadway super elevation 0. no super elevation 1. use super elevation see comment in cell to the left for more details.please enter either 0 or 1.orai  p7 -- optionalcurve's super elevation or cross-slope measured in percent grade (100 * ft/ft). a negative value causes the travel lanes of the roadway to be banked with the curve (this helps the driver). t   comment & command linehighlight the blue cells, then copy (ctl-c) and paste (ctl-v) into your sdl file. if you want the command without the comment, copy only the last line (with a box around it).\distance from start of course(distance measured in feet)-can sheet13ggdggh'h   {r  dmbp?_*+%&?'?(?)?mlexmark e210o odxxletterpriv''''222222222p dlcourier newh"dx??&u} i} } q} } } } } } } }            q      nx oup nz v n] w  n`~ st uuv wa:x  $ comment for d@ -- d@bp.+comment for cao -- continuous analog outputyyyyyyy zb zc[ wa xd xex \fyyyy c?s?t wa]? d6^?  da $by yxyyyy c@s?t wa]@ d6^?  da $by yxyyyy ~ c@ smbp? t wa ]@ d 6 ^mbp?  d a $ b y yy yyyy  ttyyyyyyyyy  u nq h6 d  da $b er6 e`  da $bcao er6 e? da $b er6 e? da $b er6 fmbp? d a $ b u u ar g su t gwi"&,&z" 0    4x(  4 4 b xpp?i]4@`  lm4' </bw: sends a continuous analog output to some external piece of equipment. the ao, cao, do, do2, sout and tdo events are the only way you can control external equipment during a simulation run. the cao event allows you to output continuous voltages that are proportional to the specified simulation variable. the voltage range on any individual channel is set based on the hardware specification (usually using dip switches on the board or through software provided by the hardware manufacturer, or both). currently the simulator only supports hardware from measurementcomputing. refer to the additional i/o hardware section for further details about the types of output cards that are supported. systems equipped with an active steering feel system already have a digital to analog (d/a) card in them, however, an additional card is needed in order to use the ao, cao, do, do2 and tdo events. the first d/a card is used to control the steering system, speedometer and tachometer (speedometer and tachometer are optional), and then the second card is used to handle any additional input and output (i/o) requirements that a user may have. if you have a system that does not use the active steering system, then you would install a single d/a card and use that for your additional i/o. you will need to refer to the hardware s documentation for specifics on voltage range, pin assignments and other details of the board. since you can use both the ao and cao in the same scenario, the cao event takes precedence over the ao event. this is because both events require you to specify the channel where the voltage will be output, and if both an active ao event and a cao event specify the same output channel, one of them must have priority. since the cao is outputting a steady stream of data, it is given priority. <" 4 bp xpp?i]4@p  =`m@m%/ l<mbw: distance (in feet) driver's vehicle has travelled when the event begins.<al 4 b xpp?i@ ]4@  bm;c i# <bw: analog channel on which the voltage will be output from the computer. refer to the output board's documentation for channel numbers and pin diagrams for determining the output pins and their grounds. < 4 b xpp?i]4@  ۳=aal*t (< bw: simulation variables that will be output on the specified channel in parameter 1. the variables that can be output are (these are almost exactly the same as those for the bsav event): see worksheet cao variables for descriptions of the 43 available variables.<(n 4 b xpp?i ]4@  >rzo_& -<.bw: gain that will be applied to the output channel. because the output board is only capable of generating a specified range of voltages, you will need to set a gain so that the voltage that is being output is proportional to the signal that you are sending. for example, lets say that you set parameter 2 to a value of 6 and that your run is 10000 feet. lets also say that the voltage range on the channel that you will be using is set to 0-10 volts. therefore for maximum output resolution you will want to set the gain to a value of .001 volts/foot (10 volts/10000 feet). this way at the beginning of the run the voltage output will be 0 and at the end of the run the voltage output will be 10. you will need to refer to the board documentation for setting the output voltages for each channel on the board. < - 4 b xpp? i]4@@ pdq,1o <comment & command line: highlight the blue cells, then copy (ctl-c) and paste (ctl-v) into your sdl file. if you want the command without the comment, copy only the last line (with a box around it).<rive michel bdard  michel bdard  michel bdard  michel bdard   michel bdard   michel bdard >@heje 7yk c:\stisim\help\sdleventcao.htmyk ../../appdata/local/microsoft/windows/stisim/help/sdleventcao.htmyx;h,]ą'cryk back to commands'command index'!a12yk c:\stisim\help\sdleventcao.htmyk h../../../../stisim/help/sdleventcao.htmyx;h,]ą'ck output channelanalog channel on which the voltage will be output from the computer. refer to the output board's documentation for channel numbers and pin diagrams for determining the output pins and their grounds. com variableserrorsimulation variables that will be output on the specified channel in parameter 1. the variables that can be output are (these are almost exactly the same as those for the bsav event). see worksheet "cao variables" for a complete list. *you must enter a number in the range 1-43.a  o+\ distance from start of course(distance measured in feet)pefi gaindgain that will be applied to the output channel. see comment in cell to the left for more details.haca   comment & command linehighlight the blue cells, then copy (ctl-c) and paste (ctl-v) into your sdl file. if you want the command without the comment, copy only the last line (with a box around it).kset  sheet14ggdggh'h   /  dmbp?_*+%      !"#$%&'()*+,-./0123456789:;<=>?@abcdefghijklmnopqrstuvwxyz[\]^_`abcdefghijklmnoqrstuvwxyz{|}~&?'?(?)?"??&u} $ r} ^s/      p q~ r? s~ r@ s~ r@ s~ r@ s ~ r@ s!~ r@ s"~ r@ s#~ r @ s$~ r"@ s%~ r$@ t&~ r&@ s'~ r(@ s(~ r(@ s)~ r*@ s*~ r*@ s+~ r,@ s,~ r.@ s-~ r0@ s.~ r1@ s/~ r2@ t0~ r3@ sz~ r4@ s[~ r5@ s\~ r6@ s4~ r7@ s5~ r8@ s6~ r9@ s7~ r:@ s8~ r;@ s9~ r<@ s:~ r=@ s;dl !"#$%&'()*+,-.~ r>@ s<~ !r?@ !s=~ "r@@ "s>~ #r@@ #s?~ $ra@ $s@~ %ra@ %sa~ &rb@ &sb~ 'rb@ 'sc~ (rc@ (sd~ )rc@ )s]~ *rd@ *s^~ +rd@ +sg~ ,re@ ,sh~ -re@ -si ." 8 (  8 8 b xpp? i0]4@ fqjrudo  <abw: this value will always be in the general range of + or  90 degrees. this is because when a driver performs a right or left hand turn, the software moves the driver back to the main road. for the inertial value of heading angle (composite value that includes turns), see parameter 41.<u d 8 bp xpp?i#]4@p` |!fk4 <bw: the accidents have the following numbers: 1 - vehicle collisions 2 - off road collisions 3 - collisions with pedestrians for example, if the current number shown for this parameter is 10, then on the next line of the stisim drive data file, this parameter has changed to 13, then an accident occurred and it was a collision with a pedestrian (13-10=3 therefore a pedestrian was run over). < 8 b xpp?ipi]4@  |9gv' &<mbw: overall minimum time to collision (ttc) for the current simulation frame. during each simulation frame the ttc for each vehicle traveling in the driver s initial direction (does not work correctly if driver does a u turn) will be computed and the lowest overall value of ttc will be used. <x&  8 b xpp?i <]4@  \ŵ4i 6s .<]bw: overall minimum range for the current simulation frame. during each simulation frame the range between the driver and for each vehicle traveling in the driver s initial direction (does not work correctly if driver does a u turn) will be computed and the lowest overall value of range will be used. <.  8 bp xpp?i'-]4@p qk-o- ވ _<`bw: driver's head yaw angle (degrees). this is only available if you are using a head tracker. <_ 8 b xpp?i -]4@ )yboqԤ] <bw: if this is set and you simultaneously press the alt-m keyboard combination the marker will increment by 1. this allows you to view the driver and then mark the data file if you see something that you may want to check later. <c  8 b xpp?i!]4@@ slf-( <bw: actual raw steering wheel input directly from the steering wheel. this variable is only available on systems that use the simple dynamics. <  8 bp xpp?i"]4@p *$֝e!'] <bw: actual raw throttle input directly from the throttle pedal. this variable is only available on systems that use the simple dynamics. <|   8 b xpp?i#]4 @ ,=e )t <bw: actual raw braking input directly from the brake pedal. this variable is only available on systems that use the simple dynamics. <r   8 b xpp?i0i]4 @` l-cv ^<_bw: this only applies to single monitor and head mounted display systems and not to systems with a wide field of view. this parameter is the current viewing angle of the center display with 0 being straight ahead and positive values mean the view is looking to the right. the view angle can be changed by pressing the f1 (left) and f2 (right) keys on the keyboard (5 degree increments), or by simultaneously activating the horn and left or right turn signal indicator. in this case the view angle will change at 90 degree increments and only allows the angle to get to a value of plus or minus 90 degrees. <? ^   8 bp xpp?i$]4 @p *3 wek&y s<tbw: total pitching angle, includes both ground slope and vehicle motion (radians) <s   8 b xpp? i%<]4 @   tf9f q<rbw: total rolling angle, includes both ground slope and vehicle motion (radians) <{q 0s  8 b xpp?"i']4 @ $t[eig?d <bw: this is set to a value of 1 if the driver selected to have the driver s view rotate 90 degrees to the left, otherwise it will be 0. <g 8 bp xpp?#i)]4@p bz@moji^u\ p <bw: this is set to a value of 1 if the driver selected to have the driver s view rotate 90 degrees to the right, otherwise it will be 0. <m 8 b xpp?$ip+]4@@ cԦݧgw>ft <kbw: note: in order to save variables 35-38, the collect time to collision data option must be activated. you can set this option in the configuration s other tabbed dialog window. <y  8 b xpp?%ip,]4@ rdױgzgu?|$ <kbw: note: in order to save variables 35-38, the collect time to collision data option must be activated. you can set this option in the configuration s other tabbed dialog window. <y  8 bp xpp?&ip-]4@p pj_o={} <kbw: note: in order to save variables 35-38, the collect time to collision data option must be activated. you can set this option in the configuration s other tabbed dialog window. <y  8 b xpp?'ip.]4@` ѩ`m s. <kbw: note: in order to save variables 35-38, the collect time to collision data option must be activated. you can set this option in the configuration s other tabbed dialog window. <y  8 b xpp?)i/]4@ t.p:*sbaz k<lbw: note: need to ask ted rosenthal if rt can be measured with finer resolution (e.g., for ior scenarios).<k 8 bp xpp?+ip3]4@p  \mgh2 <bw: byte that contains the current state of all of the input buttons. to get a particular buttons status, you will need to perform a logical and between this value and the button assignment value that was specified in the simulator configuration. <@s 8 b xpp?,ip<<]4@ 1 &b < bw: current status of the digital input port on the secondary i/o card. the input port allows for 12 bits of information (4096 values) and will require a logical and operation in order to look at the individual bits. the secondary i/o card is an optional board and does not come as standard equipment on any simulator system. review the hardware section for more information on this option. the 12 bit number is as follows: register cl: register a: bits: {12 11 10 9} {8 7 6 5 4 3 2 1} < sow bw bw bw bw bw bw bw bw  bw  bw   bw ! bw # bw $bw %bw &bw 'bw (bw *bw ,bw -bw >@ a 7 sheet15ggd  8*5  dmbp?_*+%&?'?(?)?"??al&u} u} } q} } } } } } } } } } } } $ } } 5     q nx o_p nz ` n] an n`~ s@@t uv wa:xp $ comment for d@ -- d@bp&#comment for colb -- collision block yyyyyyyyyyyyy zb zc[ wa xd xex \fyyyyyyyyyyk?s@@t wa]?( l^@@(*  la ,by ybyyyyyyyyyyk@s.t wa]@(^.( y ycyyyyyyyyyy k@s>@ t wa ]@(  ^>@(  y yd yyyyyyyyyy k@s>@ t wa ]@(  ^>@(  y ye yyyyyyyyyy~ k@ s t wa ]@(  ^x ( c:\stisim\sounds\thud.wav y yf yyyyyyyyyy k@s$@ t wa ]@(  ^$@( y y yyyyyyyyyy* ttw]^yyyyyyyyyyyy nqh6d@@  da $b er6eb  da $bcolb er6e@@  da $b er6 e.  da $b  er6 e>@  d a $ b  er6 e>@  d a $ b er6e   d a $ bc:\stisim\sounds\thud.wav er6f$@ d a $ b arg s g gwi(p t&& &.u&  4 <(  < < bp xpp?i]4@p jim^ren <ubw: this event allows an area of the roadway display to be designated as a collision area. basically, the colb event creates an invisible rectangular area that is unknown to the driver and if the driver s vehicle enters this area a collision will occur. if a collision occurs, all of the stisim drive collision routines will be activated (tdo event will trigger, number of collision will increase by one, crash routine will be activated, collision will be flagged for inclusion in the driver mistakes section of the stisim drive data file). unlike some events such as the barrels or other vehicles, when a driver has a collision with a collision block, the collision block remains. however, this event does adhere to the crash buffer option (configuration s initialize tab dialog box) meaning that if there is a collision, the driver may travel the crash buffer distance before crashing again. see help file for colb (hyperlink on line 3) for more info.< < b xpp?ri3]4@ h tuh@ve  l<mbw: distance (in feet) driver's vehicle has travelled when the event begins.<al < b xpp?ri  ]4@` k+3hrЊ }<~bw: the longitudinal distance, in feet, that the center of the block is away from the driver when it is initially activated. <+} < bp xpp?ri k]4@p ˏ hxlac \<bw: lateral position, in feet, from the roadway s dividing line to the center of the block. <\ < b xpp?ri i]4@   r]kifk^ƶ- ?<@bw: longitudinal (down the road) length of the block, in feet. <? < b xpp?r i ]4@ nx&o 8<9bw: lateral (side to side) width of the block, in feet. <8 < bp xpp?r i ]4@p pj;ta oq e<fbw: collision block sound effect file. if this parameter is left blank, then stisim drive will use its current default crash settings for handling the collision. otherwise, if a valid sound file is specified in this parameter the program will use the file for playing the sound effect instead of the stisim drive crash file. <e < b xpp?r ix]4@@ dwd&5 &<'bw: volume control. range = 0 to 10. <&  < b xpp? i']4 @ vܭjv4x <comment & command line: highlight the blue cells, then copy (ctl-c) and paste (ctl-v) into your sdl file. if you want the command without the comment, copy only the last line (with a box around it).<rive michel bdard  michel bdard  michel bdard  michel bdard   michel bdard   michel bdard   michel bdard   michel bdard  michel bdard >@heje 7yk  c:\stisim\help\sdleventcolb.htmyk ../../appdata/local/microsoft/windows/stisim/help/sdleventcolb.htmyx;h,]ą'cryk back to commands'command index'!a13yk  c:\stisim\help\sdleventcolb.htmyk j../../../../stisim/help/sdleventcolb.htmyx;h,]ą'c\ distance from start of course(distance measured in feet)et parameter 1ythe longitudinal distance, in feet, that the center of the block is away from the driver when it is initially activated. i/ parameter 2xlateral position, in feet, from the roadway s dividing line to the center of the block. ,j parameter 3;longitudinal (down the road) length of the block, in feet. h  c parameter 44lateral (side to side) width of the block, in feet.    parameter 5rcollision block sound effect file. see comment in cell to the left for more info.sd  p6 -- volume controlerror!range: 0 to 10 (please enter a number in the range 0-10.e     comment & command linehighlight the blue cells, then copy (ctl-c) and paste (ctl-v) into your sdl file. if you want the command without the comment, copy only the last line (with a box around it). sheet16ggdggh'h   -u^  dmbp?_*+%&?'?(?)?"??&u} u} } q} } } } } } } } } } 5   q  nx ohp nz i n] jn n`~ s@@t uv wa:x  $ comment for d@ -- d@bp+(comment for cset -- set crash parametersyyyyyyyyy zb zc[ wa xd xex \fyyyyyy k?s@t wa]? d6^@  da $by ykyyyyyy k@st wa]@ d6^  da $by ylyyyyyy ~ k@ bt wa ]@ d 6 ^@  d a $ b y ym yyyyyy  k@b@o@ t wa ]@ d 6 ^@o@  d a $ b y yn yyyyyy " ttyyyyyyyyyyy nq h6 d@@  da $b er6 eb  da $bcset er6 e@ da $b er6 e da $b er6 e@ d a $ b er6 f@o@ d a $ b arg s g gwi$,&& &~&& w   @(  @ @ bp xpp?i/]4@p  bhom*a]i f<bw: this is an event for changing the simulation s crash parameters. when a driver crashes during a simulation run, their vehicle is automatically set back to the position in the roadway specified by the "initial position" property in the configuration s initialize tab dialog box. additionally, under the crash options section of the configuration s sound tab dialog box you can specify if and how the crash sound effect will be used during a crash. because these parameters are specified in the simulations configuration, they will remain constant for the entire simulation run, unless there is an event that can change them. this event will do this for you. in general you will probably just set the values in the configuration and then leave them alone, however, there are some cases when you may wish you had a little more control. <uf @ b xpp?ri3]4@ lenjwa; l<mbw: distance (in feet) driver's vehicle has travelled when the event begins.<al @ b xpp?ri ]4@@ jߘbdo!Ƌx 7<8bw: this parameter is a flag that tells stisim drive how the crash sound effect will be used. to specify how accidents will be handled, set parameter 1 to one of the following: 0. play recording, reset lane position and speed 1. play recording, only reset position 2. play recording, only reset speed 3. play recording, do not reset either position or speed 4. do not play recording, reset lane position and speed 5. do not play recording, only reset position 6. do not play recording, only reset speed 7. do not play recording, do not reset either position or speed< 7 @ bp xpp?ri ]4@p pj o<bw: initial position of the vehicle with respect to the roadway s dividing line, positive to the right (feet). <o @ b xpp?riz]4@ m[$nawcb <bw: distance off the edge of the road where a crash occurs, positive to the right (feet). leaving this parameter blank will retain the same value as before. <te  @ b xpp?r i]4@` fl`m  <bw: buffer distance after an accident has occurred before another accident can occur (feet). leaving this parameter blank will retain the same value as before. <een @ bp xpp? im]4@p |dto(a6 mu <comment & command line: highlight the blue cells, then copy (ctl-c) and paste (ctl-v) into your sdl file. if you want the command without the comment, copy only the last line (with a box around it).<rive michel bdard  michel bdard  michel bdard bwc bwc bwc  michel bdard >@heje 7yk  c:\stisim\help\sdleventcset.htmyk ../../appdata/local/microsoft/windows/stisim/help/sdleventcset.htmyx;h,]ą'cryk back to commands'command index'!a14yk  c:\stisim\help\sdleventcset.htmyk j../../../../stisim/help/sdleventcset.htmyx;h,]ą'c\ distance from start of course(distance measured in feet)eta 1. crash sound effecterror!0. recording, reset position & speed 1. recording, reset position 2. recording, reset speed 3. recording, reset neither 4. no recording, reset position & speed 5. no recording, reset position 6. no recording, reset speed 7. no recording, reset neither"please enter a number from 0 to 7.sehe parameter 2kinitial position of the vehicle with respect to the roadway s dividing line, positive to the right (feet). in r parameter 3distance off the edge of the road where a crash occurs, positive to the right (feet). leaving this parameter blank will retain the same value as before. ii  parameter 4buffer distance after an accident has occurred before another accident can occur (feet). leaving this parameter blank will retain the same value as before. i    comment & command linehighlight the blue cells, then copy (ctl-c) and paste (ctl-v) into your sdl file. if you want the command without the comment, copy only the last line (with a box around it).t(  sheet17ggdggh'h   &|2  dmbp?_*+%&?'?(?)?"??&u} u} } q} } } } } } } } } } } } } } } } 5     q nx oop nz p n] gqin n`~ s@@t uv wa:x $ comment for d@ -- d@bp"comment for ct -- cross traffic$yyyyyyyyyyyyyyy zb zc[ wa xd xex \fyyyyyyyyyyyyk?s@@t wa]?( l^@@(*  la ,by yryyyyyyyyyyyyk@s@t wa]@(^@( y ysyyyyyyyyyyyy k@sy@ t wa ]@(  ^y@(  y yt yyyyyyyyyyyy k@s? t wa ]@(  ^?(  y yu yyyyyyyyyyyy~ k@ sv t wa ]@(  ^@( r y yw yyyyyyyyyyyy~ k@ sx t wa ]@(  ^(  *2~8;-5 y yy yyyyyyyyyyyy k@s? t wa ]@(  ^?( y yz yyyyyyyyyyyy.ttyyyyyyyyyyyyyyyyy nqh6d@@  da $b er6eh  da $bct er6e@@  da $b er6 e@  da $b  er6 ey@  d a $ b  er6 e?  d a $ b er6e@  d a $ br er6e  d a $ b *2~8;-5 er6f? d a $ b arg s g g\irrr g_irrrrr gw. && &2& $ w r d(  d d b xpp?i x]4@  ; 5n`"3  < bw: display a cross traffic vehicle. no intersection will be displayed when this event is called, you must display your own intersection using the i event. the speed, direction, and lateral distance of the cross traffic vehicle is set using the event parameters. <  d b xpp?ri3]4@ z:h{cmȲ l<mbw: distance (in feet) driver's vehicle has travelled when the event begins.<al d b( xpp?ri  ]4@( u'@0pba }<~bw: the longitudinal distance, in feet, that the cross traffic vehicle is away from the driver when it initially appears. <?} d b xpp?ri]4@@ z薇|mcp] .<]bw: cross traffic display options. to specify the display option set parameter 2 to one of the following: 1. set crossing vehicle so that if the driver keeps constant speed the crossing vehicle will pass behind the driver without colliding with them 2. set crossing vehicle so that if the driver keeps constant speed the crossing vehicle will collide with the driver's vehicle 3. set crossing vehicle so that if the driver keeps constant speed the crossing vehicle will pass in front of the driver without colliding with them 4. specify the crossing vehicle s characteristics using lateral position and a percentage of the driver s vehicle speed (see parameters 3 and 4) 5. specify the crossing vehicle s characteristics using lateral position and constant speed (see parameters 3 and 4) <. d b xpp?ri i]4@ {e <ubw: the initial lateral position, in feet, that the crossing vehicle is away from the roadway s dividing line. this is only used if parameter 2 is set to 4 or 5, otherwise set it to 0. <s d b( xpp?r i]4@( ^{f@heje7yk c:\stisim\help\sdleventct.htmyk f../../../../stisim/help/sdleventct.htmyx;h,]ą'cryk back to commands'command index'!a15yk vehicle index numbersyk h../../../../stisim/help/sdlvehicles.htmyx;h,]ą'cyk randon selection of parametersyk j../../../../stisim/help/randomparams.htmyx;h,]ą'cw \ distance from start of course(distance measured in feet)pr parameter 1wthe longitudinal distance, in feet, that the cross traffic vehicle is away from the driver when it initially appears. i/ 2. display optionserror!1. cv goes behind 2. cv collides 3. cv in front 4. cv relative to driver 5. cv constant speed see comment in cell to the left for more details."please enter a number from 1 to 5.ig parameter 3the initial lateral position, in feet, that the crossing vehicle is away from the roadway s dividing line. this is only used if parameter 2 is set to 4 or 5, otherwise set it to 0. heth  parameter 4velocity, in feet/second, for the cross traffic vehicle. only used if p2 in [4,5]. see comment in cell to the left for more details.a   5. side cv approaches fromkvalues: l r default is r (if parameter left blank). see comment in cell to the left for more details.ailra  p6 - vehicle model for cverror!the vehicle model index for the cross traffic vehicle {vehicles}.you may randomly have a vehicle selected for you by using stisim drive s random parameter selection capabilities. please enter either 0 or 1.ngs   p7 - intelligent vehicle flagerror!n0. cross traffic vehicles are dumb 1. ctvs are intelligent see comment in cell to the left for more details. please enter either 0 or 1.ro   comment & command linehighlight the blue cells, then copy (ctl-c) and paste (ctl-v) into your sdl file. if you want the command without the comment, copy only the last line (with a box around it). e sheet18ggdggh'h   y  dmbp?_*+%&?'?(?)?"??&u} u} } q} } } } } } 5           q     nx o{p nz | n] g}in n`~ s@@t uv wa:x  $ comment for d@ -- d@bp$!comment for cv -- control vehicleyyyyy zb zc[ wa xd xex \f yy k?st@t wa]? d6^t@  da $by y~ yy k@s?t wa]@ d6^?  da $by y yy  ttyyyyyyy nq h6 d@@  da $b er6 e  da $bcv er6 et@ da $b er6 f? da $b ar g s g gwi && &v3&     h(  h h b xpp?i x]4@ j4d <bw: control the vehicle automatically. in the program's configuration windows there is an option to use an automatic pilot (autopilot mode under the configuration s i/o control tab dialog box). the automatic pilot is limited in that it controls both the steering and the speed for the entire simulation run. unlike the autopilot option, this event allows the scenario designer to control either the steering, the speed or both. furthermore, you can change what the driver is controlling in the middle of a run. this is ideal for training drivers on how to use the steering and accelerator. note: the cv event can only be used on systems running the simple dynamics. advanced dynamics systems may hang during curves if the cv event is used. <  h bp xpp?ri3]4@p` [s+d  l<mbw: distance (in feet) driver's vehicle has travelled when the event begins.<al h b xpp?ri  ]4@ '9xeafƚv <bw: the speed, in feet/second, that the vehicle will be traveling. if this value is set to 0, then the driver will have control of the accelerator. < h b xpp?rie]4@   `"f@9l-stt <bw: flag giving the driver control of the steering wheel. to specify the steering wheel control option, set parameter 2 to one of the following: 0. driver controls the vehicle's steering. when this value is used, the program returns the crash parameters to the values that were set before the previous cv event was processed. see the cset event. 1. driver controls the vehicle's steering and all crashes will be ignored 2. computer controls the steering and all crashes will be ignored <^  h bp xpp? i]4@p !lx*hys5 e <comment & command line: highlight the blue cells, then copy (ctl-c) and paste (ctl-v) into your sdl file. if you want the command without the comment, copy only the last line (with a box around it).<rive michel bdard  michel bdard  michel bdard  michel bdard   michel bdard >@heje7yk c:\stisim\help\sdleventcv.htmyk f../../../../stisim/help/sdleventcv.htmyx;h,]ą'cryk back to commands'command index'!a16w\ distance from start of course(distance measured in feet)cm parameter 1the speed, in feet/second, that the vehicle will be traveling. if this value is set to 0, then the driver will have control of the accelerator. c.c 2. steering wheel controlerror!0. driver steering; program returns the crash parameters to the values that were set before the previous cv event was processed. 1. driver controls sterring; alll crashes ignored 2. computer controls steering; all crashes will be ignored "please enter a number from 0 to 2.esse  comment & command linehighlight the blue cells, then copy (ctl-c) and paste (ctl-v) into your sdl file. if you want the command without the comment, copy only the last line (with a box around it).gned  sheet19ggdggh'h  9  dmbp?_*+%&?'?(?)?mlexmark e210o odxxletterpriv''''222222222p dlcourier newh"dx??&u} u} } q} } } } } } } } 5            q     nx op nz  n] gin n`~ s@@t uv wa:x@6 $ comment for d@ -- d@bp&#comment for da -- divided attentionyyyyyyy zb zc[ wa xd xex \fyyyy k?s?t wa]? d6^?  da $by yyyyy k@s@t wa]@ d6^@  da $by yyyyy  k@b @ t wa ]@ d 6 ^ @  d a $ b y y yyyy  ttyyyyyyyyy nq h6 d@@  da $b er6 e  da $bda er6 e? da $b er6 e@ da $b er6 f @ d a $ b ar g s g gwi"&& &z"{&    0lx(  l l b xpp?i]4@ ~g($ak% <bw: display a divided attention symbol. in order for this event to work, the  display divided attention symbols configuration option (other tab box) must be set to on. in addition, the  divided attention options button can be used to set the specifics about displaying the symbols. additionally, this event uses the "mean divided attention response time" configuration parameter (configuration s post run tab dialog box) for displaying the da event results in the run summary, and the "maximum divided attention display time" parameter (configuration s initialize tab dialog box) for setting the maximum reaction time. the symbols will be displayed until the driver responds, or until the maximum time has elapsed. when a horn symbol is requested, the program will display the horn symbol in the specified divided attention box, and the driver will be required to press the divided attention horn input in response. when a turn indicator response is requested, a triangle pointing either left, right, up or down will be displayed (left pointing triangle in the left divided attention box, right pointing triangle in the right divided attention box and the up and down triangles in either divided attention box). when this appears, the driver must respond by using the button input that corresponds to the symbol being displayed. the correct inputs are: symbol displayed: appropriate driver response ----------------------------------------------------------------------- left triangle left divided attention input right triangle right divided attention input down triangle left divided attention input up triangle right divided attention input horn horn divided attention input using the configuration s i/o control tab dialog box you can assign the horn, left and right divided attention inputs to specific buttons on the steering console. < $ l b xpp?ri3]4@ lmbxab}h l<mbw: distance (in feet) driver's vehicle has travelled when the event begins.<al l b( xpp?ri ]4@(` |辒e <bw: divided attention symbols. 0. diamond 1. l triangle in l box 2. r triangle in r box 3. l horn in l box 4. r horn in r box 5. up in l box 6. down in r box 7. up in r box 8. down in l box < l b xpp?ri ]4@ qufe <bw: divided attention action options. to specify the divided attention action, set parameter 2 to one of the following: 0. driver is suppose to respond to symbols, all events will continue to appear whether the driver responds or not 1. wait till the driver responds or the maximum response time is met before processing other events 2. wait till the driver responds correctly before processing other events, if they respond incorrectly play the "daerror.wav" file 3. display the symbol until another da event is processed note: options 1 and 2 can have some interesting affects on the scenario. because scenarios are all distance based and new events are activated based on the driver s distance into the run, a new event will not be activated until the proper driver response is given. therefore, if the driver waits too long an event may never appear. these options were left in to keep it consistent with previous versions of the software. <, l b xpp?riz]4@  ˆn?mۋ:a7 }(<~bw: volume control if the "daerror.wav" file is played. values range from 0 to 10. note: use this parameter only if p2 = 2.<(ty}te  l bp xpp? i]4@p ?/ae$ 8c <comment & command line: highlight the blue cells, then copy (ctl-c) and paste (ctl-v) into your sdl file. if you want the command without the comment, copy only the last line (with a box around it).<rive michel bdard  michel bdard  michel bdard bwc bwc  michel bdard >@heje7yk c:\stisim\help\sdleventda.htmyk f../../../../stisim/help/sdleventda.htmyx;h,]ą'cryk back to commands'command index'!a17|\ distance from start of course(distance measured in feet)cm  1. divided attention symbolserror!0. diamond 1. l triangle in l box 2. r triangle in r box 3. l horn in l box 4. r horn in r box 5. up in l box 6. down in r box 7. up in r box 8. down in l box "please enter a number from 0 to 8.  9 2. da action optionserror!0. driver should respond; all actions continue regardless 1. wait for driver response or time limit 2. wait for correct response 3. display symbol until next da event see comment in cell to left for more details."please enter a number from 0 to 3. r 3. volume controlerrorrvolume control if the "daerror.wav" file is played. rrange: 0 to 10. note: use this parameter only if p2 = 2. correct range = 0 to 10. s u    comment & command linehighlight the blue cells, then copy (ctl-c) and paste (ctl-v) into your sdl file. if you want the command without the comment, copy only the last line (with a box around it).inel  sheet20ggdggh'h      dmbp?_*+%&?'?(?)?"??&u} u} } q} } } } 5x     nx op nz  n] gin n`~ sy@t uv wa:x@ $ comment for d@ -- d@bp"comment for di -- digital input yyy zb zc[ wa xd xex \fk?sp@t wa]? d6^p@  da $by y ww nq h6 dy@  da $b er6 e  da $bdi er6 fp@ da $b ar g s g gw iz&& &h&    x@p`(  p p b1 xpp?i]4@1 h7hbo c(< bw: this event allows you to read digital inputs from an external piece of equipment during a simulation run. the simulation accepts digital inputs on up to 12 separate pins. the signal bits are input through registers a (8 bits) and cl (4 bits) of port 1 on the digital i/o board. once the event has been activated, the system will continually poll the interface card until it detects an input on one of the available pins. at this time the system will record the response time, the correctness of the response and then turn the event off. the next di event in the events file will cancel any current di event that may be active. the final results of the di event are compiled in their own section of the stisim drive data file. review the hardware configuration section for information about the boards supported and configuring them. in addition, if you will be using the di event you must make sure that the digital i/o option has been enabled in stisim drive's configuration. to enable the digital i/o, simply check the appropriate box in the configuration s i/o controls tab dialog box. you can also use the bsav event to capture data from the digital input registers. in this case the digital input registers are scanned at each data interval and the composite input that was read is added to the stisim drive data file. note: only 1 di event can be active at a time. <(2&:c p b1 xpp?ri3]4@1 say,0!4 l<mbw: distance (in feet) driver's vehicle has travelled when the event begins.<al p b1 xpp?ri ]4@1` ԥpd&go < bw: a number that corresponds to the expected correct response for the di event. each di event requires that you specify what the correct response will be during the event. this is required because the software checks the driver s response with the expected response to determine if the driver responded correctly. when a driver responds, signals come across various pins on the digital i/o card, and the di event records which of the pins on the i/o card are currently set. if a bit is set to 1 on any of the specified pins, the program will check to see if that bit matches to the setting of the corresponding bit specified as the correct response. the number that is specified is the decimal equivalent of a 12 bit binary number, where the first 4 bits of the number are the 4 bits of register cl on the i/o card and the last 8 bits are register a. if you know which pins the desired response will be coming across on, simply use the windows scientific calculator in binary mode to specify the bits, then convert it into a decimal number. the 12 bit number is as follows: register cl: register a: bits: {12 11 10 9} {8 7 6 5 4 3 2 1} note: when creating the hardware that is required to input the signals from external devices, you may require push up or pull down resistors in order for the hardware to operate correctly. refer to the documentation that comes with your digital interface card. <a p b(2 xpp?im ]4@(2 m]-eon <comment & command line: highlight the blue cells, then copy (ctl-c) and paste (ctl-v) into your sdl file. if you want the command without the comment, copy only the last line (with a box around it).<rive michel bdard  michel bdard  michel bdard   michel bdard >@heje  7yk c:\stisim\help\sdleventdi.htmyk f../../../../stisim/help/sdleventdi.htmyx;h,]ą'cr yk back to commands'command index'!a18w\ distance from start of course(distance measured in feet)cm parameter 1error!{a number that corresponds to the expected correct response for the di event. see comment in cell to the left for details.ps comment & command linehighlight the blue cells, then copy (ctl-c) and paste (ctl-v) into your sdl file. if you want the command without the comment, copy only the last line (with a box around it).yu  sheet21ggdggh'h  %4(9  dmbp?_*+%&?'?(?)?"??&u} u} } q} } } } 5q     nx op nz  n] gin n`~ s@@t uv wa:x6 $ comment for d@ -- d@bp# comment for do -- digital output yyy zb zc[ wa xd xex \fk?sp@t wa]? d6^p@  da $by y tt nq h6 d@@  da $b er6 e  da $bdo er6 fp@ da $b ar g s g gw i{&& &h&    xpt`(  t t b(3 xpp?i z]4@(3 20nlh <bw: this event allows you to send digital outputs to external equipment during simulation runs. the ao, cao, do, do2, sout and tdo events are the only way you can control external equipment during a simulation run. the simulation allows you to specify the output of up to 12 individual pins on the i/o card. these outputs are processed through registers b (8 bits) and ch (4 bits) on port 1 of the digital i/o board. review the hardware section for information on the output board s support and how to configure them. in addition, if you will be using the do event you must make sure that the digital i/o option has been enabled in stisim drive's configuration. to enable the digital i/o, simply check the box on the configuration s i/o controls tab dialog box. <u t b3 xpp?ri3]4@3@ 'en! l<mbw: distance (in feet) driver's vehicle has travelled when the event begins.<al t b3 xpp?ri]4@3 k(lk1u <7 bw: number that sets the specified pin s outputs to high (1) or low (0). the i/o card is automatically configured so that there are 12 bits that you can set to either high (1) or low (0). the first 4 bits of the number are the high portion of register c (register ch) while the final 8 bits are from register b. register ch: register b: bits: {12 11 10 9} {8 7 6 5 4 3 2 1} when you decide which pins you will change, simply use the windows scientific calculator in binary mode to specify the bits, then convert it into a decimal number and use this number as the input. because stisim drive is used for a variety of applications, sometimes we add a custom option that will not be useful for everyone but is available for everyone to use. the do event is one of these options. several researchers that use stisim drive need real-time information about potential time to collisions (ttcs). in order for them to receive this data in real-time, stisim drive sends a digital signal that is proportional to the ttc. in order to use this special option you must set this parameter to a negative value. if this parameter is set to a negative value (we use  1) then at each simulation frame time, stisim drive will send out the smallest value of ttc that it computes (ttc is computed for each non cross traffic vehicle (ct event) in the display scene). there are a couple of limits to this approach: 1. since the ttc is sent continuously during the run, you can not use the di and tdo events at all, and you can only use the do event for sending ttc. 2. the data that is sent is 12 bits and needs to be divided by 1000 in order to compute the actual ttc value. <= t b(4 xpp?im ]4@(4 ow6fĺum <comment & command line: highlight the blue cells, then copy (ctl-c) and paste (ctl-v) into your sdl file. if you want the command without the comment, copy only the last line (with a box around it).<rive michel bdard  michel bdard  michel bdard   michel bdard >@heje  7yk c:\stisim\help\sdleventdo.htmyk f../../../../stisim/help/sdleventdo.htmyx;h,]ą'cr yk back to commands'command index'!a19w\ distance from start of course(distance measured in feet)cm  parameter 1error!rnumber that sets the specified pin s outputs to high (1) or low (0). see comment in cell to the left for details.1  comment & command linehighlight the blue cells, then copy (ctl-c) and paste (ctl-v) into your sdl file. if you want the command without the comment, copy only the last line (with a box around it).el  sheet22ggdggh'h  !x`a  dmbp?_*+%&?'?(?)?"??&u} u} } q} } } } } } } } } } 5   q  nx op nz  n] gin n`~ s@@t uv wa:x` $ comment for d@ -- d@bp/,comment for do2 -- digital output (extended)yyyyyyyyy zb zc[ wa xd xex \fyyyyyy k?s@t wa]? d6^@  da $by yyyyyyy ~ k@ st wa]@ d6^  da $b|16y yyyyyyy ~ k@ s t wa ]@ d 6 ^  d a $ b&3 y y yyyyyy ~ k@ s t wa ]@ d 6 ^c  d a $ b^255 y y yyyyyy " ttyyyyyyyyyyy nq h6 d@@  da $b er6 e  da $bdo2 er6 e@ da $b er6 e da $b|16 er6 e d a $ b&3 er6 f$c d a $ b^255 arg s g gwi$w,&& &~&& w   `x(  x x b(5 xpp? ]4@(5 pw8@'wڋ (<qbw: this event allows you to send digital outputs to external equipment during simulation runs. the ao, cao, do, do2, sout and tdo events are the only way you can control external equipment during a simulation run. this event is similar to the do event except that it only works on hardware with multiple digital i/o ports and only on ports above 1. furthermore, unlike port 1 which is setup for 12 bits of output (do event) and 12 bits of input (di event), ports 2 and higher are all configured for digital output. each digital port has 3 8 bit registers (a, b and c) that you can control. for the do2 event, you will need to specify the port that will be used and then the output value for each of the 3 registers. review the hardware section for information on the output boards supported and how to configure them. in addition, if you will be using the do2 event you must make sure that the digital i/o option has been enabled in stisim drive's configuration. to enable the digital i/o, simply check the box on the configuration s i/o controls tab dialog box. <( x b5 xpp?ri3]4@5  wb^qsd2fvt l<mbw: distance (in feet) driver's vehicle has travelled when the event begins.<al x b5 xpp?ri | ]4@5 mcsf¢sܖ <bw: port number that the specified values will be sent out on. this must be greater than 1 and less than or equal to the number of ports supported by the board being used for digital outputs. < x b(6 xpp?ri]4@(6 " eɷn7 o<bw: byte value that will be output on register a. this value can either be a completely new value or can be combined (bitwise) with the value currently being used by the register. to enter a completely new value, simply specify a new data byte. there are three options for bitwise combining a new data byte with the register s current output, or, and, and xor (exclusive or). to perform a bitwise operation, simply include the following symbol in front of the data byte that will be combined with the current register value: | or & and ^ xor no matter how the data byte is created, the program will take the specified value, and break it into individual bits that control the corresponding pins on the digital i/o board. a value of 1 will cause the specific pin to go high (approximately 5 volts), while a value of 0 will turn the pin off (0 volts). <o x b6 xpp?ri i]4@6@ j|5mzۏ y<zbw: byte value that will be output on register b. refer to parameter 2 for additional information on outputting values. <@y x b6 xpp?r i' ]4@6 Ƥo 'cow w<xbw: byte value that will be output on register c refer to parameter 2 for additional information on outputting values. <2w x b(7 xpp? im]4@(7 kq=m|l <comment & command line: highlight the blue cells, then copy (ctl-c) and paste (ctl-v) into your sdl file. if you want the command without the comment, copy only the last line (with a box around it).<rive michel bdard  michel bdard  michel bdard  michel bdard   michel bdard   michel bdard   michel bdard >@heje7yk c:\stisim\help\sdleventdo2.htmyk h../../../../stisim/help/sdleventdo2.htmyx;h,]ą'cryk back to commands'command index'!a20z\ distance from start of course(distance measured in feet)cm parameter 1dport number that the specified values will be sent out on. see comment in cell to left for details... paramter 2error!`byte value that will be output on register a. see comment in cell to the left for more details."please enter a number from 1 to 5./d parameter 3ubyte value that will be output on register b. refer to parameter 2 for additional information on outputting values. r om  parameter 4sbyte value that will be output on register c refer to parameter 2 for additional information on outputting values.    comment & command linehighlight the blue cells, then copy (ctl-c) and paste (ctl-v) into your sdl file. if you want the command without the comment, copy only the last line (with a box around it).b  sheet23ggdggh'h     dmbp?_*+%&?'?(?)?"??&u} u} } q} m} } } 5q     nx op nz  n] gin n`~ s@t uv wa:xu $ comment for d@ -- d@bp'$comment for es -- end simulation run yyy zb zc[ wa xd xex \fb?br@t wa]? d6^r@  da $by y tt nq h6 d@  da $b er6 ep  da $bes er6 fr@ da $b ar g s g gw i&& &h&    xp\`(  \ \ b(8 xpp?i' z]4@(8  bjӓo-\#g (<bw: end a simulation run. this should normally be the last event in your events file. every events file should include an es event so that the simulation knows when to end. if an es event is not included, the simulation will end after the driver has driven the distance indicated by the last event in the events file plus the distance of the far clipping plane. using this event you can end a simulation run using either distance traveled or total time since the beginning of the run. <( \ b8 xpp?ri3]4@8 jg_l l<mbw: distance (in feet) driver's vehicle has travelled when the event begins.<al \ b9 xpp?ri ]4@9 ?d5֘ 7(<8bw: time (in seconds) when the simulation run will end. it is not always desirable to end a simulation run using just the distance into the run. for cases when you want the driver to drive a set amount of time, use the es event with the on distance parameter set to 0 and this parameter set to a non zero value. if this parameter is not set or is set to 0, then the simulator will only use the on distance for determining when the simulation run will end. if this parameter and the on distance parameter are both set, then the simulation will end when the first threshold is met. examples: 10000, es -- end simulation when distance travelled = 10,000 feet 0, es, 1800 -- end simulation when time > 1800 seconds (i.e., 30 minutes) 10000, es, 300 -- end simulation when (distance = 10,000) or (time > 300 seconds) in the third example, since both a distance and a time have both been specified, the simulation run will end either when the driver has traveled more than 10000 feet down the road or has driven for more than 300 seconds, whichever comes first. <( e<n` 7 \ b9 xpp?i ]4@9@ |hgef1#% <comment & command line: highlight the blue cells, then copy (ctl-c) and paste (ctl-v) into your sdl file. if you want the command without the comment, copy only the last line (with a box around it).<rive michel bdard  michel bdard  michel bdard   michel bdard >@heje  7yk c:\stisim\help\sdleventes.htmyk f../../../../stisim/help/sdleventes.htmyx;h,]ą'cr yk back to commands'command index'!a21s\ distance from start of course(distance measured in feet)cm parameter 1error!atime (in seconds) when the simulation run will end. see comment in cell to the left for details../ comment & command linehighlight the blue cells, then copy (ctl-c) and paste (ctl-v) into your sdl file. if you want the command without the comment, copy only the last line (with a box around it). eev  sheet24ggdggh'h     dmbp?_*+%&?'?(?)?"??&u} u} } q} m} } } 5 q    nx op nz  n] gin n`~ sp@t uv wa:xy $ comment for d@ -- d@bp%"comment for esav -- end block savey zb zc[ wa yy[[[yyy nqh6dp@  da $b er6flc da $besav ar gg s q g gw iv&& &l*   `(  ` ` b: xpp?i']4@: jcu'^tiw (<bw: end a data block saving event. this option tells the simulation program to stop collecting block data. this option is used in conjunction with the bsav option. the bsav option tells the program to begin saving the data block. since all this event does is tell the program to stop collecting the block data, no parameters are required. event parameters: none example: 2000, bsav, 1, .0995, thaddeus, 1, 6, 4, 18, 19 3000, esav in the above example, the simulation will begin collecting a block of data (2000, bsav) after the driver has traveled 2000 feet down the road and the data block will end after the driver has traveled 3000 feet down the road (3000, esav). <(m5u ` b; xpp?ri3]4@;  ]s7e l<mbw: distance (in feet) driver's vehicle has travelled when the event begins.<al ` bp; xpp?i ]4@p; j3i"ls <comment & command line: highlight the blue cells, then copy (ctl-c) and paste (ctl-v) into your sdl file. if you want the command without the comment, copy only the last line (with a box around it).<rive michel bdard  michel bdard  michel bdard >@heje  7yk c:\stisim\help\sdleventes.htmyk f../../../../stisim/help/sdleventes.htmyx;h,]ą'cr yk back to commands'command index'!a22w\ distance from start of course(distance measured in feet)cm comment & command linehighlight the blue cells, then copy (ctl-c) and paste (ctl-v) into your sdl file. if you want the command without the comment, copy only the last line (with a box around it).da b sheet25ggdggh'h  a  dmbp?_*+%&?'?(?)?mlexmark e210o odxxletterpriv''''222222222p dlcourier newh"dx??&u} u} } q} o} o} o} o} o} o} o} o} o} o} o} o} o} o} o} o} o} o} o} o} o} o} o} o} 5     q nx op nz  n]  n n`~ s@t uv wa:x6 $ comment for d@ -- d@bp*'comment for fllw -- follow lead vehicle4yyy]]]]]]]]]]]]]]]]]]]] zb zc[ wa xd xex \f.]]]]]]]]]]]]]]]]]]]]~ c? st wa]?( l^(* la ,b*10y y.]]]]]]]]]]]]]]]]]]]]c@si@t wa]@(^i@( y y.]]]]]]]]]]]]]]]]]]]]~ c@ sm t wa ]@(  ^( *0 y y. ]]]]]]]]]]]]]]]]]]]] c@s(@ t wa ]@(  ^(@(  y y. ]]]]]]]]]]]]]]]]]]]] c@s>@ t wa ]@(  ^>@(  y y. ]]]]]]]]]]]]]]]]]]]] c@s$@ t wa ]@(  ^$@(  y y. ]]]]]]]]]]]]]]]]]]]] c@sr@ t wa ]@(  ^r@( y y. ]]]]]]]]]]]]]]]]]]]]~ c @ z{ wa] @(^@("c:\stisim\data\speedprofile.sin] ].]]]]]]]]]]]]]]]]]]]]c"@s?t wa]"@(^?(] ].]]]]]]]]]]]]]]]]]]]]c$@si@t wa]$@(^i@(] ].]]]]]]]]]]]]]]]]]]]]c&      !"#$%&'()*+,-./0123456789:;<=>?@abcdefghijklmnopqrstuvwxyz[\]^_`abcdefghijlmnopqrstuvwxyz{|}~@s$@t wa]&@(^$@(] ].]]]]]]]]]]]]]]]]]]]]>tt]]]]]]]]]]]]]]]]]]]]]]]]] nqh6|@  da $b }r6}dc  da $bfllw }r6}  da $b*10 }r6 }i@  da $b  }r6 }x  d a $ b*0  }r6 }(@  d a $ b }r6}>@  d a $ b }r6}$@  d a $ b }r6}r@  d a $ b }r6}  da $b"c:\stisim\data\speedprofile.sin }r6}?  da $b }r6}i@  da $b }r6~$@ da $b arg s g gwi \ _ 6&* &b&  d(  d d b(< xpp?i ]4@(<` ,(^zi& c  < bw: display a lead vehicle that the driver must then follow. the speed of the lead vehicle will change based on a sinusoidal profile that the user specifies. the driver must try and match the lead vehicle s speed in order to maintain a constant following distance between themselves and the lead vehicle. when this event is activated a vehicle will appear on the screen at the location and speed specified. this event can occur at any point in the scenario and therefore other events can be used to create additional driver workload before and after the vehicle following event is activated. in addition, multiple fllw events can occur in a single scenario, however there should only be one active at a time. this is a timed event and when the desired following time has been exceeded, the lead vehicle will disappear and the driver can continue to navigate the course. since it is a timed event, you will need to make sure that the simulation run does not end before the vehicle following task has completed. if you have trouble with the timing of this event and the simulation run ending too soon, you can specify the simulation to end as a function of time instead of distance by using the timing option of the end simulation (es) event. < d b< xpp?sim]4@< ]hkfg6u l<mbw: distance (in feet) driver's vehicle has travelled when the event begins.<al d b< xpp?si ]4@<` zj xpp?s i]4@(> da|kg <bw: time delay (in seconds) before the sine wave input kicks in. this parameter provides time that allows the driver to first adjust to the vehicle that instantly appears before the actual following task begins. < d b> xpp?s i ]4@>@ aզla&} <bw: gain on the lead vehicle s speed profile. the actual speed profile is comprised of a summation of multiple sine waves of different amplitudes and frequencies and is specified in an ascii text file (parameter 7). however since this profile can be used in multiple scenarios, you can specify a gain that will be multiplied into the amplitude of the speed profile, thus making it quick and simple to increase or decrease the magnitude of the lead vehicle s speed. <  d b> xpp?s ik]4 @> eic}e*`mnu$ \(<]bw: length of time (in seconds) that the vehicle following task will be displayed. once again this provides an easy way to modify and use an existing sinusoidal input file without changing the file. after the lead vehicle has been displayed for the specified length of time, it will disappear and data collection for the event will end. we recommend that you set the length so that it is an integer multiplier of the sine wave period. this way the event does not end in the middle of a wave. note: the time specified here must be less than or equal to the time specified in the sinusoidal input file. <( +\  d bp? xpp?s i i]4 @p? 8un{} l<mbw: name and location of a file that contains the sinusoidal input profile. <[l  d b? xpp?si]4 @?` |#"pdŕbm <bw: flag that specifies whether to save the raw data to the stisim drive data file. setting this parameter to a nonzero value will tell the software to save the data to the file, otherwise only the results of the fft will be displayed. <x  d b xpp?si ]4 @ ܴ"zeo5> a < bw: warning distance (in feet). if this parameter is set to a non zero value, it represents the distance that the driver can fall behind the lead vehicle before an auditory warning message is played that instructs the driver that they are falling behind and must catch up and match the speed of the lead vehicle. the warning message is contained is the windows wav file fllwwarn.wav that is located in the sound folder. once a warning has been played, there will be at least an approximate 5 second delay until the next warning can be issued. <0   d bp xpp?si]]4 @p  5.);+h  <bw: volume control, 0 to 10. < d b xpp?if]4@ צ|lmޞ <comment & command line: highlight the blue cells, then copy (ctl-c) and paste (ctl-v) into your sdl file. if you want the command without the comment, copy only the last line (with a box around it).<rive michel bdard  michel bdard  michel bdard  michel bdard   michel bdard   michel bdard   michel bdard   michel bdard  michel bdard  michel bdard  michel bdard  michel bdard  michel bdard  michel bdard >@heje7yk  c:\stisim\help\sdleventfllw.htmyk ../../appdata/local/microsoft/windows/stisim/help/sdleventfllw.htmyx;h,]ą'cyk vehicle index numbersyk h../../../../stisim/help/sdlvehicles.htmyx;h,]ą'cyk randon selection of parametersyk ../../appdata/local/microsoft/windows/stisim/help/randomparams.htmyx;h,]ą'cryk back to commands'command index'!a23yk  c:\stisim\help\sdleventfllw.htmyk j../../../../stisim/help/sdleventfllw.htmyx;h,]ą'cyk randon selection of parametersyk j../../../../stisim/help/randomparams.htmyx;h,]ą'c \ distance from start of course(distance measured in feet)pr parameter 1}the initial speed (feet/second) of the lead vehicle that will be followed. see comment in cell to the left for more details.hl parameter 2{the longitudinal distance, in feet, that the lead vehicle is away from the driver when the lead vehicle initially appears. { parameter 3the lateral lane position, in feet, of the center of the lead vehicle with respect to the roadway s dividing line. see comment in cell to the left for more details.avil  4. lead vehicle model no.\range: 1 to 57 random selection possible see comment in cell to the left for more details.la  5. time delay ptime delay (in seconds) before the sine wave input kicks in. see comment in cell to the left for more details.   6. gain]gain on the lead vehicle s speed profile. see comment in cell to the left for more details.wy  parameter 7length of time (in seconds) that the vehicle following task will be displayed. see comment in cell to the left for more details. e  8. sinusoidal input profilehname and location of a file that contains the sinusoidal input profile. n ll 9. save data flag0 - only results of fft will be displayed non-zero value: data saved to file see comment in cell to the left for more details.e j 10. warning distance2 see comment in cell to the left for more details.da s} 11. volume controlerror!range: 0 to 10. #please enter a number from 0 to 10.s  comment & command linehighlight the blue cells, then copy (ctl-c) and paste (ctl-v) into your sdl file. if you want the command without the comment, copy only the last line (with a box around it).  sheet26ggdggh'h  h  dmbp?_*+%&?'?(?)?"??&u} u} } q} o} o} o} o} o} o} o} o} o} o} 5   q  nx op nz  n]  n n`~ s@t uv wa:xr $ comment for d@ -- d@bp!comment for fog -- fog effectsyyy]]]]]] zb zc[ wa xd xex \f]]]]]] c?s@@t wa]? d6^@@  da $by y]]]]]] c@s@@t wa]@ d6^@@  da $by y]]]]]]  c@s@@ t wa ]@ d 6 ^@@  d a $ b y y ]]]]]]  c@s@@ t wa ]@ d 6 ^@@  d a $ b yy]]]]]] > tt]]]]]pppppppppppppp nq h6 |@  da $b }r6 }  da $bfog }r6 }@@ da $b }r6 }@@ da $b }r6 }@@ d a $ b }r6 ~@@ d a $ b"  arg s g gwi&w@&* &~b&    h(  h h bp xpp?i]4@p osekp) )(<s bw: this is an event that allows you to dynamically display fog in the roadway scene. the fog event can be used to temporarily or permanently reduce the visibility in a scenario. unlike in previous versions of the program where the fog was either on for an entire run or off for the entire run, the fog event allows the fog to be dynamic so that you can have it appear and disappear as a function of how far the driver has traveled. if you want to set fog for an entire run, this can be done using the atmospheric conditions found in the roadway scenery tab box of the configuration option found in the options menu. the fog's color can be set using the "set simulation colors" and "assign simulation colors" options also found in the options menu. note: in order to use the fog event correctly, you must have the atmospheric conditions turned on (configuration s roadway scenery tab dialog box). this is required because the software needs to transition from one state to another and if there is no fog or haze set using the atmospheric conditions option, then the software does not have a baseline to transition from and back to. if haze is not desired but the fog event is, you can set the beginning and ending distances for the haze to be large so that it is essentially not seen when the fog event is not active. <(# ) h b xpp?sim]4@ |zgzi l<mbw: distance (in feet) driver's vehicle has travelled when the event begins.<al h b( xpp?si  ]4@(` +bd,m5ri  y<zbw: longitudinal distance, in feet, that the beginning of the fog is away from the driver when it first becomes visible. <1y h b xpp?si ]4@ ʞm8 g<hbw: depth to opacity. this is the distance, in feet, that the driver will be able to see into the fog. <g h b xpp?si]4@` hjl/s4@4s * w<xbw: the longitudinal length, in feet, of the fog event. the fog will disappear after driving this distance through it. < w h b( xpp?s i -]4@( >vijmp( <bw: transition distance, in feet, to go from no fog to full fog and then back again. this allows the fog to start and end gradually. <j h b xpp? im]4@  ?o.ovf*h <comment & command line: highlight the blue cells, then copy (ctl-c) and paste (ctl-v) into your sdl file. if you want the command without the comment, copy only the last line (with a box around it).<rive michel bdard  michel bdard  michel bdard  michel bdard   michel bdard   michel bdard   michel bdard >@heje 7yk c:\stisim\help\sdleventfog.htmyk ../../appdata/local/microsoft/windows/stisim/help/sdleventfog.htmyx;h,]ą'cryk back to commands'command index'!a24yk c:\stisim\help\sdleventfog.htmyk h../../../../stisim/help/sdleventfog.htmyx;h,]ą'c@\ distance from start of course(distance measured in feet)et parameter 1ulongitudinal distance, in feet, that the beginning of the fog is away from the driver when it first becomes visible. sm parameter 2ddepth to opacity. this is the distance, in feet, that the driver will be able to see into the fog. s si parameter 3sthe longitudinal length, in feet, of the fog event. the fog will disappear after driving this distance through it.   4. lead vehicle model no.transition distance, in feet, to go from no fog to full fog and then back again. this allows the fog to start and end gradually. et  comment & command linehighlight the blue cells, then copy (ctl-c) and paste (ctl-v) into your sdl file. if you want the command without the comment, copy only the last line (with a box around it).e  4. transition distance (ft)transition distance, in feet, to go from no fog to full fog and then back again. this allows the fog to start and end gradually. e st  sheet27ggdggh'h   |.:  dmbp?_*+%&?'?(?)?"??&u} u} } } o} o} o} o} o} o} o} o} o} o} o} o} o} o} o} o} 5      nx o nz  n] n n`~ s@@u wa:xu $ comment for d@ -- d@bp comment for i -- intersection$yyy]]]]]]]]]]]] zb zc wa xd xex \f]]]]]]]]]]]]c?s wa]?( l^(*  la ,by y]]]]]]]]]]]]c@s@@ wa]@(^@@( y y]]]]]]]]]]]] c@s? wa ]@(  ^?(  y y yy]]]]]]]]]] c@s? wa ]@(  ^?(  y y yy]]]]]]]]]] c@s@ wa ]@(  ^@(  y y yy]]]]]]]]]]~ c@ b wa ]@(  ^@(  y y ]]]]]]]]]]]]~ c@  wa ]@(  ^@( y y ]]]]]]]]]]]]8yyyyyyyyyyyyyyyyy nq6|@@  da $b }r6}@  da $bi }r6}  da $b }r6 }@@  da $b  }r6 }?  d a $ b  }r6 }?  d a $ b }r6}@  d a $ b }r6} @  d a $ b }r6~@ d a $ b ar s g gw* h& f w  l(  l l bp xpp?i]4@p vtgfb{\$xv (<bw: displays an intersection on the screen. when the intersection event is activated, the intersection that is drawn will have the same characteristics and attributes (number of lanes, stripping, etc.) as the roadway that the driver is currently traversing. although turning is allowed at intersections it is not quite like the real world. stisim drive simulation runs are handled with a continuous driver approach. this means that the simulator thinks that the entire run occurred on a single roadway path without any interruptions. this is ideal for researchers who are trying to insure that participants see everything in the same order and that they experience all of the critical events that have been developed. basically, the continuous stretch of road approach prevents drivers from forging their own path. the reason all of this is important is because when a driver makes a right or left hand turn into an intersection and then drives down it approximately 100 feet, the software essential places the vehicle back on the main roadway. for all intents and purposes, objects in the display scene will look as if the driver turned, however the simulation will continue along the original path. this means that whether a driver turns right or left, they will always experience the next event in the sdl. it also means that you cannot have conditional events (if they turned right do a, b, and c or if they turned left do x, y and z) or create a true roadway network for a town or city. note: see the hyperlinked help file (one cell down) for more details.<(3 l b xpp?sim]4@ =\-ju ]l l<mbw: distance (in feet) driver's vehicle has travelled when the event begins.<al l b( xpp?si ]4@( уgdh <bw: the type of intersection that will be displayed. to specify the type of intersection, set parameter 1 to one of the following: 0. full intersection (branching both left and right) 1. right branching intersection 2. left branching intersection < l b xpp?si ]4@` "o'gξ^ d<bw: longitudinal distance offset, in feet, that is added to the event on distance to specify exactly where the intersection will be located. this parameter basically specifies when the intersection becomes visible. if this value is set to 0 then the intersection is displayed at the on distance location and will be visible when ever it enters the far clipping plane (configuration s graphics configuration tab dialog box). however, if this parameter is non zero then the intersection will be displayed at the on distance plus this value and the intersection will not be visible until it is within this distance of the driver. if you think that an intersection is annoying because it is far away and seems to be flickering, then shorting this distance will help eliminate these effects. see the warning below in the examples for some caution on using this parameter. <d l b xpp?si]4@ }ڕa( <bw: flag that tells the simulation which direction, if any, that the driver may turn the vehicle. this allows you to control whether or not the driver can turn at intersections, and therefore the driver must follow the route that you specified. if the driver tries to turn in a direction that is not allowed, then the simulation will assume that they ran off the road and issue an off the road accident response by playing the crash recording and incrementing the accident counter. to specify the steering direction option, set parameter 3 to one of the following values: 0. no turning allowed 1. full intersection (turning is allowed both directions) 2. right turns only 3. left turns only <  l b( xpp?s i-]4@(  4Թ,7f#p \<]bw: flag that specifies what type of crosswalk to display in the drivers direction. to specify the crosswalk option, set parameter 4 to one of the following values: 0. no crosswalk displayed 1. single limit line 2. two lateral (across the road) lines 3. multiple horizontal (down the road) lines 4. combination of 2 and 3 <_\ l b xpp?s i]4@ ;xЇecnb]q0= c<dbw: flag that specifies what type of crosswalk to display in the cross traffic direction. to specify the crosswalk option, set parameter 5 to one of the following values: 0. no crosswalk displayed 1. single limit line 2. two lateral (across the road) lines 3. multiple horizontal (down the road) lines 4. combination of 2 and 3 <c l b xpp?s i<]4@ ¹di%6}p g<hbw: flag that tells the simulation which direction, if any, that the driver is supposed to turn the vehicle. this allows the simulator to keep track of and score how the driver did at each intersection. if the driver follows the incorrect path, then this will be recorded in the data file and an optional message can be played informing the driver that they did not follow the correct path (see the next parameter). to specify the direction that the drive is supposed to turn, set parameter 6 to one of the following values: 0. go straight 1. turn right 2. turn left < g  l b( xpp?s ik]4 @(@ + (b {> (<bw: optional parameter that specifies the name of an auditory file (in windows .wav format) that will be played if the driver does not follow the specified path set in parameter 6. if a file name is not specified then nothing will happen. <(]  l b xpp?im]4 @ 1belc <comment & command line: highlight the blue cells, then copy (ctl-c) and paste (ctl-v) into your sdl file. if you want the command without the comment, copy only the last line (with a box around it).<rive michel bdard  michel bdard  michel bdard  michel bdard   michel bdard   michel bdard   michel bdard   michel bdard  michel bdard  michel bdard >@heje 7 yk c:\stisim\help\sdleventi.htmyk ../../appdata/local/microsoft/windows/stisim/help/sdleventi.htmyx;h,]ą'cryk back to commands'command index'!a25yk c:\stisim\help\sdleventi.htmyk d../../../../stisim/help/sdleventi.htmyx;h,]ą'cc \ distance from start of course(distance measured in feet)et p1 - type of intersectionerror!w0. full intersection 1. right branching intersection 2. left branching intersection please enter 0, 1, or 2./0122 parameter 2longitudinal distance offset, in feet, that is added to the event on distance to specify exactly where the intersection will be located. see comment in cell to the left for more details.ee 3. turns allowederror!0. no turning allowed 1. full intersection 2. right turns only 3. left turns only see comment in cell to the left for more details.'please enter a number in the range 0-3. 0 4. driver's crossswalk typeerror!0. no crosswalk displayed 1. single limit line 2. two lateral (across the road) lines 3. multiple horizontal (down the road) lines 4. combination of 2 and 3 see comment in cell to the left for more details.correct range: 0-4ta a c 5. cross-traffic crosswalkerror!0. no crosswalk displayed 1. single limit line 2. two lateral (across the road) lines 3. multiple horizontal (down the road) lines 4. combination of 2 and 3 see comment in cell to the left for more details.correct range: 0-5ss  6. correct turn directionerror!\0. go straight 1. turn right 2. turn left see comment in cell to the left for more details.correct range: 0-2lezo  parameter 7optional parameter that specifies the name of an auditory file (in windows .wav format) that will be played if the driver does not follow the specified path set in parameter 6. if a file name is not specified then nothing will happen.  dai  comment & command linehighlight the blue cells, then copy (ctl-c) and paste (ctl-v) into your sdl file. if you want the command without the comment, copy only the last line (with a box around it).isot sheet28ggdggh'h   ju  dmbp?_*+%&?'?(?)?"??&u} u} } } o} o} o} o} o} o} o} o} o} o} o} o} o} o} 5      nx o nz  n]  n n`~ s@@u wa:x $ comment for d@ -- d@bp%"comment for jbar -- jersey barrier yyy]]]]]]]]]] zb zc wa xd xex \f]]]]]]]]]]c?s@@ wa]?( l^@@(*  la ,by y]]]]]]]]]]c@s wa]@(^( y y]]]]]]]]]] c@s wa ]@(  ^(  y y yy]]]]]]]] c@s(@ wa ]@(  ^(@(  y y yy]]]]]]]] c@s@@ wa ]@(  ^@@(  y y yy]]]]]]]] c@s? wa ]@(  ^?( y y ]]]]]]]]]] 8 yyyyyyyyyyyyyyy nq6|@@  da $b }r6}c  da $bjbar }r6}@@  da $b }r6 }  da $b  }r6 }  d a $ b  }r6 }(@  d a $ b }r6}@@  d a $ b }r6~? d a $ b ar s g gw( t* |fi w 4 p(  p p b xpp?i>]4@@ a ԣkЈ) (<bw: displays an intersection on the screen. when the intersection event is activated, the intersection that is drawn will have the same characteristics and attributes (number of lanes, stripping, etc.) as the roadway that the driver is currently traversing. although turning is allowed at intersections it is not quite like the real world. stisim drive simulation runs are handled with a continuous driver approach. this means that the simulator thinks that the entire run occurred on a single roadway path without any interruptions. this is ideal for researchers who are trying to insure that participants see everything in the same order and that they experience all of the critical events that have been developed. basically, the continuous stretch of road approach prevents drivers from forging their own path. the reason all of this is important is because when a driver makes a right or left hand turn into an intersection and then drives down it approximately 100 feet, the software essential places the vehicle back on the main roadway. for all intents and purposes, objects in the display scene will look as if the driver turned, however the simulation will continue along the original path. this means that whether a driver turns right or left, they will always experience the next event in the sdl. it also means that you cannot have conditional events (if they turned right do a, b, and c or if they turned left do x, y and z) or create a true roadway network for a town or city. note: see the hyperlinked help file (one cell down) for more details.<(3 p bp xpp?sim]4@p ?)w Ϗlna l<mbw: distance (in feet) driver's vehicle has travelled when the event begins.<al p b xpp?si ]4@  7i(f <bw: the longitudinal distance, in feet, that the front (end closest to the driver) of the barrier is away from the driver when the barrier initially appears. < p b xpp?si ]4@ rp@, <bw: no longer used. <x p bp xpp?si]4@p tnrp; <bw: lateral position, in feet, of the front (end of the barrier closest to the driver) of the barrier with respect to the roadway s dividing line. this anchors the front of the barrier at a particular position in the roadway. < p b xpp?s i-]4@@ ̧`h@!* <bw: lateral position, in feet, of the rear (end of the barrier farthest away from the driver) of the barrier with respect to the roadway s dividing line. this anchors the rear of the barrier at a particular position in the roadway. <9 p b xpp?s i]4@ l)l`jwh~[  </bw: length, in feet, of the barrier that will be displayed. this parameter combined with parameters 3 and 4, tells the software where the barrier end points are located relative to the driver and the roadway, and then draws the barrier between the end points. the total length of the barrier can be almost any length as long as it does not adversely affect your simulation frame rate. furthermore, the barrier that is drawn appears in 8 foot sections with a dividing line showing the breaks between each consecutive section of the barrier. the barrier will follow the path of the roadway, therefore if the roadway is straight, the barrier that is displayed will be drawn linearly from the front end point to the rear end point. on curved roadways, the barrier will be drawn around the curve using 8 foot straight line sections (for each individual barrier). additionally, since the lateral positions of the barrier s end points are specified relative to the roadway s dividing line, the barriers can be used to cordon off a lane while in a curve. << p bp xpp?s i<]4@p knm@d <bw: type of jersey barrier to display. allowable types are: 1. 3 feet high (8 feet long, 1 and a half feet wide) barrier: 2. 4 feet high (8 feet long, 1 and a half feet wide) barrier: 3. 2 feet high (5 feet long, 2 feet wide) barrier: 4. 2 feet high (5 feet long, 2 feet wide) barrier: 5. 2 feet high (5 feet long, 2 feet wide) barrier: 6. 2 feet high (5 feet long, 2 feet wide) barrier: 7. 3 feet high (10 feet long, 2 feet wide) barrier: 8. 3 feet high (10 feet long, 2 feet wide) barrier: 9. 3 feet high (10 feet long, 1 and a third feet wide) barrier: click on hyperlink to help file (cell b3) to see pictures of the various types.<c   p b xpp? i]4 @` +ȇ @'! <comment & command line: highlight the blue cells, then copy (ctl-c) and paste (ctl-v) into your sdl file. if you want the command without the comment, copy only the last line (with a box around it).<rive michel bdard  michel bdard  michel bdard  michel bdard   michel bdard   michel bdard   michel bdard   michel bdard  michel bdard >@heje 7yk  c:\stisim\help\sdleventjbar.htmyk ../../appdata/local/microsoft/windows/stisim/help/sdleventjbar.htmyx;h,]ą'cryk back to commands'command index'!a26yk  c:\stisim\help\sdleventjbar.htmyk j../../../../stisim/help/sdleventjbar.htmyx;h,]ą'c]\ distance from start of course(distance measured in feet)et parameter 1error!the longitudinal distance, in feet, that the front (end closest to the driver) of the barrier is away from the driver when the barrier initially appears. please enter 0, 1, or 2.ą parameter 2error!no longer used. set to 0. <this paramter is no longer used. it must be set equal to 0. r 0y  parameter 3error!lateral position, in feet, of the front (end of the barrier closest to the driver) of the barrier with respect to the roadway s dividing line. this anchors the front of the barrier at a particular position in the roadway. 'please enter a number in the range 0-3. ft   parameter 4error!lateral position, in feet, of the rear (end of the barrier farthest away from the driver) of the barrier with respect to the roadway s dividing line. this anchors the rear of the barrier at a particular position in the roadway. correct range: 0-4e 3.  5. length of barriererror!klength, in feet, of the barrier that will be displayed. see comment in cell to the left for more details.correct range: 0-5a   6. type of barriererror!?range: 1-9. see comment in cell to the left for more details.correct range: 1-9ler    comment & command linehighlight the blue cells, then copy (ctl-c) and paste (ctl-v) into your sdl file. if you want the command without the comment, copy only the last line (with a box around it).eb sheet29ggdggh'h   £  dmbp?_*+%&?'?(?)?"??&u} u} } } o} o} o} o} o} o} 5     nx o nz  n]  n n`~ s@u wa:x@\ $ comment for d@ -- d@bp comment for ls -- limit speed yyy zb zc wa xd xex \fc?sk@ wa]? d6^k@  da $by yc@s@@ wa]@ d6^@@  da $by y 8  nq6 |@  da $b }r6 }  da $bls }r6 }k@ da $b }r6 ~@@ da $b*  ar s g gw * ^fw w   t(  t t bp xpp?i]4@p nd*%n < bw: change the current speed limit of the simulation. this event should be used in conjunction with a speed limit sign that can be specified using the sign event. if you set both events up at the same distance, then the new speed limit will take effect as the driver passes the new speed limit sign. when the driver reaches the speed limit sign, the simulation speed limit will change to the speed limit specified. this new speed limit will remain in effect until another ls event is specified. at the start of a simulation run, the speed limit is set from the configuration s initialize tab dialog box. since most people will not begin adjusting their speed until they are close to the speed limit sign you may want to provide a cushion for the driver so that if the police officer is present, they will not get an unwarranted ticket. therefore if the speed limit is increasing (for example from 45 to 55 miles/hour) you will want to put the ls event some distance before the sign and if the speed limit is decreasing, place the ls event some distance after the sign. in addition, this event affects the speed exceedance count because each time a driver exceeds the posted limit, the speed exceedance counter is incremented by one. therefore, you may also want to bump the actual speedlimit up a little so that the driver can fluctuate around the posted speed without having to maintain an absolute value. < t b xpp?sim]4@ 0m#ʦ l<mbw: distance (in feet) driver's vehicle has travelled when the event begins.<al t bpc xpp?si ]]4@pc@ ^a|.n j<kbw: the maximum speed, in miles/hour, that the driver may legally drive. <ij t bppc xpp?si ]4@ppc "يhnh1 )<*bw: the longitudinal distance, in feet, that the event is away from the driver when the event initially occurs. this may seem a little strange because you could simply specify the total distance, but has been kept this way so that it is consistent with earlier scenarios that displayed a sign. <o) t bpc xpp? i]4@pc "!oj 2v <comment & command line: highlight the blue cells, then copy (ctl-c) and paste (ctl-v) into your sdl file. if you want the command without the comment, copy only the last line (with a box around it).<rive michel bdard  michel bdard  michel bdard  michel bdard   michel bdard >@heje 7yk c:\stisim\help\sdleventls.htmyk ../../appdata/local/microsoft/windows/stisim/help/sdleventls.htmyx;h,]ą'cryk back to commands'command index'!a27yk c:\stisim\help\sdleventls.htmyk f../../../../stisim/help/sdleventls.htmyx;h,]ą'cl\ distance from start of course(distance measured in feet)et p1 - maximum speed (miles/hr)warning!gthe maximum speed, in miles/hour, that the driver may legally drive. ]you have entered a maximum speed that may be out of range. please verify that it is correct.led  parameter 2error!the longitudinal distance, in feet, that the event is away from the driver when the event initially occurs. see comment in cell to the left for more info. <this paramter is no longer used. it must be set equal to 0. h] comment & command linehighlight the blue cells, then copy (ctl-c) and paste (ctl-v) into your sdl file. if you want the command without the comment, copy only the last line (with a box around it).edit  sheet30ggdggh'h  f  dmbp?_*+%&?'?(?)?"??&u} u} } } o} o} o} o} 5     nx o nz  n]  n n`~ s@@u wa:x  $ comment for d@ -- d@bp+(comment for paus -- pause simulation run y]] zb zc wa xd xex \fc?s wa]? d] d] ]8yyyyy nq6 |@@  da $b }r6 }c  da $bpaus }r6 ~ da $b.  ar s g gw* ^zf w xx`(  x x bqc xpp?i]4@qc 2og`-t n<obw: the paus event is used to programmatically pause a run at specific points during the simulation. this feature is best used during training or demonstration applications when it is desired to show a driver specific features of the simulator or the particular roadway scene. when the simulation run is paused, the last roadway frame that was displayed will remain on the screen until the pause is completed or the view is altered by the experimenter. when the simulation begins again, the scenario will pickup at the next frame as if the pause never occurred. while a simulation is paused, the experimenter can use the keyboard to alter the roadway display view, or even take a snapshot of the paused screen. refer to the keystroke options table for more information on what keystroke combinations are available and what their functions are. <n x bqc xpp?sim]4@qc b;il-c.7<"j  l<mbw: distance (in feet) driver's vehicle has travelled when the event begins.<al x b(rc xpp?si ]4@(rc@ 2ztfpzs (<bw: pause duration, in seconds. if this value is 0, then the run will be paused until the experimenter instructs the simulation run to continue (by using either an alt-p key combination, or clicking on the play button to resume). <(!2 x brc xpp?im ]4@rc [w8]e깹 <comment & command line: highlight the blue cells, then copy (ctl-c) and paste (ctl-v) into your sdl file. if you want the command without the comment, copy only the last line (with a box around it).<rive michel bdard  michel bdard  michel bdard   michel bdard >@heje   7yk  c:\stisim\help\sdleventpaus.htmyk ../../appdata/local/microsoft/windows/stisim/help/sdleventpaus.htmyx;h,]ą'cp yk back to commands'command index'!b3yk  c:\stisim\help\sdleventpaus.htmyk j../../../../stisim/help/sdleventpaus.htmyx;h,]ą'cg\ distance from start of course(distance measured in feet)et p1 - pause duration (seconds)if this value is 0, then the run will be paused until the experimenter instructs the simulation run to continue (by using either an alt-p key combination, or clicking on the play button to resume). t comment & command linehighlight the blue cells, then copy (ctl-c) and paste (ctl-v) into your sdl file. if you want the command without the comment, copy only the last line (with a box around it).ayut  sheet31ggdggh'h    dmbp?_*+%&?'?(?)?"??&u} u} } } o} o} o} o} 5     nx o nz  n]  n n`~ s@@u wa:xc $ comment for d@ -- d@bp+(comment for pb -- police officer - begin y]] zb zc wa xd xex \fc?s@ wa]? d]@ d] ]8yyyyy nq6 |@@  da $b }r6 }  da $bpb }r6 ~@ da $b.  ar s g gw* ^zf w ! x|`(  | | bsc xpp?i]4@sc`c ishf i$` <bw: begin police patrol. this specifies that a police man is present and watching the driver's speed to see if they exceed the specified speed limit if the specified speed limit is exceeded, and the pb event is on, then a speeding ticket will be issued. additionally, if the siren sound is active, then it will be played. use the pe event to stop the police patrol. to change the speed limit that tickets will be issued at, use the limit speed (ls) event. <u | bsc xpp?sim]4@scc r"@/j8 l<mbw: distance (in feet) driver's vehicle has travelled when the event begins.<al | b(tc xpp?si ]4@(tc c +2r`a1 z1 {<|bw: delta speed, in feet/second, that is used when computing whether or not the driver is speeding. this parameter allows you to give the driver some leeway when it comes to receiving speeding tickets. the value specified in this parameter will be added to the current speed limit to create the speed threshold that the driver must exceed in order to obtain a speeding ticket. <{ | btc xpp?im ]4@tcc (d':um <comment & command line: highlight the blue cells, then copy (ctl-c) and paste (ctl-v) into your sdl file. if you want the command without the comment, copy only the last line (with a box around it).<rive michel bdard  michel bdard  michel bdard   michel bdard >@heje   7yk c:\stisim\help\sdleventpb.htmyk ../../appdata/local/microsoft/windows/stisim/help/sdleventpb.htmyx;h,]ą'cp yk back to commands'command index'!b4yk c:\stisim\help\sdleventpb.htmyk f../../../../stisim/help/sdleventpb.htmyx;h,]ą'c8\ distance from start of course(distance measured in feet)et parameter 1`delta speed, in feet/second, that is used when computing whether or not the driver is speeding. ./ comment & command linehighlight the blue cells, then copy (ctl-c) and paste (ctl-v) into your sdl file. if you want the command without the comment, copy only the last line (with a box around it).lv  sheet32ggdggh'h  u   dmbp?_*+%&?'?(?)?"??&u} u} } } o} o} o} o} o} o} o} o} o} o} o} o} o} o} o} o} o} o} o} o} 5      nx o nz  n]  n n`~ s@u wa:xc $ comment for d@ -- d@bp.+comment for pde -- previously defined event,yyy]]]]]]]]]]]]]]]] zb zc wa xd xex \f&]]]]]]]]]]]]]]]]~ c? z wa]? d^8 d vehahead.pdey y&]]]]]]]]]]]]]]]]~ c@ b wa]@(l^c( * la ,b*0~45y y&]]]]]]]]]]]]]]]] c@b@@ wa ]@(  ^@@(  y y& ]]]]]]]]]]]]]]]] c@b? wa ]@(  ^?(  y y& ]]]]]]]]]]]]]]]]~ c@ b wa ]@(  ^p@( * yy]]]]]]]]]]]]]]]]~ c@ b wa ]@(  ^t@( * yy]]]]]]]]]]]]]]]]~ c@ b wa ]@(  ^x@(* ]]]]]]]]]]]]]]]]]]~ c @b wa] @(^\@(*]]]]]]]]]]]]]]]]]]~ c"@b wa]"@(^`@(*]]]]]]]]]]]]]]]]]]8yyyyyyyyyyyyyyyyyyyyy nq6|@  da $b }r6}  da $bpde }r6}t\p  da $b vehahead.pde }r6 }c  da $b*0~45  }r6 }@@  d a $ b  }r6 }?  d a $ b }r6}d@  d a $ b }r6}h@  d a $ b }r6}l@  d a $ b }r6}p@  da $b }r6~t@ da $b ar s g gw. * fs! w"  (    bpuc xpp?i>]4@pucc ӓ /'ig+l e <bw: this event allows you to group a set of events in to a single file called a previously defined event (pde). you could create an event that will be used over and over in the same events file or in different events files. the problem with this approach is that you will always have to change the longitudinal distances so that they will work in the current simulation. this option allows you to create a group of events and reference the longitudinal distance to the pde event s on distance. this means that all of the longitudinal distances in the pde group are specific to the beginning of the pde, not the beginning of the simulation. the longitudinal distance that you specify for the pde event is specific to the beginning of the simulation. for this option, you must specify a file name that contains the event, and any variables that you would like passed to the pde. the format for these files is the same as it is for a normal events file, and pde files can call other pde files that can call other pde files and well you get the idea. click on the hyperlink for the help file to see more info about this command.< %e  buc xpp?sim]4@uc`c 8枚l l<mbw: distance (in feet) driver's vehicle has travelled when the event begins.<al  bvc xpp?si ]4@vcc m#`n*2be/ u<vbw: the name of the file that contains the group of events to be run. the file name can be any file name that conforms to windows file name criteria. to insure that the program can find the pde file that is specified, make sure that you include the full file name including both the path and the file extension. for example c:\stisim\projects\sample.pde. if the entire path is not included, stisim drive will use the folder where the scenario file that is calling the pde file is located. if the pde file cannot be found, then the simulation run will be terminated and you will have to fix the problem in order to run your file. <y u  bpvc xpp?l ]4@pvc c ͬ)jmv7ea i0<jbw: parameters 2-9 allow you to pass specific parameters to your pde. what the parameters are depends on what the command is in the pde file. for example, if the command in the pde file is a (approaching vehicle), then parameters 2-9 will be parameters of command a. click on the hyperlink for the pde help file for more info.<0@-p:si  bvc xpp?si ]4@vcc bn!#bg>ab i0<jbw: parameters 2-9 allow you to pass specific parameters to your pde. what the parameters are depends on what the command is in the pde file. for example, if the command in the pde file is a (approaching vehicle), then parameters 2-9 will be parameters of command a. click on the hyperlink for the pde help file for more info.<0@-p:si  bwc xpp?s i ]4@wcc a./!@6vo i0<jbw: parameters 2-9 allow you to pass specific parameters to your pde. what the parameters are depends on what the command is in the pde file. for example, if the command in the pde file is a (approaching vehicle), then parameters 2-9 will be parameters of command a. click on the hyperlink for the pde help file for more info.<0@-p:si  bpwc xpp?s i ]4@pwc@c <|e(y#z i0<jbw: parameters 2-9 allow you to pass specific parameters to your pde. what the parameters are depends on what the command is in the pde file. for example, if the command in the pde file is a (approaching vehicle), then parameters 2-9 will be parameters of command a. click on the hyperlink for the pde help file for more info.<0@-p:si  bwc xpp?s i ]4@wcc 5ոe4km7u$ i0<jbw: parameters 2-9 allow you to pass specific parameters to your pde. what the parameters are depends on what the command is in the pde file. for example, if the command in the pde file is a (approaching vehicle), then parameters 2-9 will be parameters of command a. click on the hyperlink for the pde help file for more info.<0@-p:si  bxc xpp?s i ]4 @xcc e gmf6q i0<jbw: parameters 2-9 allow you to pass specific parameters to your pde. what the parameters are depends on what the command is in the pde file. for example, if the command in the pde file is a (approaching vehicle), then parameters 2-9 will be parameters of command a. click on the hyperlink for the pde help file for more info.<0@-p:si  bpxc xpp?s i ]4 @pxc`c ĝow i0<jbw: parameters 2-9 allow you to pass specific parameters to your pde. what the parameters are depends on what the command is in the pde file. for example, if the command in the pde file is a (approaching vehicle), then parameters 2-9 will be parameters of command a. click on the hyperlink for the pde help file for more info.<0@-p:si  bxc xpp?si ]4 @xcc &([h{t i0<jbw: parameters 2-9 allow you to pass specific parameters to your pde. what the parameters are depends on what the command is in the pde file. for example, if the command in the pde file is a (approaching vehicle), then parameters 2-9 will be parameters of command a. click on the hyperlink for the pde help file for more info.<0@-p:si  byc xpp?if]4 @yc c ohf t <comment & command line: highlight the blue cells, then copy (ctl-c) and paste (ctl-v) into your sdl file. if you want the command without the comment, copy only the last line (with a box around it).<rive michel bdard  michel bdard  michel bdard bwc bwc bwc bwc bwc bwc bwc bwc michel bdard >@heje 7yk c:\stisim\help\sdleventpde.htmyk ../../appdata/local/microsoft/windows/stisim/help/sdleventpde.htmyx;h,]ą'cpyk back to commands'command index'!b5yk c:\stisim\help\sdleventpde.htmyk h../../../../stisim/help/sdleventpde.htmyx;h,]ą'cn \ distance from start of course(distance measured in feet)et p1 - name of pde filewarning!1see comment in cell to the left for more details.]you have entered a maximum speed that may be out of range. please verify that it is correct.hm parameter 2warning! see comment in cell to the left.]you have entered a maximum speed that may be out of range. please verify that it is correct.ery  parameter 3warning! see comment in cell to the left.]you have entered a maximum speed that may be out of range. please verify that it is correct.ery   parameter 4warning! see comment in cell to the left.]you have entered a maximum speed that may be out of range. please verify that it is correct.ery   parameter 5warning! see comment in cell to the left.]you have entered a maximum speed that may be out of range. please verify that it is correct.ery   parameter 6warning! see comment in cell to the left.]you have entered a maximum speed that may be out of range. please verify that it is correct.ery   parameter 7warning! see comment in cell to the left.]you have entered a maximum speed that may be out of range. please verify that it is correct.ery   parameter 8warning! see comment in cell to the left.]you have entered a maximum speed that may be out of range. please verify that it is correct.ery  parameter 9warning! see comment in cell to the left.]you have entered a maximum speed that may be out of range. please verify that it is correct.ery  comment & command linehighlight the blue cells, then copy (ctl-c) and paste (ctl-v) into your sdl file. if you want the command without the comment, copy only the last line (with a box around it).e sheet33ggdggh'h   w04  dmbp?_*+%&?'?(?)?"??&u} u} } } o} o} 5     nx o nz  n]  n n`~ s@@u wa:x@c $ comment for d@ -- d@bp,)comment for pe -- police officer end/exity zb zc wa yy8yyy nq6|@@  da $b }r6~ da $bpe2 ar s g gw* bf" w# (    byc xpp?ie]4@ycc qܓi=r a<bbw: end police patrol. this specifies that a police officer is no longer watching the driver's actions. use the pb event to begin the police patrol. since this event is simply used to turn off the police monitoring, no parameters are required. event parameters: none example: 1000, pe this event is used to turn the police officer off. this means that after a pe event and before the next pb event, if the driver is speeding (as defined by the limit speed (ls) event) they will not be issued a ticket. the example shown turns the police officer off after the driver has traveled 1000 feet down the road. <y a  b(zc xpp?si]4@(zcc x츾cg`Ҵs+ l<mbw: distance (in feet) driver's vehicle has travelled when the event begins.<al  bzc xpp?i ]4@zc`c &ڶ0v,i0se <comment & command line: highlight the blue cells, then copy (ctl-c) and paste (ctl-v) into your sdl file. if you want the command without the comment, copy only the last line (with a box around it).<rive michel bdard  michel bdard  michel bdard >@heje   7yk c:\stisim\help\sdleventpde.htmyk ../../appdata/local/microsoft/windows/stisim/help/sdleventpde.htmyx;h,]ą'cp yk back to commands'command index'!b6yk c:\stisim\help\sdleventpe.htmyk f../../../../stisim/help/sdleventpe.htmyx;h,]ą'c`\ distance from start of course(distance measured in feet)et comment & command linehighlight the blue cells, then copy (ctl-c) and paste (ctl-v) into your sdl file. if you want the command without the comment, copy only the last line (with a box around it).de sheet34ggdggh'h  al  dmbp?_*+%&?'?(?)?"??&u} u} } } o} o} o} o} o} o} o} o} o} o} o} o} o} 5      nx o nz  n]  n n`~ s@@u wa:xc $ comment for d@ -- d@bp comment for ped -- pedestrian yyy zb zc wa xd xex \fc?s@@ wa]? d^@@ dy yc@s@ wa]@ d6^@  da $by y c@s@ wa ]@ d 6 ^@  d a $ b y y   c@s4@ wa ]@ d 6 ^4@  d a $ b y y  ~ c@ sv wa ]@ d 6 ^|@  d a $ br y y   c@s@ wa ]@ d 6 ^@  d a $ b y y 8  nq6|@@  da $b }r6}  da $bped }r6}@@  da $b }r6 }@  da $b  }r6 }@  d a $ b  }r6 }4@  d a $ b }r6}@  d a $ br }r6~@ d a $ b ar s g gw(a t* ^zfp# w$ 4  (    bp[c xpp?ie]4@p[cc z l[t g (<bw: displays an intersection on the screen. when the intersection event is activated, the intersection that is drawn will have the same characteristics and attributes (number of lanes, stripping, etc.) as the roadway that the driver is currently traversing. although turning is allowed at intersections it is not quite like the real world. stisim drive simulation runs are handled with a continuous driver approach. this means that the simulator thinks that the entire run occurred on a single roadway path without any interruptions. this is ideal for researchers who are trying to insure that participants see everything in the same order and that they experience all of the critical events that have been developed. basically, the continuous stretch of road approach prevents drivers from forging their own path. the reason all of this is important is because when a driver makes a right or left hand turn into an intersection and then drives down it approximately 100 feet, the software essential places the vehicle back on the main roadway. for all intents and purposes, objects in the display scene will look as if the driver turned, however the simulation will continue along the original path. this means that whether a driver turns right or left, they will always experience the next event in the sdl. it also means that you cannot have conditional events (if they turned right do a, b, and c or if they turned left do x, y and z) or create a true roadway network for a town or city. note: see the hyperlinked help file (one cell down) for more details.<(3  b[c xpp?si]4@[cc 눝>f%k| l<mbw: distance (in feet) driver's vehicle has travelled when the event begins.<al  b(\c xpp?si ]4@(\c@c zmpew_ {<|bw: the longitudinal distance, in feet, that the pedestrian is away from the driver when the pedestrian initially appears. <?{  b\c xpp?si t]4@\cc "dlv@u oՐ <ibw: the collision time, in seconds, between the driver and the pedestrian when the pedestrian first begins to walk across the road. this is based on the driver s current velocity. <o  b\c xpp?si]4@\cc yf^ysi1qtc <bw: velocity, in feet/second, that the pedestrian will be walking. if the pedestrian s velocity is set to 0, then they will just stand there and will not begin to walk. setting this parameter to an asterisk ( * ) tells the software to automatically set the velocity based on the driver s speed when the pedestrian begins walking. therefore, if the driver does react (either by steering or adjusting their speed) a collision will occur. this essentially removes the driver s speed as a potential problem when creating an event. if you use a constant pedestrian velocity, then a fast driver could pass the pedestrian to early or a slow driver too late for them to react as desired. using the asterisk should help to avoid these problems. <t   b(]c xpp?s i-]4@(]c`c lxeglv@heje 7yk c:\stisim\help\sdleventped.htmyk ../../appdata/local/microsoft/windows/stisim/help/sdleventped.htmyx;h,]ą'cpyk back to commands'command index'!b7yk c:\stisim\help\sdleventped.htmyk h../../../../stisim/help/sdleventped.htmyx;h,]ą'ck\ distance from start of course(distance measured in feet)et parameter 1error!wthe longitudinal distance, in feet, that the pedestrian is away from the driver when the pedestrian initially appears. please enter 0, 1, or 2.np parameter 2error!the collision time, in seconds, between the driver and the pedestrian when the pedestrian first begins to walk across the road. this is based on the driver s current velocity. <this paramter is no longer used. it must be set equal to 0. es parameter 3error!velocity, in feet/second, that the pedestrian will be walking. if the pedestrian s velocity is set to 0, then they will just stand there and will not begin to walk. 'please enter a number in the range 0-3.onr   parameter 4error!zinitial pedestrian lateral position, in feet, with respect to the roadway dividing line. correct range: 0-4kn d 5. pedestrian directionerror!b - approaching driver from the back (walking away from driver) f - approaching driver from the front (walking towards the driver) l - approaching from the left r - approaching from the right<you must enter one of the values shown in the pulldown list. hbflr  6. pedestrian model no.error!jrange: 1-11. pictures of the 11 models can be seen in the ped help file.correct range: 1-11ntki   comment & command linehighlight the blue cells, then copy (ctl-c) and paste (ctl-v) into your sdl file. if you want the command without the comment, copy only the last line (with a box around it).fr t sheet35ggdggh'h    vz  dmbp?_*+%&?'?(?)?"??&u} u} } } o} o} 5     nx o nz  n]  n n`~ s@@u wa:xc $ comment for d@ -- d@bp&#comment for plbm -- playback marker] zb zc wa y]8yyy nq6|@@  da $b }r6~0d da $bplbm2 ar s g gw* bf$ w% 0(    bp_c xpp?ie]4@p_cc e"ve0fx <! bw: the plbm event is used to place a specific marker into the playback file. this marker allows the user to jump to specific sections of the scenario so that the user can more efficiently use stisim drive s playback feature. when the plmb event is encountered during a simulation run, a specific marker is set in the playback file that is being created. during a subsequent playback of the run, the user can use the  jump to next marker option to advance the playback to the next specified marker that is found in the file. the jump option works in sequential order so if you have multiple plbm or other markers that are being searched for you may have to jump several times in order to find the desired scenario section. event parameters: none examples: 10000, plbm, 20000, plbm the first line tells the program to add a jump marker into the playback file when the driver has driven 10000 feet down the road. the second line does the same thing when the driver reaches 20000 feet. during a playback of a drive that used a scenario with these lines in them, if event markers are specified as part of the playback and the  jump to option is used the playback will fast forward to 10000 feet and then backup the specified number of seconds and begin playing. if the  jump to option is used again, the playback with then fast forward to 20000 feet, backup the specified number of seconds and then begin playing again. <  b_c xpp?si]4@_cc hwuc"6۲t l<mbw: distance (in feet) driver's vehicle has travelled when the event begins.<al  bpd xpp?i ]4@pd`c )gno1y <comment & command line: highlight the blue cells, then copy (ctl-c) and paste (ctl-v) into your sdl file. if you want the command without the comment, copy only the last line (with a box around it).<rive michel bdard  michel bdard  michel bdard >@heje   7lyk  c:\stisim\help\sdleventplbm.htmyk ../../appdata/local/microsoft/windows/temporary internet files/low/content.ie5/0r3kps15/help/sdleventplbm.htmyx;h,]ą'cp yk back to commands'command index'!b8yk  c:\stisim\help\sdleventplbm.htmyk j../../../../stisim/help/sdleventplbm.htmyx;h,]ą'c\ distance from start of course(distance measured in feet)et comment & command linehighlight the blue cells, then copy (ctl-c) and paste (ctl-v) into your sdl file. if you want the command without the comment, copy only the last line (with a box around it). sheet36ggdggh'h  q  dmbp?_*+%&?'?(?)?mlexmark e210o odxxletterpriv''''222222222p dlcourier newh"dx??&u} u} } } } } } } } } } } } } } m } } } } } }  } } 5      nx o nz  n]  n n`~ s@@u wa:xc $ comment for d@ -- d@bpcomment for poly -- polygons0yyyyyyyyyyyyyyyyyyyyy zb zc wa xd xex \f*yyyyyyyyyyyyyyyyyyc?s wa]? d^ dy y*yyyyyyyyyyyyyyyyyyc@s? wa]@( l^?( * la ,by y*yyyyyyyyyyyyyyyyyy c@s? wa ]@(  ^?(  y y* yyyyyyyyyyyyyyyyyy c@s wa ]@(  ^(  y y* yyyyyyyyyyyyyyyyyy c@s0@ wa ]@(  ^0@(  y y* yyyyyyyyyyyyyyyyyy~ c@ z wa ]@(  ^c( !c:\stisim\data\testpolyscn.pol y y* yyyyyyyyyyyyyyyyyy c@s? wa ]@(  ^?( y y* yyyyyyyyyyyyyyyyyyc @s$@ wa] @(^$@(y y*yyyyyyyyyyyyyyyyyy~ c"@ z wa]"@(^pc(# c:\stisim\data\textures\num9.gify y*yyyyyyyyyyyyyyyyyyc$@s? wa]$@(^?(y y*yyyyyyyyyyyyyyyyyy4yyyyyyyyyyyyyyyyyyyyyyy nq6d@@  da $b er6eld  da $bpoly er6e  da $b er6 e?  da $b  er6 e?  d a $ b  er6 e  d a $ b er6e0@  d a $ b er6ec  d a $ b!c:\stisim\data\testpolyscn.pol er6e?  d a $ b er6e$@  da $b er6e d  da $b# c:\stisim\data\textures\num9.gif er6f? da $b ar s g gwgrrrrrrrrrrrrrr 43* b% & rd@ l(    bpd xpp?i]4@pdc ilka{ p <bw: display a 2 dimensional polygon as either a roadway object (fixed item in the roadway) or as a screen object (fixed to the screen). if the polygon is defined as a roadway object, then it is transformed so that as the driver approaches it, it is displayed in perspective. for screen-based polygons, the polygon remains at the same screen coordinates for a user specified amount of time. polygons can be filled with any active color, or they may have a texture map associated with them. screen-based polygons can be used to display information to the user (like navigation arrows, or directions), while road-based polygons can be used to add features to existing models, create billboards, etc. when trying to specify the events parameters for this event, refer to the various views shown in the accompanying figure. since multiple polygons can be used, stisim drive requires that each polygon be specified in its own ascii text file. the polygons that are displayed can only be 2 dimensional and in a single plane, therefore, the program requires an anchor point and then the polygon data with respect to this anchor point. also, because of memory and speed concerns, the maximum number of vertices in any polygon is limited to 25. <l  b(qd xpp?si]4@(qd c c&}eh l<mbw: distance (in feet) driver's vehicle has travelled when the event begins.<al  bqd xpp?si m ]4@qdc jkvi [ <bw: the longitudinal distance, in feet, of the polygon s first vertex. this is the distance that the polygon is away from the driver when it initially appears, positive forward. for screen-based polygons, this parameter is 0. <.  bqd xpp?si t]4@qdc 2hu__ &<mbw: the physical lateral position, in feet, of the polygon s first vertex. this is with respect to the roadway s dividing line. for screen-based polygons, this parameter is the lateral position (left to right across the screen) on the screen where the first polygon point will appear. the screen is defined as 0, 0 in the lower left hand corner and 1, 1 in the upper right hand corner. for screen-based polygons, the software will automatically adjust the values in the polygon file so that the polygon is drawn with respect to this initial point. < &  b(rd xpp?si|]4@(rd@c wayb=d 1<cbw: the physical vertical position, in feet, of the polygon s first vertex. this is with respect to the ground. this should always be positive. for screen-based polygons, this parameter is the vertical position (up and down, bottom to top) on the screen where the first polygon point will appear. the screen is defined as 0, 0 in the lower left hand corner and 1, 1 in the upper right hand corner. for screen-based polygons, the software will automatically adjust the values in the polygon file so that the polygon is drawn with respect to this initial point. <m 1  brd xpp?s if]4@rdc yfd <bw: the plane in which the polygon will be displayed. this only applies to roadway polygons. screen-based polygons are always displayed in the screen reference plane, and therefore this parameter will be ignored. the polygon can only be displayed in 1 of 3 planes. these planes are shown in the accompanying figure. to specify the plane that the polygon will be displayed in, set parameter 4 to one of the following: 0. y plane, polygon will be displayed laterally and vertically like on a billboard 1. z plane, polygon will be displayed longitudinally and vertically like on a building that is extending down the roadway. 2. x plane, polygon will be displayed longitudinally and laterally. <   brd xpp?s ix]4@rdc '[or <bw: the polygon color. the valid colors are defined using the "set simulation colors" and "assign simulation colors" options, found in the "options" menu. you may also assign the polygon a random color by using stisim drive s random parameter selection capabilities. the basic colors are numbered: 1-16. the custom colors are numbered: 17-64. this is important because any event in the sdl (for example the blck and poly events) that requires a simulation color will have a parameter that is the color's number. to determine a color's number, simply put the cursor on the color's box and wait a second and the program will display the number. <a   b(sd xpp?s ia]4@(sd`c lhscn܈ܜ [<\bw: name of an ascii text file that contains the polygon data. the format of the polygon file is as follows: total number of vertices in the polygon (n) vertex 1 lateral position (x1), vertical position (y1) vertex 2 lateral position (x2), vertical position (y2) l l l vertex n lateral position (xn), vertical position (yn) in the above format, lateral position means left and right across the polygon and vertical means up and down the polygon. the maximum number of vertices in any polygon is 25. < [  bsd xpp?s i]4 @sdc 2Αnkb,= <bw: flag specifying if the polygon being displayed is a roadway object or is screen-based. to specify the type of polygon, set parameter 7 to one of the following: 0. roadway-based polygon 1. screen-based polygon <v  bsd xpp?s i -]4 @sd c j&#o7 <bw: duration, in seconds, that a screen based polygon will be displayed. for roadway based polygons, this parameter is ignored. <  b(td xpp?six]4 @(tdc % mfy4 <bw: complete name of any texture map that will be displayed on the polygon. the name should include both the path to the folder where the texture is located and the file name extension. most standard bitmapped file formats (jpg, bmp, gif, tga, etc.) can be used. when using a texture map, it is best to set the polygon color value (parameter 5) to a value of 16 (white). this way no color bleeds through the texture map and it will be displayed as it looks in a bitmap viewer. one final note on textures. the program will automatically assign the texture coordinates for mapping the bitmap onto the polygon. for rectangles, this is quite easy since the bitmap is also square, however for irregular shaped polygons the software maps the textures based on the minimum and maximum polygon values in each direction. this means that part of the bitmap may be missing when it is mapped onto the polygon for display. <]  btd xpp?si ]4 @tdc (Ȁބpn%~!tg o<pbw: display system that the polygon will be displayed on. this is only applicable to wide field of view systems where the polygon can be displayed on any of the 3 screens. to select the desired screen set parameter 10 to one of the following values: 0. center display system 1. left display system 2. right display system <po  btd xpp?i/]4 @td@c /?6 b7g <comment & command line: highlight the blue cells, then copy (ctl-c) and paste (ctl-v) into your sdl file. if you want the command without the comment, copy only the last line (with a box around it).<rive michel bdard  michel bdard  michel bdard  michel bdard   michel bdard   michel bdard   michel bdard   michel bdard  michel bdard  michel bdard  michel bdard  michel bdard  michel bdard >@heje7yk  c:\stisim\help\sdleventpoly.htmyk ../../appdata/local/microsoft/windows/stisim/help/sdleventpoly.htmyx;h,]ą'cpyk back to commands'command index'!b9yk  c:\stisim\help\sdleventpoly.htmyk j../../../../stisim/help/sdleventpoly.htmyx;h,]ą'c= \ distance from start of course(distance measured in feet)et parameter 1the longitudinal distance, in feet, of the polygon s first vertex. this is the distance that the polygon is away from the driver when it initially appears, positive forward. for screen-based polygons, this parameter is 0. . ne parameter 2the physical lateral position, in feet, of the polygon s first vertex. this is with respect to the roadway s dividing line. see comment in cell to the left for more details.rs parameter 3the physical vertical position, in feet, of the polygon s first vertex. this is with respect to the ground. this should always be positive. see comment in cell to the left for more details.oy  4. display planeerror0. y-plane (like billboard) 1. z-plane (extending down road) 2. x-plane (longitudinal & lateral) see comment in cell to the left for more details.correct range: 0-2 t  5. polygon colourerror!cbasic colours: 1-16 custom colours: 17-64 see comment in cell to the left for more details.1basic colours: 1-16 custom colours: 17-64orra@  6. polygon data filenname of an ascii text file that contains the polygon data. see comment in cell to the left for more details.s:   7. type of polygonerror!20. roadway-based polygon 1. screen-based polygoncorrect range: 0-1elth  8. duration of polygon (s)~duration, in seconds, that a screen based polygon will be displayed. for roadway based polygons, this parameter is ignored. cour 9. texture map file{complete name of any texture map that will be displayed on the polygon. see comment in cell to the left for more details.ed 10. display systemerror!}0. center display system 1. left display system 2. right display system see comment in cell to the left for more details.correct range: 0-2 comment & command linehighlight the blue cells, then copy (ctl-c) and paste (ctl-v) into your sdl file. if you want the command without the comment, copy only the last line (with a box around it).  sheet37ggdggh'h    dmbp?_*+      !"#$%&'()*+,-./0123456789:;<=>?@abcdefghijklmnopqrstuvwxyz[\]^_`abcdefghijklmnopqrstvwxyz{|}~%&?'?(?)?"??&u} u} } } } } } } } 5                 nx o nz  n]  n n`~ s@@u wa:xd $ comment for d@ -- d@bp# comment for pr -- play recordingyyyyyyy zb zc wa xd xex \fyyyy c?z wa]? d^ dy yyyyy c@s? wa]@ d6^?  da $by yyyyy  c@s? wa ]@ d 6 ^?  d a $ b y y yyyy   yyyyyyyyy nq6 d@@  da $b er6 e  da $bpr er6 e da $b er6 e? da $b er6 f? d a $ b ar s g gw"b* p&q& w '  px(    bwd xpp?ie]4@wd`c  lda9wdo <bw: display a 2 dimensional polygon as either a roadway object (fixed item in the roadway) or as a screen object (fixed to the screen). if the polygon is defined as a roadway object, then it is transformed so that as the driver approaches it, it is displayed in perspective. for screen-based polygons, the polygon remains at the same screen coordinates for a user specified amount of time. polygons can be filled with any active color, or they may have a texture map associated with them. screen-based polygons can be used to display information to the user (like navigation arrows, or directions), while road-based polygons can be used to add features to existing models, create billboards, etc. when trying to specify the events parameters for this event, refer to the various views shown in the accompanying figure. since multiple polygons can be used, stisim drive requires that each polygon be specified in its own ascii text file. the polygons that are displayed can only be 2 dimensional and in a single plane, therefore, the program requires an anchor point and then the polygon data with respect to this anchor point. also, because of memory and speed concerns, the maximum number of vertices in any polygon is limited to 25. <l  bxd xpp?si]4@xdc ;6kreo 6_ l<mbw: distance (in feet) driver's vehicle has travelled when the event begins.<al  bpxd xpp?si m ]4@pxd c Ͻk;rmcs <bw: the complete name of the file that contains the message to be played, including the path. you must include the file name extension (.wav) in the file name. <"  bxd xpp?sin]4@xdc աěƠiqx/ <bw: the playback flag: to specify the type of playback, set parameter 2 to one of the following: 0. play the recording and continue to run the simulation 1. play the recording, continue to run the simulation, but hold all subsequent events until the recording has finished <;  byd xpp?si ']4@ydc |*g+:z j<kbw: volume control when playing back the file. values range from 0 to 10. <bj  bpyd xpp? i]4@pyd@c d sagky@heje 7yk c:\stisim\help\sdleventpr.htmyk ../../appdata/local/microsoft/windows/stisim/help/sdleventpr.htmyx;h,]ą'cryk back to commands'command index'!b10yk c:\stisim\help\sdleventpr.htmyk f../../../../stisim/help/sdleventpr.htmyx;h,]ą'cf\ distance from start of course(distance measured in feet)et parameter 1the complete name of the file that contains the message to be played, including the path. you must include the file name extension (.wav) in the file name. myx  2. playback typeerror!0. play the recording and continue to run the simulation 1. play the recording, continue to run the simulation, but hold all subsequent events until the recording has finishedcorrect range: 0-1d 3. volume controlerror!range: 0 to 10 correct range: 0-10ru s   comment & command linehighlight the blue cells, then copy (ctl-c) and paste (ctl-v) into your sdl file. if you want the command without the comment, copy only the last line (with a box around it).dco  sheet38ggdggh'h   4  dmbp?_*+%&?'?(?)?"??&u} u} } } } } } } 5                nx o nz  n]  n n`~ s@@u wa:xc $ comment for d@ -- d@bp,)comment for rmsb -- begin taking rms datayyyyy zb zc wa xd xex \f yy c?s wa]? d^ dy y yy ~ c@ z wa]@ d6^0d  da $b$!curve to right with 2 pedestriansy y yy   yyyyyyy nq6 d@@  da $b er6 ed  da $brmsb er6 e da $b er6 fd da $b$!curve to right with 2 pedestrians ar s g gw * l"s' w (  wi`(    b([d xpp?i]4@([d c d, :l(ym q(<rstisim drive (sdl) - rmsb - begin rms data block begin collecting rms data on the driver. you can use rmsb with the rmse event to collect rms data anytime during a simulation run. for reference, the rms here refers to the root mean square of the deviations. this is more commonly known as standard deviation. the simulation will keep track of the data and the order that the data is taken. you must use an rmse event before using a new rmsb event. if you do not first use an rmse before the next rmsb, then all of the data will be lumped together into one block and the final data for both blocks will be incorrect. for a complete list of the variables that are collected using the rmsb event, refer to the discussion on rms blocks in the stisim drive data file. example: 1000, rmsb, 0, curve to the right with 2 pedestrians in this example, stisim drive will begin collecting rms data after the driver has traveled 1000 feet down the road. when the rms data that is collected is stored in the stisim drive data file, the block of data that is collected with this event line will be entitled "curve to the right with 2 pedestrians". <(22~ 2q  b[d xpp?si]4@[dc xo䫵ei= l<mbw: distance (in feet) driver's vehicle has travelled when the event begins.<al  b\d xpp?si n ]4@\dc  g^iq  < this parameter is no longer used, but is still required so that event files that ran with previous versions of the software will still be compatible with this version. <    bp\d xpp?si ]4@p\d@c !s `fp,4 r a<bbw: this is a string variable that allows you to mark a particular rms data block with its own individual title. this parameter is intended to help you with your data reduction needs. labeling a block of rms data with a descriptive name makes it easy to search through the data that was collected and find the block of data that you are trying to find. <|a  b\d xpp? i |]4@\dc eafj}˪w~r <comment & command line: highlight the blue cells, then copy (ctl-c) and paste (ctl-v) into your sdl file. if you want the command without the comment, copy only the last line (with a box around it).<rive michel bdard  michel bdard  michel bdard  michel bdard   michel bdard >@heje 7yk  c:\stisim\help\sdleventrmsb.htmyk ../../appdata/local/microsoft/windows/stisim/help/sdleventrmsb.htmyx;h,]ą'cryk back to commands'command index'!b11yk  c:\stisim\help\sdleventrmsb.htmyk j../../../../stisim/help/sdleventrmsb.htmyx;h,]ą'cf\ distance from start of course(distance measured in feet)et parameter 1no longer used. but is still required so that event files that ran with previous versions of the software will still be compatible with this version. tm| 2. rms data block nameerror!*string variable (label for rms data block)correct range: 0-1eron comment & command linehighlight the blue cells, then copy (ctl-c) and paste (ctl-v) into your sdl file. if you want the command without the comment, copy only the last line (with a box around it).  sheet39ggdggh'h   $'  dmbp?_*+%&?'?(?)?"??&u} u} } } 1     nx o nz  n]  n n`~ sp@u wa:x`d $ comment for d@ -- d@bp*'comment for rmse -- end taking rms data] zb zc wa y] yyy nq6dp@  da $b er6fd da $brmse ar s g gw5* b( w) p(    b]d xpp?iez]4@]d c ?gglzo؜ (<stisim drive (sdl) - rmse - end rms data block end collecting rms data on the driver. you use rmse with the rmsb event to collect rms data anytime during a simulation run. since all this event does is tell the software to stop collecting rms data, there are no parameters required. for reference, the rms here refers to the root mean square of the deviations. this is more commonly known as standard deviation. event parameters: none example: 2000, rmsb, 0, curve to the right with 2 pedestrians 3000, rmse in the above example, the simulation will begin collecting a block of rms data (2000, rmsb) after the driver has traveled 2000 feet down the road and the rms data block will end after the driver has traveled 3000 feet down the road (3000, rmse). <(/5-  b(^d xpp?si]4@(^dc |9j jsl l<mbw: distance (in feet) driver's vehicle has travelled when the event begins.<al  b^d xpp?i ]4@^dc ymnpfb  <comment & command line: highlight the blue cells, then copy (ctl-c) and paste (ctl-v) into your sdl file. if you want the command without the comment, copy only the last line (with a box around it).<rive michel bdard  michel bdard  michel bdard >@heje   7yk  c:\stisim\help\sdleventrmse.htmyk ../../appdata/local/microsoft/windows/stisim/help/sdleventrmse.htmyx;h,]ą'cr yk back to commands'command index'!b12yk  c:\stisim\help\sdleventrmse.htmyk j../../../../stisim/help/sdleventrmse.htmyx;h,]ą'c\ distance from start of course(distance measured in feet)et comment & command linehighlight the blue cells, then copy (ctl-c) and paste (ctl-v) into your sdl file. if you want the command without the comment, copy only the last line (with a box around it). sheet40ggdggh'h  ,^5sb  dmbp?_*+%&?'?(?)?"??&u} u} } } } } } } } } } } } } } } } } } } } } } } } } } } } } } !!} ""} ##} $$} %%} &&} ''} ((} ))} **} ++} ,,} --} ..} //} 00} 11} 22} 33} 44} 55,6666666666 6 6 6 6 6666666666666666666 nx o  nz   n]   n n`~ su wa:xd $ comment for d@ -- d@bp&#comment for road -- road parametershyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyy5 zb zc wa xd xex \fbyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyy5c?s(@ wa]? d^(@ dy y byyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyy5c@s@ wa]@(%l^@( *% la ,by y byyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyy5 c@s? wa ]@(  ^?(  y yb yyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyy5 c@s@ wa ]@(  ^@(  y yb yyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyy5 c@s? wa ]@(  ^?(  y yb yyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyy5 c@s$@ wa ]@(  ^$@(  y yb yyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyy5 c@s$@ wa ]@(  ^$@( y yb yyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyy5~ c @szd;o? wa] @(^zd;o?(y ybyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyy5~ c"@szd;o? wa]"@(^zd;o?(y ybyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyy5c$@s wa]$@(^(y ybyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyy5c&@b wa]&@(^(y ybyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyy5c(@b wa](@(^(y ybyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyy5c*@b wa]*@(^(y ybyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyy5c,@b@ wa],@(^@(y ybyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyy5c.@b wa].@(^(y ybyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyy5c0@b@ wa]0@(^@(y ybyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyy5c1@b wa]1@(^(y ybyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyy5c2@b$@ wa]2@(^$@(y ybyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyy5c3@b wa]3@(^(y ybyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyy5c4@b$@ wa]4@(^$@(y ybyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyy5c5@b wa]5@(^(y y byyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyy5~ c6@b wa]6@(^@(y y!byyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyy5~ c7@b wa]7@(^@(y y"byyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyy5~ c8@b wa]8@(^@(y y#byyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyy5~ c9@b wa]9@(^@( y y$byyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyy5dl* ! 6!6"6#6$6%6&6'6)6*6+6~ c:@ b wa ]:@(  ^@(! y y%b yyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyy5~ !c;@!b !wa!];@(!!^@("!y !y&b!yyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyy5~ "c<@"b "wa"]<@(""^@(#"y "y'b"yyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyy5~ #c=@#b #wa#]=@(##^@($#y #y(b#yyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyy5~ $c>@$b $wa$]>@($$^@(%$y $y)b$yyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyy5~ %c?@%b %wa%]?@(%%^@('%y %y*b%yyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyy5&l&yyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyy5 'nq6'd ' da $b 'er6'ed ' da $broad 'er6'e(@ ' da $b 'er6' e@ ' da $b ' er6' e? ' d a $ b ' er6' e@ ' d a $ b 'er6'e? ' d a $ b 'er6'e$@ ' d a $ b 'er6'e$@ ' d a $ b 'er6'ezd;o? ' da $b 'er6'ezd;o? ' da $b 'er6'e ' da $b 'er6'e ' da $b 'er6'e ' da $b 'er6'e '! da $b ' er6'!e@ '# da $b '"er6'#e '% da $b '$er6'%e@ '' da $b '&er6''e ') da $b '(er6')e$@ '+ da $b '*er6'+e '- da $b ',er6'-e$@ '/ da $b '.er6'/e '1 da $b '0er6'1e@ '3 da $b '2er6'3e@ '5 da $b '4er6'5f@ da $b )ar )s *g +gw5z[) w'* 5#"(    bp_d xpp?i!x]4@p_dc ,dj=  8<stisim drive (sdl) - road - road parameters the road event displays the simulation roadway allowing the experimenter to specify a variety of different roadway attributes. the default roadway (if no road event is specified) consists of a single lane of traffic in each direction, a dashed line separating the 2 lanes, and no edge lines. the lanes are 12 feet wide and the center stripes are 10 feet long and .3334 feet wide with a 10 foot spacing between the lines. it is recommended that if you will be using the road event, it should appear as the first line in your events file, thus starting the simulation with the roadway you desire. you can then change the roadway later on in your scenario by activating another road event. with stisim drive, you can specify some additional roadway parameters such as shoulder width, foreslope, and roadway cross-slope. these along with the vc (vertical curvature) event allow you to generate three dimensional roadways. these parameters are numbers 11 through 21 and are optional. if you do not specify parameters 11 through 21 they will be ignored. additionally, parameters 22-31 allow you to change the look of the road (either colors or textures) as a function of distance down the road. one other caveat of the roadway that you should know about deals with the roadway center line. the roadway that you display can have traffic flowing in both directions separated by some roadway striping (total # of lanes does not equal # of right hand lanes), or you can have roadways with traffic heading in only 1 direction (total # of lanes equals # of right hand lanes). add to this that the number of lanes on the left and right do not have to be equal, and there are numerous roadway possibilities. because of all these possibilities, the lateral position of most events is defined with respect to the roadway s dividing line. the roadway dividing line is defined as the lateral position on the road where the right hand lanes and left hand lanes meet. for roadways with traffic in both directions, the roadway dividing line is the center stripe. for roadways where the traffic is only heading forward, the roadway dividing line is defined as the left edge of the roadway. note: some important facts to remember when designing your roads: always include some cross slope in the roadway lanes, shoulders and foreslopes. this will make the roadway display better. if you do not include some cross slope, the graphics engine will sometimes have trouble distinguishing between the ground and the roadway elements and this can cause the roadway display to breakup and look funny. changing roadway attributes too close together is not a good idea. since the roadway is essentially generated on the fly, the program sometimes has trouble distinguishing between roadway attributes when they are changed too quickly. there is no magical distance that should be used, you will have to use visual verification. example: 0, road, 12, 2, 1, 3, .5, 10, 10, .333, .333, 0, -1, -1, 0, 6, 0, 6, -5, 10, -5, 10, 0<8,( 5    b_d xpp?si]4@_d`c 1`o`w l<mbw: distance (in feet) driver's vehicle has travelled when the event begins.<al  bg xpp?si m ]4@gpg }+9k^e}% <bw: width, in feet, of each roadway lane. all of the lanes no matter what direction the traffic is heading will have the same widths. <  bpg xpp?si f-]4@pg`pg jgdk <bw: total number of lanes that will be displayed for the desired roadway. this total includes all lanes traveling in both directions. <r  bg xpp?si|]4@gpg ޟ e>ith7++i <bw: total number of right hand side lanes. this total only includes lanes that will appear to the right of the roadway s dividing line. <z  bg xpp?s i]4@g qg /%k1a:uԹ <bw: roadway s dividing line striping option (the color for these lines is specified with the "set simulation colors" and "assign simulation colors" options, found in the "options" menu. 0. no dividing line is displayed 1. broken or dashed line 2. solid double line 3. solid line on left and broken or dashed line on right 4. solid line on the right and a broken or dashed line on the left 5. double solid line on each side of the dividing line 6. single solid line 7. double dashed line <v   bpg xpp?s i>]4@pgqg 6 s)ccm[c <bw: edge line flag. if this parameter is 0, then no edge lines will be displayed, otherwise the value that is used specifies the distance, in feet, from the edge of the roadway to the inside edge of the edge line. <  bg xpp?s i ]4@gqg .&k#l9h <bw: for cases when the lane markers are stripes, this parameter specifies the length, in feet, of the stripes that will be displayed. <o  bg xpp?s i]4 @g@rg l "m6mfaтП <bw: width, in feet, of the lane division markers. this parameter effects the widths of the dividing line markings and any lane marking between lanes headed in the same direction. <u  bg xpp?dx]4 @gsg sh%0g::_* q<rbw: width, in feet, of the edge lines, if they will be displayed on the roadway. <xq  bg xpp?si ]4 @g`sg 4}:bw_79 <bw: transition length, in feet, to change from previous road event. the road width will linearly change over the transition length. <  bpg xpp?si]4 @pgsg "!~)uh +<,bw: cross-slope for the left hand side travel lanes, in percent grade (100 * feet/feet). all of the lanes on the left hand side of the road will have this cross-slope. negative values for the cross-slope mean that the road is sloping down as you go from the centerline to the roadway's outer edge. <+  bg xpp?si>]4@g tg uf*^csn <bw: cross-slope of the right hand side shoulder, in percent grade (100 * feet/feet). negative values for the cross-slope mean that the road is sloping down as you go from the centerline to the roadway's outer edge. <   bg xpp?si ]4@gtg hoguxdu<' 5<6bw: width, in feet, of the right hand side shoulder. <5  bpg xpp?si]4@pgtg d&q@rtr4 <bw: cross-slope of the left hand side shoulder, in percent grade (100 * feet/feet). negative values for the cross-slope mean that the road is sloping down as you go from the centerline to the roadway's outer edge. <  bg xpp?si>-]4@g@ug 89jgm<$: <bw: slope of the right hand side foreslope, in percent grade (100 * feet/feet). negative values for the slope mean that the road is sloping down as you go from the centerline to the roadway's outer edge. <  bg xpp?si ]4@gug rxbyc[lϤ 7<8bw: width, in feet, of the right hand side foreslope. <7  bpg xpp?si]4@pgvg z]4@gvg & @x.b%y <bw: width, in feet, of the center median. the center median will always be flat and symmetric about the roadway center line as shown in the roadway figure. <  bpg xpp?si "]4@pg wg & [>cki(& <bw: either the color value or the name of a file containing the texture map that will be used for displaying the roadway lanes. <y  bg xpp?si ]4@gwg zn0@ x<ybw: if a texture map will be used in parameter 22, then this parameter specifies the width of the texture map in feet. <?x  bg xpp?si f!-]4@gwg bitrpl;  <bw: either the color value or the name of a file containing the texture map that will be used for displaying the roadway shoulders. <n  bpg xpp?si]4@pg@xg aӠ)ozfb -<.bw: cross-slope for the right hand side travel lanes, in percent grade (100 * feet/feet). all of the lanes on the right hand side of the road will have this cross-slope. negative values for the cross-slope mean that the road is sloping down as you go from the centerline to the roadway's outer edge. <-  bg xpp?si]4@gxg b:cf0m 4<5bw: width, in feet, of the left hand side shoulder. <4ewh  bg xpp?si#]4@gyg %o|g ds w<xbw: if a texture map will be used in parameter 24, then this parameter specifies the width of the texture map in feet. <4w   bpg xpp?si ]$]4@pg`yg `*l<, <bw: either the color value or the name of a file containing the texture map that will be used for displaying the roadway foreslopes. <r   bg xpp?s i%]4@gyg  4}n w<xbw: if a texture map will be used in parameter 26, then this parameter specifies the width of the texture map in feet. <4w   bg xpp?s!i&]4@g zg gg~g y<zbw: either the color value or the name of a file containing the texture map that will be used for displaying the ground. <*y   bpg xpp?s"i']4@pgzg ܨa'bdac& w<xbw: if a texture map will be used in parameter 28, then this parameter specifies the width of the texture map in feet. <)w   bg xpp?s#i 6(]4 @gzg ״h/ m <bw: either the color value or the name of a file containing the texture map that will be used for displaying the roadway median. <b  ! bg xpp?s$i)]4!@g@[g 3edqi#y w<xbw: if a texture map will be used in parameter 30, then this parameter specifies the width of the texture map in feet. <4w  " bpg xpp?&i+]4"@pg[g j$ ,a~)} <comment & command line: highlight the blue cells, then copy (ctl-c) and paste (ctl-v) into your sdl file. if you want the command without the comment, copy only the last line (with a box around it).<rive michel bdard  michel bdard  michel bdard  michel bdard   michel bdard   michel bdard   michel bdard   michel bdard  michel bdard  michel bdard  michel bdard  michel bdard  michel bdard  michel bdard  michel bdard  michel bdard  michel bdard bwc michel bdard  michel bdard  michel bdard  michel bdard  michel bdard  michel bdard  michel bdard  michel bdard bwc bwc!bwc"bwc#bwc$ bwc%!bwc'" michel bdard >(@hejea 53+++ 7 yk c:\stisim\help\sdleventa.htmyk ../../appdata/local/microsoft/windows/stisim/help/sdleventa.htmyx;h,]ą'cr++yk back to commands'command index'!b13yk  c:\stisim\help\sdleventroad.htmyk j../../../../stisim/help/sdleventroad.htmyx;h,]ą'cb!\ distance from start of course(distance measured in feet)et 1. lane widthwidth, in feet, of each roadway lane. all of the lanes no matter what direction the traffic is heading will have the same widths. /d: 2. total # of laneswarningtotal number of lanes that will be displayed for the desired roadway. this total includes all lanes traveling in both directions.uyou have entered a number of lanes outside the range 1-6. please verify that the number you have entered is correct.er. k 3. number of r laneswarningztotal number of right hand side lanes. includes only lanes that will appear to the right of the roadway s dividing line.4please check that the number you entered is correct."i  4. dividing line styleerror!0. none 1. broken/dashed 2. solid double line 3. l=solid, r=broken 4. l=broken, r=solid 5. double solid on each side 6. single solid line 7. double broken linecorrect range: 0-7 e  21. width of medianwidth, in feet, of the center median. the center median will always be flat and symmetric about the roadway center line as shown in the roadway figure. keli 22. roadway texture}either the color value, or the name of a file containing the texture map that will be used for displaying the roadway lanes. inhe 23. texture map widthsif a texture map will be used in parameter 22, then this parameter specifies the width of the texture map in feet. .  5. edge line flagwif 0: no edge lines else: value = distance (feet) from the edge of the roadway to the inside edge of the edge line .   6. length of stripesfor cases when the lane markers are stripes, this parameter specifies the length, in feet, of the stripes that will be displayed.   7. stripe gapfor cases when the lane markers are stripes, this parameter specifies the longitudinal distance, in feet, between the end of one stripe and the beginning of the next stripe.  r  8. division marker widthwidth, in feet, of the lane division markers. this parameter effects the widths of the dividing line markings and any lane marking between lanes headed in the same direction.   9. edge line widthmwidth, in feet, of the edge lines, if they will be displayed on the roadway. dt o 10. transition lengthtransition length, in feet, to change from previous road event. the road width will linearly change over the transition length. g tw1 11. cross-slope (r side)in percent grade (100 * feet/feet) all of the lanes on the right hand side of the road will have this cross-slope. negative values for the cross-slope mean that the road is sloping down as you go from the centerline to the roadway's outer edge.ea cl 14. width of r shoulder1width, in feet, of the right hand side shoulder. n e k 16. width of l shoulder0width, in feet, of the left hand side shoulder. ne 17. slope of r foreslopein percent grade (100 * feet/feet). negative values for the slope mean that the road is sloping down as you go away from the centerline.s-opn 18. width of r foreslope2width, in feet, of the right hand side foreslope. r e 0 12. cross-slope (l side)in percent grade (100 * feet/feet) all of the lanes on the left hand side of the road will have this cross-slope. negative values for the cross-slope mean that the road is sloping down as you go from the centerline to the roadway's outer edge.e  13. cross-slope, r shoulderin percent grade (100 * feet/feet) negative values for the cross-slope mean that the r shoulder is sloping down as you go away from the centerline.hath 15. cross-slope, l shoulderin percent grade (100 * feet/feet) negative values for the cross-slope mean that the l shoulder is sloping down as you go away from the centerline.hath 19. slope of l foreslopein percent grade (100 * feet/feet). negative values for the slope mean that the road is sloping down as you go away from the centerline.ernem 20. width of l foreslope1width, in feet, of the left hand side foreslope. orhe 24. shoulder textureeither the color value or the name of a file containing the texture map that will be used for displaying the roadway shoulders. tein 25. width of texture mapsif a texture map will be used in parameter 24, then this parameter specifies the width of the texture map in feet. s. 26. foreslope textureeither the color value or the name of a file containing the texture map that will be used for displaying the roadway foreslopes.   27. width of texture mapsif a texture map will be used in parameter 26, then this parameter specifies the width of the texture map in feet. pe !! 28. ground textureueither the color value or the name of a file containing the texture map that will be used for displaying the ground. pe"" 29. width of texture mapsif a texture map will be used in parameter 28, then this parameter specifies the width of the texture map in feet. pe"## 30. median texture}either the color value or the name of a file containing the texture map that will be used for displaying the roadway median. "#$$ 31. width of texture mapsif a texture map will be used in parameter 30, then this parameter specifies the width of the texture map in feet. "%% comment & command linehighlight the blue cells, then copy (ctl-c) and paste (ctl-v) into your sdl file. if you want the command without the comment, copy only the last line (with a box around it).do a'' sheet41ggdggh'h%  b  dmbp?_*+%&?'?(?)?"??&u} u} } } } } } } } } } } } } } } } } } } } } } } } } } } } 5      nx o+ nz , n] g-n n`~ s@@u wa:x\g $ comment for d@ -- d@bp-*comment for rsa -- road surface attributes yyyyyyyyyyyyy zb zc wa xd xex \fyyyyyyyyyyk?s? wa]? d^? dy y.yyyyyyyyyyk@s$@ wa]@ d6^$@  da $by y/yyyyyyyyyy k@b wa ]@ d 6 ^  d a $ b y y. yyyyyyyyyy k@b@ wa ]@ d 6 ^@  d a $ b y y/ yyyyyyyyyy~ k@ b wa ]@ d 6 ^@  d a $ b y y. yyyyyyyyyy~ k@ b wa ]@ d 6 ^@  d a $ b y y/ yyyyyyyyyy $ yyyyyyyyyyyyyyy nq6d@@  da $b er6e  da $brsa er6e?  da $b er6 e$@  da $b  er6 e  d a $ b  er6 e@  d a $ b er6e @  d a $ b er6f$@ d a $ b ar s g gw( t |2j* w+ 4 (    bg xpp?i]4@g ]g 387b=v l<mbw: the road surface attribute event "rsa" is used to assign an attribute number to a section of the roadway. attribute numbers are used to tell the vehicle simulation which set of tire parameters to use for a particular roadway section. the rsa has two parameters: a lane number (see figure), and an attribute number. initially, all lanes are set to attribute number 0, which tells the simulation to use its standard tire parameters. if a lane has its attribute number changed, it retains the new attribute number until a new value is set. for simple dynamics systems, this event allows the roadway friction coefficient to be changed whereas for advanced dynamic systems new tire parameters for each attribute number can be defined in tire attribute files. note: this event has different definitions for simple and complex dynamic systems. <l  bpg xpp?ri3]4@pg]g y f[n夜 l<mbw: distance (in feet) driver's vehicle has travelled when the event begins.<al  bg xpp?rim x]4@g]g |7j:j >kk <bw: desired lane number(s) that will have their surface attribute changed. see the accompanying figure for a complete list of the various lanes. <  bg xpp?rim x]4@g@^g jejy`~@ <bw: desired lane number(s) that will have their surface attribute changed. see the accompanying figure for a complete list of the various lanes. <  bpg xpp?r imx]4@pg^g )wێj7. <bw: desired lane number(s) that will have their surface attribute changed. see the accompanying figure for a complete list of the various lanes. <  bg xpp?ri m-]4@g_g j5j}95  <abw: this parameter is effected by the type of dynamics that are being used and therefore has a different definition based on the dynamics: simple dynamics: ten times the surface s coefficient of friction. therefore a value of 3 would mean a friction coefficient of .3. the nominal friction coefficient is set internally to a value of .8 (which means setting this parameter to a value of 8 will do nothing). therefore values above 8 will mean the vehicle s tires have more traction, values below 8 mean that the vehicle s tires will have less traction. advanced dynamics: new attribute number that will be assigned to the specified lane. this number will then be used with the data contained in the tire attribute file to determine which tire characteristics will be used with this new attribute. <   bg xpp?r i m-]4@g`_g (o8   <abw: this parameter is effected by the type of dynamics that are being used and therefore has a different definition based on the dynamics: simple dynamics: ten times the surface s coefficient of friction. therefore a value of 3 would mean a friction coefficient of .3. the nominal friction coefficient is set internally to a value of .8 (which means setting this parameter to a value of 8 will do nothing). therefore values above 8 will mean the vehicle s tires have more traction, values below 8 mean that the vehicle s tires will have less traction. advanced dynamics: new attribute number that will be assigned to the specified lane. this number will then be used with the data contained in the tire attribute file to determine which tire characteristics will be used with this new attribute. <   bpg xpp?r i m-]4@pgh dfhe7  <abw: this parameter is effected by the type of dynamics that are being used and therefore has a different definition based on the dynamics: simple dynamics: ten times the surface s coefficient of friction. therefore a value of 3 would mean a friction coefficient of .3. the nominal friction coefficient is set internally to a value of .8 (which means setting this parameter to a value of 8 will do nothing). therefore values above 8 will mean the vehicle s tires have more traction, values below 8 mean that the vehicle s tires will have less traction. advanced dynamics: new attribute number that will be assigned to the specified lane. this number will then be used with the data contained in the tire attribute file to determine which tire characteristics will be used with this new attribute. <   bg xpp? i]4 @g`h regdї5 <comment & command line: highlight the blue cells, then copy (ctl-c) and paste (ctl-v) into your sdl file. if you want the command without the comment, copy only the last line (with a box around it).<rive michel bdard  michel bdard bwcbwc bwc bwc bwc bwc michel bdard >@heje7yk c:\stisim\help\sdleventrsa.htmyk h../../../../stisim/help/sdleventrsa.htmyx;h,]ą'cryk back to commands'command index'!b14x\ distance from start of course(distance measured in feet)cm 1. lane number(s)lane number(s) that will have their surface attribute changed. see the accompanying figure for a complete list of the various lanes. ee 3. lane number(s)lane number(s) that will have their surface attribute changed. see the accompanying figure for a complete list of the various lanes. ee  5. lane number(s)lane number(s) that will have their surface attribute changed. see the accompanying figure for a complete list of the various lanes. ee % parameter 2simple dynamics: ten times the surface s coefficient of friction. advanced dynamics: number used with the data contained in the tire attribute file to determine which tire characteristics will be used with this new attribute. see comment to left. 3% parameter 4simple dynamics: ten times the surface s coefficient of friction. advanced dynamics: number used with the data contained in the tire attribute file to determine which tire characteristics will be used with this new attribute. see comment to left. 3 % parameter 6simple dynamics: ten times the surface s coefficient of friction. advanced dynamics: number used with the data contained in the tire attribute file to determine which tire characteristics will be used with this new attribute. see comment to left. 3  comment & command linehighlight the blue cells, then copy (ctl-c) and paste (ctl-v) into your sdl file. if you want the command without the comment, copy only the last line (with a box around it).sd sheet42ggdggh'h      dmbp?_*+%&?'?(?)?"??&u} u} } } } } } } } } } } } } } } } } } } } } } } } } } } } 5                 nx o0 nz 1 n] g2n n`~ su wa:x@h $ comment for d@ -- d@bp"comment for rt -- reaction time yyy zb zc wa xd xex \fk?s wa]? d^ dy y3k@s$@ wa]@ d6^$@  da $by y4~ k@ z5 wa ]@ d 6 ^h  d a $ b data\miscellaneous\rtstop.3ds y y6  nq6 d  da $b er6 e  da $brt er6 e da $b er6 e$@ da $b er6 fh d a $ b data\miscellaneous\rtstop.3ds ar s g gw"5 ^z + w ,  eoux(    bqh xpp?i]4@qhh  Ïjh'r,u <stisim drive (sdl) - rt - reaction time this is a very specialized event for measuring a driver's reaction time. the rt event simply displays a large image of a stop sign (or other image if you prefer) in the center of the screen. the driver is then supposed to press the brake pedal as fast and as hard as possible. you can then setup the scenario to collect data and get the driver's reaction time and stopping distance. stisim drive comes with a pde file named reactiontime.pde that does this for you and is explained in the example below. if you use the reactiontime.pde file, the average reaction time and stopping distance (in case you do it multiple times in a single run) will be displayed as part of the run summary. it should be noted that while the reaction time image is being displayed, the hood and rear view mirror(s) will be turned off. after the image has been displayed for the specified duration, the hood and mirror(s) will be restored. <)  bpqh xpp?ri3]4@pqhh ' uaze/~ l<mbw: distance (in feet) driver's vehicle has travelled when the event begins.<al  bqh xpp?rim x]4@qh@h ާ0bh`h2bx s<tbw: flag specifying what measure will be used to turn the image off: 0. time (seconds) 1. distance (feet) <!s  brh xpp?ri m ]4@rhh la3|  p<qbw: duration of the image in either seconds or feet based on parameter 2 above. <p  bprh xpp?ri ]4@prhh on{@cpm <bw: name of the image file that will be used. this must be located within the stisim drive root directory. in the reactiontime.pde file the file that is used is data\miscellaneous\rtstop.3ds, however you can use any image you desire. <`  brh xpp? i]4@rh`h _}筼mnf <comment & command line: highlight the blue cells, then copy (ctl-c) and paste (ctl-v) into your sdl file. if you want the command without the comment, copy only the last line (with a box around it).<rive michel bdard  michel bdard bwcbwc bwc  michel bdard >@heje7yk c:\stisim\help\sdleventrt.htmyk f../../../../stisim/help/sdleventrt.htmyx;h,]ą'cryk back to commands'command index'!b15v\ distance from start of course(distance measured in feet)cm~ 1. image turn-off flagerror!- 0. time (seconds) 1. distance (feet) enter 0 or 1.! 3. image file namethis must be located within the stisim drive root directory. in the reactiontime.pde file the file that is used is data\miscellaneous\rtstop.3ds, however you can use any image you desire.u si | parameter 2m duration of the image in either seconds or feet based on parameter 2 above. ti.p comment & command linehighlight the blue cells, then copy (ctl-c) and paste (ctl-v) into your sdl file. if you want the command without the comment, copy only the last line (with a box around it).  sheet43ggdggh'h   - 9  dmbp?_*+%&?'?(?)?"??&u} u} } } } } } } } } } } } } } } } } } } } } } } } } } } } 5      nx o7 nz 8 n] 9n n`~ zp@o wa:xh $ comment for d@ -- d@bp+(comment for sign -- display roadway sign yyyyyyyyyyyyy zb nc wa xd xex \fyyyyyyyyyyk?zy@ wa]? d^y@ dy y:yyyyyyyyyyk@z@@ wa]@ d6^@@  da $by y;yyyyyyyyyy~ k@ z< wa ]@ d 6 ^d  d a $ b$!c:\stisim\data\signs\rgtcrv30.3ds y y= yyyyyyyyyy k@z wa ]@ d 6 ^  d a $ b y y> yyyyyyyyyy~ k@  wa ]@ d 6 ^4@  d a $ b y y? yyyyyyyyyy~ k@  wa ]@ d 6 ^8@  d a $ b y y@ yyyyyyyyyy $ yyyyyyyyyyyyyyy nq6dp@  da $b er6ed  da $bsign er6ey@  da $b er6 e@@  da $b  er6 e`d  d a $ b$!c:\stisim\data\signs\rgtcrv30.3ds  er6 e  d a $ b er6e<@  d a $ b er6f@@ d a $ b ar s g gw(7 t& |2s, w- 4 (    bsh xpp?in]4@sh@h ai6oh<% <stisim drive (sdl) - sign - roadway signs event for displaying roadway traffic signs. the type of sign and any special properties associated with the sign are specified with event parameters. this event supercedes and should be used in place of all the other original sign events (d, ia, l, q, r, sa and t). the original sign events can still be used but this event will be used in the future and therefore any additional functionality will be included here instead of for each individual sign event. the sign event allows you to specify whether or not united states signs will be used or if generic european signs will be used. the models for the us signs are found in the data\signs directory and the generic european signs are found in data\eurosigns. it should be noted that the european signs are generic because of the differences from country to country. you can create your own sign and have it replace an existing sign by simply renaming your sign model with the same name of the sign model you will be replacing. since road signs are an important part of driving and differ from country to country, it is impossible for sti to include all the road signs that you may desire. therefore we have prepared a simple road sign creation guideline that can be used to help you create your own road signs. <*  b(th xpp?ri3]4@(thh u>d l<mbw: distance (in feet) driver's vehicle has travelled when the event begins.<al  bth xpp?ri  ]4@thh ues @%vm q<rbw: type of sign that will be displayed. sign images and descriptions are shown below. simply use the number of the sign from the images below and enter that number as parameter 1 to display the desired sign. you can also specify your own road sign files, simply use the value of 100 for the sign type (this parameter) and then look at the description of parameter 3. < q  bth xpp?ri m-]4@th`h #vrj&l q<rbw: the longitudinal distance, in feet, that the sign is away from the driver when the sign initially appears. because the roadway is more flexible in stisim drive than it was in the dos version of stisim, we have added some additional functionality to this parameter for the stop sign. if this parameter is specified as a negative number, then the program will automatically figure out (to the best of its knowledge based on the current roadway) where the stop signs will be placed. otherwise, it will act as specified. this option was added because it is now easy to have the roadway transition from a set number of lanes to another set number of lanes and if you are trying to use a pde that has stop signs in it and the roadway is a different size, you may have trouble. the longitudinal distance is still the same, it just has a minus sign (-) in front of it. if you are using this option, you must make sure that the stop sign event lines up with the intersection event, otherwise the signs will be mis-aligned. for example if you have an intersection that is 1200 feet away, you want the stop sign event to be -1200 feet away. <q  b(uh xpp?ri]4@(uhh sy6nǷqe <bw: specialty parameters for any signs that require them: stop sign (parameter 1 = 7): 1. single stop sign in driver's direction 2. two way stop in the driver's direction 3. single stop sign in cross traffic's direction on right 4. 4 way stop 5. two way cross traffic stop 6. single stop sign in cross traffic's direction on left special signs (parameter 1 = 100): full name (including path) of the sign that will be displayed. this option lets you specify the sign, but the program takes care of placing the sign in the roadway. this way if you change the shape of your road, the sign will be placed just like all of the other stisim drive signs. <l   buh xpp?r i m]4@uh h ˬd&yn˾te u<vbw: sign source: 0. united states road signs 1. generic european road signs <u  buh xpp?r i]]4@uhh "_vh*ph (<bw: flag specifying if the sign should be displayed on the opposite side of the road: 0. sign displayed on driver s side of road 1. sign displayed on opposite side of road note: default value appears to be 0.<(t  bpvh xpp?r i m]4@pvhh \:d"jz (<bw: sign heading rotation value, in degrees. this allows you to display road signs whose faces are rotated relative to the roadway. for example a sign on the other side of the road facing in the other direction. note: default value appears to be 0 degrees.<(  bvh xpp? i]4 @vh@h n2vb89r <comment & command line: highlight the blue cells, then copy (ctl-c) and paste (ctl-v) into your sdl file. if you want the command without the comment, copy only the last line (with a box around it).<rive michel bdard  michel bdard bwcbwc bwc bwc bwc bwc michel bdard >@heje 7yk  c:\stisim\help\sdleventsign.htmyk ../../appdata/local/microsoft/windows/stisim/help/sdleventsign.htmyx;h,]ą'cryk back to commands'command index'!b16yk  c:\stisim\help\sdleventsign.htmyk j../../../../stisim/help/sdleventsign.htmyx;h,]ą'c^\ distance from start of course(distance measured in feet)et 1. type of signerror!rvalid values: 1-16, 100 see help file for pictures of us or european road signs.valid values: 1-16, 100-t*123456789101112131415161001 3. special parameterspecial parameter for any sign that requires it (e.g., stop sign). or, if p1=100, full name (including path) of the sign that will be displayed. see comment in cell to the left.6  5. side of road to display signerror!d 0. sign on driver s side of road 1. sign on opposite side of roadvalid values: 0,1le  parameter 2the longitudinal distance, in feet, that the sign is away from the driver when the sign initially appears. see comment to left for details.o  parameter 4: road sign sourceerror!' 0. usa road signs 1. generic european valid values: 0,1gnia d parameter 6warning!sign heading rotation value, in degrees. this allows you to display road signs whose faces are rotated relative to the roadway. for example a sign on the other side of the road facing in the other direction. 7you entered a rotation outside the range 0-360 degrees.adh  comment & command linehighlight the blue cells, then copy (ctl-c) and paste (ctl-v) into your sdl file. if you want the command without the comment, copy only the last line (with a box around it).n e  sheet44ggdggh'h   la q  dmbp?_*+%&?'?(?)?"??&u} u} } } } } } } } } } } } } } } } } } } } } } } } } } } } } } !!} ""} ##} $$} %%} &&} ''} ((} ))} **} ++} ,,} --} ..} //} 00} 11} 22} 33} 44} 55      nx oa nz b n] c n n`~ s@@u wa:xd $ comment for d@ -- d@bp74comment for sl -- signal light (i.e., traffic light),yyyyyyyyyyyyyyyyyyy zb zc wa xd xex \f&yyyyyyyyyyyyyyyyc?s@@ wa]? d^@@ dy yd&yyyyyyyyyyyyyyyyc@s@ wa]@(l^@( * la ,by ye&yyyyyyyyyyyyyyyy c@s@ wa ]@(  ^@(  y yf& yyyyyyyyyyyyyyyy c@s$@ wa ]@(  ^$@(  y yg& yyyyyyyyyyyyyyyy c@s wa ]@(  ^(  y yh& yyyyyyyyyyyyyyyy c@s. wa ]@(  ^.(  y yi& yyyyyyyyyyyyyyyy c@s? wa ]@(  ^?( y yj& yyyyyyyyyyyyyyyyc @s? wa] @(^?(y yk&yyyyyyyyyyyyyyyyc"@s wa]"@(^(y yl&yyyyyyyyyyyyyyyy0yyyyyyyyyyyyyyyyyyyyy nq6d@@  da $b er6e  da $bsl er6e@@  da $b er6 e@  da $b  er6 e@  d a $ b  er6 e$@  d a $ b er6e  d a $ b er6e.  d a $ b er6e?  d a $ b er6e?  da $b er6f da $b ar s g gw. * >!- w.  (    bxh xpp?i]4@xhh qv%*hxuyt  (<astisim drive (sdl) - sl - signal light display a traffic signal light. this option does not display an intersection, that must be done with the i event. when the signal light is red and a driver drives past the signal light, a ticket will be issued to the driver and the siren sound effect will be played (if active). the current status of the lights can be output to the stisim drive data file using the bsav event and therefore the driver s reactions to the signal light can be measured. additionally, data is included in the stisim drive data file that tells you how many of the signal lights that the driver stopped at. a stop is defined as a signal light where the driver came to a complete stop (forward speed = 0) and the light changed from red to green before the driver went through. the lateral position of the stop lights is based on the sign post distance parameter defined in the configuration s initialize tab dialog box. examples: 1000, sl, 1000, 5, 3, 10, 0, -15, 1, 1, 0 1000, sl, -1200, 5, 3, 10, 0, -15, 1, 1, 1 2200, i, 0, 0, 1 <((<   byh xpp?si]4@yh h &b,j- l<mbw: distance (in feet) driver's vehicle has travelled when the event begins.<al  bpyh xpp?si/]4@pyhh y;xwjs3 <i bw: the longitudinal distance, in feet, that the signal is away from the driver when the signal initially appears. this distance refers to the light post that is in the driver s direction and all other light posts are drawn relative to this initial post based on the roadway geometry. if this parameter is specified as a negative number, then the program will automatically figure out (to the best of its knowledge based on the current roadway dimensions and the location of the center of the intersection) where the signal lights will be placed. otherwise, it will act as specified. this option was added because the roadway can transition from a set number of lanes to another set number of lanes and if you are trying to use a pde that has signal lights in it and the roadway is a different size, you may have trouble. the longitudinal distance is still the same, it just has a minus sign (-) in front of it. if you are using this option, you must make sure that the signal light event lines up with the intersection event, otherwise the lights will be misaligned. for example if you have an intersection that is 1200 feet away, you want the signal light event to be -1200 feet away. <  byh xpp?si f-]4@yhh <&| mϧ y<zbw: the amount of time, in seconds, that the driver is away from a green traffic light signal when it changes to yellow. <.y  bzh xpp?si|]4@zh@h ] ax3` f<gbw: the length of time, in seconds, that the yellow light remains on. <<f  bpzh xpp?s i ]4@pzhh odl~'k c<dbw: the length of time, in seconds, that the red light remains on. <9c  bzh xpp?s i>]4@zhh ,:"da4w x<ybw: initial light setting: 0. green light 1. yellow light 2. red light <x  b[h xpp?s i/-]4@[h`h ]4 @\hh n` kŭ . ]<bw: option for specifying whether the light will appear in front of or behind the intersection. in general in the united states, the signal light posts are behind the intersection, however this is not always the case and in european and other countries, having signal lights in front of the intersection is more prevalent. set parameter 9 to one of the following: 0. signal light post is located behind the intersection 1. signal light post is located in front of the intersection remember when setting this option that the reference distance is for the light post in the driver s direction. < ]  bp\h xpp?i]4 @p\hh umfck ͳ <comment & command line: highlight the blue cells, then copy (ctl-c) and paste (ctl-v) into your sdl file. if you want the command without the comment, copy only the last line (with a box around it).<rive michel bdard  michel bdard  michel bdard  michel bdard   michel bdard   michel bdard   michel bdard   michel bdard  michel bdard  michel bdard  michel bdard  michel bdard >@heje 7yk c:\stisim\help\sdleventsl.htmyk ../../appdata/local/microsoft/windows/stisim/help/sdleventsl.htmyx;h,]ą'cryk back to commands'command index'!b17yk c:\stisim\help\sdleventsl.htmyk f../../../../stisim/help/sdleventsl.htmyx;h,]ą'c* \ distance from start of course(distance measured in feet)et parameter 1the longitudinal distance, in feet, that the signal is away from the driver when the signal initially appears. see comment to left for more details.s. parameter 2warninguthe amount of time, in seconds, that the driver is away from a green traffic light signal when it changes to yellow. uyou have entered a number of lanes outside the range 1-6. please verify that the number you have entered is correct.ga parameter 3warningbthe length of time, in seconds, that the yellow light remains on. 4please check that the number you entered is correct. hnt  parameter 4warning!?the length of time, in seconds, that the red light remains on. 9please check that the number you entered is within range. <  5. initial light settingerror!- 0. green light 1. yellow light 2. red light valid values: 0, 1, 2 tmb  parameter 6|distance (in ft) from the traffic signal location to the "true" limit line. see comment in cell to the left for more info.   7. signal light typeerror! 1. on a post at the four corners of the intersection 2. overhanging the roadway 15 feet at the four corners 3. overhanging the roadway 25 feet at the four corners valid values: 1, 2, 3 n y  8. traffic light sequenceerror!> 1. usa: green, amber, red, green 2. european: g, a, r, r/a, gvalid values: 1, 2t ou 9. sl locationerror!> 0. behind the intersection 1. in front of the intersection valid values: 0, 1es 2 comment & command linehighlight the blue cells, then copy (ctl-c) and paste (ctl-v) into your sdl file. if you want the command without the comment, copy only the last line (with a box around it).s:1, sheet45ggdggh'h    dmbp?_*+%&?'?(?)?"??&u} u} } } } } } } } } } } } } } } } } } } } } } } } } } } } } } !!} ""} ##} $$} %%} &&} ''} ((} ))} **} ++} ,,} --} ..} //} 00} 11} 22} 33} 44} 55      nx om nz n n] o n n`~ s@u wa:x`g $ comment for d@ -- d@bp*'comment for sobj -- add a static object$yyyyyyyyyyyyyyy zb zc wa xd xex \fyyyyyyyyyyyyc?s@@ wa]? d^@@ dy ypyyyyyyyyyyyyc@s. wa]@( l^.( *  la ,by yqyyyyyyyyyyyy c@s wa ]@(  ^(  y yr yyyyyyyyyyyy c@sf@ wa ]@(  ^f@(  y ys yyyyyyyyyyyy c@s wa ]@(  ^(  y yt yyyyyyyyyyyy c@s wa ]@(  ^(  y yu yyyyyyyyyyyy~ c@ v wa ]@(  ^h("c:\stisim\data\signs\rcurve.3ds y yw yyyyyyyyyyyy(yyyyyyyyyyyyyyyyy nq6d@  da $b er6e$e  da $bsobj er6e@@  da $b er6 e.  da $b  er6 e  d a $ b  er6 ef@  d a $ b er6e  d a $ b er6e  d a $ b er6fh d a $ b"c:\stisim\data\signs\rcurve.3ds ar s g gw* h* 6. w0 \si (    b^h xpp?i!x]4@^h`h nh|4c5;  8<stisim drive (sdl) - road - road parameters the road event displays the simulation roadway allowing the experimenter to specify a variety of different roadway attributes. the default roadway (if no road event is specified) consists of a single lane of traffic in each direction, a dashed line separating the 2 lanes, and no edge       !"#$%&'()*+,-./0123456789:;<=>?@abcdefghijklmnopqrstuvwxyz[\]^_`abcdefghijklmnopqrstuvwxyz{|}~lines. the lanes are 12 feet wide and the center stripes are 10 feet long and .3334 feet wide with a 10 foot spacing between the lines. it is recommended that if you will be using the road event, it should appear as the first line in your events file, thus starting the simulation with the roadway you desire. you can then change the roadway later on in your scenario by activating another road event. with stisim drive, you can specify some additional roadway parameters such as shoulder width, foreslope, and roadway cross-slope. these along with the vc (vertical curvature) event allow you to generate three dimensional roadways. these parameters are numbers 11 through 21 and are optional. if you do not specify parameters 11 through 21 they will be ignored. additionally, parameters 22-31 allow you to change the look of the road (either colors or textures) as a function of distance down the road. one other caveat of the roadway that you should know about deals with the roadway center line. the roadway that you display can have traffic flowing in both directions separated by some roadway striping (total # of lanes does not equal # of right hand lanes), or you can have roadways with traffic heading in only 1 direction (total # of lanes equals # of right hand lanes). add to this that the number of lanes on the left and right do not have to be equal, and there are numerous roadway possibilities. because of all these possibilities, the lateral position of most events is defined with respect to the roadway s dividing line. the roadway dividing line is defined as the lateral position on the road where the right hand lanes and left hand lanes meet. for roadways with traffic in both directions, the roadway dividing line is the center stripe. for roadways where the traffic is only heading forward, the roadway dividing line is defined as the left edge of the roadway. note: some important facts to remember when designing your roads: always include some cross slope in the roadway lanes, shoulders and foreslopes. this will make the roadway display better. if you do not include some cross slope, the graphics engine will sometimes have trouble distinguishing between the ground and the roadway elements and this can cause the roadway display to breakup and look funny. changing roadway attributes too close together is not a good idea. since the roadway is essentially generated on the fly, the program sometimes has trouble distinguishing between roadway attributes when they are changed too quickly. there is no magical distance that should be used, you will have to use visual verification. example: 0, road, 12, 2, 1, 3, .5, 10, 10, .333, .333, 0, -1, -1, 0, 6, 0, 6, -5, 10, -5, 10, 0<8,( 5    b^h xpp?si]4@^hh 9eai-4 l<mbw: distance (in feet) driver's vehicle has travelled when the event begins.<al  b(_h xpp?si m ]4@(_h`h  eee/=vdp n<obw: the longitudinal distance, in feet, that the static object is away from the driver when it first appears. <n  b_h xpp?si f-]4@_hh 0jpkyp& l<bw: lateral position, in feet, from the roadway s dividing line to bottom left corner of the static object. <l  b_h xpp?si|]4@_h h , $ woo5 o<pbw: height, in feet, from the ground to the origin of the static object model. <no  b(m xpp?s i]4@(mh q:3/3m~~0 <bw: rotation angle, in degrees, of the static object about its vertical axis. this allows the static object to be rotated in the display, so it can be positioned correctly. <  bm xpp?s i>]4@mh o(?w <bw: rotation angle, in degrees, of the static object about its pitch axis. this allows the static object to be rotated in the display, so it can be positioned correctly. <  bm xpp?s i ]4@m@h mqйsncwe <bw: rotation angle, in degrees, of the static object about its roll axis. this allows the static object to be rotated in the display, so it can be positioned correctly. <  b(m xpp?s i]4 @(mh qs d[t p<qbw: file name of the model file defining the static object. this is the complete file name, including the path. <p  bm xpp?i]4 @mh 2|mb <comment & command line: highlight the blue cells, then copy (ctl-c) and paste (ctl-v) into your sdl file. if you want the command without the comment, copy only the last line (with a box around it).<rive michel bdard  michel bdard  michel bdard  michel bdard   michel bdard   michel bdard   michel bdard   michel bdard  michel bdard  michel bdard >@heje 7yk  c:\stisim\help\sdleventsobj.htmyk ../../appdata/local/microsoft/windows/stisim/help/sdleventsobj.htmyx;h,]ą'cryk back to commands'command index'!b18yk  c:\stisim\help\sdleventsobj.htmyk j../../../../stisim/help/sdleventsobj.htmyx;h,]ą'c\ distance from start of course(distance measured in feet)et parameter 1jthe longitudinal distance, in feet, that the static object is away from the driver when it first appears. ./y parameter 2warninghlateral position, in feet, from the roadway s dividing line to bottom left corner of the static object. uyou have entered a number of lanes outside the range 1-6. please verify that the number you have entered is correct.ut parameter 3warningkheight, in feet, from the ground to the origin of the static object model. 4please check that the number you entered is correct.tm  parameter 4error!rotation angle, in degrees, of the static object about its vertical axis. this allows the static object to be rotated in the display, so it can be positioned correctly. correct range: 0-360 degreesth  parameter 5error!rotation angle, in degrees, of the static object about its pitch axis. this allows the static object to be rotated in the display, so it can be positioned correctly. valid range: 0-360 degreeseeh  parameter 6errorrotation angle, in degrees, of the static object about its roll axis. this allows the static object to be rotated in the display, so it can be positioned correctly. valid range: 0-360 degreesh  comment & command linehighlight the blue cells, then copy (ctl-c) and paste (ctl-v) into your sdl file. if you want the command without the comment, copy only the last line (with a box around it).grs sheet46ggdggh'h    i   dmbp?_*+%&?'?(?)?"??&u} u} } } } i} } } } } } } } } } } } } } } } } } } } } } } } } } } } } !!} ""} ##} $$} %%} &&} ''} ((} ))} **} ++} ,,} --} ..} //} 00} 11} 22} 33} 44  nx ox nz y n] zn ar [ \o gwt0  (    bm xpp?i]!x]4@m h iu2se _ <stisim drive (sdl) - sout  serial data output this event allows for a select set of program variables to be output using a computer s rs-232 serial communications port. most computer systems come with at least 1 accessible rs-232 serial communication port that can be used for communication between 2 computer systems. with stisim drive the communication is only one direction, from stisim drive to an external device, but it does provide a relatively straightforward method of accessing a select group of stisim drive variables. using the sout event is a multiple step process: 1. create a program on the other machine that will accept the data stream 2. set the stisim drive communication parameters 3. include the sout event in your scenarios the first step is the most difficult and requires the most amount of work from the user. basically, on an external piece of equipment a program must be written that will accept the serial data stream and decipher it into the raw data from the simulator. this will require programming expertise from the user and will not be discussed in detail here. the format of the data stream is relatively simple with a 5 byte header and then the selected data. each variable that is selected for output is passed as a 4 byte single precision (float for c programmers) value. the format is: 255 (byte) 255 (byte) 255 (byte) 255 (byte) number of variables in the data stream (byte) variable 1 (4 bytes) variable 1 (4 bytes) " " " variable n (4 bytes) the programmer can select any serial communication protocols that are desired, however the stisim drive computer system must also match these protocols in order for the communication to work. to set the serial communication protocols from within stisim drive, select the serial data output option from the configuration s other tab dialog box and enter values for the communications port to be used, the baud rate, parity, data bits and stop bits. these values must match exactly those on the external piece of equipment otherwise the data will be wrong. click on help file hyperlink (cell b3) for more info.<  0&*:_ michel bdard_>@heje 7 yk c:\stisim\help\sdleventa.htmyk ../../appdata/local/microsoft/windows/stisim/help/sdleventa.htmyx;h,]ą'cryk back to commands'command index'!b19yk  c:\stisim\help\sdleventsout.htmyk j../../../../stisim/help/sdleventsout.htmyx;h,]ą'c sheet47ggd  9   dmbp?_*+%&?'?(?)?mlexmark e210o odxxletterpriv''''222222222p dlcourier newh"dx??&u} u} } } } } } } } } } } } } } }  } } } } } } } } } } } } } } } !!} ""} ##} $$} %%} &&} ''} ((} ))} **} ++} ,,} --} ..} //} 00} 11} 22} 33} 44} 55     nx o] nz ^ n] _ n n`~ s@@u wa:x@h $ comment for d@ -- d@bp,)comment for spcw -- speed control warningyyyyyyy zb zc wa xd xex \fyyyy c?s@ wa]? d^@ dy y`yyyy ~ c@s *t@ wa]@ d6^ *t@  da $by yagg  c@s$@ wa ]@ d 6 ^$@  d a $ b y yb yyyy   yyyyyyyyy nq6 d@@  da $b er6 exe  da $bspcw er6 e@ da $b er6 e *t@ da $b er6 f$@  d a $ b ar s g gw l  am7a` v@ an%[ܫ*t@ d&:û)? o  ap *t@ aq% v@ d(yu?.* p&s*a*0 1 x(    bm xpp?i]4@mh n)ilcw o (<stisim drive (sdl) - spcw - speed control warning this event allows you to give the driver a speed warning when they are training to use the system. the idea behind this event is that when a driver lets their speed drop below a certain level, the system plays a recording that reminds them to keep the speed at a certain level, thus providing training on how to maintain a desired speed. this event plays a windows wav file named speedwrn.wav found in the stisim drive sound folder (generally c\stisim\sound). the default recording that is supplied with the installation is for a speed of 50 miles per hour. however, if you would like to play a different warning, then you will need to record a new message named speedwrn.wav and save it in the wav format. this file must then be placed in the stisim drive sound folder. example: 1000, spcw, 2, 80.667, 10 one unfortunate consequence of using a simulator is that it does not act like the vehicle the driver normally drives and therefore there is some learning that the driver must go through in order to become familiar with the simulator. this event informs the driver that they are driving below the speed specified. if the driver is unable to maintain the speed (within a predetermined tolerance) stisim drive will play the warning message. in the example shown, the on distance is set to 1000 feet, therefore, the driver's vehicle will have proceeded 1000 feet down the road before this event takes place. the first parameter tells stisim drive that the speed warning will be given every time the driver s velocity drops below 80.667 feet/second (55 miles/hour). since the main focus of this event is to provide the driver with some auditory feedback on their speed control, in the example the volume has been set to a maximum value of 10. <(935\  bm xpp?si]4@mh jh{pb l<mbw: distance (in feet) driver's vehicle has travelled when the event begins.<al  bpm xpp?si m]4@pm`h c_/fy/ <bw: speed control option flag. to set the speed control option, set parameter 1 to one of the following: 0. turns the event off 1. gives the warning message only once 2. continually gives the warning while the driver is under the specified speed <  bm xpp?si f-]4@mh + @ <bw: the speed, in feet/second, that will trigger the warning message. when the driver's speed drops below this value the program will play the warning message. <   bm xpp?si|]4@m h ihjl : r<sbw: volume control when playing back the warning file. values range from 0 to 10. <r  bpm xpp? ir]4@pmh guntwf <comment & command line: highlight the blue cells, then copy (ctl-c) and paste (ctl-v) into your sdl file. if you want the command without the comment, copy only the last line (with a box around it).<rive michel bdard  michel bdard  michel bdard  michel bdard   michel bdard   michel bdard >@heje:7yk  c:\stisim\help\sdleventspcw.htmyk ../../appdata/local/microsoft/windows/stisim/help/sdleventspcw.htmyx;h,]ą'cryk back to commands'command index'!b20yk  c:\stisim\help\sdleventspcw.htmyk j../../../../stisim/help/sdleventspcw.htmyx;h,]ą'c\ distance from start of course(distance measured in feet)et 1. speed control flagerror! 0. turns the event off 1. gives the warning message only once 2. continous warning while the driver is under the specified speed valid values: 0, 1, 2m 2. trigger speedthe speed, in feet/second, that will trigger the warning message. when the driver's speed drops below this value the program will play the warning message. j 3. volume controlerror!valid range: 0 to 10 valid range: 0 to 10insa  ,warning!warning!cdo not enter data here--there is a formula in this cell. enter a speed in km/hr in the green cell.jthere is a formula in this cell. please enter data in the green cell only. mb,warning!warning!ddo not enter data here--there is a formula in this cell. enter a speed in ft/sec in the green cell.jthere is a formula in this cell. please enter data in the green cell only. mb comment & command linehighlight the blue cells, then copy (ctl-c) and paste (ctl-v) into your sdl file. if you want the command without the comment, copy only the last line (with a box around it).  sheet48ggdggh'h   a m  dmbp?_*+%&?'?(?)?"??&u} u} } } } } } } } } } } } } } } } } } } } } } } } } } } } } } !!} ""} ##} $$} %%} &&} ''} ((} ))} **} ++} ,,} --} ..} //} 00} 11} 22} 33} 44} 55      nx oc nz d n] e n n`~ su wa:xh $ comment for d@ -- d@bp,)comment for stcw -- steer control warningyyyyyyyyyyy zb zc wa xd xex \fyyyyyyyyc?s>@ wa]? d^>@ dy yfyyyyyyyyc@s@ wa]@ d6^@  da $by ygyyyyyyyy c@s? wa ]@ d 6 ^?  d a $ b y yh yyyyyyyy c@s>@ wa ]@ d 6 ^>@  d a $ b y yi yyyyyyyy c@s$@ wa ]@ d 6 ^$@  d a $ b y yj yyyyyyyy  yyyyyyyyyyyyy nq6 d  da $b er6 ee  da $bstcw er6 e>@ da $b er6 e@ da $b er6 e? d a $ b er6 e>@  d a $ b er6 f$@ d a $ b ar s g gw&@* x.1 w 2  (    bm xpp?i]4@mh ƥ4nqn\w  (<stisim drive (sdl) - stcw - steering control warning this event allows you to test the driver to see if they can adequately control the vehicle's steering. the program checks the drivers rms steering rate and lane position over a specified time interval. if the driver is able to control the steering, the program continues, if not, the program will play a steering warning message. the steering warning message is named steerwrn.wav and is located in the stisim drive sound folder (generally c:\stisim\sound). the idea behind this event is that the driver must be able to control the vehicle, or all of the data you collect could be worthless. this event allows you to see if the driver can control the vehicle's steering within some minimally acceptable band. the driver must "pass" both the steering and lane positioning criteria before the program will continue. example: 0, stcw, 30, 5, 1, 30, 10 one unfortunate consequence of using a simulator is that it does not handle and respond like the driver s normal vehicle and therefore there is some learning that the driver must go through in order to became familiar with the simulator. this is particularly important when it comes to steering the vehicle. if the driver can not control the lane position and heading of the vehicle, then they may not be able to perform the simulation task that you have designed. unlike the spcw event, this test actually computes a pass/fail to determine if the driver can control the vehicle. the parameters allow you to set the criteria for passing as well as the number of tries the driver gets before they will automatically pass. during any testing interval, if the driver is unable to sufficiently control the vehicle with steering, stisim drive will play the warning message. in the above example the on distance is set to 0 so the event will take place at the start of the run. the first 2 parameters tell stisim drive that there will be 5, 30 second testing intervals (30, 5). the criteria for passing is set to 1 foot for the lane deviation and 30 degrees/second for the steering wheel rate (1, 30). if the driver fails during the first interval, the recording will be played and a new interval will begin. if the driver passes, then the event ends and the driver should be able to sufficiently steer the vehicle during the simulation run. since the main focus of this event is to provide the driver with some auditory feedback on their steering control, in the example the volume has been set to a maximum value of 10. <(f6e5m\   bpm xpp?si]4@pm`h (wy&g$l l<mbw: distance (in feet) driver's vehicle has travelled when the event begins.<al  bm xpp?si m ]4@mh vik(i*g@c v<wbw: the time, in seconds, of the interval when the driver's steering will be checked. <v  bm xpp?si f-]4@m h r)gno_Ȕr l<bw: lateral position, in feet, from the roadway s dividing line to bottom left corner of the static object. <l  bpm xpp?si|]4@pmh щsg2kړ <bw: the passing rms value for the driver's lane deviation, in feet, during the testing interval. if the driver's score is less than this value and the criteria in parameter 4 is met, they will "pass" and the program will proceed as normal. <p  bm xpp?s i]4@mh \x:o[ـېh <bw: the passing rms value for the driver's steering rate response, in degrees/second, during the testing interval. if the driver's score is less than this value, and the criteria in parameter 3 is met, they will "pass" and the program will proceed as normal. <  bm xpp?s i>]4@m@h h@s0xo.-_t r<sbw: volume control when playing back the warning file. values range from 0 to 10. <r  bpm xpp? i]4@pmh  #tsgnβ <comment & command line: highlight the blue cells, then copy (ctl-c) and paste (ctl-v) into your sdl file. if you want the command without the comment, copy only the last line (with a box around it).<rive michel bdard  michel bdard  michel bdard  michel bdard   michel bdard   michel bdard   michel bdard   michel bdard >@heje 7yk  c:\stisim\help\sdleventstcw.htmyk ../../appdata/local/microsoft/windows/stisim/help/sdleventstcw.htmyx;h,]ą'cryk back to commands'command index'!b21yk  c:\stisim\help\sdleventstcw.htmyk j../../../../stisim/help/sdleventstcw.htmyx;h,]ą'c\ distance from start of course(distance measured in feet)et parameter 1sthe time, in seconds, of the interval when the driver's steering will be checked.   parameter 2athe number of times, the driver can "fail" the steering criteria before they automatically pass. . parameter 3the passing rms value for the driver's lane deviation, in feet, during the testing interval. if the driver's score is less than this value and the criteria in parameter 4 is met, they will "pass" and the program will proceed as normal. 'c h 4. the passing rms valueerror!for the driver's steering rate response (degrees/sec) during the testing interval. if the driver's score is less than this value, and the criteria in parameter 3 is met, they will "pass" and the program will proceed as normal. correct range: 0-360 degreesn h s 5 volume control for warningerror! valid range: 0 to 10 valid range: 0-10ecin   comment & command linehighlight the blue cells, then copy (ctl-c) and paste (ctl-v) into your sdl file. if you want the command without the comment, copy only the last line (with a box around it). wl   sheet49ggdggh'h   }y ;  dmbp?_*+%&?'?(?)?"??&u} u} } } } } } } } } } } } } } } } } } } } } } } } } } } } } } !!} ""} ##} $$} %%} &&} ''} ((} ))} **} ++} ,,} --} ..} //} 00} 11} 22} 33} 44} 55                 nx ok nz l n] mrrrrn n`~ su wa:xh $ comment for d@ -- d@bp.+comment for tdo -- triggered digital outputyyyyyyy zb zc wa xd xex \fyyyy c?s@ wa]? d^@ dy ynyyyy c@s @ wa]@ d6^ @  da $by yoyyyy  c@s? wa ]@ d 6 ^?  d a $ b y yp yyyy   yyyyyyyyy nq6 d  da $b er6 e  da $btdo er6 e@ da $b er6 e @ da $b er6 f? d a $ b ar s g gw"v2 p&r2 w 3  x(    bm xpp?i]4@m h f>k.a/@hm&  (<stisim drive (sdl) - stcw - steering control warning this event allows you to test the driver to see if they can adequately control the vehicle's steering. the program checks the drivers rms steering rate and lane position over a specified time interval. if the driver is able to control the steering, the program continues, if not, the program will play a steering warning message. the steering warning message is named steerwrn.wav and is located in the stisim drive sound folder (generally c:\stisim\sound). the idea behind this event is that the driver must be able to control the vehicle, or all of the data you collect could be worthless. this event allows you to see if the driver can control the vehicle's steering within some minimally acceptable band. the driver must "pass" both the steering and lane positioning criteria before the program will continue. example: 0, stcw, 30, 5, 1, 30, 10 one unfortunate consequence of using a simulator is that it does not handle and respond like the driver s normal vehicle and therefore there is some learning that the driver must go through in order to became familiar with the simulator. this is particularly important when it comes to steering the vehicle. if the driver can not control the lane position and heading of the vehicle, then they may not be able to perform the simulation task that you have designed. unlike the spcw event, this test actually computes a pass/fail to determine if the driver can control the vehicle. the parameters allow you to set the criteria for passing as well as the number of tries the driver gets before they will automatically pass. during any testing interval, if the driver is unable to sufficiently control the vehicle with steering, stisim drive will play the warning message. in the above example the on distance is set to 0 so the event will take place at the start of the run. the first 2 parameters tell stisim drive that there will be 5, 30 second testing intervals (30, 5). the criteria for passing is set to 1 foot for the lane deviation and 30 degrees/second for the steering wheel rate (1, 30). if the driver fails during the first interval, the recording will be played and a new interval will begin. if the driver passes, then the event ends and the driver should be able to sufficiently steer the vehicle during the simulation run. since the main focus of this event is to provide the driver with some auditory feedback on their steering control, in the example the volume has been set to a maximum value of 10. <(f6e5m\   b(m xpp?si]4@(mh  vj !@kj<@ l<mbw: distance (in feet) driver's vehicle has travelled when the event begins.<al  bm xpp?si]4@mh f;(s^ <bw: control byte that tells stisim drive what event(s) will trigger a digital output. the control byte must be constructed based on the individual events that can trigger an output. this allows you to group triggered events together and have them all sent across a single pin, or you can specify them individually and have them each sent across their own pin. to set the control byte so that the simulation will trigger on the specified events, the bit position that corresponds to the trigger event, must be set to 1. if not, the event will not trigger an output pulse. in the table below, the decimal value for each bit position is listed next to the event trigger. you specify multiple events by adding these values together and using this value as parameter 1. the control byte has the following format: event trigger control byte position: (decimal byte value) ------------------------- ---------------------------------- 1 collisions with objects (1) 2 off road accidents (2) 3 hit pedestrian (4) 4 speeding ticket (8) 5 traffic light ticket (16) 6 stop sign ticket (32) 7 not used 8 not used to turn off any event trigger, simply set its corresponding bit to 0, therefore if parameter 1 is set to 0, all triggers will be deactivated. <  bm xpp?si f]4@m@h "%mb2 f<gbw: sets the bit on register b that the triggered output pulse will be transmitted with. the allowable values for this parameter are as follows: value: register b bit affected: ----- ----------------------- 1 0 2 1 3 2 4 3 5 4 6 5 7 6 8 7 <f  b(m xpp?si|]4@(mh ej#m(qjj  < bw: duration of the minimum output pulse that will be sent over the digital i/o pin. the length of the pulse will be a function of the simulation frame time and may not be exactly what is specified with this parameter, however it will always be at least this long. <   bm xpp? i]4@mh l}pmef+ <comment & command line: highlight the blue cells, then copy (ctl-c) and paste (ctl-v) into your sdl file. if you want the command without the comment, copy only the last line (with a box around it).<rive michel bdard  michel bdard  michel bdard  michel bdard   michel bdard   michel bdard >@heje 7ryk back to commands'command index'!b22yk c:\stisim\help\sdleventtdo.htmyk ../../appdata/local/microsoft/windows/stisim/help/sdleventtdo.htmyx;h,]ą'cyk c:\stisim\help\sdleventtdo.htmyk h../../../../stisim/help/sdleventtdo.htmyx;h,]ą'c\ distance from start of course(distance measured in feet)et 1. control byte control byte that tells stisim drive what event(s) will trigger a digital output. see comment in cell to the left for details. sl parameter 2{sets the bit on register b that the triggered output pulse will be transmitted with. see comment to the left for details. il ( 3. duration of minimum outputpulse that will be sent over the digital i/o pin. the length of the pulse will be a function of the simulation frame time and may not be exactly what is specified with this parameter, however it will always be at least this long.  6  comment & command linehighlight the blue cells, then copy (ctl-c) and paste (ctl-v) into your sdl file. if you want the command without the comment, copy only the last line (with a box around it).amer  sheet50ggdggh'h   ˰ b  dmbp?_*+%&?'?(?)?"??&u} u} } } } } } } } } } } } } } } } } } } } } } } } } } } } } } !!} ""} ##} $$} %%} &&} ''} ((} ))} **} ++} ,,} --} ..} //} 00} 11} 22} 33} 44} 55      nx oq nz r n] srrrrn n`~ s@@u wa:x@m $ comment for d@ -- d@bp%"comment for tree -- roadside trees yyyyyyyyyyyyy zb zc wa xd xex \fyyyyyyyyyyc?s.@ wa]? d^.@ dy ytyyyyyyyyyyc@s wa]@ d6^  da $by yuyyyyyyyyyy~ c@ sv wa ]@ d 6 ^e  d a $ b*1~18 y yw yyyyyyyyyy c@s4@ wa ]@ d 6 ^4@  d a $ b y yx yyyyyyyyyy c@si@ wa ]@ d 6 ^i@  d a $ b y yy yyyyyyyyyy c@s@ wa ]@ d 6 ^@  d a $ b y yz yyyyyyyyyy $ yyyyyyyyyyyyyyy nq6d@@  da $b er6ee  da $btree er6e.@  da $b er6 e  da $b  er6 ee  d a $ b*1~18  er6 e4@  d a $ b er6ei@  d a $ b er6f@ d a $ b ar s g gw g{ |,o |2 |2w3 4 4  (    bm xpp?itz]4@m`0n Ԥucrj l8<mstisim drive (sdl) - tree - roadside trees display trees along the sides of the roadway. this event allows you to specify the tree density, spacing and type. you use this event to turn the displaying of trees on and off for particular sections of your simulation. this allows you to transition from a rural setting into a town by initially having the trees on and then turning them off as the driver approaches the town. if you do not use the tree event, then no trees will be displayed on the sides of the roadway. although you now have some control over how trees are displayed in the roadway scene, you still do not have total control. for most of the tree event parameters, you will be specifying a range of values that the parameters can be within, and the simulation will randomly choose the actual values that will be used for each tree. of course, the values that the program chooses will be within the limits specified. see the section on random numbers for some additional insight into using random numbers and how it may affect the displaying of trees. note: for those of you who are previous users of stisim drive, pay close attention to parameter 3 in the table below. this has changed from previous versions and could affect how your scenario will look. example: 1000, tree, 15, 0, *1~18, 20, 200, 2 in the example shown, trees will located only on the right side of the road from 1000 feet on. a maximum of 15 trees will be randomly displayed ahead of the driver at any one time. as the driver goes past trees, other trees will appear out near the edge of the far clipping plane. since parameter 3 is set to randomly select trees between 1 and 18, all types of trees will be displayed. finally, the trees will be laterally located anywhere from 20 to 200 feet away from the roadway centerline, and only appear on the right side of the road (2). <8 , ) 2 l  bm xpp?si]4@m0n vjtaގ=g` l<mbw: distance (in feet) driver's vehicle has travelled when the event begins.<al  b(m xpp?si ']4@(m 1n 0/:^aaj,ypn <bw: maximum number of trees that will be displayed at any one time. since it takes a finite amount of time to display the trees, you will need to decide the maximum amount of trees that your scenario can handle without degrading the simulation performance. in general, a maximum of 50-100 trees gives good results. setting this parameter to 0 will prevent trees from being displayed until a new tree event is processed. the maximum number of trees allowed is 250, and the distribution of the trees is affected by the clipping plane distance set in the configuration s graphics tab dialog box. the program tries to distribute the number of trees over the clipping plane distance, therefore the shorter the clipping plane distance is the tighter the trees will appear. <a  bm xpp?si f-]4@m1n dajr3  \<]bw: no longer used but has been left so that older scenario files will still be compatible. <\  bm xpp?si]4@m1n ȋi%cul <bw: type of tree that will be displayed. there are numerous types of trees that the simulation will display. to choose the tree type set parameter 3 to the number, from the list of trees below, that corresponds to the type of tree you would like to have displayed. you can also have the program automatically select trees for you (from a user supplied list) by using the stisim drive random number selection process. if you set parameter 3 to a range of trees, the software will randomly pick each tree from within the range specified. you cannot have the software randomly pick a type of tree and then have that tree be the only one shown. instead you would have to specify a single value for the desired tree. for backward compatibility, if you set parameter 3 to a value of 0, it will randomly select each tree from all of the available trees. this parameter is only used when the first tree event is encountered. the program will ignore this parameter in all subsequent tree events. unlike previous versions of the software, you cannot change trees in the middle of a run. the tree types that are specified when the first tree event is processed will be the tree types for the entire simulation run. <  b(m xpp?s it]4@(m@2n ̒xoko- s<tbw: minimum lateral distance from the roadway dividing line to the trees, in feet. <xs  bm xpp?s i]4@m2n rtvceokj s<tbw: maximum lateral distance from the roadway dividing line to the tree, in feet. <s  bm xpp?s i ]4@m3n ڛڦg@a. <bw: rotation angle, in degrees, of the static object about its roll axis. this allows the static object to be rotated in the display, so it can be positioned correctly. <  b(pn xpp? i]4 @(pn`3n )kd>p <comment & command line: highlight the blue cells, then copy (ctl-c) and paste (ctl-v) into your sdl file. if you want the command without the comment, copy only the last line (with a box around it).<rive michel bdard  michel bdard  michel bdard  michel bdard   michel bdard   michel bdard   michel bdard   michel bdard  michel bdard >@heje7ryk back to commands'command index'!b23yk  c:\stisim\help\sdleventtree.htmyk j../../../../stisim/help/sdleventtree.htmyx;h,]ą'cyk list of tree typesyk j../../../../stisim/help/sdleventtree.htmyx;h,]ą'c treelistyk random number selectionyk j../../../../stisim/help/randomparams.htmyx;h,]ą'c\ distance from start of course(distance measured in feet)in parameter 1bmaximum number of trees that will be displayed at any one time. see comment to left for details.ts parameter 2warningyno longer used but has been left so that older scenario files will still be compatible. uyou have entered a number of lanes outside the range 1-6. please verify that the number you have entered is correct.li t 3. type of tree }valid range: 1-18. random selection possible. tree types are shown in help file. see comment to the left for more details. 4please check that the number you entered is correct.yoha  parameter 4error!pminimum lateral distance from the roadway dividing line to the trees, in feet. correct range: 0-360 degreese ta  parameter 5error!omaximum lateral distance from the roadway dividing line to the tree, in feet. valid range: 0-360 degreess   6. side of the roaderroratrees will appear on. 0. both sides 1. left only 2. right only valid values: 0, 1, 260ee  comment & command linehighlight the blue cells, then copy (ctl-c) and paste (ctl-v) into your sdl file. if you want the command without the comment, copy only the last line (with a box around it).  sheet51ggdggh'h   )    dmbp?_*+%&?'?(?)?"??&u} u} } } } } } } } } } } } } } } } } } } } } } } } } } } } } } !!} ""} ##} $$} %%} &&} ''} ((} ))} **} ++} ,,} --} ..} //} 00} 11} 22} 33} 44} 55} 66} 77)8888888888 8 8 8 8 8888888888888888888 nx } nz r~ rr n] rrn n`~ sy@u wa:x4n $ comment for d@ -- d@bp2/comment for v -- vehicle ahead in driver's lanelyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyy7 zb zc wa xd xex \ffyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyy7~ c?  wa]? d^ d/30y yfyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyy7c@s@o wa]@(l^@o( * la ,by yfyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyy7~ c@ sm wa ]@(  ^( *0 y yf yyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyy7 c@s? wa ]@(  ^?(  y yf yyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyy7 c@s@ wa ]@(  ^@(  y yf yyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyy7 @s@ wa ]@(  ^@(  y yf yyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyy7~ @  wa ]@(  ^(/12 y yf yyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyy7~  @ s wa] @(^(*30y yfyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyy7"@s@ wa]"@(^@(y yfyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyy7$@b wa]$@(^(y yfyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyy7~ &@ bm wa]&@(^(*0y yfyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyy7~ (@  wa](@(^(/30y yfyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyy7*@@ wa]*@(^@(y yfyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyy7~ ,@b wa],@(^@(y yfyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyy7~ .@b wa].@(^@(y yfyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyy7~ 0@b wa]0@(^@(y yfyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyy7~ 1@b wa]1@(^@(y yfyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyy7~ 2@b wa]2@(^@(y yfyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyy7~ 3@b wa]3@(^@(y yfyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyy7~ 4@b wa]4@(^@(y yfyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyy7~ 5@b wa]5@(^@(y yfyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyy7~ 6@b wa]6@(^@(y yfyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyy7~ 7@b wa]7@(^@(y yfyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyy7~ 8@b wa]8@(^@(y yfyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyy7~ 9@b wa]9@(^@(!y yfyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyy7dl*. % 8!8#8$8%8'8(8 p yyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyy7 !nq6!dy@ ! da $b !er6!e@ ! da $bv !er6!e8 ! da $b/30 !er6! e@o ! da $b ! er6! e  ! d a $ b*0 ! er6! e? ! d a $ b !er6!e@ ! d a $ b !er6!e@ ! d a $ b !er6!e( ! d a $ b/12 !er6!e ! da $b*30 !er6!e@ ! da $b !er6!e ! da $b !er6!e0 ! da $b*0 !er6!e ! da $b/30 !er6!e@ !! da $b ! er6!!e@ !# da $b !"er6!#e @ !% da $b !$er6!%e@ !' da $b !&er6!'e@ !) da $b !(er6!)e@ !+ da $b !*er6!+e@ !- da $b !,er6!-e @ !/ da $b !.er6!/e$@ !1 da $b !0er6!1e(@ !3 da $b !2er6!3e,@ !5 da $b !4er6!5e0@ !7 da $b !6er6!7f4@ da $b #ar #s $g %gw 'g\'rrrrrr (_ (\ x~$4 !5 770(    bqn xpp?si]4@qn4n 3ΒtkNj)ݼ" l<mbw: distance (in feet) driver's vehicle has travelled when the event begins.<al  bqn xpp?si]4@qn@5n & >isj& g0<parameter 1: the speed, in feet/second, of the new vehicle. you may also reference the vehicle s speed with respect to the driver s speed by using a * or / in front of this parameter. if a * symbol appears as the first character in the parameter specification, the program will take the value of parameter 1 and add it to the current speed of the driver s vehicle and use this as the new vehicle speed. this speed will remain constant, based on the driver s speed when the event begins. if a / symbol appears as the first character in the parameter specification, the program will take the value of parameter 1 and add it to the current speed of the driver s vehicle at each time step. this means that the new vehicle speed will be changing as the driver s speed changes. therefore, if the driver s vehicle slows down, the new vehicle will slow down accordingly. note: in excel, pressing "/" will take you to the file menu at the top of the screen. to have a forward slash (/) appear in a cell, you must precede it with a single quote. e.g., to enter /30 for parameter 1, enter this: '/30<0j a$fh%g  b(rn xpp?si ]4@(rn5n hs]ed> ~<parameter 2: the longitudinal distance, in feet, that the vehicle is away from the driver when the vehicle initially appears. <j ~  brn xpp?si|-]4@rn6n |xb>mvq <cparameter 3: the lateral lane position, in feet, of the center of the vehicle with respect to the roadway s dividing line. you may also reference the vehicle s position with respect to the driver s position by using a * or / in front of this parameter. if a * symbol appears as the first character in the parameter, the program will take the value of parameter 3 and add it to the current lateral position of the driver s vehicle and use this as the vehicle s lateral position. if a / symbol appears as the first character in the parameter, the program will take the value of parameter 3 and add it to the current lateral position of the driver s vehicle at each time step. this new value will be used as the vehicle s lateral position. this means that the new vehicle s lateral position will be changing as a function of the driver s lateral position. therefore, if the driver goes to the right, the new vehicle will also move to the right. <j   brn xpp?s i -]4@rn`6n tdluuy #<$parameter 4: if the new vehicle will be decelerating (set using parameters 6-25), then this tells the simulation whether or not to use the brake lights on the new vehicle. 0. brake lights will remain the same color 1. brake lights become brighter when the vehicle begins braking. <j .#  b(sn xpp?s i>x]4@(sn6n n[ci+ + <parameter 5: vehicle model type number {vehicles}. you may assign the vehicle a random number by using stisim drive s random parameter selection capabilities. in addition to the vehicle model type number you can also append the letters r or l to the model number in order to change the vehicle s orientation. this allows you to rotate the vehicle 90 degrees to the left (l, e.g. 14l) or right (r, e.g. 27r) so that you can do things like vehicles backing up or pulling out of driveways and such. to accomplish this, you first set the orientation and then use parameters6-25 to specify how the vehicle will respond. examples of this behavior can be found in the construction_2.evt and suburban_5.evt example files (c:\stisim\projects). <j    bsn xpp?s i i]4@sn 7n  l1 h <{ parameters 6, 10, 14, 18, 22: closure time, in seconds, between the driver s vehicle and the vehicle you are controlling, this can be both positive and negative depending on the action that is desired. positive meaning that the two vehicles are getting closer to one another, negative meaning that the vehicles are getting farther apart. specifying the closure time so that the event acts as you intended is not an easy task. since the closure times are irrespective of the locations of the 2 vehicles, you can add an additional attribute to the closure time parameter that tells stisim drive to only activate the closure time if the event vehicle is in front of or behind the driver s vehicle. if the closure time parameter ends with an f, the action will only be activated when the new vehicle is in front of the driver s vehicle and the closure time criteria is met (e.g. 10f would mean only in front of the driver s vehicle and within 10 seconds and closing). placing a b at the end of the closure time parameter, instructs stisim drive to only take action when the new vehicle is behind the driver s vehicle. if neither f or b appears, stisim drive will activate when ever the closure time criteria is met. <  bsn xpp?s i]4@sn7n 3gk]dg=xg+ (<parameters 7, 11, 15, 19, 23: lateral distance that the new vehicle will move, with respect to its current lateral position, in feet. the vehicle s current lateral position is always with respect to the roadway s dividing line, with positive to the right. like parameter 3 above, you may use the * and / symbols at the beginning of the parameter specification in order to reference the lateral position of the vehicle with that of the driver s vehicle. <(    bptn xpp?s i]4 @ptn7n rt֊n~) <parameters 8, 12, 16, 20, 24: new speed, in feet/second, that the vehicle will be traveling at the end of the transition period. since you will be specifying a transition time, the program will perform a linear transition from the vehicle s speed when the transition begins until it reaches the specified speed at the end of the transition period. if you specify a speed that is slower than the current vehicle speed, then the vehicle will decelerate during the transition period. as with parameter 1 above, you may use the * and / symbols at the beginning of the parameter specification to reference the new speed to the driver s vehicle. <m   btn xpp?si><]4 @tn@8n |<Ήe+r g(<hparameters: 9, 13, 17, 21, 25: the amount of time, in seconds, that the transition will occur over. <(jd eg  b(un xpp?si  i]4 @(un8n aغmifr <{ parameters 6, 10, 14, 18, 22: closure time, in seconds, between the driver s vehicle and the vehicle you are controlling, this can be both positive and negative depending on the action that is desired. positive meaning that the two vehicles are getting closer to one another, negative meaning that the vehicles are getting farther apart. specifying the closure time so that the event acts as you intended is not an easy task. since the closure times are irrespective of the locations of the 2 vehicles, you can add an additional attribute to the closure time parameter that tells stisim drive to only activate the closure time if the event vehicle is in front of or behind the driver s vehicle. if the closure time parameter ends with an f, the action will only be activated when the new vehicle is in front of the driver s vehicle and the closure time criteria is met (e.g. 10f would mean only in front of the driver s vehicle and within 10 seconds and closing). placing a b at the end of the closure time parameter, instructs stisim drive to only take action when the new vehicle is behind the driver s vehicle. if neither f or b appears, stisim drive will activate when ever the closure time criteria is met. <  bun xpp?si $i]4 @un9n o j+܇' <{ parameters 6, 10, 14, 18, 22: closure time, in seconds, between the driver s vehicle and the vehicle you are controlling, this can be both positive and negative depending on the action that is desired. positive meaning that the two vehicles are getting closer to one another, negative meaning that the vehicles are getting farther apart. specifying the closure time so that the event acts as you intended is not an easy task. since the closure times are irrespective of the locations of the 2 vehicles, you can add an additional attribute to the closure time parameter that tells stisim drive to only activate the closure time if the event vehicle is in front of or behind the driver s vehicle. if the closure time parameter ends with an f, the action will only be activated when the new vehicle is in front of the driver s vehicle and the closure time criteria is met (e.g. 10f would mean only in front of the driver s vehicle and within 10 seconds and closing). placing a b at the end of the closure time parameter, instructs stisim drive to only take action when the new vehicle is behind the driver s vehicle. if neither f or b appears, stisim drive will activate when ever the closure time criteria is met. <  bun xpp?si (i]4 @un`9n u&l t7r?f <{ parameters 6, 10, 14, 18, 22: closure time, in seconds, between the driver s vehicle and the vehicle you are controlling, this can be both positive and negative depending on the action that is desired. positive meaning that the two vehicles are getting closer to one another, negative meaning that the vehicles are getting farther apart. specifying the closure time so that the event acts as you intended is not an easy task. since the closure times are irrespective of the locations of the 2 vehicles, you can add an additional attribute to the closure time parameter that tells stisim drive to only activate the closure time if the event vehicle is in front of or behind the driver s vehicle. if the closure time parameter ends with an f, the action will only be activated when the new vehicle is in front of the driver s vehicle and the closure time criteria is met (e.g. 10f would mean only in front of the driver s vehicle and within 10 seconds and closing). placing a b at the end of the closure time parameter, instructs stisim drive to only take action when the new vehicle is behind the driver s vehicle. if neither f or b appears, stisim drive will activate when ever the closure time criteria is met. <  b(vn xpp?si ,i]4@(vn9n +Ӥ/lg@ <{ parameters 6, 10, 14, 18, 22: closure time, in seconds, between the driver s vehicle and the vehicle you are controlling, this can be both positive and negative depending on the action that is desired. positive meaning that the two vehicles are getting closer to one another, negative meaning that the vehicles are getting farther apart. specifying the closure time so that the event acts as you intended is not an easy task. since the closure times are irrespective of the locations of the 2 vehicles, you can add an additional attribute to the closure time parameter that tells stisim drive to only activate the closure time if the event vehicle is in front of or behind the driver s vehicle. if the closure time parameter ends with an f, the action will only be activated when the new vehicle is in front of the driver s vehicle and the closure time criteria is met (e.g. 10f would mean only in front of the driver s vehicle and within 10 seconds and closing). placing a b at the end of the closure time parameter, instructs stisim drive to only take action when the new vehicle is behind the driver s vehicle. if neither f or b appears, stisim drive will activate when ever the closure time criteria is met. <  bvn xpp?si]4@vn :n mhk[3 (<parameters 7, 11, 15, 19, 23: lateral distance that the new vehicle will move, with respect to its current lateral position, in feet. the vehicle s current lateral position is always with respect to the roadway s dividing line, with positive to the right. like parameter 3 above, you may use the * and / symbols at the beginning of the parameter specification in order to reference the lateral position of the vehicle with that of the driver s vehicle. <(    bwn xpp?si]4@wn:n o}lln̫ (<parameters 7, 11, 15, 19, 23: lateral distance that the new vehicle will move, with respect to its current lateral position, in feet. the vehicle s current lateral position is always with respect to the roadway s dividing line, with positive to the right. like parameter 3 above, you may use the * and / symbols at the beginning of the parameter specification in order to reference the lateral position of the vehicle with that of the driver s vehicle. <(    bwn xpp?si]4@wn:n Ȼajm (<parameters 7, 11, 15, 19, 23: lateral distance that the new vehicle will move, with respect to its current lateral position, in feet. the vehicle s current lateral position is always with respect to the roadway s dividing line, with positive to the right. like parameter 3 above, you may use the * and / symbols at the beginning of the parameter specification in order to reference the lateral position of the vehicle with that of the driver s vehicle. <(    bxn xpp?si#]4@xn@;n =)edb@u  (<parameters 7, 11, 15, 19, 23: lateral distance that the new vehicle will move, with respect to its current lateral position, in feet. the vehicle s current lateral position is always with respect to the roadway s dividing line, with positive to the right. like parameter 3 above, you may use the * and / symbols at the beginning of the parameter specification in order to reference the lateral position of the vehicle with that of the driver s vehicle. <(    bxn xpp?si]4@xn;n $wz5pog <parameters 8, 12, 16, 20, 24: new speed, in feet/second, that the vehicle will be traveling at the end of the transition period. since you will be specifying a transition time, the program will perform a linear transition from the vehicle s speed when the transition begins until it reaches the specified speed at the end of the transition period. if you specify a speed that is slower than the current vehicle speed, then the vehicle will decelerate during the transition period. as with parameter 1 above, you may use the * and / symbols at the beginning of the parameter specification to reference the new speed to the driver s vehicle. <m   bxn xpp?si]4@xn<]4@yn =n e7و΃b=km̳z g(<hparameters: 9, 13, 17, 21, 25: the amount of time, in seconds, that the transition will occur over. <(jd eg  bpzn xpp?si><]4@pzn=n dm!]uh g(<hparameters: 9, 13, 17, 21, 25: the amount of time, in seconds, that the transition will occur over. <(jd eg  bzn xpp?si><]4@zn=n ol{j? g(<hparameters: 9, 13, 17, 21, 25: the amount of time, in seconds, that the transition will occur over. <(jd eg  bp{n xpp?si>#<]4@p{n@>n dqjq. g(<hparameters: 9, 13, 17, 21, 25: the amount of time, in seconds, that the transition will occur over. <(jd eg  b{n xpp?i]4@{n>n zauyhm"b|wo (<ystisim drive (sdl) - v - vehicle ahead (in driver's lane) display a vehicle in the driver s lane, traveling the same direction as the driver. if the driver s vehicle comes in contact with this new vehicle, the crash sound effect will be played (if active), and a collision will be added to the driver s collision total. because of memory limitations, the v event is limited to a total of 550 occurrences in the entire scenario. vehicles that are displayed using the v event have some intelligence built into them. if they are approaching another vehicle from behind, or approaching a stop sign or traffic signal light, they will attempt to do the right thing. when dealing with traffic lights, if the light changes from green, and they are capable of stopping without breaking the laws of physics, the vehicle will stop at the light. when the light changes to green, the vehicles will then accelerate back up to their specified speed. the same action will take place at stop signs. when in traffic, a vehicle that is approaching another vehicle (including the driver) from behind and in the vehicles lane, will try to slow down so that it does not collide with the lead vehicle. if a driver were to swerve in front of an approaching vehicle, the approaching vehicle will try to slow down, but it may not be enough to avoid a collision. unfortunately, the vehicle intelligence only applies to speed and vehicles will not try and go around each other. instead they will always stay behind the lead vehicle. note: if you will be controlling additional vehicle actions (parameters 6-25), then all vehicle intelligence will be turned off (the vehicle will pass through other vehicles, and will not stop at signal lights and stop signs) as long as additional vehicle motions remain. once all of the vehicle motions have been completed, the vehicle will revert back to an intelligent vehicle and will begin paying attention to other vehicles and traffic control devices. the reason for this is that you are specifically requesting the vehicle to do something and if it tries to avoid colliding with other vehicles or stopping at stop signs and signal lights, then this may affect what you have requested the vehicle to do. <(79t   bp|n xpp? i%]4@p|n?n kd{\ifg- <comment & command line: highlight the blue cells, then copy (ctl-c) and paste (ctl-v) into your sdl file. if you want the command without the comment, copy only the last line (with a box around it).<rivebw michel bdard  michel bdard  michel bdard   michel bdard   michel bdard   michel bdard   michel bdard   michel bdard  michel bdard  michel bdard  michel bdard  michel bdard  michel bdard  michel bdard  michel bdard  michel bdard  michel bdard  michel bdard  michel bdard  michel bdard  michel bdard  michel bdard  michel bdard  michel bdard  michel bdard  michel bdard ! michel bdard >"@hejea 56%%%((7((yk randon selection of parametersyk ../../appdata/local/microsoft/windows/stisim/help/randomparams.htmyx;h,]ą'cr%%yk back to commands'command index'!b24''yk vehicle index numbersyk h../../../../stisim/help/sdlvehicles.htmyx;h,]ą'cyk c:\stisim\help\sdleventv.htmyk d../../../../stisim/help/sdleventv.htmyx;h,]ą'c((yk randon selection of parametersyk j../../../../stisim/help/randomparams.htmyx;h,]ą'c\ distance from start of course(distance measured in feet)pr 1. speed of new vehicle (ft/s)you may also reference the vehicle s speed with respect to the driver s speed by using a * or / in front of this parameter. see comment in cell to the left for more details.hc parameter 2qthe longitudinal distance, in feet, that the vehicle is away from the driver when the vehicle initially appears. seo parameter 3the lateral lane position, in feet, of the center of the vehicle with respect to the roadway s dividing line. see comment in cell to the left for more details.et  4. brakelights (if v slows)error!& 0. no brake lights 1. brake lights valid values: 0, 1 t u 6. closure time (s)closure time, in seconds, between the driver s vehicle and the vehicle you are controlling, see comment in cell to the left for more details.ed  7. lateral distance of vlateral distance that the new vehicle will move, with respect to its current lateral position, in feet. see comment in cell to the left for more details.rl  8. new speed (ft/s)new speed, in feet/second, that the vehicle will be traveling at the end of the transition period. see comment to the left for more details.reet 9. transition time (s)ethe amount of time, in seconds, that the transition will occur over. e an 5. vehicle model numberzrange: 1 to 57 random selection possible append r or l for orientation see comment in cell to the left for more details. dai v 10. closure time (s)closure time, in seconds, between the driver s vehicle and the vehicle you are controlling, see comment in cell to the left for more details.v 14. closure time (s)closure time, in seconds, between the driver s vehicle and the vehicle you are controlling, see comment in cell to the left for more details.v 18. closure time (s)closure time, in seconds, between the driver s vehicle and the vehicle you are controlling, see comment in cell to the left for more details.v 22. closure time (s)closure time, in seconds, between the driver s vehicle and the vehicle you are controlling, see comment in cell to the left for more details. 11. lateral distance of vlateral distance that the new vehicle will move, with respect to its current lateral position, in feet. see comment in cell to the left for more details.rl 15. lateral distance of vlateral distance that the new vehicle will move, with respect to its current lateral position, in feet. see comment in cell to the left for more details.rl 19. lateral distance of vlateral distance that the new vehicle will move, with respect to its current lateral position, in feet. see comment in cell to the left for more details.rl 23. lateral distance of vlateral distance that the new vehicle will move, with respect to its current lateral position, in feet. see comment in cell to the left for more details.rl 12. new speed (ft/s)new speed, in feet/second, that the vehicle will be traveling at the end of the transition period. see comment to the left for more details.reet 16. new speed (ft/s)new speed, in feet/second, that the vehicle will be traveling at the end of the transition period. see comment to the left for more details.reet 20. new speed (ft/s)new speed, in feet/second, that the vehicle will be traveling at the end of the transition period. see comment to the left for more details.reet 24. new speed (ft/s)new speed, in feet/second, that the vehicle will be traveling at the end of the transition period. see comment to the left for more details.reet 13. transition time (s)ethe amount of time, in seconds, that the transition will occur over. e an 17. transition time (s)ethe amount of time, in seconds, that the transition will occur over. e an 21. transition time (s)ethe amount of time, in seconds, that the transition will occur over. e an 25. transition time (s)ethe amount of time, in seconds, that the transition will occur over. e an comment & command linehighlight the blue cells, then copy (ctl-c) and paste (ctl-v) into your sdl file. if you want the command without the comment, copy only the last line (with a box around it). e!! sheet52ggdggh'h  q  dmbp?_*+%&?'     #$%&'()6+,-./012345"789:;<=>?@abcdefghijklmnopq?(?)?"??&u} u} } } } } } } } } } } } } } } } } } } } } } } } } } } } } } !!} ""} ##} $$} %%} &&} ''} ((} ))} **} ++} ,,} --} ..} //} 00} 11} 22} 33} 44} 55                nx o nz  n] rrn n`~ s@@u wa:xm $ comment for d@ -- d@bp'$comment for vc -- vertical curvatureyyyyy zb zc wa xd xex \f yy c?s@@ wa]? d^@@ dy y yy c@s? wa]@ d6^{gz?  da $by y yy   yyyyyyy nq6 d@@  da $b er6 e  da $bvc er6 e@@ da $b er6 f{gz? da $b ar s g gw s. l")5 w 6  @(    b}n xpp?itz]4@}no   <comment & command line: highlight the blue cells, then copy (ctl-c) and paste (ctl-v) into your sdl file. if you want the command without the comment, copy only the last line (with a box around it).<rive michel bdard  michel bdard  michel bdard  michel bdard   michel bdard >@heje 7ryk back to commands'command index'!b25yk c:\stisim\help\sdleventvc.htmyk f../../../../stisim/help/sdleventvc.htmyx;h,]ą'c\ distance from start of course(distance measured in feet)ett parameter 1ethe longitudinal length of the vertical curvature, measured in feet. d 2. rate of changewarningof the grade with distance along the vertical curve, measured in (percent grade/feet) (100 * feet/feet)/feet. this parameter causes the grade to change linearly along the roadway. uyou have entered a number of lanes outside the range 1-6. please verify that the number you have entered is correct.y vi comment & command linehighlight the blue cells, then copy (ctl-c) and paste (ctl-v) into your sdl file. if you want the command without the comment, copy only the last line (with a box around it).u   sheet53ggdggh'h  d  dmbp?_*+%&?'?(?)?"??&u} u} } } } } } } } } } } } } } } } } } } } } } } } } } } } } } !!} ""} ##} $$} %%} &&} ''} ((} ))} **} ++} ,,} --} ..} //} 00} 11} 22} 33} 44} 55                 nx o nz  n] rrn n`~ s@@u wa:xy $ comment for d@ -- d@bpcomment for wg -- wind gustsyyyyyyy zb zc wa xd xex \fyyyy c?s@ wa]? d^@ dy yyyyy c@s$@ wa]@ d6^?  da $by yyyyy  c@s$@ wa ]@ d 6 ^$@  d a $ b y y yyyy   yyyyyyyyy nq6 d@@  da $b er6 e@  da $bwg er6 e@ da $b er6 e? da $b er6 f$@ d a $ b ar s g gw"b. p&q 6 wpx(    b(@y xpp?i] ]4@(@y`o #قgmb  8<mstisim drive (sdl) - wg - wind gust this event applies a continuous wind gust to the driver s vehicle for a specified amount of time. this event allows you to put a pseudo-random wind gust into the scenario, thus causing the vehicle to drift off the road, and fluctuate in speed. the end result is that the driver must continually try to maintain the desired vehicle heading and speed by controlling the steering wheel and using the throttle. this event requires the user to specify a sinusoidal parameter file named windgust.par, that must be located in the stisim/data folder. this file contains the shape of the wind gust that will be used by this event. when stisim drive recognizes that the wg event will be used, it will automatically look for and try to load the information contained in the windgust.par file. if it can not find windgust.par, then an error message will be displayed and the wg event will be ignored. note: the wind gust event is specified slightly differently if running with the advanced dynamics option. with the advanced dynamics, the amplitude of the wind gust in windgust.par is specified as a true lateral wind speed in feet/second. example: sample windgust.par file: 3 6 1,6 1,3 1,1 the sum of sines that will be used for this run includes 3 separate sine waves that will be summed together into 1 final wave. the total length of the final wave will be 6 seconds. each of the 3 sine waves specified has an amplitude of 1 and their periods vary from 6 to 1. the sine wave with a period of 6 will have 6 maximum peaks occur during the 6 second wave, the wave with a period of 3 will have 3 maximum peaks occur, and the wave with 1 period will have a single maximum peak. wg event: 1000, wg, 2, .1, 10 this example will add a wind gust to the scenario when the driver has traveled 1000 feet down the road (1000, wg). the sum of sines will consist of the wave data from the windgust.par file with the steering gust being twice the total sum of sines amplitude (2) and the throttle gust being 1/10th the total sum of sines amplitude (.10). since the sum of sines is 6 seconds long and the run time multiplier is 10, the wind gust will be in effect for a total of 60 seconds. <8%1d $  b@y xpp?si]4@@yo  tjumd l<mbw: distance (in feet) driver's vehicle has travelled when the event begins.<al  b@y xpp?si ']4@@y o },c-&jfa]9 <<=bw: steering wheel gain, in radians. since the same gust parameters are used for both steering and throttle, stisim drive provides you with the ability to change the relative amplitude of each by specifying individual steering and throttle gains. note: with advanced dynamics systems, this parameter is not used. <<  b(ay xpp?si ]4@(ayo f- np@h8 5<6bw: throttle controller gain. since the same gust parameters are used for both steering and throttle, stisim drive provides you with the ability to change the relative amplitude of each by specifying individual steering and throttle gains. note: with advanced dynamics systems, this parameter is not used. <5  bay xpp?si]4@ayo u|age/Շ <bw: run length multiplier. this parameter sets the total time that the gust will remain on. since the gust is based on sine waves, stisim drive forces the gust to remain on until it is over. parameter 3 is multiplied by the total length of the combined sine wave to determine the actual simulation run time where the wind gust will be active. therefore, this should be an integer value greater than or equal to one. <  bay xpp? i]4@ay@o ~w~k! <comment & command line: highlight the blue cells, then copy (ctl-c) and paste (ctl-v) into your sdl file. if you want the command without the comment, copy only the last line (with a box around it).<rive michel bdard  michel bdard  michel bdard  michel bdard   michel bdard   michel bdard >@heje 7ryk back to commands'command index'!b26yk c:\stisim\help\sdleventwg.htmyk f../../../../stisim/help/sdleventwg.htmyx;h,]ą'c\ distance from start of course(distance measured in feet)ete 1. steering wheel gain (radians)! see comment to left for details. 2. throttle controller gainwarning' see comment to left for more details. uyou have entered a number of lanes outside the range 1-6. please verify that the number you have entered is correct.'c 3. run length multipliermthis parameter sets the total time that the gust will remain on. see comment to the left for more details. 4please check that the number you entered is correct.t.'c  comment & command linehighlight the blue cells, then copy (ctl-c) and paste (ctl-v) into your sdl file. if you want the command without the comment, copy only the last line (with a box around it).   sheet54ggdggh'h  oh+'0@h`p bruce weaverlorettamicrosoft excel@ф8r@  f&microsoft office excel 2003 worksheetbiff8excel.sheet.89q| slu 6 instructionscommand indexu./stisim/help/sdleventb.htm"&j"'command index'!a5f>@../../appdata/local/microsoft/windows/stisim/help/sdleventb.htm"y)../../../../stisim/help/sdleventbarl.htm"&i"'command index'!a6&lc../../appdata/local/microsoft/windows/stisim/help/sdleventbarl.htm"s)../../../../stisim/help/sdleventblck.htm"&h"'command index'!a77fc../../appdata/local/microsoft/windows/stisim/help/sdleventblck.htm"_)../../../../stisim/help/sdleventbldg.htm"0jc../../appdata/local/microsoft/windows/stisim/help/sdleventbldg.htm"&g"'command index'!a8/y (../../../../stisim/help/sdleventbrk.htm" l b../../appdata/local/microsoft/windows/stisim/help/sdleventbrk.htm"&f "'command index'!a9q )../../../../stisim/help/sdleventbsav.htm"&n "'command index'!a105d c../../appdata/local/microsoft/windows/stisim/help/sdleventbsav.htm"e  &../../../../stisim/help/sdleventc.htm"&n "'command index'!a11g> @../../appdata/local/microsoft/windows/stisim/help/sdleventc.htm"*j (../../../../stisim/help/sdleventcao.htm"&n "'command index'!a12_ b../../appdata/local/microsoft/windows/stisim/help/sdleventcao.htm"y)../../../../stisim/help/sdleventcolb.htm"&n"'command index'!a139lc../../appdata/local/microsoft/windows/stisim/help/sdleventcolb.htm"s)../../../../stisim/help/sdleventcset.htm"&n"'command index'!a140fc../../appdata/local/microsoft/windows/stisim/help/sdleventcset.htm"_)..՜.+,d՜.+, pxd lt| slu 6 instructionscommand indexunits of speedaaobbarlblckbldgbrkbsavbsav variablesccaocao variablescolbcsetctcvdadidodo2esesavfllwfogijbarlspauspbpdepepedplbmpolyprrmsbrmseroadrsartsignslsobjsoutspcwstcwtdotreevvcwg  worksheets6@\ 8@ _pid_hlinksa[&n"'command index'!a1>3 ../../../../stisim/help/sdl.htm"v2"wg!b1w1"vc!b10"v!b10u/"tree!b1yt."tdo!b11a-"stcw!b1(s,"'units of speed'!a11e+"spcw!b1'y*"sout!b10g)"sobj!b1r("sl!b15e'"sign!b1s&"rt!b1qc%"rsa!b12i$"road!b1 j#"rmse!b1 m""rmsb!b1q!"pr!b1=t "poly!b13c"plbm!b1vu"ped!b1q"pe!b1wt"pde!b1q"pb!b1-f"instructions!a1$p"paus!b1m"ls!b1*r"jbar!b1 "i!b1c"fog!b1+y"fllw!b1%g"esav!b1d"es!b1 f" 'do2'!b1e "do!b1e "di!b1e"da!b1b "cv!b1b "ct!b1'e "cset!b1.o "colb!b1nq "cao!b1bs"'c'!b1"g"bsav!b1kb"brk!b1'i"bldg!b1 e"blck!b11o"barl!b1"b!b1@ "ao!b1"a!b1%l"'command index'!b30&l"'command index'!a3g &../../../../stisim/help/sdleventa.htm"_)../../../../stisim/help/randomparams.htm"-g(../../../../stisim/help/sdlvehicles.htm"&l"'command index'!a3-jc../../appdata/local/microsoft/windows/stisim/help/randomparams.htm"rb../../appdata/local/microsoft/windows/stisim/help/sdlvehicles.htm"e>@../../appdata/local/microsoft/windows/stisim/help/sdleventa.htm"u;'../../../../stisim/help/sdleventao.htm"&k"'command index'!a4wa../../appdata/local/microsoft/windows/stisim/help/sdleventao.htm"d &../../.././../../../stisim/help/randomparams.htm"-g(../../../../stisim/help/sdlvehicles.htm"&n"'command index'!a15w '../../../../stisim/help/sdleventct.htm"&n"'command index'!a16w"'../../../../stisim/help/sdleventcv.htm"&n"'command index'!a17p5'../../../../stisim/help/sdleventda.htm"&n"'command index'!a18p='../../../../stisim/help/sdleventdi.htm"&n"'command index'!a19p;'../../../../stisim/help/sdleventdo.htm"&m"'command index'!a20pd(../../../../stisim/help/sdleventdo2.htm"&m"'command index'!a21q''../../../../stisim/help/sdleventes.htm"&m"'command index'!a22q''../../../../stisim/help/sdleventes.htm"_)../../../../stisim/help/randomparams.htm"o)../../../../stisim/help/sdleventfllw.htm"&m"'command index'!a23-jc../../appdata/local/microsoft/windows/stisim/help/randomparams.htm"-g(../../../../stisim/help/sdlvehicles.htm"<zc../../appdata/local/microsoft/windows/stisim/help/sdleventfllw.htm"'d(../../../../stisim/help/sdleventfog.htm"&m"'command index'!a24qb../../appdata/local/microsoft/windows/stisim/help/sdleventfog.htm"o &../../../../stisim/help/sdleventi.htm"&m"'command index'!a25m>@../../appdata/local/microsoft/windows/stisim/help/sdleventi.htm"d)../../../../stisim/help/sdleventjbar.htm"&m"'command index'!a26=qc../../appdata/local/microsoft/windows/stisim/help/sdleventjbar.htm"x''../../../../stisim/help/sdleventls.htm"&m"'command index'!a27za../../appdata/local/microsoft/windows/stisim/help/sdleventls.htm"f)../../../../stisim/help/sdleventpaus.htm"%l"'command index'!b33sc../../appdata/local/microsoft/windows/stisim/help/sdleventpaus.htm"d6'../../../../stisim/help/sdleventpb.htm"%k"'command index'!b4fa../../appdata/local/microsoft/windows/stisim/help/sdleventpb.htm"3o (../../../../stisim/help/sdleventpde.htm"%j "'command index'!b5z b../../appdata/local/microsoft/windows/stisim/help/sdleventpde.htm"d1!'../../../../stisim/help/sdleventpe.htm"%i!"'command index'!b6z!b../../appdata/local/microsoft/windows/stisim/help/sdleventpde.htm"2n"(../../../../stisim/help/sdleventped.htm"%h""'command index'!b7["b../../appdata/local/microsoft/windows/stisim/help/sdleventped.htm"u#)../../../../stisim/help/sdleventplbm.htm"%g#"'command index'!b8#n../../appdata/local/microsoft/windows/temporary internet files/low/content.ie5/0r3kps15/help/sdleventplbm.htm"b$)../../../../stisim/help/sdleventpoly.htm"%f$"'command index'!b9*w$c../../appdata/local/microsoft/windows/stisim/help/sdleventpoly.htm"d&%'../../../../stisim/help/sdleventpr.htm"%n%"'command index'!b10f%a../../appdata/local/microsoft/windows/stisim/help/sdleventpr.htm"[&)../../../../stisim/help/sdleventrmsb.htm"%n&"'command index'!b117n&c../../appdata/local/microsoft/windows/stisim/help/sdleventrmsb.htm"\')../../../../stisim/help/sdleventrmse.htm"%n'"'command index'!b127i'c../../appdata/local/microsoft/windows/stisim/help/sdleventrmse.htm"_()../../../../stisim/help/sdleventroad.htm"%n("'command index'!b13e>(@../../appdata/local/microsoft/windows/stisim/help/sdleventa.htm"%n)"'command index'!b145x)(../../../../stisim/help/sdleventrsa.htm"%n*"'command index'!b15f *'../../../../stisim/help/sdleventrt.htm"s+)../../../../stisim/help/sdleventsign.htm"%n+"'command index'!b16"f+c../../appdata/local/microsoft/windows/stisim/help/sdleventsign.htm"g8,'../../../../stisim/help/sdleventsl.htm"%n,"'command index'!b17e ,a../../appdata/local/microsoft/windows/stisim/help/sdleventsl.htm"q-)../../../../stisim/help/sdleventsobj.htm"%n-"'command index'!b18'd-c../../appdata/local/microsoft/windows/stisim/help/sdleventsobj.htm"o.)../../../../stisim/help/sdleventsout.htm"%n."'command index'!b19e>.@../../appdata/local/microsoft/windows/stisim/help/sdleventa.htm"s/)../../../../stisim/help/sdleventspcw.htm"%m/"'command index'!b20&f/c../../appdata/local/microsoft/windows/stisim/help/sdleventspcw.htm"w0)../../../../stisim/help/sdleventstcw.htm"%m0"'command index'!b21&b0c../../appdata/local/microsoft/windows/stisim/help/sdleventstcw.htm"=o1(../../../../stisim/help/sdleventtdo.htm"z1b../../appdata/local/microsoft/windows/stisim/help/sdleventtdo.htm"%m1"'command index'!b22_2)../../../../stisim/help/randomparams.htm" i2)../../../../stisim/help/sdleventtree.htm treelistc2)../../../../stisim/help/sdleventtree.htm"%m2"'command index'!b23_3)../../../../stisim/help/randomparams.htm"p 3&../../../../stisim/help/sdleventv.htm"-g3(../../../../stisim/help/sdlvehicles.htm"%m3"'command index'!b24-j3c../../appdata/local/microsoft/windows/stisim/help/randomparams.htm"b74'../../../../stisim/help/sdleventvc.htm"%m4"'command index'!b25c35'../../../../stisim/help/sdleventwg.htm"%m5"'command index'!b26compobjr