Reuse through Groups - Revision history

Anna Dizack at 21:44, 24 February 2017

2017-02-24T21:44:36Z

Ciera Headley at 01:05, 7 December 2016

2016-12-07T01:05:12Z

Ciera Headley at 00:53, 7 December 2016

2016-12-07T00:53:16Z

Ciera Headley at 23:58, 5 December 2016

2016-12-05T23:58:38Z

Show changes

Ciera Headley at 23:58, 5 December 2016

2016-12-05T23:58:17Z

Ciera Headley: /* Reuse through Groups */

2016-12-05T23:56:42Z

‎Reuse through Groups

Show changes

Ciera Headley at 23:50, 5 December 2016

2016-12-05T23:50:12Z

Ciera Headley: Created page with "==Reuse through Groups== Groups can be used to store groups of objects in a separate file. This allows these groups to be imported in other scenarios or linked to another scen..."

2016-12-05T23:46:00Z

Created page with "==Reuse through Groups== Groups can be used to store groups of objects in a separate file. This allows these groups to be imported in other scenarios or linked to another scen..."

Show changes

← Older revision		Revision as of 21:44, 24 February 2017
Line 1:		Line 1:
		+	[[ISAT_User%27s_Guide_Table_of_Contents\|ISAT User's Guide Table of Contents]]
		+
	[[Introduction_II\|◄PREVIOUS]] [[Appendix_B_Data_Verification_using_ISAT_Playback\|NEXT►]]		[[Introduction_II\|◄PREVIOUS]] [[Appendix_B_Data_Verification_using_ISAT_Playback\|NEXT►]]
	==Reuse through Groups==		==Reuse through Groups==

← Older revision		Revision as of 01:05, 7 December 2016
Line 69:		Line 69:

	[[File: ExpressionT.png\|600px\|thumb\|center]]		[[File: ExpressionT.png\|600px\|thumb\|center]]
		+
		+	[[#top\|TOP]]
		+
		+
		+	[[Introduction_II\|◄PREVIOUS]] [[Appendix_B_Data_Verification_using_ISAT_Playback\|NEXT►]]

@@ Line 3: / Line 3: @@
 Groups can be used to store groups of objects in a separate file. This allows these groups to be imported in other scenarios or linked to another scenario. When a group is imported, it adds a copy of the group to the scenario file. Any changes to the elements in these groups will not affect the original group file. When a group is linked or added as an external reference, this adds a reference to the file in the scenario file, and does not store the actual members of the group. This means that when a group files is added as external reference the group file must always be kept with the file. In addition, you cannot modify members of groups that are added as external references. This has the advantage of allowing a single section of a scenario to be saved as a group and used across multi scenarios. Groups are discussed in detail in section 3.18.
 ===Appendix A: Authoring a Lead Vehicle Pull Out (LVPO) Event===
@@ Line 10: / Line 11: @@
 For this tutorial, you may select any LRI with a 3 or 4-way intersection with traffic lights. For this example, we chose WirelessUA.bli, and used the southern most intersection.
 ====Step 1====
@@ Line 17: / Line 20: @@
 [[File: 1087.png | 600px| thumb| center | '''Figure 10-87 Initial Conditions''']]
 ====Step 2====
 Place the Lead Vehicle. Now that we have placed the external driver, we need to place the lead vehicle that is to cut off our participant, hence creating our event. We need to select a ADO. To place an ADO go to Insert->ADO from the main menu, or by clicking on the ADO button on the toolbar. The Lead Vehicle needs to be placed such that it can make a right hand turn in front of our driver. In addition, the ADO needs to be close enough to the intersection that it is stopped at the intersection before the start of the event. Once we have place the Lead Vehicle we need to instruction it to make a right hand turn. This can be done by specifying the Lead Vehicle’s path. To do this, right click on the Lead Vehicle, and select the extend path option, and click on the lane the Lead Vehicle will be turning onto, past the intersection. This will place a blue path showing the path the Lead Vehicle will travel. Once the Lead Vehicle reaches the end of the path it will just continue as normal.
@@ Line 22: / Line 26: @@
 [[File: 1088.png| 600px| thumb| center | '''Figure 10-88 ADO Path''']]
 ====Step 3====
 Setting up the traffic lights. In order to make sure the lead vehicle waits at the intersection for the external driver to approach we need to make sure the light at the intersection is red. We do this through the traffic light manager. The traffic light manager can be accessed through Edit-
@@ Line 28: / Line 33: @@
 [[File: 1089.png|600px|thumb|center|'''Figure 10-89 Traffic Light Manager''']]
 ====Step 4====
 Lead vehicle pull out. In this step, we want to cause the lead vehicle to make a right turn when the driver is within 7 seconds of the intersection. Remember triggers operate effectively as “if then” statements, if its predicate is satisfied then execute the action(s). We will place a road pad trigger and a time to arrival trigger to accomplish this. The first step is to place the time to arrival trigger. The road pad trigger can be inserted from Insert->Time to Arrival menu. Once placed, ISAT will bring up the road pad trigger settings dialog.  On the predicate tab, place the time as 7, and hit the “Set Ext Driver” button, this will select the external driver as the predicate set (only the members of the predicate set may be evaluated by the predicate). Next click on the Actions tab. Hit the new button and select “Set Dial” in the “action type” combo box, and “ForcedVelocity” in the Dial combo. Next, hit the “Set Params” button. This will bring up the Set Forced Velocity dialog. Select Target Velocity and set MPH to 7 and Accel to 2.9. This will cause the target to accelerate to 7 Mph at a rate of 2.9. Hit “OK”. In the Action tab, select under “who to effect” the “Name” option and hit the “…” button to the right of the name option. This will pop up a dialog. Add the “Lead Vehicle” to the candidate set. This action will force the Lead Vehicle to start pulling out in front of
@@ Line 43: / Line 49: @@
 [[File:1090.png|600px |thumb |center | '''Figure 10-90 Turn lane Accel''']]
 ====Step 6 Testing====
 Now that we have, the basic elements of our event down, we can now use the rehearsal mode to insure that our event is working. The   icon in the mode tool bar to enter the rehearsal mode. Here we can “run” the scenario. You can also start the rehearsal mode through the menu Mode → Rehearsal. The rehearsal mode will run two iterations of dynamics and one iteration of behaviors every frame. The behaviors and dynamics modules are also used in the NADS. Press the play button on the rehearsal dialog to start the simulation. The lead car should be pulling out just in front of the external driver in this scenario. If the lead vehicle is not pulling out in front of the external driver, we will have to check our setting on the individual scenario elements. Is the “SetForcedVel” action set right? Is the Time to arrival trigger firing?
 ====Step 7 Data Reduction====

@@ Line 1: / Line 1: @@
-[[Introduction_II|◄PREVIOUS]]                   [[Other_Things|NEXT►]]
+[[Introduction_II|◄PREVIOUS]]                   [[Appendix_B_Data_Verification_using_ISAT_Playback|NEXT►]]
 ==Reuse through Groups==
 Groups can be used to store groups of objects in a separate file. This allows these groups to be imported in other scenarios or linked to another scenario. When a group is imported, it adds a copy of the group to the scenario file. Any changes to the elements in these groups will not affect the original group file. When a group is linked or added as an external reference, this adds a reference to the file in the scenario file, and does not store the actual members of the group. This means that when a group files is added as external reference the group file must always be kept with the file. In addition, you cannot modify members of groups that are added as external references. This has the advantage of allowing a single section of a scenario to be saved as a group and used across multi scenarios. Groups are discussed in detail in section 3.18.

← Older revision		Revision as of 23:50, 5 December 2016
Line 1:		Line 1:
		+	[[Introduction_II\|◄PREVIOUS]] [[Other_Things\|NEXT►]]
	==Reuse through Groups==		==Reuse through Groups==
	Groups can be used to store groups of objects in a separate file. This allows these groups to be imported in other scenarios or linked to another scenario. When a group is imported, it adds a copy of the group to the scenario file. Any changes to the elements in these groups will not affect the original group file. When a group is linked or added as an external reference, this adds a reference to the file in the scenario file, and does not store the actual members of the group. This means that when a group files is added as external reference the group file must always be kept with the file. In addition, you cannot modify members of groups that are added as external references. This has the advantage of allowing a single section of a scenario to be saved as a group and used across multi scenarios. Groups are discussed in detail in section 3.18.		Groups can be used to store groups of objects in a separate file. This allows these groups to be imported in other scenarios or linked to another scenario. When a group is imported, it adds a copy of the group to the scenario file. Any changes to the elements in these groups will not affect the original group file. When a group is linked or added as an external reference, this adds a reference to the file in the scenario file, and does not store the actual members of the group. This means that when a group files is added as external reference the group file must always be kept with the file. In addition, you cannot modify members of groups that are added as external references. This has the advantage of allowing a single section of a scenario to be saved as a group and used across multi scenarios. Groups are discussed in detail in section 3.18.