2009-02-03T18:39:57Z

Mcd8604: /* Stellar Prospector */

Each Minigame has a variety of settings that can be configured individually.

==Config==

The Config.script file holds general settings. It can be opened with any general text editor, such as Notepad or Vim. Each line ending with a semicolon (;) indicates a command for the game to follow. Lines beginning with two forward slashes (//) are considered comments, and will not be processed. A block comment is a section beginning with (/*) and ending at (*/).

===Lab, Home and Debug configurations===

The only difference between the lab and the home versions of the game is the config file that is used. The program will automatically use the LabConfig.script file if it exists; otherwise it will use Config.script. To run the program in the lab, simply make certain that the LabConfig.script file is present.

(When the game is being run from within the debugger, a third configuration script, DebugConfig.script, is used.)

These config files will be found in "[Game Install Directory]\Configs\" (Default: "C:\Program Files\Autism Collaborative\Configs\")

See also: [[Differences in Home vs Lab Configuration]]

===Location===

[Installation Directory]\Configs\Config.script (Default: "C:\Program Files\Autism Collaborative\Configs\")

The Global Config.script can be found in the Configs folder under the Autism Collaborative folder -- typically C:\Program Files\Autism Collaborative\Configs\Config.script. This holds global settings that will be applied automatically when the game starts. Individual minigames may have individual configurations specific to those minigames. This individual config file is also called Config.script, and can be found in the Configs folder under the minigame's folder -- typically C:\Program Files\Autism Collaborative\Minigames\[MiniGameName]\Configs\Config.script.

===Global===

Util.Settings.SetResolution([horizontal],[vertical]);
* Set the screen resolution this game will be played at, for example, Util.Settings.SetResolution(1024,768);

Util.Settings.FullScreen = [true/false];
* Set whether the game window will be fullscreen, for example, Util.Settings.FullScreen = true;

Util.Settings.ParallelPortEnabled = [true/false];
* Set whether codes should be written out the Parallel Port, for example, Util.Settings.ParallelEnabled = true; If not specified, this will default to False.

Util.Settings.ParallelPort = ParallelPort.Port1;
* Set which Parallel Port codes should be written to, if enabled. Valid values are Port1, Port2, and Port3. Defaults to Port1.

Util.Settings.SetScreenDimensions([Width], [Height], [Distance]);
* Width is the width of the display, in centimeters. Height is as height of the display, in centimeters. Distance is the distance between the display and the viewer's eyes, in centimeters. For the dot coherence phase of Maritime Defender, the dots are based on the size of the visual display as it appears to the player. For example, Util.Settings.SetScreenDimensions(8.5, 6.25, 24.0);

===Maritime Defender===

MaritimeDefender.Settings.DotsPerSquareRadian = [Number];
MaritimeDefender.Settings.DotsPerSquareDegree = [Number];
* For the dot coherence phase, the dots are based on the size of the visual display as it appears to the player. This sets the density of the dots as they appear on the screen. Either measure, radians or degrees, may be used. For example, MaritimeDefender.Settings.DotsPerSquareRadian = 10000.0;

MaritimeDefender.Settings.DotsPerRadian = [Number];
MaritimeDefender.Settings.DotsPerDegree = [Number];
* Specify the dot density as the number of dots within a circular patch of screen space with a diameter of one radian or degree of visual angle as it appears to the user.

MaritimeDefender.Settings.NumberDots = [Number];
* Override the above settings, specifying exactly the number of dots that should be drawn on the screen. This setting is optional.

MaritimeDefender.Settings.DotDiameter = System.Math.PI / 1028;
* Affects the average size of the coherence dots in terms of radians.

MaritimeDefender.Settings.DotSpeed = System.Math.PI / 16;
* Affects how fast the coherence dots appear to move across the screen in terms of radians per second.

MaritimeDefender.Settings.DotLifeSpan = 4 / 60.0;
* How long each dot exists on the screen. 4 / 60.0 reflects 4 frames on a 60 hertz display.

MaritimeDefender.Settings.DotRefreshDelay = 1;
* Additional Delay in seconds between each dot test, for the EEG readings. This is in addition to a random jitter of, by default, between 0 and 150ms; this jitter is controlled by the DotRefreshDelayJitter.

MaritimeDefender.Settings.DotRefreshDelayJitter = 0.15;
* A random amount of jitter between 0 and [value] seconds will added to the DotRefreshDelay so that the time between two successive coherence trials is not constant. The default is 0.15 of a second, or 150 milliseconds.

MaritimeDefender.Settings.DotResponseWait = 0.5;
* The duration of time in seconds immediately after a trial with no response in which late responses can be excepted.

MaritimeDefender.Settings.DotTrialLength = 2;
* The average duration of a dot test trial in seconds.

MaritimeDefender.Settings.SetPhaseQueue(2, "IdentityTest, 1, Shooter, 3, DotTest, 140, Shooter, 3, DotTest, 140, Shooter, 3, DotTest, 140, Shooter, 1, Boss, 0");
* The game phases for Maritime Defender. A list of pairs, a name and a value. Currently, the Game must start with an IdentityTest phase. The Shooter value is how many wormholes must be opened and ships identified in order to move on to the next Phase. The DotTest value is how many dot trials will take place during that phase, where a trial may be a motion of dots, or an absence of motion.

MaritimeDefender.Settings.HaveNonCoherentTrials = false;
* Whether NonCoherentTrials should be included. If false, there will be coherent motion to the left or right for every trial.

===Stellar Prospector===

StellarProspector.Settings.StimulusWaitMax = 1500f;
* The maximum amount of time in milliseconds before a stimulus must appear after the offset of the previous stimulus.

StellarProspector.Settings.StimulusWaitMin = 500f;
* The minimum amount of time in milliseconds before a stimulus can appear after the offset of the previous stimulus.

StellarProspector.Settings.DistractorWaitMax = 10000f;
* The maximum amount of time in milliseconds before a distractor must appear after the offset of the previous distractor.

StellarProspector.Settings.DistractorWaitMin = 2000f;
* The minimum amount of time in milliseconds before a distractor can appear after the offset of the previous distractor.

StellarProspector.Settings.DistractorLifeMax = 10000f;
* The maximum amount of time in milliseconds that a distractor can live for after it has been created.

StellarProspector.Settings.DistractorLifeMin = 2000f;
* The minimum amount of time in milliseconds that a distactor must live for after it has been created.

StellarProspector.Settings.StimulusLifeMax = 6000f;
* The maximum time in milliseconds that a stimulus can be displayed.

StellarProspector.Settings.StimuliPerCueMin = 1;
* The minimum number of stimuli that must appear before the cued sector can change.

StellarProspector.Settings.StimuliPerCueMax = 1;
* The maximum number of stimuli that can appear before the cued sector must change.

StellarProspector.Settings.MaxProgress = 100;
* The amount of progress needed to completely finish the game. This is in arbitrary units.

StellarProspector.Settings.PeripheralProgress = 5;
* The maximum amount of progress the player can receive from correctly responding to peripheral stimuli. In the same arbitrary units as max progress.

StellarProspector.Settings.ProgressLostPerMiss = 1;
* The amount of progress lost anytime an incorrect response is given

StellarProspector.Settings.CentralStimulusProgressDrain = 1;
* Amount of progress drained every 2 seconds during a central stimulus

StellarProspector.Settings.UseFlickering = false;
* Determines whether or not to use flickering

StellarProspector.Settings.AutoCalculateFlickering = true;
* Whether the frames on/off and intensities of the flickering effect are automatically calculated by the frequency or are just taken from the manually set values.

StellarProspector.Settings.CenterHertz = 6.67;
* The rate at which the center sector flickers per second

StellarProspector.Settings.CenterOnFrames = 4;
* How many frames (out of 60 frames per second) in a row does the center sector remain flickered on

StellarProspector.Settings.CenterOffFrames = 5;
* How many frames (out of 60 frames per second) in a row does the center sector remain flickered off

StellarProspector.Settings.CenterIntensity = 1.25;
* The percentage of intensity of the center sector when it is flickered on. 1.0 denotes 100% intensity.

StellarProspector.Settings.Sector1Hertz = 8.57;
* The rate at which sector one flickers per second

StellarProspector.Settings.Sector1OnFrames = 3;
* How many frames (out of 60 frames per second) in a row does sector one remain flickered on

StellarProspector.Settings.Sector1OffFrames = 4;
* How many frames (out of 60 frames per second) in a row does sector one remain flickered off

StellarProspector.Settings.Sector1Intensity = 1.33;
* The percentage of intensity of sector one when it is flickered on. 1.0 denotes 100% intensity.

StellarProspector.Settings.Sector2Hertz = 10;
* The rate at which sector two flickers per second

StellarProspector.Settings.Sector2OnFrames = 3;
* How many frames (out of 60 frames per second) in a row does sector two remain flickered on

StellarProspector.Settings.Sector2OffFrames = 3;
* How many frames (out of 60 frames per second) in a row does sector two remain flickered off

StellarProspector.Settings.Sector2Intensity = 1.0;
* The percentage of intensity of sector two when it is flickered on. 1.0 denotes 100% intensity.

StellarProspector.Settings.Sector3Hertz = 12;
* The rate at which sector three flickers per second

StellarProspector.Settings.Sector3OnFrames = 2;
* How many frames (out of 60 frames per second) in a row does sector three remain flickered on

StellarProspector.Settings.Sector3OffFrames = 3;
* How many frames (out of 60 frames per second) in a row does sector three remain flickered off

StellarProspector.Settings.Sector3Intensity = 1.5;
* The percentage of intensity of sector three when it is flickered on. 1.0 denotes 100% intensity.

StellarProspector.Settings.Sector4Hertz = 15;
* The rate at which sector four flickers per second

StellarProspector.Settings.Sector4OnFrames = 2;
* How many frames (out of 60 frames per second) in a row does sector four remain flickered on

StellarProspector.Settings.Sector4OffFrames = 2;
* How many frames (out of 60 frames per second) in a row does sector four remain flickered off

StellarProspector.Settings.Sector4Intensity = 1.0;
* The percentage of intensity of sector four when it is flickered on. 1.0 denotes 100% intensity.

==Keyboard Configuration==

Keyboard bindings are stored in a separate file, also specific to each minigame. For example, the keyboard bindings for the ColonySim could be found at [Installation Directory]\testkeybindings.txt (Default: "C:\Program Files\Autism Collaborative\testkeybindings.txt"). It is stored as a list of in-game events, each followed by the action that triggers it.

Quit Escape
* Trigger the Quit event when Escape is pressed.

PlaceBuilding Left mouse
* Trigger the PlaceBuilding event when the Left ''Mouse Button'' is pressed.

ZoomInStop OemPlus released
* Trigger the ZoomInStop event when the Plus Key is ''released''.

==Logging==

The current default path for the log file is in the Application Data folder. The exact location will vary depending on the operating system installed.

Vista: C:\Users\[WindowsLoginName]\Documents\Roaming\Autism Collaborative\

XP: C:\Documents and Settings\[WindowsLoginName]\My Documents\Autism Collaborative\

The documentation for the building placement log for the Colony Simulation can be found here -> [[Building_Placement_Log_Specification]].

End-user Setup

2009-02-03T18:38:09Z

2008-07-04T19:20:13Z

2008-07-04T17:29:01Z

Mcd8604: /* Phases */

Spaceship Shenanigans

2008-07-04T17:16:41Z

Mcd8604: /* Gameplay */

==Summary==

This game resembles the arcade game Missile Command. Tests focus on the Posner paradigm, distribution and shifting of attention, and the effect of multimodal (auditory and visual) stimuli.

==Premise==

The colony is in need of raw material resources. You are in control of the colony's Resource Gatherer. Use its tractor beam to collect as many resources as possible.

==Objective==

Collect as many resources as possible.

==Characters==

Colony Resource Gatherer

[[Image:ComingSoon.png]]

Resource/Ore:

[[Image:ComingSoon.png]]

==Specifications==

===Game Screen===

The game screen is a semi-circle divided into a central (d1) sector and 4 intermediate (d2) and peripheral (d3) sectors.

(image link)

Sector d1 is a fills the player's visual field (1.78 degrees at a 50 cm viewing distance is 15.5 mm). This sector corresponds to the resource gatherer's control panel.

The d2 sectors make up the alert system of the resource gatherer.

The d3 sectors are monitors of outer space.
(The diameter of sector d3 is currently equal to the width of the game screen - 800 px in the demo)

===Flashing===

(update this)

==Gameplay==

The player is inside the control room of the colony's resource gatherer.

There are two main tasks for the player:

1 - The player must respond, by pressing the Down arrow, when a bad ore is detected and displayed by the control panel.

2 - The player must respond, by pressing the Up arrow, when an ore appears in any of the d3 sectors.

==Phases==

===Gathering Phase===

====Player====

The player controls the Resource Collector, at the bottom-center of the screen, floating somewhere in space. This can rotate left and right. The Resource Collector is capable of firing a tractor beam. The player presses the Up-arrow key to fire the tractor beam.

====Resource Detection System====

Display a large, 10 hz (50% duty cycle) flashing arrow at the bottom of the screen, under the location that the stimulus will appear. The arrow appears either 100 ms (one flash) or 800 ms (eight flashes) prior to the materialization of the cargo and remains until the cargo materializes.

<div style="color: #aa0000;">Not "under" the location, but rather at the bottom centre of the display (i.e. on top of the resource collector) pointing to the location. A purely symbolic cue will always appear in the same location on the display, that is, the location of the cue will bear no relation at all to the location of the target. If the SPATIAL *location* of the arrow rather than (or even in addition to) the SYMBOLIC *direction* of the arrowhead signifies the expected location of the cargo, then the arrow becomes a mixture of symbolic and spatial cueing. We want either a purely symbolic cue or a purely spatial cue. If you want to do a purely spatial cue, you could just flash something in the location at which the cargo is expected to appear. That might be simpler for the game play.</div>

The resource detection system is fallible. 20% of the time, it indicates an invalid alert.
'''(TODO: determine position of invalid warning)'''

This aspect of the task combines a variation of a centrally cued Posner attention paradigm (testing effects of cue validity and cue-target onset asynchrony) (Posner et al. 1987).

====Starfield Passive Stimulus====

The background of space is cluttered with stars.

Prior to the cue-target appearing, random stars blink/sparkle at 10 blinks/sparkles per second.
'''(TODO: Determine distance/distribution)'''

====Resource Stimulus====

Following the resource detection alert, a resource will appear on the screen. At this time, the player will have control to rotate and activate the tractor beam. The first button pressed will be considered the reaction.
'''(TODO: Determine random resource distribution)'''

The resource will slowly lose point value over time, disappearing over the duration of 6000 ms. A subtle particle affect will convey the resource as disintigrating.
Once the tractor beam has been actived or the duration has elapsed, the player will no longer be able to move.

===Unimodal vs. Multimodal Phase===

An system activates a stimulus in one of three different conditions of sensory modality:

'''Unisensory Visual'''

'''Multisensory Audiovisual'''

The arrow is accompanied by a klaxon (100 hz square wave modulated at 10 hz in synchrony with the arrow).

'''Unisensory Auditory'''

The klaxon alone. <div style="color: #aa0000;">If we were to go to two quadrants instead of four (i.e., placing the base at the bottom of the display instead of in the centre), we could perhaps use a monaural (left or right) klaxon to give some directional information, akin to the valid or invalid direction cue that's given by the arrow.</div>

<div style="color: #0000ff;">Would it be better to remove directional specificity from the test altogether to focus strictly on the multi-modal aspect?</div>

<div style="color: #aa0000;">I have thought about this, and on reflection, we can go with the plain, non-directional klaxon. It seems useful to "kill two birds with one stone," as it were, in getting both a Posner attention-shifting paradigm and a unimodal-multimodal paradigm out of the same single task, if we can pack both in.</div>

This aspect of the task is a test of multimodal (audiovisual) integration. (Senkowski, Molholm,
Gomez-Ramirez, Foxe)(auditory_visual_integration_2006.pdf)

==Scoring==

Cash is awarded for each resource collected. (The cash values will be determined along with the Colony Simulator design)

Spaceship Shenanigans

2008-06-20T21:22:06Z

Mcd8604:

Mini Game Scenarios

2008-06-18T00:12:24Z

Mcd8604:

==Scenarios==
<table style="border: solid;">
<tr><th>Inside Colony</th><th>Both</th><th>Outside Colony</th></tr>
<tr><td>Medicine/Hospital</td><td>Resource Gathering/Mining</td><td>Navigation</td></tr>
<tr><td>Research/Edumacation/Monkey Test Labs</td><td>Repairs Planets</td></tr>
<tr><td>Farms/Agriculture</td><td>Asteroids</td><td>Meteors/Comets</td></tr>
<tr><td>Factories/Industry</td><td>Aliens/ETs/space pirates/ninjas</td><td>Black Holes</td></tr>
<tr><td>Power</td><td>Plants</td><td>Gravity</td></tr>
<tr><td>Leisure/Recreation</td><td>Space Fishing</td></tr>
<tr><td>Construction/Architecture</td><td>Refueling</td></tr>
</table>

==Mini-game Ideas==
*Successfully completing a mini-game can upgrade or improve efficiency of a building or technology.
===Medicine===
*Mixing/Alchemy/Pharmacy/Herbology
*Repairing an arm/Operating room
===Research/Education===
*Trick question game (test for literal interpretation?)
*Memory games
===Farm/Agriculture===
*Farm simulation
*Harvesting game – picking ripe foods (symbolic cue)
*Livestock Breeding / Crossbreeding (like chocobos)
===Factory/Industry===
*Factory frenzy
*Quality assurance – item inspection
**Circuit boards / electronics
**Toys
**Spaceships
*Assembly Line / Building product
===Power Plant===
*Solar panel construction (like Tetris)
===Leisure===
*Theme park
*Carnival games
**Ring toss
**Water guns
**Duck slinger
**Baseball throw
**Catching goldfish
===Construction/Architecture===
*Lego style – replicating things
*Finding flaws in blueprints (similar to quality assurance)
*Making cement
*Terrain (de)formation
*Sims type of house creation
===Resource Gathering/Mining===
*Puzzle style – like columns
*Breakout
*Picture finding (Where’s Waldo)
*Detecting and collecting asteroids
===Repairs===
*Tetris type game, carpentry
*Glass crack repair
*Electric repair
**mess of wires, line up and connect the correct ones
===Navigation===
*Forced scrolling
**clear a path through asteroid belt
**dodging asteroids – like Battletoads, show blinking alert, move left or right
*Mazes
*Sound / sonar
===Aliens, etc..===
*Defense game (Spaceship Shenanigans)
*Diplomacy
===Gravity===
*Inside core of colony – physics puzzles to fix gravity
*(use (planetary) gravity in navigation)
===Refueling===
*Line up the fuel pump with the ship - precision flying
*Pipe organizing