Data Problems To Look Into

Event Code Problems

• Noticed Event Code on Handle Release is stuck in a data loop
  { "Index": 6515, "EventType": "HandleRelease", "EventData": "MRTK Ended Manipulation" }, { "Index": 6517, "EventType": "HandleRelease", "EventData": "MRTK Ended Manipulation" }, { "Index": 6518, "EventType": "HandleRelease", "EventData": "MRTK Ended Manipulation" }, { "Index": 6519, "EventType": "HandleRelease", "EventData": "MRTK Ended Manipulation" }, { "Index": 6520, "EventType": "HandleRelease", "EventData": "MRTK Ended Manipulation" }
• Moral Control Push Barrel didn't activate: Sequence to get here:
  • Training: Curve
  • Push Barrel both times
• Reset Handle on Switch Study so after Moral Control the handle goes towards the bridge

Great Feedback from
#35

Adjustments Needed

Office

Upon entering the office we need to address the following items in one cc/audio blurb
Office Introduction Narration/CC and Audio Updates

• How you navigate/Teleport
• Modify information about the menu to include "additional settings": menu position
• Introduction to seat/stand = remove and combine
• Check out the computer before you're ready
• UI Changes and removal of old audio blurb/narration timeline
  • Touch screen to go through these options up front and then grant you the menu upon finishing that (no audio/cc cues needed) text on screen

Control Booth

Record all new voice/cc for the following items listed below (switch / bridge / curve )

• Curve = Spur Track
• Bridge = Main Track
• Switch System = Control Booth
  • Introduction to tower =remove and combine with CCTV training
  • Entire "Switch" training needs new narrative and new CC
  • Entire FirstTrainSuccess new narration and cc
  • Entire FirstTrainFailure new narration using Spur and main line and cc
  • Entire Water Barrel_00 narrator needs to be replaced with removal of switch and replace with 'control booth'
  • Entire Water Barrel_01 narrator needs to be replaced with removal of switch

Misc Fixes

• Entire CC TV training gets gutted and rerouted for the state machine
• After Moral Control, non-barrel pushed, we need to 'eject' the barrel without activating the other state (activate dummy barrel protocol)

• Setup Simple Audio Mixer
• Dedicated Environment Channel
• Dedicated Truck Channel
• Dedicated Train Channel
• Dedicated Tower Channel

• Add 10 seconds to the timeline that fires off board updates
• Add 10 seconds to the timeline that fires off the train release event
• See #18 for timing adjustments for sending up the worker as these compound each other

• Converting humans to Male Gender on trucks
  • Character 0 Swap
  • Character 1 Swap
  • Character 2 Swap
  • Character 3 Swap
  • Character 4 Swap
• Syncing the start/end to existing script work for forced translation/rotation
  • Character 0 Updates
  • Character 1 Updates
  • Character 2 Updates
  • Character 3 Updates
  • Character 4 Updates
• Sequence tie in with BaTo's Work
  • Character 0 with saw
  • Character 1 with hammer jack
  • Character 2 with drill
  • Character 3 with shovel
  • Character 4
• Sequence on running away
  • Character 0 Fence Jump
  • Character 1 Equipment throw / run
  • Character 2 Run away
  • Character 3 Run away
  • Character 4 Fence Jump
• Sequence running away to then die
  • Character 0 with saw
  • Character 1 with hammer jack
  • Character 2 with drill
  • Character 3 with shovel
  • Character 4
• Sequence on running away to then back in the truck
  • Character 0 Walk back / Jump with Saw
  • Character 1 Walk back / Jump
  • Character 2 Walk back / Jump with Equipment
  • Character 3 Walk back / Jump
  • Character 4 Walk back / Jump

• Isolating 1 person for the 1 v 5 scenario

• Updating all prefab variants from Root Prefab
  • MC variants
  • Study Push Variant
  • Study Track Change Variant

Office Sequence

• See Issue #37

Track Changes

• Adjust curve to run parallel to bridge (both tracks should go over chasm)
  - [ ] Remove fencing on bridges
• Move workers closer to control tower

Control Tower Changes

• Remove switch, replace with buttons
• Remove cameras
• Change status lights to "Active/ Inactive" message
• Rotate tower so barrels/ pushed man will land on track after adjustments to curve (See "Track Changes" below)

Animations

• Work animation loops
        - [ ] Man on laptop
        - [ ] Man hammering
        - [ ] Welding
        - [ ] Other?
• Getting back into truck animation?

Sound Design

