Settings button - Revision history

Anna Dizack at 19:51, 24 February 2017

2017-02-24T19:51:51Z

Ciera Headley at 22:20, 26 September 2016

2016-09-26T22:20:03Z

Ciera Headley at 22:18, 26 September 2016

2016-09-26T22:18:08Z

Ciera Headley: /* Show Report After Drive */

2016-09-26T21:28:41Z

‎Show Report After Drive

Ciera Headley: /* Show Report After Drive */

2016-09-26T21:28:19Z

‎Show Report After Drive

Ciera Headley: /* Show Report After Drive */

2016-09-26T21:27:34Z

‎Show Report After Drive

Ciera Headley: /* Show Report After Drive */

2016-09-26T21:20:52Z

‎Show Report After Drive

Ciera Headley: /* Data Collection Mode and the DAQ Button */

2016-09-26T21:11:24Z

‎Data Collection Mode and the DAQ Button

Ciera Headley: /* Data Collection Mode and the DAQ Button */

2016-09-26T21:10:30Z

‎Data Collection Mode and the DAQ Button

Ciera Headley: /* Data Collection Mode and the DAQ Button */

2016-09-26T21:09:18Z

‎Data Collection Mode and the DAQ Button

@@ Line 1: / Line 1: @@
 [[Using_the_Minisim|◄PREVIOUS]]                                         [[More_Buttons|NEXT►]]
@@ Line 5: / Line 7: @@
 ==Screensaver==
-If the '''Enable Screen Save''' option is checked, when the MiniSim stays in the stopped mode for a prolonged period of time, the screen saver mode will start automatically, with the visuals showing a chase view and replaying a pre-recorded drive. As soon as the “Start Drive” button in the GUI is clicked, the screen saver mode will stop. The Windows desktop screen saver on the visuals computer is automatically disabled when the MiniSim visuals is running.
+If the '''Enable Screen Save''' option is checked, when the miniSim stays in the stopped mode for a prolonged period of time, the screen saver mode will start automatically, with the visuals showing a chase view and replaying a pre-recorded drive. As soon as the “Start Drive” button in the GUI is clicked, the screen saver mode will stop. The Windows desktop screen saver on the visuals computer is automatically disabled when the miniSim visuals is running.
 If a screensaver file does not exist for your visual database, or you just created a new database, use the following procedure to create a screensaver file:
 ==Data Collection Mode and the DAQ Button==
-The MiniSim data acquisition system (DAQ) runs every time a scenario is run. However, when the MiniSim is placed in Data Collection Mode, the operator must select the Experiment Name and Test Subject ID from a list you create. The Experiment and Test Subject ID selected then restricts the allowable scenarios that can be run according to a matrix defined by the user – ensuring that the data collection conforms to your experimental design. In addition, you may enter notes or comments about a particular test subject or drive and these comments are saved for future reference, Figure 23. You may also manually enter The Experiment and Test Subject ID at runtime.
+The miniSim data acquisition system (DAQ) runs every time a scenario is run. However, when the miniSim is placed in Data Collection Mode, the operator must select the Experiment Name and Test Subject ID from a list you create. The Experiment and Test Subject ID selected then restricts the allowable scenarios that can be run according to a matrix defined by the user – ensuring that the data collection conforms to your experimental design. In addition, you may enter notes or comments about a particular test subject or drive and these comments are saved for future reference, Figure 23. You may also manually enter The Experiment and Test Subject ID at runtime.
 [[File:fig23.png|500px|thumb|center|Figure 23: MiniSim Data Collection Window]]
-Every time a scenario is run on the MiniSim a data collection (*.daq) file is created. DAQ files are located in the C:\DAQ folder.  Checking the Data Collection Mode box simply changes how the data collection interface works.
+Every time a scenario is run on the miniSim a data collection (*.daq) file is created. DAQ files are located in the C:\DAQ folder. Checking the Data Collection Mode box simply changes how the data collection interface works.
 ''With the box un-checked:''
@@ Line 40: / Line 42: @@
 </ul>
