Path to Pilot and Experiment

[DavidGoedicke]

Purchasing:

• Buy Additional Traffic cones (4 tall cones)

Technically:

• Install extra RAM on laptop
• ROS to Unity delay (waiting response from Varjo)
• Alignment of Car mask (Button Interaction)
• Video Pass-through (Mark correct material)
• Traffic Cones Adjustment
• Include CAN Bus speed in Unity (ROS side is already programmed[needs testing])

Calibration:

• Calibrate ART tracker in the vehicle (Roll and pitch accuracy)
• Zed Mini to the base_link (vehicle) (esp. correct height offset)
• test existing orientation calibration code in Unity.

Experiment (recording):

• Ros Logging (Exclude non used Zedm Topics)
• Ros Logging Test Logging (Pilot)
• Install/test video Cameras

Experiment:

• edit/adjust protocol to include all 3 conditions (w/wo headset, virtual obj/real obj, no headset & virtual obj not a condition)
• set up Latin square ordering design
• Fix post experiment questionnaire (writable for experimenter) overleaf
• Run a pilot
• Participants Recruitment
• Run the study

Paper:

• update experiment description
• update technical section
• perform and write up data Analysis (video coding) (participants response coding)
• Write Results
• Write Discussion

[bremers]

Car model now has VST material attached. If video see through doesn't work, double check settings.

[bremers]

Status on 14th Dec 2020:

• FPS unacceptably low (20 FPS, screen tearing, potential ROS data input delays - required FPS is 60)
• Screen delay should be 20-30ms, easily reaching 100+ ms.
• We've explored temperature issue, did not solve - became power issue
• We've expanded laptop memory, did not solve

Options:

1. Try to run experiment on Unity + laptop. Will be too low FPS, not really an option. Questionable results.
2. Buy new desktop. Might help, definitely will delay project. We would need to explore options that could both run the simulator, as well as be suitable to be put in a car (power). All our existing laptop and desktop alternatives don't have required Thunderbolt 3 port.
3. Rebuild in Varjo SDK, which is C++. Downside: it will not be easy to change or update. Development will take unknown amount of time. Unknown unknowns.
4. FrankenXR-OOM: move CPUs and GPUs and update motherboard.

Desktop requirements:

• Thunderbolt 3 port
• https://varjo.com/use-center/get-started/system-requirements/compatible-computers/