Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

issues with experimentation (CHECKLIST) #36

Open
12 tasks
BenedictWilkins opened this issue May 16, 2023 · 0 comments
Open
12 tasks

issues with experimentation (CHECKLIST) #36

BenedictWilkins opened this issue May 16, 2023 · 0 comments

Comments

@BenedictWilkins
Copy link
Contributor

BenedictWilkins commented May 16, 2023

Various things need updating to make experiments easier to analysis later.

  • give an option to place eye tracking events in a different file (they flood the log file)
  • standardize the input event format
  • when logging changes, also log the current value (e.g. fuel change -1, value 100) this makes it easier to process the file and is less error prone.
  • have a mode where agents give "fake" feedback (not shown on the interface, but logged) so that we can do counter factual analysis more easily.
  • show more obvious warning if the eye tracking system crashes so that the experimenter can be aware!
  • position of the target in the tracking task is not in window coordinates. The position of the tracking task should be given in a log file. Complete window information (can use window_properties in init.py) should be logged.
  • when eyes move out of the ICU interface window this should be known, add a new label "outofbounds"
  • eye tracking timestamp is wrong, it is current "time since eye-tracker has been on"
  • it would be good to include a start up or "ready" event with a timestamp
  • record all mouse and keyboard input regardless of whether it is a "valid" interaction.
  • there should be an event triggered when a task is "in failure", this is only true for the fuel task, make it so for the others.
  • the "cause" property of an event is difficult to parse, it should just be the ID of the causing event.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant