The attached data files in "cogProcessModel.zip" contain the data and Matlab files necessary to recreate the cognitive process model presented in Zarrin K. Chua's 2013 dissertation "System design considerations for human-automation function allocation during lunar landing," from the Georgia Institute of Technology. This set of data files are effectively complete as of July 2013 and have no further revisions. There are no caveats regarding the data outside of what is explained in the dissertation of Z.K.Chua 2013. The cognitive model was developed over the period of time from 20130104-20130228 at the Georgia Institute of Technology. The cognitive model relies on two sets of files: training.m and Apollo.m or moderate.m (this data set includes current version numbers for each within the title). Training.m is only used to set up all of the basic sensing files, interpretation, and codification of the decision making cues. It will produce a .mat file that is called up during each run of Apollo.m or Moderate.m. Having this .mat file is particularly useful to speed up the computational process as it does minimize the frequency of rote computations. Apollo.m and moderate.m handle the creating and selecting aspects dependent on the function allocation evaluated. Both codes randomly select the number and type of cues used and the relative importance for each decision. The associated cost functions and interpretations (generated through training.m) are then combined and used to generate landing site options and a final decision. To run the model from scratch (e.g., any landing site location other than these four): 1. Make sure you have MATLAB installed. 2. The cognitive process model requires the following inputs: - landing site coordinates - nominal/off-nominal flag - function allocation (apollo-like, moderatE) 3. with the landing site coordinates, use DEMmaker to produce a DEM of that area. 4. With APLNav, run a slope analysis (look at documentation/howToUseDEMmaker/UsingDEMmaker_v4.doc). These two software programs are not part of this data set and must be requested from NASA. 5. You will need to produce the following files, saved into a mapName folder that is located within dataFiles (see apollo.m or moderate.m comments for more details): - png of white background, blue dot of where automation suggested site #1 is - png of white background, blue dot of where automation suggested site #2 is - png of white background, blue dot of where automation suggested site #3 is - jpg of the DEM - jpg of the DEM + slope scan - jpg of white background, dots outlining the major craters (definition from experiment) - jpg of white background, green and red highlighting good and bad areas - jpg of white background with red highlighting of large craters - jpg of white background with red highlighting of hazards (aka slope map over white background) - jpg of slope map for baseline - jpg of slope map for shallow The areas are either hand selected or provided through another source, such as an automation system. I have included one with fauxTSAR2.m. The image files are not necessarily required in jpg or png format (when processing a large number of landing sites one may consider saving these files as matrices or some non-image format). However, the code must be modified to account for this change in input data. 6. go to mainCodes/training.m (right now it's training_v5 but if there are future versions, just use the latest one). run it and get mapName.mat output 7. run apollo.m or moderate.m and get a [filename].mat which includes three things: A) apollo_save B) apollo_save_cues C) apollo_save_strat moderate_save(z,1) = cputime - t_start; moderate_save(z,2) = siteChosen(1); moderate_save(z,3) = siteChosen(2); moderate_save(z,4) = timeChosen; moderate_save(z,5) = finalScore; moderate_save_cues(z,1:11) = cueUse(1,:); moderate_save_cues(z,12:22) = cueUse(2,:); moderate_save_cues(z,23:33) = cueWeight( 1,:); moderate_save_cues(z,34:44) = cueWeight(2,:); moderate_save_strat(z) = apStrat; apollo_save(z,1) = cputime - t_start; apollo_save(z,2) = siteChosen(1); apollo_save(z,3) = siteChosen(2); apollo_save(z,4) = timeChosen; apollo_save(z,5) = finalScore; apollo_save_cues(z,1:11) = cueUse(1,:); apollo_save_cues(z,12:22) = cueUse(2,:); apollo_save_cues(z,23:33) = cueWeight(1,:); apollo_save_cues(z,34:44) = cueWeight(2,:); apollo_save_strat(z) = apStrat The code itself has greater commentary and documentation on what each of these columns mean. 8. To view the data, use plotSites.m. It uses the output data structure (*_save_cues) from Apollo.m or Moderate.m to visualize the information. The information already collected includes: - .mat files in the same structure of *_save_cues, but for 1000 randomly generated points: 1000dataPts/Apollo/ and 1000dataPts/moderate/. Use plotSites.m to visualize. This data is a mixing of two different types of buffers of the craters. mapName-bufferAwayFromCrater/ indicates that the data assumes the lander cannot be any closer than one landing area from a large crater. The mapName/ without any designation assumes that landing right next to the crater is acceptable. - .fig files for every landing site area, identifying different properties. These data points are for every astronaut (coded with id number 1NN) for each run ([function allocation]_[trajectory type]_[nominal or off nominal scenario]). The data includes (in either .gcf or .fig format): - a figure of the astronaut's selected site overlayed on a photograph of the expected landing area (no hazard highlighting) - naked - a figure of the astronaut's selected site overlayed on a photograph of the expected landing area with hazard highlighting - back - a contour of the cost map at the landing site level based on the cues for that particular level, and a three level identification of secondary landing sites, primary landing sites, and primary landing sites that are within a landing footprint of the chosen landing site. - costMapL - plots showing the distribution of cues, weightings of cues, and timing selected by the cognitive model in comparison to the model data In total, "cogProcessModel.zip" contains 1476 files and includes the following data file formats: .m (MATLAB code), .mat (MATLAB data file), .jpg, .png, .IMG, .lbl, .fig, .xlsx, .gcf, and .doc. The file tree is listed below. > analyses/ > 1000dataPts/ > apollo/ > AP_B_LI.fig, .mat, .png: 1000 data points (500 with a one landing site buffer from large craters, 500 without the buffer) for Tulsa, the off-nominal LIDAR scenario with a baseline trajectory and an Apollo-like function allocation. The .mat file is the data, the .fig is the MATLAB figure file, the .png file is the output. > AP_B_NO.fig, .mat, .png: 1000 data points (500 with a one landing site buffer from large craters, 500 without the buffer) for Fargo, the nominal scenario with a baseline trajectory and an Apollo-like function allocation. The .mat file is the data, the .fig is the MATLAB figure file, the .png file is the output. > AP_S_LI.fig, .mat, .png: 1000 data points (500 with a one landing site buffer from large craters, 500 without the buffer) for Vegas, the off-nominal LIDAR scenario with a shallow trajectory and an Apollo-like function allocation. The .mat file is the data, the .fig is the MATLAB figure file, the .png file is the output. > AP_S_NO.fig, .mat, .png: 1000 data points (500 with a one landing site buffer from large craters, 500 without the buffer) for Annapolis, the nominal scenario with a shallow trajectory and an Apollo-like function allocation. The .mat file is the data, the .fig is the MATLAB figure file, the .png file is the output. > moderate/ > MO_B_LI.fig, .mat: 1000 data points (500 with a one landing site buffer from large craters, 500 without the buffer) for Tulsa, the off-nominal LIDAR scenario with a baseline trajectory and a Moderate function allocation. The .mat file is the data, the .fig is the MATLAB figure file, the data is a set of bar plots. > MO_B_NO.fig, .mat: 1000 data points (500 with a one landing site buffer from large craters, 500 without the buffer) for Fargo, the nominal scenario with a baseline trajectory and a Moderate function allocation. The .mat file is the data, the .fig is the MATLAB figure file, the data is a set of bar plots. > MO_S_LI.fig, .mat: 1000 data points (500 with a one landing site buffer from large craters, 500 without the buffer) for Vegas, the off-nominal LIDAR scenario with a shallow trajectory and a Moderate function allocation. The .mat file is the data, the .fig is the MATLAB figure file, the data is a set of bar plots. > MO_S_NO.fig, .mat: 1000 data points (500 with a one landing site buffer from large craters, 500 without the buffer) for Annapolis, the off-nominal scenario with a shallow trajectory and a Moderate function allocation. The .mat file is the data, the .fig is the MATLAB figure file, the data is a set of bar plots. > README.txt: > dataFiles/ > annapolis/ > annapolis_apDataset#.mat: these series of dataFiles are contour maps of specific cue and weighting combinations. The full list of identifiers is in [mapName].mat. As more data is collected, the more files will be added on. Additionally, if a specific cue and weighting combination has previously been run, the affiliated .mat file will be uploaded and added to, as necessary. It is an output of Apollo.m and moderate.m > annapolis_area1.png, _2.png, _3.png: they are an overlay to the landing area - white background, blue circle representing the landing area chosen by the automation. The number corresponds to the rank. Input to training.m > annapolis_backdrop.jpg: the photograph of the landing area with the hazard scan (including LIDAR abnormalities) overlayed on top. Input to plotSites.m. > annapolis_bwBlank.jpg: the photograph of the landing area. No overlays. Output from DEMmaker, input to training.m. > annapolis_bwSites.jpg: the photograph of the landing area with the automation suggested landing sites overlayed on top. Not really an input to anything. > annapolis_craters_pts_s.jpg: an overlay of the landing area. White background and black dots outlining the major craters. An input to training.m, used for approximating the distance from a major crater. > annapolis_DEM.IMG: the digital elevation map of the landing area. Input to training.m, and an output of DEMmaker. > annapolis_expectations.jpg: an overlay of the landing area. White background and red and green highlights indicating a general trend of where astronauts thought good and bad sites were. This information is generated from the experiment. Input to training.m and Apollo.m and moderate.m > annapolis_largeCraters.jpg: an overlay of the landing area. White background with red corresponding to what large craters were with respect to participants' general opinion. Input to training.m, Apollo.m, moderate.m > annapolis_perceivedHaz.jpg: an overlay of the landing area. White background with red corresponding to what astronauts considered as hazards. Input to training.m. > annapolis_pilotSites.jpg: a figure illustrating where pilots from the experiment chose sites for this particular landing area. Used as a backdrop when plotting the data from 1000dataPts. > annapolis_slope.tex.img: the slope file that indicates what is hazardous. Used in training.m > ls1.png, 2.png, 3.png: overlays to indicate where the automation's top three landing sites are. Used in training.m > myRead.m: sub function used to read data files. Input to training.m, Apollo.m, moderate.m > site.png, site1.png: image files associated with marking off different types of sites chosen by the cognitive model. > annapolis - bufferFromCraters/ > annapolis_apDataset#.mat: these series of dataFiles are contour maps of specific cue and weighting combinations. The full list of identifiers is in [mapName].mat. As more data is collected, the more files will be added on. Additionally, if a specific cue and weighting combination has previously been run, the affiliated .mat file will be uploaded and added to, as necessary. It is an output of Apollo.m and moderate.m > annapolis_area1.png, _2.png, _3.png: they are an overlay to the landing area - white background, blue circle representing the landing area chosen by the automation. The number corresponds to the rank. Input to training.m > annapolis_backdrop.jpg: the photograph of the landing area with the hazard scan (including LIDAR abnormalities) overlayed on top. Input to plotSites.m. > annapolis_bwBlank.jpg: the photograph of the landing area. No overlays. Output from DEMmaker, input to training.m. > annapolis_bwSites.jpg: the photograph of the landing area with the automation suggested landing sites overlayed on top. Not really an input to anything. > annapolis_craters_pts_s.jpg: an overlay of the landing area. White background and black dots outlining the major craters. An input to training.m, used for approximating the distance from a major crater. > annapolis_DEM.IMG: the digital elevation map of the landing area. Input to training.m, and an output of DEMmaker. > annapolis_expectations.jpg: an overlay of the landing area. White background and red and green highlights indicating a general trend of where astronauts thought good and bad sites were. This information is generated from the experiment. Input to training.m and Apollo.m and moderate.m > annapolis_largeCraters.jpg: an overlay of the landing area. White background with red corresponding to what large craters were with respect to participants' general opinion. Input to training.m, Apollo.m, moderate.m > annapolis_perceivedHaz.jpg: an overlay of the landing area. White background with red corresponding to what astronauts considered as hazards. Input to training.m. > annapolis_pilotSites.jpg: a figure illustrating where pilots from the experiment chose sites for this particular landing area. Used as a backdrop when plotting the data from 1000dataPts. > annapolis_slope.tex.img: the slope file that indicates what is hazardous. Used in training.m > ls1.png, 2.png, 3.png: overlays to indicate where the automation's top three landing sites are. Used in training.m > myRead.m: sub function used to read data files. Input to training.m, Apollo.m, moderate.m > site.png, site1.png: image files associated with marking off different types of sites chosen by the cognitive model. > annapolis.mat: output from training.m, includes codification of each cue perceptions, and LIDAR scan > fargo/ > fargo_apDataset#.mat: these series of dataFiles are contour maps of specific cue and weighting combinations. The full list of identifiers is in [mapName].mat. As more data is collected, the more files will be added on. Additionally, if a specific cue and weighting combination has previously been run, the affiliated .mat file will be uploaded and added to, as necessary. It is an output of Apollo.m and moderate.m > fargo_area1.png, _2.png, _3.png: they are an overlay to the landing area - white background, blue circle representing the landing area chosen by the automation. The number corresponds to the rank. Input to training.m > fargo_backdrop.jpg: the photograph of the landing area with the hazard scan (including LIDAR abnormalities) overlayed on top. Input to plotSites.m. > fargo_bwBlank.jpg: the photograph of the landing area. No overlays. Output from DEMmaker, input to training.m. > fargo_bwSites.jpg: the photograph of the landing area with the automation suggested landing sites overlayed on top. Not really an input to anything. > fargo_craters_pts_s.jpg: an overlay of the landing area. White background and black dots outlining the major craters. An input to training.m, used for approximating the distance from a major crater. > fargo_DEM.IMG: the digital elevation map of the landing area. Input to training.m, and an output of DEMmaker. > fargo_expectations.jpg: an overlay of the landing area. White background and red and green highlights indicating a general trend of where astronauts thought good and bad sites were. This information is generated from the experiment. Input to training.m and Apollo.m and moderate.m > fargo_largeCraters.jpg: an overlay of the landing area. White background with red corresponding to what large craters were with respect to participants' general opinion. Input to training.m, Apollo.m, moderate.m > fargo_perceivedHaz.jpg: an overlay of the landing area. White background with red corresponding to what astronauts considered as hazards. Input to training.m. > fargo_pilotSites.jpg: a figure illustrating where pilots from the experiment chose sites for this particular landing area. Used as a backdrop when plotting the data from 1000dataPts. > fargo_slope.tex.img: the slope file that indicates what is hazardous. Used in training.m > ls1.png, 2.png, 3.png: overlays to indicate where the automation's top three landing sites are. Used in training.m > myRead.m: sub function used to read data files. Input to training.m, Apollo.m, moderate.m > site.png, site1.png: image files associated with marking off different types of sites chosen by the cognitive model. > fargo - bufferFromCraters/ > fargo_apDataset#.mat: these series of dataFiles are contour maps of specific cue and weighting combinations. The full list of identifiers is in [mapName].mat. As more data is collected, the more files will be added on. Additionally, if a specific cue and weighting combination has previously been run, the affiliated .mat file will be uploaded and added to, as necessary. It is an output of Apollo.m and moderate.m > fargo_area1.png, _2.png, _3.png: they are an overlay to the landing area - white background, blue circle representing the landing area chosen by the automation. The number corresponds to the rank. Input to training.m > fargo_backdrop.jpg: the photograph of the landing area with the hazard scan (including LIDAR abnormalities) overlayed on top. Input to plotSites.m. > fargo_bwBlank.jpg: the photograph of the landing area. No overlays. Output from DEMmaker, input to training.m. > fargo_bwSites.jpg: the photograph of the landing area with the automation suggested landing sites overlayed on top. Not really an input to anything. > fargo_craters_pts_s.jpg: an overlay of the landing area. White background and black dots outlining the major craters. An input to training.m, used for approximating the distance from a major crater. > fargo_DEM.IMG: the digital elevation map of the landing area. Input to training.m, and an output of DEMmaker. > fargo_expectations.jpg: an overlay of the landing area. White background and red and green highlights indicating a general trend of where astronauts thought good and bad sites were. This information is generated from the experiment. Input to training.m and Apollo.m and moderate.m > fargo_largeCraters.jpg: an overlay of the landing area. White background with red corresponding to what large craters were with respect to participants' general opinion. Input to training.m, Apollo.m, moderate.m > fargo_perceivedHaz.jpg: an overlay of the landing area. White background with red corresponding to what astronauts considered as hazards. Input to training.m. > fargo_pilotSites.jpg: a figure illustrating where pilots from the experiment chose sites for this particular landing area. Used as a backdrop when plotting the data from 1000dataPts. > fargo_slope.tex.img: the slope file that indicates what is hazardous. Used in training.m > ls1.png, 2.png, 3.png: overlays to indicate where the automation's top three landing sites are. Used in training.m > myRead.m: sub function used to read data files. Input to training.m, Apollo.m, moderate.m > site.png, site1.png: image files associated with marking off different types of sites chosen by the cognitive model. > fargo.mat: output from training.m, includes codification of each cue perceptions, and LIDAR scan > tulsa/ > tulsa_apDataset#.mat: these series of dataFiles are contour maps of specific cue and weighting combinations. The full list of identifiers is in [mapName].mat. As more data is collected, the more files will be added on. Additionally, if a specific cue and weighting combination has previously been run, the affiliated .mat file will be uploaded and added to, as necessary. It is an output of Apollo.m and moderate.m > tulsa_area1.png, _2.png, _3.png: they are an overlay to the landing area - white background, blue circle representing the landing area chosen by the automation. The number corresponds to the rank. Input to training.m > tulsa_backdrop.jpg: the photograph of the landing area with the hazard scan (including LIDAR abnormalities) overlayed on top. Input to plotSites.m. > tulsa_bwBlank.jpg: the photograph of the landing area. No overlays. Output from DEMmaker, input to training.m. > tulsa_bwSites.jpg: the photograph of the landing area with the automation suggested landing sites overlayed on top. Not really an input to anything. > tulsa_craters_pts_s.jpg: an overlay of the landing area. White background and black dots outlining the major craters. An input to training.m, used for approximating the distance from a major crater. > tulsa_DEM.IMG: the digital elevation map of the landing area. Input to training.m, and an output of DEMmaker. > tulsa_expectations.jpg: an overlay of the landing area. White background and red and green highlights indicating a general trend of where astronauts thought good and bad sites were. This information is generated from the experiment. Input to training.m and Apollo.m and moderate.m > tulsa_largeCraters.jpg: an overlay of the landing area. White background with red corresponding to what large craters were with respect to participants' general opinion. Input to training.m, Apollo.m, moderate.m > tulsa_perceivedHaz.jpg: an overlay of the landing area. White background with red corresponding to what astronauts considered as hazards. Input to training.m. > tulsa_pilotSites.jpg: a figure illustrating where pilots from the experiment chose sites for this particular landing area. Used as a backdrop when plotting the data from 1000dataPts. > tulsa_slope.tex.img: the slope file that indicates what is hazardous. Used in training.m > ls1.png, 2.png, 3.png: overlays to indicate where the automation's top three landing sites are. Used in training.m > myRead.m: sub function used to read data files. Input to training.m, Apollo.m, moderate.m > site.png, site1.png: image files associated with marking off different types of sites chosen by the cognitive model. > tulsa - bufferFromCraters/ > tulsa_apDataset#.mat: these series of dataFiles are contour maps of specific cue and weighting combinations. The full list of identifiers is in [mapName].mat. As more data is collected, the more files will be added on. Additionally, if a specific cue and weighting combination has previously been run, the affiliated .mat file will be uploaded and added to, as necessary. It is an output of Apollo.m and moderate.m > tulsa_area1.png, _2.png, _3.png: they are an overlay to the landing area - white background, blue circle representing the landing area chosen by the automation. The number corresponds to the rank. Input to training.m > tulsa_backdrop.jpg: the photograph of the landing area with the hazard scan (including LIDAR abnormalities) overlayed on top. Input to plotSites.m. > tulsa_bwBlank.jpg: the photograph of the landing area. No overlays. Output from DEMmaker, input to training.m. > tulsa_bwSites.jpg: the photograph of the landing area with the automation suggested landing sites overlayed on top. Not really an input to anything. >tulsa_craters_pts_s.jpg: an overlay of the landing area. White background and black dots outlining the major craters. An input to training.m, used for approximating the distance from a major crater. > tulsa_DEM.IMG: the digital elevation map of the landing area. Input to training.m, and an output of DEMmaker. > tulsa_expectations.jpg: an overlay of the landing area. White background and red and green highlights indicating a general trend of where astronauts thought good and bad sites were. This information is generated from the experiment. Input to training.m and Apollo.m and moderate.m > tulsa_largeCraters.jpg: an overlay of the landing area. White background with red corresponding to what large craters were with respect to participants' general opinion. Input to training.m, Apollo.m, moderate.m > tulsa_perceivedHaz.jpg: an overlay of the landing area. White background with red corresponding to what astronauts considered as hazards. Input to training.m. > tulsa_pilotSites.jpg: a figure illustrating where pilots from the experiment chose sites for this particular landing area. Used as a backdrop when plotting the data from 1000dataPts. > tulsa_slope.tex.img: the slope file that indicates what is hazardous. Used in training.m > ls1.png, 2.png, 3.png: overlays to indicate where the automation's top three landing sites are. Used in training.m > myRead.m: sub function used to read data files. Input to training.m, Apollo.m, moderate.m > site.png, site1.png: image files associated with marking off different types of sites chosen by the cognitive model. > tulsa.mat: output from training.m, includes codification of each cue perceptions, and LIDAR scan > vegas/ > vegas_apDataset#.mat: these series of dataFiles are contour maps of specific cue and weighting combinations. The full list of identifiers is in [mapName].mat. As more data is collected, the more files will be added on. Additionally, if a specific cue and weighting combination has previously been run, the affiliated .mat file will be uploaded and added to, as necessary. It is an output of Apollo.m and moderate.m > vegas_area1.png, _2.png, _3.png: they are an overlay to the landing area - white background, blue circle representing the landing area chosen by the automation. The number corresponds to the rank. Input to training.m > vegas_backdrop.jpg: the photograph of the landing area with the hazard scan (including LIDAR abnormalities) overlayed on top. Input to plotSites.m. > vegas_bwBlank.jpg: the photograph of the landing area. No overlays. Output from DEMmaker, input to training.m. > vegas_bwSites.jpg: the photograph of the landing area with the automation suggested landing sites overlayed on top. Not really an input to anything. > vegas_craters_pts_s.jpg: an overlay of the landing area. White background and black dots outlining the major craters. An input to training.m, used for approximating the distance from a major crater. > vegas_DEM.IMG: the digital elevation map of the landing area. Input to training.m, and an output of DEMmaker. > vegas_expectations.jpg: an overlay of the landing area. White background and red and green highlights indicating a general trend of where astronauts thought good and bad sites were. This information is generated from the experiment. Input to training.m and Apollo.m and moderate.m > vegas_largeCraters.jpg: an overlay of the landing area. White background with red corresponding to what large craters were with respect to participants' general opinion. Input to training.m, Apollo.m, moderate.m > vegas_perceivedHaz.jpg: an overlay of the landing area. White background with red corresponding to what astronauts considered as hazards. Input to training.m. > vegas_pilotSites.jpg: a figure illustrating where pilots from the experiment chose sites for this particular landing area. Used as a backdrop when plotting the data from 1000dataPts. > vegas_slope.tex.img: the slope file that indicates what is hazardous. Used in training.m > ls1.png, 2.png, 3.png: overlays to indicate where the automation's top three landing sites are. Used in training.m > myRead.m: sub function used to read data files. Input to training.m, Apollo.m, moderate.m > site.png, site1.png: image files associated with marking off different types of sites chosen by the cognitive model. > vegas - bufferFromCraters/ > vegas_apDataset#.mat: these series of dataFiles are contour maps of specific cue and weighting combinations. The full list of identifiers is in [mapName].mat. As more data is collected, the more files will be added on. Additionally, if a specific cue and weighting combination has previously been run, the affiliated .mat file will be uploaded and added to, as necessary. It is an output of Apollo.m and moderate.m > vegas_area1.png, _2.png, _3.png: they are an overlay to the landing area - white background, blue circle representing the landing area chosen by the automation. The number corresponds to the rank. Input to training.m > vegas_backdrop.jpg: the photograph of the landing area with the hazard scan (including LIDAR abnormalities) overlayed on top. Input to plotSites.m. > vegas_bwBlank.jpg: the photograph of the landing area. No overlays. Output from DEMmaker, input to training.m. > vegas_bwSites.jpg: the photograph of the landing area with the automation suggested landing sites overlayed on top. Not really an input to anything. > vegas_craters_pts_s.jpg: an overlay of the landing area. White background and black dots outlining the major craters. An input to training.m, used for approximating the distance from a major crater. > vegas_DEM.IMG: the digital elevation map of the landing area. Input to training.m, and an output of DEMmaker. > vegas_expectations.jpg: an overlay of the landing area. White background and red and green highlights indicating a general trend of where astronauts thought good and bad sites were. This information is generated from the experiment. Input to training.m and Apollo.m and moderate.m > vegas_largeCraters.jpg: an overlay of the landing area. White background with red corresponding to what large craters were with respect to participants' general opinion. Input to training.m, Apollo.m, moderate.m > vegas_perceivedHaz.jpg: an overlay of the landing area. White background with red corresponding to what astronauts considered as hazards. Input to training.m. > vegas_pilotSites.jpg: a figure illustrating where pilots from the experiment chose sites for this particular landing area. Used as a backdrop when plotting the data from 1000dataPts. > vegas_slope.tex.img: the slope file that indicates what is hazardous. Used in training.m > ls1.png, 2.png, 3.png: overlays to indicate where the automation's top three landing sites are. Used in training.m > myRead.m: sub function used to read data files. Input to training.m, Apollo.m, moderate.m > site.png, site1.png: image files associated with marking off different types of sites chosen by the cognitive model. > vegas.mat: output from training.m, includes codification of each cue perception and LIDAR scan > mainCodes/ > apollo_v20.m: the main code used to process the Apollo-like function allocation. More details within the body of the code. Developed in MATLAB. > collectIndividualData_mo.m: wrapper used for validation - collects cognitive process model output using the same inputs as with each experimental run. > collectIndividualData.m: wrapper used for validation - collects cognitive process model output using the same inputs as with each experimental run. > fauxTSAR2.m: faux automation algorithm based on the work of Cohanim et al 2008. > makeMap900p.m: converts a figure into one of 900 x 900 px. > makeSiteMaps.m: code for creating the data-only (non image) version of area1.png 2.png, 3.png. Not quite meant for this set of data, but inadvertently stuck in here. > moderate_v10.m: code used for the moderate function allocation. More details within the code. Developed in MATLAB. > plotSites.m: takes outputs from Apollo.m or moderate.m > processSlopeMaps.m: takes _slope.tex inputs and converts them into images of 1s and 0s indicating whats a hazard and whats not a hazard. > training.m: used to produce input files into Apollo.m and moderate.m > uploadSlopeMap.m: takes _slope.tex inputs and converts them into images of 1s and 0s indicating whats a hazard and whats not a hazard. > validationIndividualRuns/ > back_chosenHaz/: all of these images feature a black and white background of the expected landing site, with an overlay of the hazard shading and the chosen landing site. > back_ap-b-li_tulsa_#.fig > back_ap-b-no_fargo_#.fig > back_ap-s-li_vegas_#.fig > back_ap-s-no_annapolis_#.fig > back-whereLand-ap-b-li-tulsa.docx, -ap-b-no-fargo.docx, -ap-s-no-annapolis.docx, -ap-s-li-vegas.docx > back-whereLand.docx > back-whereLand.pdf > costMapL/: all of these images feature a contour map of the landing site scores in accordance to cue combinations for the localized selection. > costMap-whereLand-ap-b-no-fargo.docx, -ap-s-no-annapolis.docx, -ap-b-li-tulsa.docx, -ap-s-li-vegas.docx > costMap-whereLand.docx, .pdf > costMapL_ap-b-li-tulsa_#.fig, _ap-s-li-vegas_#.fig, _ap-b-no-fargo_#.fig, _ap-s-no-annapolis_#.fig > cueDistributionTiming/ all of these charts compare experiment and cognitive model selection in terms of cue usage, timing, and cue weightings. > cueChartsApollo.png > cueWeightsApollo.png > dataForValidationPlots.xlsx > modelValidate_v2.m: code to calculate specific data for modelValidation2.xlsx > modelValidation2.xlsx: individual runs analyzed here. Analogy to signal detection theory. The excel spreadsheet has a lot more information. > naked_chosenNoHaz/: these charts show just the chosen site on the background, no other annotations. > naked_ap-b-li_tulsa_#.fig, _ap-s-li_fargo_#.fig, _ap-b-no_vegas_#.fig, _ap-s-no_annapolis_#.fig > plain-whereLand.. Docx, PDF, fig > validation.docx: document showing the process of validation.