https://github.com/humanfactors/drivingaq

Driving AQ for Visser Lab
https://github.com/humanfactors/drivingaq

Last synced: about 1 month ago
JSON representation

Driving AQ for Visser Lab

• Host: GitHub
• URL: https://github.com/humanfactors/drivingaq
• Owner: humanfactors
• License: mit
• Created: 2017-09-07T06:57:00.000Z (about 7 years ago)
• Default Branch: master
• Last Pushed: 2019-10-01T04:16:35.000Z (about 5 years ago)
• Last Synced: 2024-10-09T15:44:09.378Z (about 1 month ago)
• Language: Scilab
• Size: 43 KB
• Stars: 0
• Watchers: 1
• Forks: 0
• Open Issues: 0
• Metadata Files:
  • Readme: README.md
  • License: LICENSE

Awesome Lists containing this project

README

        
# drivingAQ

Driving AQ for Visser Lab

## Dependencies

To run the scripts requires Python 3.6 due to the use of `random.choices()`.

This can be changes to random sample for backward compatibility.

## Structure

* `docs/` - Supporting documentation directory

* `input/` - static directory, files should be considered part of the package

* `output/` - dynamic directory for output files

* `locations.py` - library functions for generating dot location lists

* `sceparser.py` - procedural script for finding/replacing sce dot locations + times 

* `subjectcall.py` - Contains 'Subject' class which generates a subject randomisation cell + output

* `times.py` -  library functions for randomisation of inter-stimulus interval for PDT

## Summary of Processing Order

Tweaks to the experimental configuration should be relatively straight forward,

though I would speak to [Michael](mailto:[email protected]). Anything to

do with the actual`.sce` reading and writing should all be contained within the

`.sceparser` file. Any appeared convolution is just a result of having several

dictionaries calling each other. If lookup keys aren't working as intended,

ensure that the keys are strings for lookup dicts or integer for `finaldict`.

`locations.py` is effectively just reading the input of X and Y coordinates from

relevant input files, shuffling them up and assigning each coordinate an ID.

`times.py` has a bunch of functions mostly just for generating the times that dots

appear. The majority of confusing stuff is just regarding sampling the

inter-stimulus intervals. Finally, `subjectcall` contains the class `Subject`.

This requires a name at instantiation (i.e. subject number) and each `Subject`

instance will have a unique order of locations, and unique timings for PDT.