Working with Components - Revision history

Anna Dizack at 21:39, 24 February 2017

2017-02-24T21:39:40Z

Ciera Headley at 00:59, 7 December 2016

2016-12-07T00:59:17Z

Ciera Headley at 00:38, 7 December 2016

2016-12-07T00:38:45Z

Ciera Headley: /* SOL Model */

2016-12-07T00:38:06Z

‎SOL Model

Ciera Headley: /* Activation Delay */

2016-12-07T00:37:52Z

‎Activation Delay

Ciera Headley: /* Defining Common Scenario Element Parameters */

2016-12-07T00:37:40Z

‎Defining Common Scenario Element Parameters

Ciera Headley: /* Comment Objects */

2016-12-07T00:37:30Z

‎Comment Objects

Ciera Headley at 22:47, 5 December 2016

2016-12-05T22:47:35Z

Show changes

Ciera Headley: Created page with "==Working with Components== Components are a mechanism by which scenario elements can be grouped together for re-use. ==Emailing Scenarios== To e-mail the current scenario,..."

2016-12-05T22:41:33Z

Created page with "==Working with Components== Components are a mechanism by which scenario elements can be grouped together for re-use. ==Emailing Scenarios== To e-mail the current scenario,..."

Show changes

← Older revision		Revision as of 21:39, 24 February 2017
Line 1:		Line 1:
		+	[[ISAT_User%27s_Guide_Table_of_Contents\|ISAT User's Guide Table of Contents]]
		+
	[[Moving_Scenario_Elements\|◄PREVIOUS]] [[Authoring_Deterministic_Dynamic_Objects\|NEXT►]]		[[Moving_Scenario_Elements\|◄PREVIOUS]] [[Authoring_Deterministic_Dynamic_Objects\|NEXT►]]
	==Working with Components==		==Working with Components==

← Older revision		Revision as of 00:59, 7 December 2016
Line 137:		Line 137:

	[[File:signTest.png\|800px\|thumb\|center\|'''Figure 3-41 Control Points''']]		[[File:signTest.png\|800px\|thumb\|center\|'''Figure 3-41 Control Points''']]
		+
		+
		+	[[Moving_Scenario_Elements\|◄PREVIOUS]] [[Authoring_Deterministic_Dynamic_Objects\|NEXT►]]

@@ Line 35: / Line 35: @@
 ===Creation Radius===
@@ Line 57: / Line 58: @@
 The activation delay is often useful in conjunction with a creation radius. Using a larger than needed creation radius can help minimize the chance that the simulator driver will observe an object popping out of nowhere, and the activation delay can ensure that the object does not begin its activity until the driver is closer. For example, consider a DDO vehicle that is programmed to begin traveling at 50 mph, has a creation radius of 500, and has an activation delay of 3. Once the driver gets within 500 feet of the DDO, the DDO will be created and the vehicle will appear in the virtual environment. However, another 3 seconds have to go by before the DDO will begin moving.
 ===Lifetime===
@@ Line 83: / Line 86: @@
 The SOL has been designed so it can be extended with additional objects or even additional categories. Adding new objects involves creating entries for the various NADS-correlated databases, such as the visual and audio databases, and rebuilding the NADS software. Although this process is not complicated, it requires access to all the NADS software and intimate knowledge of the software’s structure. Therefore, it is not possible at this time for ISAT users to extend the SOL.
 ===Buttons and Dials===
@@ Line 93: / Line 98: @@
 For each type of behavior that can be authored by the ISAT, this document will provide a listing of all buttons and dials and a description of how they will affect the behavior at runtime. At runtime, the actual pressing of buttons and setting of dials is done though coordinators such as the trigger or, to some limited extent, interactively by the user though the ISAT. The rehearsal mode of the ISAT can then be used to execute the scenario and verify that the runtime behavior is what was expected.
 ==Group Bar==
@@ Line 109: / Line 116: @@
 [[File:external.png|800px|thumb|center|'''Figure 3-39 External References''']]
 ==Preferences==

@@ Line 65: / Line 65: @@
 It is the user’s responsibility to ensure that the lifetime, if specified, is large enough to ensure the scenario element is not close enough for the driver to observe its disappearance.
 ===SOL Model===
@@ Line 80: / Line 82: @@
 The SOL has been designed so it can be extended with additional objects or even additional categories. Adding new objects involves creating entries for the various NADS-correlated databases, such as the visual and audio databases, and rebuilding the NADS software. Although this process is not complicated, it requires access to all the NADS software and intimate knowledge of the software’s structure. Therefore, it is not possible at this time for ISAT users to extend the SOL.
-−
 ===Buttons and Dials===

← Older revision		Revision as of 00:37, 7 December 2016
Line 49:		Line 49:
	[[File:comment.png\|800px\|thumb\|center]]		[[File:comment.png\|800px\|thumb\|center]]

		+
		+	[[#top\|TOP]]
	===Activation Delay===		===Activation Delay===

← Older revision		Revision as of 00:37, 7 December 2016
Line 24:		Line 24:
	[[File:3.36.png\|800px\|thumb\|center\| '''Figure 3-36 Comment''']]		[[File:3.36.png\|800px\|thumb\|center\| '''Figure 3-36 Comment''']]

		+
		+	[[#top\|TOP]]
	=Defining Common Scenario Element Parameters=		=Defining Common Scenario Element Parameters=

← Older revision		Revision as of 00:37, 7 December 2016
Line 16:		Line 16:
	To associate a textual comment with a scenario, select the Edit->Scenario Comment menu option. It is recommended that long descriptive descriptions be added for each scenario to make it easier to remember the goals of a scenario that was built by others. Keep in mind that the scenario comment appears in the preview window when opening an existing scenario file (see Section 3.5 for more details).		To associate a textual comment with a scenario, select the Edit->Scenario Comment menu option. It is recommended that long descriptive descriptions be added for each scenario to make it easier to remember the goals of a scenario that was built by others. Keep in mind that the scenario comment appears in the preview window when opening an existing scenario file (see Section 3.5 for more details).

		+
		+	[[#top\|TOP]]
	==Comment Objects==		==Comment Objects==