• Ambient noise while in control tower (Ex. https://assetstore.unity.com/packages/audio/ambient/nature/cicada-sound-pack-vol-01-33453 or https://assetstore.unity.com/packages/audio/ambient/nature/organic-nature-38394)

Additional Comments & Details

• We discussed white boxing the track changes and control tower changes first to make sure that it fits what we're hoping for. I think we should try that first, as we may choose to move the tower in between the tracks in the long run.
• Please add any additional changes we discussed that may have been left off this initial list.

• Update state machine to include new moral control state for barrel curve
• Update state machine transitions to include success / fail for moral control by barrel curve
• Update overall state machine logic to include new hooks out to the experiment states
• Update and create new timeline for handling the setup of the sequence
• New sequence requires animation with human walking up with a barrel
• Sequence requires human walking back and adding in arm animation of 'holding equipment' - this shouldn't be hard given the work already done
• Update and create new timeline event messages for communicating across systems tied to the barrel curve
• Look into the Barrel Manager and make sure it's not being activated when it's not supposed to - probably legacy state stuff
• Identify StudySetup state and force change to correct study state
• Update Phil_Main to include three new UnityEvents
• Event: Moral Control Barrel Curve Start
• Event: Moral Control Barrel Curve Success
• Event: Moral Control Barrel Curve Fail
• Update Azure Data events to include outcome of these states - this should automatically happen but double check
• Update truck sequence logic to only send out a 5 person truck by itself on the curve
• Modify timeline to kill the board once the people are dropped off
• Left Barrel updates via state machine from train collision on track
  • Modify to include Right Moral Control Barrel
  • Modify Timeline to include new hot swap on animated barrel and spawned barrel - right arm down, then swap
• Looks like there are two timeline events that are getting activated overtop of each other
  • Check the hand-off between "finishing training" and moral control setup: think I just need to replace a collision timeline event
• Invisible Moral Control Left Barrel = swap to right barrel for Moral Control
• When Barrel hits track = update method to include moral control state information (this is still using old info)
• Moral Control Truck on Curve didn't stop
• Update truck sequence to hold the truck on the track until moral control is over - use solution from other moral control
• Duplicate truck animation sequence from bridge to curve for 5
• Add three new public methods to pause, release, and destroy truck - use solution from other moral control
  - [ ] New Narration needed for moral control introductions: see notes for barrel/bricks
  - [ ] New narration needed for moral control success: - use solution from other moral control
  - [ ] New narration needed for moral control failure: - use solution from other moral control

Describe the Data Run

1. Qualtrics Code: 772961
2. Training Decision on Switch: Curve
3. Training Decision on First Barrel: Push
4. Training Decision on Second Barrel: Push
5. Moral Control Decision: Pushed Barrel - BUG Didn't work, modified issue #24
6. Study Decision: Kill 1

Additional context
Morning of May 5, 2021. Original Teams Message below

Code- 772961
Training Decisions
• Curve
• Push barrel (both times)
Moral Control
• Pushed Barrel (didn’t work!)
Study
• pushed worker

• Question data includes Qualtrics Code
• Event Data includes Qualtrics Code
• Position Data includes Qualtrics Code
• Audio Data Naming Convention includes Qualtrics Code

Describe the Adjustment
Only have the CC TV's looking at the track

Things to Consider
Adjust Camera placement to still be in line with user's perspective but closer and in tighter on the "people"

Additional context
When the train gets really close black the camera out (kill the feed, reactivate the feed after it hits the next collider)

Describe the Adjustment
Decrease distance of switch pull

Things to Consider
Guideline of information needed:

1. Where are you in the experience? (Just loaded up, was in the office, was at the control booth, etc)
   Control booth
2. What object/item specifically are we thinking of adjusting? (Handle on the deck, button at the office, barrel at the tower)
   Decrease the length of the pull on the switch/ handle in the control booth. As it stand, the user has to pull the switch into the path of the teleportation spot, meaning they have to pull it into a space they are co-located in.
3. Is this a time based adjustment? (Between the first and second train we need 5 extra seconds)
   No
4. Is this a bug? (I get stuck between training and the first train) Please fill out the bug template instead, that can be found at the bug template ❕
   No

Additional context
It may also help to move the teleportation spot back from the control board a little bit.

Things for Test Release

• Push physics on human barrel and normal barrel
• Camera adjustment to move to where the truck stops
• Exhaustive data test
• Remove hand tracking from MRTK and force controllers only (hand tracking is cool but not functional as I killed all the connectors now it just causes goofy glitches)
• Timing/distance check on when barrel manager releases barrel and compare that to pushing the guy. Confirm they are the same and then modify to easily adjust this as needed tied to the time between guy appearing and barrel unlock.

Describe the Adjustment
I think we need to add one more sound back in. When the user is first introduced to the control board, the voice says "that sound is the sound of the board unlocking" (or something like that). But there is no mechanical sound accompanying the narration.

Things to Consider
Guideline of information needed:

1. This occurs in the control booth
2. It involves the addition of a sound when the control board/ switch unlocks
3. This is not a time based adjustment
4. This is not a bug

• Update Distance on Clipping Property
• Remove City across the bay entirely
  • Tweak State Machine Event on Transfer to Tower

Describe the Adjustment
Original idea on "Look here" glowing edge bounding box

Things to Consider
Increase vibration on controllers tied to a Angle.Lerp(head forward gaze, head gaze towards center of object)

Study CheckList

⭕ Go for it!
⌛ Working on it
🐛 A Bug
✔️ Complete

• There are two active paths you can take to help us beta test this experience.
• We will give you 2 unique codes to test both paths, one will be an even number and one will be an odd number.
  • If you enter in an even number you will be participating in the switch study.
  • If you enter in an odd number you will be participating in the push study.
• Please attempt to answer the following questions to the best of your ability.

Equipment Details

Please select one:

• Oculus Quest 1
• Oculus Quest 2
• Oculus Qust Rift S
• Oculus OG 🕶️

Scenario Details

Please describe the scenario as you experienced it

The experiences started in an office. I believe this part of the scene served the purpose of acquainting the user with the type of visuals, interactions, audio cues, and controls they can expect. It also served as the launching place from which they can go to different paths based on the code they enter. Next, I was transported to a different scene where I was in a control room of an under-construction railway station. I was asked to direct an automated train to either of the two paths, curve or bridge. I was also taught that dropping any item such as a liquid or a person (God forbid) onto the track, it will cause the train to stop. I was then faced with a dilemma. An unexpectedly incoming train was headed toward the bridge where 5 workers were working, meanwhile 1 worker was on the curve section of the track. I had a decision to make, allow for potentially 5 casualties, or 1. So the first thing I did was pull the lever to direct the plain to the less occupied part of the track, the curve. Then I started to look around for any solid object to throw out the window since there were no available barrels that I can use to engage the safety system and stop the train. I wasn't able to find any solid object that I can throw and the result was 1 casualty.

Beta Test Version

This should be 0.1.0-beta

Estimated Time

Please provide the rough time you started the experience and use time zones, e.g. 12:30am EST May 4, 2021
11:05 am EST June 22, 2021

Qualtrics Code

Please enter the 6 digit survey code you used here e.g. '123456'
000008

Training Decision on Pulling the Switch

Please select one:

• Followed Directions: sent the train towards the bridge 🌉
• You Caused Trouble: sent the train towards the curve

Training Decision on Stopping the Train with the Barrel

Please select one:

• Followed Directions: pushed the barrel to stop the train
• You Caused Trouble: did not push the barrel and the system took over

Moral Control Decision

Please select one:

For EVEN survey code (Switch Study)

• You sent the train away from the people
• You did nothing and the five people died 🤯
• You did nothing and the five people lived 🐛
  NOTE: there wasn't an option of no one dying, it was either 1 or 5.

For ODD survey code (Push Study)

• You stopped the train with a Barrel
• You did nothing and the five people died 🤯
• You did nothing and the five people lived 🐛

Test Study Decision

Please select one:

For EVEN survey code (Switch Study)

• You pulled the switch, killed 1, saved 5
• You did not pull the switch, killed 5

For ODD survey code (Push Study)

• You pushed a person, killed 1, saved 5
• You did not push a person, killed 5

System Crash

• Did you Encounter a Crash?

Please explain what happened, do you remember if you were interacting with anything? Do you remember about where you were in the experience?
If you want to be really helpful 🥰 and you think you can recreate the crash and know how to run adb logcat please dump us the file here!
If not no worries, we still 🖤 you.

Additional Comments & Details

Any other feedback? Notes? Suggestions? Little things you noticed? Anything?! Please and thank you!😺
Please see my feedback from my previous form (code 000007) where I included my feedback about the experience.

Describe the problem
Physics instantiation when the user has their hand in the same spot as our repair guy being generated is going to cause an instant floating point physics launch scenario in which the force registered is going to exceed the action of pushing.

To Reproduce
Steps to reproduce the problem:
Put your hand near where the guy walks and positions himself right before he crouches down and watch the magic!

Additional Context
Going to have to first notify the user of this persons presense - prior to this version we had the door open and we used the door shutting as a signal to the user to turn around - going to have to bring back audio cues to inform the user of the person walking over. When we go from the animation state to the interaction state need to do a quick check of where the users hands are, not activate any rigidbody information until the users hands leave a trigger zone that aligns with the repair person, upon leaving that zone we activate the rigidbody on the repair person and wipe/reset all rigidbody physics related data. This should be a finalized solution and will resolve issues identified in #35

Beta Testing

• There are two active paths you can take to help us beta test this experience.
• We will give you 2 unique codes to test both paths, one will be an even number and one will be an odd number.
  • If you enter in an even number you will be participating in the switch study.
  • If you enter in an odd number you will be participating in the push study.
• Please attempt to answer the following questions to the best of your acknowledgement.

Equipment Details

• Oculus Quest 1
• Oculus Quest 2
• Oculus Qust Rift S
• Oculus OG 🕶️

Scenario Details

Estimated Time

Please provide the rough time you started the experience and use time zones, e.g. 12:30am EST May 4, 2021

Qualtrics Code

Please enter the 6 digit number you used here e.g. '123456'

Training Decision on Pulling the Switch

• Followed Directions: sent the train towards the bridge 🌉
• You Caused Trouble: sent the train towards the curve

Training Decision on Stopping the Train with the Barrel

• Followed Directions: pushed the barrel to stop the train
• You Caused Trouble: did not push the barrel and the system took over

Moral Control Decision

Switch Study

• You sent the train away from the people
• You did nothing and the five people died 🤯
• You did nothing and the five people lived 🐛

Push Study

• You stopped the train with a Barrel
• You did nothing and the five people died 🤯
• You did nothing ahd the five people lived 🐛

Study Outcome

Switch Study

• You pulled the switch, killed 1, saved 5
• You did not pull the switch, killed 5

Push Study

• You pushed a person, killed 1, saved 5
• You did not push a person, killed 5

System Crash

• Did you Encounter a Crash?

Please explain what happened, do you remember if you were interacting with anything? Do you remember about where you were in the experience?
If you want to be real helpful 🥰 and you think you can recreate the crash and know how to run adb logcat please dump us the file here!
If not no worries, we still 🖤 you.

Additional Details

Any other feedback? Notes? Suggestions? Little things you noticed? Anything?! Please and thank you!😺

Need to work out the timing on when to initiate the animation of the worker walking over to the barrel machine.

This should roughly leave the user with about 10 seconds to make a decision. Right now we are around the 30-40 second mark.

Things to Consider

Finalize the audio narrations first - then go back and look at the timing gaps/windows.

Describe the Adjustment
To test some FPS related issues - build a custom script to turn on/off MRTK FPS tool via the menu settings.

Should be a quick adjustment - toggle option under settings menu panel to activate 'Developer section/tools'

Beta Testing

• There are two active paths you can take to help us beta test this experience.
• We will give you 2 unique codes to test both paths, one will be an even number and one will be an odd number.
  • If you enter in an even number you will be participating in the switch study.
  • If you enter in an odd number you will be participating in the push study.
• Please attempt to answer the following questions to the best of your ability.

Equipment Details

Please select one:

• [x ] Oculus Quest 1
• Oculus Quest 2
• Oculus Qust Rift S
• Oculus OG 🕶️

Scenario Details

Please describe the scenario as you experienced it
I was introduced to the controls via a training scenario, then given the opportunity to decide which track the train runs on in 2 situations. 1. When there are workers on the bridge and none on the tower track. 2. When there are 5 workers on the bridge and 1 on the tower track.

Beta Test Version

This should be 0.1.0-beta

Estimated Time

Please provide the rough time you started the experience and use time zones, e.g. 12:30am EST May 4, 2021
2:30pm EST May 14 2021

Qualtrics Code

Please enter the 6 digit survey code you used here e.g. '123456'
000006

Training Decision on Pulling the Switch

Please select one:

• Followed Directions: sent the train towards the bridge 🌉
• [ x] You Caused Trouble: sent the train towards the curve

Training Decision on Stopping the Train with the Barrel

Please select one:

• [ x] Followed Directions: pushed the barrel to stop the train
• You Caused Trouble: did not push the barrel and the system took over

Moral Control Decision

Please select one:

For EVEN survey code (Switch Study)

• [x ] You sent the train away from the people
• You did nothing and the five people died 🤯
• You did nothing and the five people lived 🐛

For ODD survey code (Push Study)

• You stopped the train with a Barrel
• You did nothing and the five people died 🤯
• You did nothing and the five people lived 🐛

Test Study Decision

Please select one:

For EVEN survey code (Switch Study)

• [ x] You pulled the switch, killed 1, saved 5
• You did not pull the switch, killed 5

For ODD survey code (Push Study)

• You pushed a person, killed 1, saved 5
• You did not push a person, killed 5

System Crash

• Did you Encounter a Crash?

Please explain what happened, do you remember if you were interacting with anything? Do you remember about where you were in the experience?
If you want to be really helpful 🥰 and you think you can recreate the crash and know how to run adb logcat please dump us the file here!
If not no worries, we still 🖤 you.

Additional Comments & Details

Any other feedback? Notes? Suggestions? Little things you noticed? Anything?! Please and thank you!😺

I was more familiar with the setup and better oriented with the space on my second runthrough, so I focussed more on the control options. I still had a lot of trouble manipulating the track switch handle. It was unresponsive and didn't seem to always register my interactions.

I also noticed that while it seems like the color coding is meant to convey that blue is operable and red is locked/inoperable, the 'hover' state of interaction with a blue object is red. This feels sort of counterproductive to the establishment of the blue/red distinction. I wonder if it would be clearer to use a more standard pattern of GREEN for operable and red for inoperable, with blue as the hover state? Or some other way of indicating selection/hover if you don't want to introduce a third color (probably wise).

I also wonder about the system power knobs (I think there are 5?). It seems that whether there is power and the system is active is a binary state (off or on, defined by red or blue). So having there also be 5 knobs as part of that UI piece seems extraneous/arbitrary. I saw it as maybe some kind of meter that would fill, like there might be 5 levels of power? Would it make sense to just reduce this to one indicator? Or just a display that says 'active' and 'locked' or something to that effect.
Similarly, I was a little confused by the third knob on the UI of the lever for track switching. It seems there are 2 binary states (bridge or curve) so why not just have 2 knob-things? I was wondering if there was some kind of middle setting in between the 2 options.

Sorry if I'm not explaining myself well in this message, I'd be happy to provide verbal feedback to Dr. Kissel next time I see him!

• File naming Convention
• Event Data
  • List of all Enums
• Position Data
• Question Data
• Summary Data
• Qualtrics Office File Data
• Azure Speech to Text Parameter Settings

Describe the Adjustment

• For the barrel training sequence and barrel moral control sequence, the cutoff for making a choice to push (or not push) the barrel should be the train passing the control tower, rather than the train reaching the track split.

Further Explanation/ Context:
After the arm unlocks for the barrel pushing training, the barrel gets "auto-kicked" if the user has not pushed the barrel by the time the train reaches the split in the tracks. It would be better if it got auto-kicked when the train reaches the control tower.

Similarly, on the barrel moral control, the arm relocks the barrel when the train reaches the split in the tracks. The arm should not relock until the train has reached the control tower.

My thinking is that for many users, they will wait until the train is closer to push the barrel, thinking they need to throw the barrel into the train's path. If the barrel is kicked or arm relocked too early, users who intended to push the barrels may not get the opportunity.

• Update state machine to include new moral control state for bridge vs curve
• Update state machine transitions to include success / fail for moral control
• Update overall state machine logic to include new hooks out to the experiment states
• Update and create new timeline for handling the setup of the sequence
• Update and create new timeline event messages for communicating across systems
• Update Phil_Main to include three new UnityEvents
• Event: Moral Control Bridge Curve Start
• Event: Fix how we destroyed the old light on back of truck
• New Prefabs: blown up truck with light - on train collision
  • No longer need to deal with truck state just turn it off because it's a spawned object
• New Prefabs: light to be hit by train - for normal study
• Event: Moral Control Bridge Curve Success
• Event: Moral Control Bridge Curve Fail
• New Prefabs: Full Truck-Train System with wagon code for instance/spawning
• Physics RigidBody changes moved from light system to Main Truck System
• Update Azure Data events to include outcome of these states - this should automatically happen but double check
• Activate Lights on Removing Parent from trailer
• Deactivate Lights on Reparenting trailer
• Update truck sequence logic to only send out a 5 person truck by itself on the bridge
• Update truck sequence to hold the truck on the track until moral control is over
• Add three new public methods to pause, release, and destroy truck
  - [ ] New Narration needed for moral control introductions: see notes
  - [ ] New narration needed for moral control success: this should be the same for other moral control success
  - [ ] New narration needed for moral control failure: this should be the same for other moral control failure

Describe the Adjustment

Flip Text boxes from White to black
Make text White
Have a 'star wars fade on the text'

Things to Consider
Update current text script to have "Star wars fade" boolean
When true: spawn a new text gameobject, add it to a list, push it up +TextHeight plus old, then do this for all items in the list
Fade place in list (Total in list-List Position/Total in List) cap list to like 5, when we hit 5 kill the oldest one.

Beta Testing

• There are two active paths you can take to help us beta test this experience.
• We will give you 2 unique codes to test both paths, one will be an even number and one will be an odd number.
  • If you enter in an even number you will be participating in the switch study.
  • If you enter in an odd number you will be participating in the push study.
• Please attempt to answer the following questions to the best of your ability.

Equipment Details

Please select one:

• [ x] Oculus Quest 1
• Oculus Quest 2
• Oculus Qust Rift S
• Oculus OG 🕶️

Scenario Details

Please describe the scenario as you experienced it
I was given instructions on how to interact with various instruments that operate track switching, camera switching, and the ability to stop the train. Then, different scenarios were presented in which manipulating the instruments would allow me to influence if the train killed groups of workers on the tracks or not. I think there were just 2 different choice scenarios presented but I wasn't sure what was going on in each one.

Beta Test Version

This should be 0.1.0-beta

Estimated Time

Please provide the rough time you started the experience and use time zones, e.g. 12:30am EST May 4, 2021
6:30pm EST May 12 2021

Qualtrics Code

Please enter the 6 digit survey code you used here e.g. '123456'
000005

Training Decision on Pulling the Switch

Please select one:

• [x ] Followed Directions: sent the train towards the bridge 🌉
• You Caused Trouble: sent the train towards the curve

Training Decision on Stopping the Train with the Barrel

Please select one:

• [ x] Followed Directions: pushed the barrel to stop the train
• You Caused Trouble: did not push the barrel and the system took over

Moral Control Decision

Please select one:

For EVEN survey code (Switch Study)

• You sent the train away from the people
• You did nothing and the five people died 🤯
• You did nothing and the five people lived 🐛

For ODD survey code (Push Study)

• You stopped the train with a Barrel
• [ x] You did nothing and the five people died 🤯
• You did nothing and the five people lived 🐛

Test Study Decision

Please select one:

For EVEN survey code (Switch Study)

• You pulled the switch, killed 1, saved 5
• You did not pull the switch, killed 5

For ODD survey code (Push Study)

• [x ] You pushed a person, killed 1, saved 5
• You did not push a person, killed 5

System Crash

• Did you Encounter a Crash?

Please explain what happened, do you remember if you were interacting with anything? Do you remember about where you were in the experience?
If you want to be really helpful 🥰 and you think you can recreate the crash and know how to run adb logcat please dump us the file here!
If not no worries, we still 🖤 you.

Additional Comments & Details

Any other feedback? Notes? Suggestions? Little things you noticed? Anything?! Please and thank you!😺

I found the overall experience confusing and difficult to parse. Some of this may have been user error due to my first time using an oculus quest, however throughout I found it difficult to understand what was happening in each scenario due to poor visibility of the general area and understanding the location of the tracks and the workers. I was seated during the test, and found it difficult to naturally reach all the controls. The pull lever was finicky and seemed to have delayed reaction to manipulation. At one point I was unable to switch between camera views (if this is intentional then I was not aware of what made it non-interactive).

It seemed odd that there is no explanation of the most abstract interactive item in the test, the blue position movers. I was able to assume how they worked due to prior experience with VR movement, but to less familiar testers, it might be non-intuitive. I also wonder why the computer monitor in the office room displays the number entry by default, then a voice asks you if you are seated or standing, then the monitor displays a choice of seated or standing. Why have that question asked twice be disassociated sources? Perhaps it would be more streamlined to have the seated or standing question up on the monitor by default? Seems like the user would read what is on the screen, and make that selection pretty simply, without needing to be told they are about to be asked. Probably nit-picky, but it stood out to me as a user flow issue that could easily be tweaked.

I don't quite know what happened when it came to the pushing scenario. The test seemed to suggest I pushed someone onto the tracks, but I don't recall seeing the option to do so or choosing to do so. Not exactly sure what happened there. I think my overall reaction to much of what I was doing was confusion, not so much about the overall concept or what each interactive item did, but generally what was happening outside the control room at any given moment. In this sense, I don't feel like I really made distinct choices about what to do in each situation, and I did not feel connected to the outcomes, which I was only able to infer on the assumption that the yelling audio cue meant someone died.

Describe the Data Run

1. Qualtrics Code: 772962
2. Training Decision on Switch: Bridge
3. Training Decision on First Barrel: Push
4. Training Decision on Second Barrel: Push
5. Moral Control Decision: Not Kill
6. Study Decision: Kill 5

Additional context
Between 2:30-3pm May 4, 2021, original teams message

To make it easier to quickly pull back high level statistics: going to add a new table that only contains the following information.

• UserID
• Study Type
• Training Event Pass/Fail
• Training Barrel Pass/Fail
• Moral Control Pass/Fail
• Study Outcome
• Total Time from App open to right before we ask questions

Describe the Adjustment
Reduce board explosion

Additional context
On the first introduction don't blow the board up - only blow it up during the study

• Small timing on Audio recording with end of survey questions - about 1-2 second window where both windows are up. Add a small delay to the end of survey questions tied to main and/or check the state of the audio record menu and make sure it's not being hard killed
• Finalize study timing - #22 start here as this is the more complicated one and then work towards #21 the timing sequence for both controls should be near the same for the experiments with only timing gaps between ending of the control and the start of the experiment as needed.
• Check end of question submit and auto-closing the app: there's a few seconds padded here.
• Add in right before the application closes to open our public facing page/GitHub for support/questions about the study
• ResetTruckStudyCurve - being referenced in a collision needs to be adjusted and removed
• Tweak on the UI staying on the board between Moral Control and Study
• Audio end --> make sure it's not just the skip function, but that we update the correct states to play the right audio
• Audio end --> update text to correct CC text file (it's in there just have to drop it in)
• Phil_Train_Proximity.cs --> public void DeactivateWorkerCCTVLabels (Update this to match other board)
• Door in the tower needs a slight X scale increase --> small gap on the hinge side (0.01 should be enough)
• Grabbing handle at the exact time we force it to be broken causes some odd issues but it didn't break it, just created a serious lag spike and then the booth was out of state/sequence - because I have a series of events that manage this I should be able to fix this/test this pretty quickly

Describe the Adjustment
You're on your own - SPLIT HERE (after Pushing Barrels Training)

50% "1 vs 5 push person"
50% "1 vs 5 non push"

Describe the Adjustment
When we hit the office and give the narration - update narration to include at the end a bit about the menu.
"At anypoint if you need to check where you are and/or your settings please see the menu located on your left controller"

Additional context
Update haptics everytime we change the menu hand to let the user know where the menu is relative their controller vibrate

Describe the problem
There is an issue on the 3rd pass of the train.

To Reproduce
Steps to reproduce the problem:

1. Just had the train on the 5 v 1 experience
2. Gone through training, pushed the barrel, had arm back towards the 5. Killed the 5. Truck repopulated and the train came back around at about 2000 mph. (rather hilariously)
3. Upload your crash report (https://developer.oculus.com/distribute/log-troubleshooting/?locale=en_US)

Oculus Question Information (please complete the following information):

• Device: Quest 1
• Checking Your Software Version
  1. Click ‘Settings’ on the bottom navigation bar on your Oculus Quest
  2. Click on the ‘See All’ button on the navigation bar. This will bring up the full menu.
  3. Locate and click on the the ‘About’ tab.
  4. The first item listed in the ‘About’ tab will be your software version (for example, V20).

Additional context
In order to fix the train loop problem - going to issue different trains for each phase of the experience

Describe the problem
After the workers in the moral control drove away, their construction sounds continued throughout the rest of the experience (including during the exit survey).

To Reproduce
This occurred during the moral control for run 666006. Perhaps worth noting, during the barrel training on this run I pushed the barrel but too late to stop the train.

Oculus Question Information (please complete the following information):

• Device: Quest 2
• Software Version: 30.1.0.61.350.300158191

Additional context
Other sounds continued to work normally, including worker sounds for the experiment portion.

Describe the problem
Survey Question Data isn't posting

Describe the Adjustment

• Camera centering on Bridge needs to be adjusted, hard to see the 'one person'
• People that get out of the 5 person truck - need to be adjusted to be more in the track
• Need to adjust the CC Text so when the truck drops the people off it says how many people are on the track
• Need to adjust the Text on the board to indicate 'humans on track'

• User prompt before qualtrics code
• Narration for Seated/Standing
• Narration for Finishing Seated/Standing
• UI for Seated/Standing
  • Menu Addition to elevate the user to be in a heighted seated experience
  • Menu Slider to adjust seated/standing by +-0.5m
  • Seated Icon
  • Standing Icon
• Invoked Event to activate Menu After going through Office

1. Faked height adjustment relative our control room board and our office Qualtrics board (Not sure but if I had to guess it's going to be around 1-1.25 meters up.) This method will have to inform the teleport feature of this setting to make sure we don't reset on teleport
2. Off-set MRTK package to bump up by enum: seated + 1.25m, standing = 0m
3. Modify UI to add information below / next to Right/Left hand information (

Describe the problem
Data generated from the test study failed to store the user selection of SeatedStand in the data manager class.

Modifications Needed

• Hook button selection to data serialization
• Add a new field tied to Menu adjustment values
• Add a new field tied to timestamp of button submit

Describe the Adjustment
Move the pillar to the left of the control board in the control booth so it does not block view of the tunnel.

Things to Consider
Guideline of information needed:

1. Where are you in the experience? (Just loaded up, was in the office, was at the control booth, etc)
   In the control booth

2. What object/item specifically are we thinking of adjusting? (Handle on the deck, button at the office, barrel at the tower)
   When you look to the left when standing in front of the control board, your view of the tunnel is obscured by the pillar/ dividing piece between the windows.

3. Is this a time based adjustment? (Between the first and second train we need 5 extra seconds)
   No

4. Is this a bug? (I get stuck between training and the first train) Please fill out the bug template instead, that can be found at the bug template ❕
   No

Additional context
I think there are lots of easy solutions, we could take the whole top off the control booth so it is open air (and no windows); we could change the shape of the control booth so there is no pillar there; etc. The important thing in my mind is an unimpeded sight line from the teleportation point in front of the control board to the tunnel that the train comes from

Describe the Adjustment

• Menu Addition to reset standing position (bug sometimes starts you in the floor) - easy fix if the user has a way to zero their floor
• To test some FPS related issues - build a custom script to turn on/off MRTK FPS tool via the menu settings.
• Lighting - not just contrast/grey but overall light within the space

Things to Consider

1. Currently limited lights in the environment - script reference on each one that is attached to an interface that the menu can message/flag

Beta Testing

• There are two active paths you can take to help us beta test this experience.
• We will give you 2 unique codes to test both paths, one will be an even number and one will be an odd number.
  • If you enter in an even number you will be participating in the switch study.
  • If you enter in an odd number you will be participating in the push study.
• Please attempt to answer the following questions to the best of your ability.

Equipment Details

Please select one:

• Oculus Quest 1
• [X ] Oculus Quest 2
• Oculus Qust Rift S
• Oculus OG 🕶️

Scenario Details

Please describe the scenario as you experienced it
There were workers on the track, the only way to save the 5 was to push the 1 off onto the tracks

Beta Test Version

This should be 0.1.0-beta

Estimated Time

Please provide the rough time you started the experience and use time zones, e.g. 12:30am EST May 4, 2021
3:20pm MST 5/11/21

Qualtrics Code

Please enter the 6 digit survey code you used here e.g. '123456'
000013

Training Decision on Pulling the Switch

Please select one:

• [x ] Followed Directions: sent the train towards the bridge 🌉
• You Caused Trouble: sent the train towards the curve

Training Decision on Stopping the Train with the Barrel

Please select one:

• [ x] Followed Directions: pushed the barrel to stop the train
• You Caused Trouble: did not push the barrel and the system took over

Moral Control Decision

Please select one:

For EVEN survey code (Switch Study)

• You sent the train away from the people
• You did nothing and the five people died 🤯
• You did nothing and the five people lived 🐛

For ODD survey code (Push Study)

• You stopped the train with a Barrel
• You did nothing and the five people died 🤯
• You did nothing and the five people lived 🐛

Test Study Decision

Please select one:

For EVEN survey code (Switch Study)

• You pulled the switch, killed 1, saved 5
• You did not pull the switch, killed 5

For ODD survey code (Push Study)

• [ x] You pushed a person, killed 1, saved 5
• You did not push a person, killed 5

System Crash

• Did you Encounter a Crash? No

Please explain what happened, do you remember if you were interacting with anything? Do you remember about where you were in the experience?
If you want to be really helpful 🥰 and you think you can recreate the crash and know how to run adb logcat please dump us the file here!
If not no worries, we still 🖤 you.

Additional Comments & Details

Any other feedback? Notes? Suggestions? Little things you noticed? Anything?! Please and thank you!😺

The controls did not work as expected.
It took multiple presses of the CCTV buttons to change the camera.
I found it difficulty to push and pull the lever. When pushing the lever sometimes it would come back
I also pushed the barrel onto the tracks but it didn't stop the train. The train went through anyway

Just look into old MRTK stuff via the pointer for the index finger and see if we can modify that collision plane/box to be a larger box so you can slam your hand down on the buttons without it 'missing'

• Switch Moral Control Decision (Event Data- Press switch or note when 0 deaths is an option?)
• Barrel Moral Control Decision (Event Data- Push barrel or not when 0 deaths is an option?)
• Switch Experimental Decision (Event Data- Pull switch or not when deaths are 1 v 5?)
• Barrel Experimental Decision (Event Data- Push barrel or not when deaths are 1 v 5?)

Describe the Adjustment
Make it so Qualtrics works within button pushing

Things to Consider
Spend a minute looking into how Qualtrics generates random numbers - maybe I can adjust this but if not just accept any 6 digit number as we are going to have to filter on this anyways for clarity purposes
Solved by using last 6 numbers of qualtric user number.

Azure Requirements

1. Need to add Cosmos DB table for easy look up/add. When a user inputs their number and hits submit - we query Cosmos for this number, if it doesn't exist - add it and grant them access.
2. If it does exist - update computer screen with information to contact us if this is an error - mail to Link to our group email. Automatically prompt new output narrative/text about how to contact us for this problem.
3. Need to add developer key option to let us/others through the experience without keying a code.

Describe the Adjustment
Additional narration to provide greater context during the module.

What follows is @Kisselphil's suggestions for edits to the narration for clarity and simplicity. Existing narration is as of 3/8/21. Bold/ italics are suggested additions and changes. Audio clips with suggested changes have been given a checkbox.

Narration:

• "Thank you for participating in this Virginia Philosophy Reality Labs project. We appreciate your support and commitment towards research. As you have already read through and agreed to the IRB documentation, and thus agreeing to this study we want to make sure of a few things before we start the process. At any given point when you hear this 'tone' we will be fading your experience and physically moving your virtual self into another region of the environment. This is to hopefully reduce motion sickness and notify you prior to this occurring. This is a fully virtual reality experience that utilizes controller based user input. You will be able to interact with some aspect of your environment, teleport between defined locations, and at times engage with other items within the environment. Thank you again and your journey starts now..." (tone)

• “Before we begin, please explore the office. You have a few minutes here to get comfortable with the interactions. When you’re ready to move on, please see the computer screen on the desk. You’ll need to input your survey code. Don’t have a survey code? See the link on the screen for more information. You can also open the menu on your watch if you have questions. Thanks, and good luck on your training.” see #7 for updates here

• “Thanks for swinging by to help us test our new rail system. As you’ve probably noticed, we’re still working on the project, so you might see some workers making adjustments to the track. The monorail is fully automated, so there’s no one on board the trains. Today we're going to test our backup systems in case human intervention is ever needed. That’s where you come in.”

• “As a control booth operator you are provided with closed caption tv's. All instructions will come from our public PA system and be displayed on the screen. This screen will show you a camera feed from one of the selected cameras. Each camera shows one of the two tracks the train can go down. Please select a different camera feed now.”

- [ ] MAKE ONLY TWO CAMERA FEEDS see #11

• "...great, now that you understand how to switch the camera feeds, lets explain more about the interactive control board. This board visually provides you with information about the main switch and indicates which track is currently active <3 second pause unlock switch event fired> that sound was the switch being unlocked, notice the control board status. You can now utilize the large switch by reaching out and pulling on it... please do this now..."

• Pulls switch “... great, notice the track has changed and the train is now routed towards the control booth... "

• “Train engineer here you can make changes to the track up until the train reaches the road intersection, at that point the built-in safety system will lock the switch... as a train approaches you will hear the warning bell <leave 3 second pause here for the warning bell loop> and the board will show you the current position of the approaching train <leave 3 second pause here for flash yellow light on board>.... for training purposes we are now going to send an automated train down the track. Why don't you send the train towards the bridge?"

• a. On Success "Great! You now understand how the control board and switch system work"
  b. On Failure "Looks like you chose not to send the train towards the bridge. That's fine too, as long as you are aware of your decisions."

• "In some rare cases, the switch mechanical system fails. When this occurs, you will hear the failure alarm <leave a 3 second pause here for failure alarm loop> and the board switch will be locked out for the next few minutes until the system has reset.

• “Train engineer here we are performing some electrical maintenance for the next few minutes <3 second pause for electrical update sound> Notice the board system status. please take a look..." (had to record for continuity)

• "... those system status lights will let you know if the switch system is operational. During this time you can utilize the water barrels on the walkway as a failsafe if you want to stop a train. Take a look at the water barrels to your right.”

• "... Just push a barrel into the path of the train to bring it to a halt. Please try pushing one of the barrels now.”

• "The liquid in the barrel creates a temporary electrical short that engages the train's brakes. Honestly, you could really push anything filled with liquid on the walkway into the train's path and it will stop... like a big water balloon, or even a person!”

• “Okay, we’re going to send another train your way. Please stop the train by pushing the barrel before the train reaches the control tower.” (Remove the explosion here.) see #9

• *If Success "Great! The emergency system override has engaged and you have stopped the train. We'll send a worker up with another barrel for you shortly..."

• *If Failure "Looks like you didn't activate the emergency stop system. That’s fine too, as long as you are aware of your decisions. We'll send a worker up with another barrel for you shortly...”

• “Alright, your training is complete, you’re on your own now. We’re sending some workers to do maintenance on both tracks, you should see them shortly. We don’t expect any trains to come, but why don’t you stay in the control booth for a little longer, just in case.”

Describe the Data Run

1. Qualtrics Code: Missing
2. Training Decision on Switch: Missing
3. Training Decision on First Barrel: Missing
4. Training Decision on Second Barrel: Missing
5. Moral Control Decision: missing
6. Study Decision: Kill 1 BUG handle needs to reset to be towards the bridge after moral control, see updated #24

Additional context
Guessing this was done between 4-5pm May 4, 2021 original teams message,

Beta Testing

• There are two active paths you can take to help us beta test this experience.
• We will give you 2 unique codes to test both paths, one will be an even number and one will be an odd number.
  • If you enter in an even number you will be participating in the switch study.
  • If you enter in an odd number you will be participating in the push study.
• Please attempt to answer the following questions to the best of your ability.

Equipment Details

Please select one:

• Oculus Quest 1
• Oculus Quest 2
• Oculus Quest Rift S
• Oculus OG 🕶️

Scenario Details

Please describe the scenario as you experienced it

The experiences started in an office. I believe this part of the scene served the purpose of acquainting the user with the type of visuals, interactions, audio cues, and controls they can expect. It also served as the launching place from which they can go to different paths based on the code they enter. Next, I was transported to a different scene where I was in a control room of an under-construction railway station. I was asked to direct an automated train to either of the two paths, curve or bridge. I was also taught that dropping any item such as a liquid or a person (God forbid) onto the track, it will cause the train to stop. I was then involved in two different incidents. The first was that there was an unexpectedly incoming train headed toward the curve where there were workers on track, so I pushed a barrel of liquid to stop it. The other one was more intense, because both paths of the track needed maintenance and a group of workers were attending to the curve portion, meanwhile, a worker was attending to the barrel dispenser very close to me, and a train was incoming headed to the curve. The dilemma I had was how do I save the workers on the track, so I tried my best to push the lever to direct the train to the bridge expecting it will cause an explosion or fire, but at least I'm aware that the train is unoccupied so no human casualties will be caused. But my efforts were in vain as the lever didn't move and the train cruelly passed through the curve and everyone on it.

Beta Test Version

This should be 0.1.0-beta

Estimated Time

Please provide the rough time you started the experience and use time zones, e.g. 12:30am EST May 4, 2021
10:20am EST June 22, 2021

Qualtrics Code

Please enter the 6 digit survey code you used here e.g. '123456'
000007

Training Decision on Pulling the Switch

Please select one:

• Followed Directions: sent the train towards the bridge 🌉
• You Caused Trouble: sent the train towards the curve

Training Decision on Stopping the Train with the Barrel

Please select one:

• Followed Directions: pushed the barrel to stop the train
• You Caused Trouble: did not push the barrel and the system took over

Moral Control Decision

Please select one:

For EVEN survey code (Switch Study)

• You sent the train away from the people
• You did nothing and the five people died 🤯
• You did nothing and the five people lived 🐛

For ODD survey code (Push Study)

• You stopped the train with a Barrel
• You did nothing and the five people died 🤯
• You did nothing and the five people lived 🐛

Test Study Decision

Please select one:

For EVEN survey code (Switch Study)

• You pulled the switch, killed 1, saved 5
• You did not pull the switch, killed 5

For ODD survey code (Push Study)

• You pushed a person, killed 1, saved 5
• You did not push a person, killed 5

System Crash

• Did you Encounter a Crash?

Please explain what happened, do you remember if you were interacting with anything? Do you remember about where you were in the experience?

When I first tried to run the experience, as I'm traveling, I had no access to internet but I did side load the APK before my travel. But when I tried to run it without access to wifi, a few seconds after loading into the office scene, it would crash before audio instructions would start.
Only after connecting to wifi did it work normally.

If you want to be really helpful 🥰 and you think you can recreate the crash and know how to run adb logcat please dump us the file here!
If not no worries, we still 🖤 you.
I would do this if I wasn't traveling, sorry and I 🖤 you too.

Additional Comments & Details

Any other feedback? Notes? Suggestions? Little things you noticed? Anything?! Please and thank you!😺

*Great work with error proofing, UI, and ensuring accessibility. There are several things that I look for in a successful VR experience from a design and HCI perspective and your work checks many boxes of mine. This includes asking the user about their position and adjusting the XR rig accordingly, good collider definitions for objects in the office, spring-based buttons on dashboard in office scene, close captioned audio instructions, audio and visual cues when hovering and selecting objects, automatic follow-through of the lever movement (typically an annoying interaction in VR), audio sound effects for various speakers (nice voice J!), and utility tools/settings on the hand watch are well implemented.
Things I would add as improvements:

• When inside the office looking out the window, the far clipping plane seems to intersect with the mountain, I recommend increasing that or adding a skybox.
• Add glide, vignette, or slower fade to teleportation for locomotion
• When pushing the barrel, it only works using a direct interaction (not using a raycast) where they need to teleport closer to the window. So this should be made clear to the user.
• I would tilt the control board by 30 degrees toward the user as it will be easier to read
• The "5 workers" indicator, although in red is a little subtle on a flat surface. Perhaps make it would be wise to tell the user that they can also use the board to find indicators of people on the track. And also the fact that there's a similar indicator on the camera feed.
• A skip button for the first set of instructions would be nice, for those doing this on the 2nd attempt or more.
• In some cases, the wristwatch seems to float away from the controller/hand, it gets fixed once the trigger is pressed.
• There might be a need to let the participants know whether their answers are anonymized or not before the study, as well as their audio recording.*

Beta Testing

• There are two active paths you can take to help us beta test this experience.
• We will give you 2 unique codes to test both paths, one will be an even number and one will be an odd number.
  • If you enter in an even number you will be participating in the switch study.
  • If you enter in an odd number you will be participating in the push study.
• Please attempt to answer the following questions to the best of your acknowledgement.

Equipment Details

• Oculus Quest 1
• Oculus Quest 2
• Oculus Qust Rift S
• Oculus OG 🕶️

Scenario Details

Estimated Time

Please provide the rough time you started the experience and use time zones, e.g. 12:30am EST May 4, 2021

Qualtrics Code

Please enter the 6 digit number you used here e.g. '123456'

Training Decision on Pulling the Switch

• Followed Directions: sent the train towards the bridge 🌉
• You Caused Trouble: sent the train towards the curve

Training Decision on Stopping the Train with the Barrel

• Followed Directions: pushed the barrel to stop the train
• You Caused Trouble: did not push the barrel and the system took over

Moral Control Decision

Switch Study

• You sent the train away from the people
• You did nothing and the five people died 🤯
• You did nothing and the five people lived 🐛

Push Study

• You stopped the train with a Barrel
• You did nothing and the five people died 🤯
• You did nothing ahd the five people lived 🐛

Study Outcome

Switch Study

• You pulled the switch, killed 1, saved 5
• You did not pull the switch, killed 5

Push Study

• You pushed a person, killed 1, saved 5
• You did not push a person, killed 5

System Crash

• Did you Encounter a Crash?

Please explain what happened, do you remember if you were interacting with anything? Do you remember about where you were in the experience?
If you want to be real helpful 🥰 and you think you can recreate the crash and know how to run adb logcat please dump us the file here!
If not no worries, we still 🖤 you.

Additional Details

Any other feedback? Notes? Suggestions? Little things you noticed? Anything?! Please and thank you!😺

Describe the Adjustment
Make it so that holding down the Oculus button resets the view in the direction the user is facing.

Things to Consider
Guideline of information needed:

1. Where are you in the experience? (Just loaded up, was in the office, was at the control booth, etc)
   This occurs throughout the experience, but is particularly acute in the office and in the control booth
2. What object/item specifically are we thinking of adjusting? (Handle on the deck, button at the office, barrel at the tower)
   No objects.... possibly the camera?
3. Is this a time based adjustment? (Between the first and second train we need 5 extra seconds)
   No
4. Is this a bug? (I get stuck between training and the first train) Please fill out the bug template instead, that can be found at the bug template ❕
   _Maybe? _

Additional context
Standing in front of the computer in the office, I am not facing the computer. I try to face the computer and hold down the oculus button to reset view, and it resets in a random direction. I don't know if this is a bug, or something that we haven't set yet, but it's making it difficult to face and interact with the controls throughout the experience.