-The MiniSim can also be launched from a DOS prompt. This command line options to do this include the option to specify exactly where each DAQ file is to be located. This covered in a later section.
+The miniSim can also be launched from a DOS prompt. This command line options to do this include the option to specify exactly where each DAQ file is to be located. This covered in a later section.
 [[#top|TOP]]
@@ Line 46: / Line 48: @@
 ====Show Report After Drive====
-When this box is checked, and the scenario is properly authored, the MiniSim will display measures in a pop-up window immediately after the completion of a drive. The same measures are recorded in a text file located in the C:\DAQ\Texpr\Tsub folder. The construction of the filename is as follows:
+When this box is checked, and the scenario is properly authored, the miniSim will display measures in a pop-up window immediately after the completion of a drive. The same measures are recorded in a text file located in the C:\DAQ\Texpr\Tsub folder. The construction of the filename is as follows:
 Scenarioname_timedatestamp_report.txt
-If this box is not checked, the MiniSim will still calculate measures, and record them in the text file, but not display them in the pop-up window.
+If this box is not checked, the miniSim will still calculate measures, and record them in the text file, but not display them in the pop-up window.
 The current list of measures that are calculated are as follows:

@@ Line 1: / Line 1: @@
-[[Using_the_Minisim|◄PREVIOUS]]                                         [[More_Buttons|NEXT->]]
+[[Using_the_Minisim|◄PREVIOUS]]                                         [[More_Buttons|NEXT►]]
 =Settings Button=
@@ Line 72: / Line 72: @@
 [[#top|TOP]]
-[[Using_the_Minisim|◄PREVIOUS]]                                         [[More_Buttons|NEXT->]]
+[[Using_the_Minisim|◄PREVIOUS]]                                         [[More_Buttons|NEXT►]]

@@ Line 1: / Line 1: @@
-[[Using_the_Minisim|<-PREVIOUS]]                                         [[More_Buttons|NEXT->]]
+[[Using_the_Minisim|◄PREVIOUS]]                                         [[More_Buttons|NEXT->]]
 =Settings Button=
@@ Line 72: / Line 72: @@
 [[#top|TOP]]
-[[Using_the_Minisim|<-PREVIOUS]]                                         [[More_Buttons|NEXT->]]
+[[Using_the_Minisim|◄PREVIOUS]]                                         [[More_Buttons|NEXT->]]

← Older revision		Revision as of 21:28, 26 September 2016
Line 67:		Line 67:
	The report format is as follows. Note that the results in the first line are for the total drive starting with the first event and ending with the last event. Only four events were defined for the example below.		The report format is as follows. Note that the results in the first line are for the total drive starting with the first event and ending with the last event. Only four events were defined for the example below.

−	[[File:event.png\|~~650px~~\|thumb\|center]]	+	[[File:event.png\|750px\|thumb\|center]]

← Older revision		Revision as of 21:28, 26 September 2016
Line 67:		Line 67:
	The report format is as follows. Note that the results in the first line are for the total drive starting with the first event and ending with the last event. Only four events were defined for the example below.		The report format is as follows. Note that the results in the first line are for the total drive starting with the first event and ending with the last event. Only four events were defined for the example below.

−	[[File:event.png\|~~450px~~\|thumb\|center]]	+	[[File:event.png\|650px\|thumb\|center]]

@@ Line 67: / Line 67: @@
 The report format is as follows. Note that the results in the first line are for the total drive starting with the first event and ending with the last event. Only four events were defined for the example below.
-<gallery mode="traditional">
+[[File:event.png|450px|thumb|center]]
-Image: Report Format|Report Format</gallery>

@@ Line 52: / Line 52: @@
 The current list of measures that are calculated are as follows:
-<gallery mode="traditional">
+[[File:fig25.png|450px|thumb|center]]
-Image: List of Measures|: List of Measurest</gallery>
 The scenario must be set up so that the measures will be calculated. There are two variables that must be initialized in the scenario and incremented to define the ‘events’ in the following way. Note <span style="text-decoration: underline"> '''All must be set to type short :'''</span>

@@ Line 32: / Line 32: @@
 <li>You create the experimental design using the '''ExperimentConfig.txt''' file located in the '''C:\NadsMiniSim_v1.8.x\Data\Rcm_data''' folder. A sample file is shown below. The first column is the experiment name, the second column is the test subject name, and the third column is a comma-separated list of the allowable scenarios for that participant. Note the use of the ‘Ops’ Experiment to allow use of the calibration and verification scenarios only to the operator.</li>
-[[File:fig24.png|500px|thumb|center]]
+[[File:fig24.png|550px|thumb|center]]
 <li>When in DAQ mode, the operator may enter notes about the participant or drive, and these are recorded in a text file located in the C:\DAQ\Texpr\Tsub folder. The construction of the filename is as follows:</li>