The attached data files in "EvaluationLunarLandingAutomation.tar" contain the data and documents necessary to recreate the cognitive process model presented in Zarrin K. Chau's 2013 dissertation "System design considerations for human-automation function allocation during lunar landing," from the Georgia Institute of Technology. The folder contains all of the files used to design an experiment conducted at Johnson Space Center with the NASA Astronaut Office. 

This set of files are effectively complete as of August 2013, and have no further revisions. Caveats regarding these files include: The engine scenario was determined to be not representative of what it actually would be in reality, so it was removed from the data. Specifically, the fuel consumption values are not accurate for those runs.

Period of experimentation was August 2012, and data collection occurred at the NASA Johnson Space Center, Houston, TX 77058.

Area of Investigation: Astronaut decision-making process during lunar landing in areas around the South Pole of the Moon. 

Data Creators: Karen M. Feigh, Principal Investigator, Aerospace Engineering, Georgia Institute of Technology; Robert L. Hirsh, Principal Investigator, NASA Johnson Space Center; Zarrin K. Chua, Investigator/Graduate Assistant, Aerospace Engineering, Georgia Institute of Technology;

The file tree is listed below. There are a total of 1,298 files in "EvaluationLunarLandingAutomation.zip"

I. NASA_astroDMstudy_Aug2012/
   A. briefingMaterials/
      1. briefing-5-apollo.pdf: powerpoint used to provide a pre-experiment briefing for participants using the Apollo-like function allocation. Sent after the participants were recruited. 
      2. briefing-5-mode.pdf: powerpoint used to provide a pre-experiment briefing for participants using the moderate function allocation. Sent after the participants were recruited. 
      3. briefing-5-preview.pdf: powerpoint used to provide a preview of the experiment (attached during recruitment).  
   B. debriefQ/
      1. Apollo-5.docx: Set of questions used for debriefing the participants using the Apollo-like function allocation. Used during training and after each experiment run. 
      2. Moderate-5.docx: Set of questions used for debriefing the participants using the moderate function allocation. Used during training and after each experiment run. 
      3. scenarioTiming.pdf: a small analysis conducted prior to the experiment to determine how long it would take people to answer the set of debriefing questions. 
      4. thesisExpPlan_debriefViz-5.pptx: at one point, I was considering pre-printing a series of basic strategies and having the participants self-edit from this general template. Eventually decided it was faster if I drew the diagrams as they described their thought process to me. 
   C. expDesign
      1. reconfigs/ (best way to figure out which files need to be replaced is to search for the equivalent file - when operating in the ROC -  and compare between files for differences)
         i. input.USER: input file that needs to be used within the Reconfigurable Operational Cockpit in order to run the sim as it was during the experiment. 
         ii. run_alhat_apollo: input file that needs to be used within the Reconfigurable Operational Cockpit in order to run the sim as it was during the experiment. 
         iii. run_manager: (I believe one of these is needed, I'm not sure which one) input file that needs to be used within the Reconfigurable Operational Cockpit in order to run the sim as it was during the experiment. 
         iv. run_manager_roc: (I believe one of these is needed, I'm not sure which one) input file that needs to be used within the Reconfigurable Operational Cockpit in order to run the sim as it was during the experiment. 
         v. run_manager_roc2: (I believe one of these is needed, I'm not sure which one) input file that needs to be used within the Reconfigurable Operational Cockpit in order to run the sim as it was during the experiment. 
         vi. user.cfg: input file that needs to be used within the Reconfigurable Operational Cockpit in order to run the sim as it was during the experiment. 
         vii. user_env.csh: input file that needs to be used within the Reconfigurable Operational Cockpit in order to run the sim as it was during the experiment. 
      2. configs.tar.gz: the configuration folder (used for tcl coding - EDGE/DOUG visualization) that was used during the experiment, all zipped up (list of files contained in zipped folder follows). 
	    alhat_trackcam.cfg
|           input_experiment.cfg
|           kepler.cfg
|           kepler_models.cfg
|           ld_models.cfg
|           lsam_gear.cfg
|           lsam_plume.cfg
|           lunar_dust.cfg
|           planet2.cfg
|           planet2.cfg.june28
|           README
|           run_ap_b_en_configs.cfg
|           run_ap_b_li_configs.cfg
|           run_ap_b_no_configs.cfg
|           run_ap_s_en_configs.cfg
|           run_ap_s_li_configs.cfg
|           run_ap_s_no_configs.cfg
|           run_mo_b_en_configs.cfg
|           run_mo_b_li_configs.cfg
|           run_mo_b_no_configs.cfg
|           run_mo_s_en_configs.cfg
|           run_mo_s_li_configs.cfg
|           run_mo_s_no_configs.cfg
|           user_models.cfg
|           user_models.cfg.orig
|           user_models_apollo.cfg
      3. CraterCatalog.txt: this crater Catalog file needs to be used with DEMmaker, it reformats some of the craters so it doesn't cause substantial imaging issues. 
      4. CraterCatalog.txt.orig: original crater catalog file for DEMmaker. 
      5. DoE.ods: the design of experiments considered for this experiment. Sheet1 is just crap. committee is stuff I prepped for the committee and has a bunch of different designs. greenVars is what was actually used at some point, especially when I was considering between 6 and 8 runs. 
      6. gui.tar.gz: the configuration folder (used for tcl coding - EDGE/DOUG visualization) that was used during the experiment, all zipped up (list of files contained in zipped folder follows). 
          alhat_camera_control.tcl
|   |   ALHAT_input.key
|   |   altair_lunar_terrain.tcl
|   |   elevation_of_lander.tcl
|   |   elevation_profile.tcl
|   |   heading_pitch_roll.tcl
|   |   heading_pitch_roll.tcl.orig
|   |   input_hx.tcl
|   |   joystick2_alhat.tcl
|   |   joystick_control.tcl
|   |   joystick_control.tcl-noAlgorithm
|   |   joystick_control.tcl.contROD
|   |   joystick_control.tcl.noBigMovement
|   |   joystick_control.tcl.p66
|   |   joystick_control.tcl.usesFlightMode
|   |   joystick_control.tcl.working
|   |   joystick_control.tcl~
|   |   joystick_usb.tcl
|   |   landing_gear_position.tcl
|   |   logfile.tcl
|   |   logfile.tcl.orig
|   |   lsam_main_plume_visibility.tcl
|   |   lsam_plumes.tcl
|   |   lunar_dust_visibility.tcl
|   |   moon_rotator.tcl
|   |   mousefly.tcl
|   |   README
|   |   rocuei_alhat.tcl
|   |   roc_button_control.tcl
|   |   roc_button_panel.tcl
|   |   tmr.txt
|   |   trick2edge.tcl
|   |   
|   +---images
|   |       guard.gif
|   |       guardH.gif
|   |       toggleBigDown.gif
|   |       toggleBigUp.gif
|   |       toggleDown.gif
|   |       toggleLeft.gif
|   |       toggleMid.gif
|   |       toggleMidH.gif
|   |       toggleNut.gif
|   |       toggleRight.gif
|   |       toggleUp.gif
|   |       
|   +---oldCopiesJoystick
|   |       joystick2_alhat.tcl.ete
|   |       joystick2_alhat.tcl.orig
|   |       joystick_control.tcl-0726
|   |       joystick_control.tcl.ete
|   |       joystick_control.tcl~
|   |       joystick_usb.tcl-0726
|   |       joystick_usb.tcl-~~
|   |       joystick_usb.tcl.ete
|   |       
|   +---overlays
|   |   |   scene_overlay.tcl
|   |   |   scene_overlay.tcl-0726
|   |   |   viewport_overlay.tcl
|   |   |   viewport_overlay.tcl-0726
|   |   |   viewport_overlay.tcl-0727
|   |   |   viewport_overlay.tcl-usesACmodels
|   |   |   viewport_overlay.tcl.june
|   |   |   viewport_overlay.tcl.june5
|   |   |   viewport_overlay.tcl.usesFlightMode
|   |   |   viewport_overlay.tcl.working
|   |   |   viewport_overlay.tcl~
|   |   |   v_o.tcl
|   |   |   v_o.tcl~
|   |   |   
|   |   +---scene
|   |   |       distance_markers.tcl
|   |   |       fuel_circles.tcl
|   |   |       fuel_circles.tcl-0410
|   |   |       fuel_circles.tcl-zkc
|   |   |       fuel_circles.tcl.older
|   |   |       fuel_circles.tcl~
|   |   |       landing_hazards.tcl
|   |   |       landing_select.tcl
|   |   |       landing_site_flags.tcl
|   |   |       landing_site_flags.tcl~
|   |   |       landing_site_icons.tcl
|   |   |       landing_site_icons.tcl.orig
|   |   |       landing_site_icons.tcl_
|   |   |       landing_site_icons.tcl~
|   |   |       lsam_footprint.tcl
|   |   |       lsam_icon.tcl
|   |   |       
|   |   +---viewport
|   |   |       altitude_bar.tcl
|   |   |       distance_marker.tcl
|   |   |       distance_marker.tcl.1
|   |   |       distance_marker.tcl.working
|   |   |       engine_gauge.tcl
|   |   |       fuel_bar.tcl
|   |   |       hdot_indicator.tcl
|   |   |       heading_pitch_roll.tcl
|   |   |       heading_pitch_roll.tcl.dontuse
|   |   |       lpd_predictor.tcl
|   |   |       ls_selection.tcl
|   |   |       ov_altitude_tape.tcl
|   |   |       ov_altitude_tape.tcl.dontuse
|   |   |       ov_altitude_tape.tcl.june7
|   |   |       ov_vert_sit.tcl
|   |   |       ov_vert_sit.tcl.dontuse
|   |   |       ov_vert_sit.tcl.june7
|   |   |       progress_bar.tcl
|   |   |       range_bar.tcl
|   |   |       screen_control.tcl
|   |   |       screen_control.tcl.orig
|   |   |       screen_control.tcl.usesFlightMode
|   |   |       text_overlays.tcl
|   |   |       text_overlays2.tcl
|   |   |       text_overlays2.tcl.june20
|   |   |       tfd_altitude_tape.tcl.dontuse
|   |   |       tfd_altitude_tape2.tcl
|   |   |       tfd_heading.tcl
|   |   |       tfd_pitch.tcl
|   |   |       tfd_pitch.tcl~
|   |   |       tfd_roll.tcl
|   |   |       tfd_vertical_speed.tcl.dontuse
|   |   |       tfd_vertical_speed2.tcl
|   |   |       tfd_vertical_speed_review.tcl
|   |   |       velocity_vector_box.tcl
|   |   |       velocity_vector_box2.tcl
|   |   |       vertSitProjectedPath.txt
|   |   |       warning_overlay.tcl
|   |   |       warning_overlay.tcl.clean
|   |   |       warning_overlay.tcl.dspcanvas
|   |   |       warning_overlay.tcl.june5
|   |   |       
|   |   \---viewport.orig
|   |           altitude_bar.tcl
|   |           distance_marker.tcl
|   |           distance_marker.tcl.1
|   |           distance_marker.tcl.working
|   |           engine_gauge.tcl
|   |           fuel_bar.tcl
|   |           hdot_indicator.tcl
|   |           heading_pitch_roll.tcl
|   |           heading_pitch_roll.tcl.dontuse
|   |           ls_selection.tcl
|   |           ov_altitude_tape.tcl
|   |           ov_altitude_tape_back.tcl
|   |           ov_vert_sit.tcl
|   |           ov_vert_sit_back.tcl
|   |           progress_bar.tcl
|   |           range_bar.tcl
|   |           screen_control.tcl
|   |           screen_control.tcl.orig
|   |           screen_control.tcl.usesFlightMode
|   |           text_overlays.tcl
|   |           text_overlays2.tcl
|   |           tfd_altitude_tape.tcl
|   |           tfd_altitude_tape2.tcl
|   |           tfd_heading.tcl
|   |           tfd_pitch.tcl
|   |           tfd_pitch.tcl~
|   |           tfd_roll.tcl
|   |           tfd_vertical_speed.tcl
|   |           tfd_vertical_speed2.tcl
|   |           velocity_vector_box.tcl
|   |           velocity_vector_box2.tcl
|   |           vertSitProjectedPath.txt
|   |           
|   \---util
|           alhat_library.tcl
|           determine_alhat_monitor_list.tcl
|           dynamic_menu.tcl
|           dynamic_menu.tcl.tcl
   D. expTraining/
      1. answerKey-justSafe/
         i.     prac[1/2/3]_[01/02/03/04/05/06/07/08/09/10]_[ap/mo]_[b/s]_[no/en/li]_[1/2/3].jpg: a series of answer keys (color-coded based on score of landing site, green is great, red is bad) for different practice scenarios. There are three practice sessions (in case the participants really wanted a lot of different practice), that's indicated by the first and last number. There are ten different scenarios (second number), the description is indicated by the third, fourth, and fifth designations: ap: apollo, mo: moderate; b: baseline, s: shallow; no: nominal, en: engine, li: LIDAR. (full list of files in expTraining follows). 
                    prac1_01_ap_s_no_1.jpg
    |   |           prac1_02_ap_s_li_1.jpg
    |   |           prac1_03_ao_s_en_1.jpg
    |   |           prac1_04_ap_b_en_1.jpg
    |   |           prac1_05_ap_b_li_1.jpg
    |   |           prac1_06_mo_s_no_1.jpg
    |   |           prac1_07_mo_s_li_1.jpg
    |   |           prac1_08_mo_s_en_1.jpg
    |   |           prac1_09_mo_b_en_1.jpg
    |   |           prac1_10_mo_b_li_1.jpg
    |   |           prac2_01_ap_s_no_2.jpg
    |   |           prac2_02_ap_s_li_2.jpg
    |   |           prac2_03_ap_s_en_2.jpg
    |   |           prac2_04_ap_b_en_2.jpg
    |   |           prac2_05_ap_b_li_2.jpg
    |   |           prac2_06_mo_s_no_2.jpg
    |   |           prac2_07_mo_s_li_2.jpg
    |   |           prac2_08_mo_s_en_2.jpg
    |   |           prac2_09_mo_b_en_2.jpg
    |   |           prac2_10_mo_b_li_2.jpg
    |   |           prac3_01_ap_s_li_3.jpg
    |   |           prac3_02_ap_s_li_3.jpg
    |   |           prac3_03_ap_b_en_3.jpg
    |   |           prac3_04_ap_b_li_3.jpg
    |   |           prac3_05_mo_s_li_3.jpg
    |   |           prac3_06_mo_s_en_3.jpg
    |   |           prac3_07_mo_b_en_3.jpg
    |   |           prac3_08_mo_b_li_3.jpg
    |   |           
   E. media/
     >briefingScript.txt
     >Photo Jul 06, 15 57 26.jpg
     >Photo Jul 06, 15 57 28.jpg
     >Photo Jul 06, 15 57 36.jpg
     >Photo Jul 19, 11 07 42.jpg
     >Photo Jul 19, 11 07 52.jpg
     >Photo Jul 19, 11 08 00.jpg
     >Photo Jul 27, 10 39 50.jpg
     >Photo Jul 27, 10 43 44.jpg
     >Photo Jul 27, 10 43 52.jpg
     >Photo Jul 27, 10 49 14.jpg
     >Photo Jul 27, 10 49 23.jpg
     >Photo Jul 27, 10 49 27.jpg
     >Photo Jul 27, 10 49 41.jpg
     >photo_1.JPG
     >Video Jul 06, 15 53 51.mp4
     >Video Jul 06, 15 57 00.mp4   
   F. rawMaps/
      1. baseline/
         > city_[annapolis/fargo/honolulu/littlerock/madison/tulsa/vegas]_baseline_alg.jpg: graphic of the DEM + slope created at one of those regions (900 x 900 px, see thesis for coordinates)
         > city_[annapolis/fargo/honolulu/littlerock/madison/tulsa/vegas]_baseline_alg_slope.img: slope of DEM created at one of those regions (900 x 900 px, see thesis for coordinates)
         > city_[annapolis/fargo/honolulu/littlerock/madison/tulsa/vegas]_b_sites.jpg: graphic of the DEM + slope created at one of those regions (900 x 900 px, see thesis for coordinates)
      2. baseline-offnom/
         > city_[annapolis/fargo/honolulu/littlerock/madison/tulsa/vegas]_base-offnom_alg.jpg: graphic of the DEM + slope created at one of those regions (900 x 900 px, see thesis for coordinates) but for the off-nominal scenario
         > city_[annapolis/fargo/honolulu/littlerock/madison/tulsa/vegas]_base-offnom_alg_slope.img: slope of DEM created at one of those regions (900 x 900 px, see thesis for coordinates) but for the off-nominal scenario 
         > city_[annapolis/fargo/honolulu/littlerock/madison/tulsa/vegas]_bon_sites.jpg:: graphic of the DEM + slope created at one of those regions (900 x 900 px, see thesis  for coordinates) for the off-nominal scenario
      3. officialMapData/
         > [area/continent/country/hemisphere/region].cdat, .rdat, .wcdat: input files for the step-sizing DEMs (as DEMmaker cannot go straight to something small) and creating the cities/states. 
         > [area/continent/country/hemisphere/region]DEM.IMG: actual DEM for the step-sizing DEMs (as DEMmaker cannot go straight to something small) and creating the cities/states. 
         > [area/continent/country/hemisphere/region]DEM.IMG.2011-288T12-00-00.000.tex.img, .jpg, .lbl: shading for the step-sizing DEMs (as DEMmaker cannot go straight to something small) and creating the cities/states. 
         > [area/continent/country/hemisphere/region]DEM.LBL: label file for the DEM for the step-sizing DEMs (as DEMmaker cannot go straight to something small) and creating the cities/states. 
         > city_[annapolis/fargo/honolulu/littlerock/madison/tulsa/vegas].cdat, .rdat, .wcdat: actual DEM for the step-sizing DEMs (as DEMmaker cannot go straight to something small) and creating the cities/states
         > city_[annapolis/fargo/honolulu/littlerock/madison/tulsa/vegas]DEM.IMG: actual DEM for the step-sizing DEMs (as DEMmaker cannot go straight to something small) and creating the cities/states. 
         > city_[annapolis/fargo/honolulu/littlerock/madison/tulsa/vegas]DEM.IMG.2011-288T12-00-00.000.tex.img, .jpg, .lbl: label file for the DEM for the step-sizing DEMs (as DEMmaker cannot go straight to something small) and creating the cities/states. 
         > city_[annapolis/fargo/honolulu/littlerock/madison/tulsa/vegas]DEM.IMG_slope.tex.img, .lbl: slope file for the DEM in the city/states
         > city_[annapolis/fargo/honolulu/littlerock/madison/tulsa/vegas]DEM.LBL: label file for the DEM for the step-sizing DEMs (as DEMmaker cannot go straight to something small) and creating the cities/states. 
         > city_[annapolis/fargo/honolulu/littlerock/madison/tulsa/vegas]_blank.jpg: blank image of the shading for these specific sites. 
         > city_[annapolis/fargo/honolulu/littlerock/madison/tulsa/vegas]s_hazEdge.jpg: an outline of all of the major hazards within the area. 
         > city_[annapolis/fargo/honolulu/littlerock/madison/tulsa/vegas]_slope.jpg: a graphic of just the hazardous areas (in red). 
         > state_[arkansas/hawaii/maryland/ndakota/nevada/ok/wisconsin].cdat, .rdat, .wcdat: actual DEM for the step-sizing DEMs (as DEMmaker cannot go straight to something small) and creating the cities/states
         > state_[arkansas/hawaii/maryland/ndakota/nevada/ok/wisconsin]DEM.IMG: actual DEM for the step-sizing DEMs (as DEMmaker cannot go straight to something small) and creating the cities/states. 
         > state_[arkansas/hawaii/maryland/ndakota/nevada/ok/wisconsin]DEM.IMG.2011-288T12-00-00.000.tex.img, .jpg, .lbl: label file for the DEM for the step-sizing DEMs (as DEMmaker cannot go straight to something small) and creating the cities/states. 
         > state_[arkansas/hawaii/maryland/ndakota/nevada/ok/wisconsin]DEM.LBL: slope file for the DEM in the city/states
      4. shallow/
         > city_[annapolis/fargo/honolulu/littlerock/madison/tulsa/vegas]_shallow_alg.jpg: graphic of the DEM + slope created at one of those regions (900 x 900 px, see thesis for coordinates)
         > city_[annapolis/fargo/honolulu/littlerock/madison/tulsa/vegas]_shallow_alg_slope.img: slope of DEM created at one of those regions (900 x 900 px, see thesis for coordinates)
         > city_[annapolis/fargo/honolulu/littlerock/madison/tulsa/vegas]_s_sites.jpg: graphic of the DEM + slope created at one of those regions (900 x 900 px, see thesis for coordinates)
      5. shallow-offnom/
         > city_[annapolis/fargo/honolulu/littlerock/madison/tulsa/vegas]_shallow-offnom.jpg: graphic of the DEM + slope created at one of those regions (900 x 900 px, see thesis for coordinates)
         > city_[annapolis/fargo/honolulu/littlerock/madison/tulsa/vegas]_offnom_shallow_alg_slope.img: slope of DEM created at one of those regions (900 x 900 px, see thesis for coordinates)
         > city_[annapolis/fargo/honolulu/littlerock/madison/tulsa/vegas]_son_sites.jpg: graphic of the DEM + slope created at one of those regions (900 x 900 px, see thesis for coordinates)
   G. scoringAlgorithms/
      1. mapScoring.m: a matlab code that scores the maps and produces all of the answer keys. 
      2. slopeMapAlgorithm.m: a matlab code that extracts slope information from anything that is *_slope.img
II. NASA_astroDMstudy_results/
   A. expectations/
      1. b_li-tulsa_combined.xcf: a GIMP file with individual expectations maps (reproduced from what they drew for me during the debriefing), where each of the pilots landed, the automation suggested sites, and a compilation map of everybody's expectations maps. 
      2. b_no-fargo_combined.xcf: a GIMP file with individual expectations maps (reproduced from what they drew for me during the debriefing), where each of the pilots landed, the automation suggested sites, and a compilation map of everybody's expectations maps. 
      3. s_li-vegas_combined.xcf: a GIMP file with individual expectations maps (reproduced from what they drew for me during the debriefing), where each of the pilots landed, the automation suggested sites, and a compilation map of everybody's expectations maps. 
      4. s_no-annapolis_combined.xcf: a GIMP file with individual expectations maps (reproduced from what they drew for me during the debriefing), where each of the pilots landed, the automation suggested sites, and a compilation map of everybody's expectations maps. 
   B. rawExpResults/
      1-13. 101/, 102/, 104/, 105/, 106/, 107/, 108/, 109/, 110/, 111/, 112/, 113/, 115/
         i. 2012-08-01_10.24.43/
            a. AGNC_[AfmOutput/ContInput/ContOutput/ContOutput_DEBUG/GuidInput/GuidOutput/GuidOutput_DEBUG/NavOutput].csv
         ii. 2012-08-01_10.33.14/
            a. AGNC_[AfmOutput/ContInput/ContOutput/ContOutput_DEBUG/GuidInput/GuidOutput/GuidOutput_DEBUG/NavOutput].csv: a series of output files from the Trick sim. contains state information per time. AfmOutput: output from the AFM; ContInput: input into the control system; ContOutput: output from the contrl system; ContOutput_DEBUG: used for debugging; GuidInput: input into guidance system; GuidOutput_DEBUG: output from the guidance system; NavOutput: output from the Nav system. I believe there is a timing error in all of these - for some reason the system did not record all the way to landing. I also didn't build these files so I don't know what's in all of the columns either. 
         iii. 2012-08-01_10.42.01/
            a. AGNC_[AfmOutput/ContInput/ContOutput/ContOutput_DEBUG/GuidInput/GuidOutput/GuidOutput_DEBUG/NavOutput].csv: a series of output files from the Trick sim. contains state information per time. AfmOutput: output from the AFM; ContInput: input into the control system; ContOutput: output from the contrl system; ContOutput_DEBUG: used for debugging; GuidInput: input into guidance system; GuidOutput_DEBUG: output from the guidance system; NavOutput: output from the Nav system. I believe there is a timing error in all of these - for some reason the system did not record all the way to landing. I also didn't build these files so I don't know what's in all of the columns either. 
         iv. 2012-08-01_10.51.23/
            a. AGNC_[AfmOutput/ContInput/ContOutput/ContOutput_DEBUG/GuidInput/GuidOutput/GuidOutput_DEBUG/NavOutput].csv: a series of output files from the Trick sim. contains state information per time. AfmOutput: output from the AFM; ContInput: input into the control system; ContOutput: output from the contrl system; ContOutput_DEBUG: used for debugging; GuidInput: input into guidance system; GuidOutput_DEBUG: output from the guidance system; NavOutput: output from the Nav system. I believe there is a timing error in all of these - for some reason the system did not record all the way to landing. I also didn't build these files so I don't know what's in all of the columns either. 
         v. 2012-08-01_10.59.44/
            a. AGNC_[AfmOutput/ContInput/ContOutput/ContOutput_DEBUG/GuidInput/GuidOutput/GuidOutput_DEBUG/NavOutput].csv: a series of output files from the Trick sim. contains state information per time. AfmOutput: output from the AFM; ContInput: input into the control system; ContOutput: output from the contrl system; ContOutput_DEBUG: used for debugging; GuidInput: input into guidance system; GuidOutput_DEBUG: output from the guidance system; NavOutput: output from the Nav system. I believe there is a timing error in all of these - for some reason the system did not record all the way to landing. I also didn't build these files so I don't know what's in all of the columns either. 
         vi. 2012-08-01_11.08.18/
            a. AGNC_[AfmOutput/ContInput/ContOutput/ContOutput_DEBUG/GuidInput/GuidOutput/GuidOutput_DEBUG/NavOutput].csv: a series of output files from the Trick sim. contains state information per time. AfmOutput: output from the AFM; ContInput: input into the control system; ContOutput: output from the contrl system; ContOutput_DEBUG: used for debugging; GuidInput: input into guidance system; GuidOutput_DEBUG: output from the guidance system; NavOutput: output from the Nav system. I believe there is a timing error in all of these - for some reason the system did not record all the way to landing. I also didn't build these files so I don't know what's in all of the columns either. 
         vii. EDGE_[101/102/104/105/106/107/108/109/110/111/112/113/115].rtf: rich text file of my compilation of each person's experience and button presses from the EDGE output. 
         viii. EDGE_[101/102/104/105/106/107/108/109/110/111/112/113/115].txt: text file of my compilation of each person's experience and button presses from the EDGE output. 
         iv. exp_log_[101/102/104/105/106/107/108/109/110/111/112/113/115].txt: auto-generated text file of my compilation of each person's experience and button presses from the EDGE output. 

   C. statisticsSheets/
      *Original file were analyzed and stored in SPSS; for preservation and access, files have been converted to either .csv or .ods.
      1. Cuecorrelation.csv: determines if there was a correlation between cues, SPSS file (either data or output). 
      2. cueCorrelationOutput.ods: determines if there was a correlation between cues, SPSS file (either data or output). 
      3. demographicsOutput.ods: used to come up with counts of different responses, means, etc. 
      4. impactCovariatesOutput.ods: what is the impact of covariates such as level of astronaut training, SPSS file
      5. impactMainEffectsOutput.ods: what is the impact of the main effects (automation, trajectory, scenario) on the dependent variables, SPSS file
      6. impactMainEffects_fullOutput.ods: what is the impact of the main effects (automation, trajectory, scenario) on the dependent variables, SPSS file (data modified)
      7. impactMainEffects_full2Output.ods: what is the impact of the main effects (automation, trajectory, scenario) on the dependent variables, SPSS file (data removed)
      8. impactOfStratOnTimeOutput.ods: impact of strategies on timing (expectations
      9. mmEffectsOutput.ods
      10. rowPart_full_2sansEngineNewLSS.csv: all of the data, with each participant on a singular row. 
      11. rowRun_full_2sansEngineNewLSS.csv: all of the data, with each run on each row. 
      12. sansEngineOutput.ods: this data doesn't have anything from the engine runs. 
      13. sansEngineNewLSSOutput.ods: this data doesn't have the engine runs AND has the new LSS calculation. 
      14. sansEngineNewLSS_searchOutput.ods: this data doesn't have the engine runs, has the new LSS calculation, and listing of the search pattern used. 
      15. stratCompare.csv: comparison of the different strategies used. 
   D. statsResultsSummaries/
      1. statsAnalysis-3.pdf: statistical analysis results, in pptx, with one question per slide. 
      2. statsAnalysis.pdf: statistical analysis results, in pptx, with one question per slide! 
      3. stratCritUsage-graphics.pdf: graphics for each of these stats analysis 
      4. stratCritUsage.pdf: usage of criteria and all of the strategies. 
   E. taskDiagrams/
      1. taskDiag-all.pdf: strategies represented in a task diagram of all of the participants. 
      2. taskDiag-ap.pdf: strategies represented in a task diagram of just those using apollo-like automation. 
      3. taskDiag-mod.pdf: strategies represented in a task diagram of just those using moderate automation. 
   F. timeAnalysisActivity/
      1. dist-by-scen.jpg: compilation of the activities conducted by the astronauts during the session. 
      2. indivDistTimeActivity/
         a. dist-[101/102/105/106/107/108/109/110/111/112/113/115].jpg: compilation by individual
      3. mapJoystickCursor/
         a. ap_[s/b]_[en/li/no]-[101/102/105/106/107/108/109/110/111/112/113/115]-[1/2/3/4/5/6].jpg: mapping of where they moved their cursory. listed by scenario description and participant number: ap: apollo-like automation; s: shallow, b: baseline; en: engine scenario, li: LIDAR scenario, no: nominal scenario. 
      4. runDistTimeActivity/
         a. ap_[s/b]_[en/li/no]-[101/102/105/106/107/108/109/110/111/112/113/115]-[1/2/3/4/5/6]-dist.jpg: distribution of activity per scenario by participant. 
   G. transcript/
      1. displayComments.pdf: comments about the display from the participants
      2. transcription.pdf: (pdf version) a full transcript of the entire experiment including debriefing materials tucked into the end 
   H. variableWeightingAnalysis/
      1. proxLSS_variability_data_SansEngineNewLSS.mat: data for determining the change in performance due to different weights of safety or proximity to point of interest. missing the engine data and calculated with the new LSS scoring system (the new system accounts for the average LSS within the landing area, not just the center point)
      2. prox_LSS_variability_code_SansEngine.m: code that produces the different graphics.
   I. cueDistribution.ods: distribution of the different cues used during each of the scenarios. 
   J. debriefResponseSansEngineNewLSS.ods: raw data and some timing information, use this to generate the SPSS data files. 

Software used in the production, rendering, compression, and analyse of these data include the following:
DEMmaker (NASA)
Trick (NASA)
EDGE/DOUG (NASA)
SPSS
MATLAB
GIMP
Microsoft Office 2007