-
Notifications
You must be signed in to change notification settings - Fork 3
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
000005 #35
Comments
Thanks so much @thetrashy1 for testing out the application! I have your raw data cleaned up to remove some unique information and will be building some additional tests from your contribution/submission. Once we get some of that testing data parsed I am planning on releasing a simple web viewer app that will let you replay your motion and event data. This is probably a few weeks off. Coming up within by next week we are planning on releasing the raw data back to the users and that will be done here with me closing out the issue. Right now this is looking like May 17th, 2021. Specific Feedback from the Comments
|
Created Issue #37 as this needs to be adjusted prior to us going in on the larger study. |
This is really helpful feedback @thetrashy1 , thanks! Would you mind if I followed up in person? |
Sure, I'd be happy to.
…On Thu, May 13, 2021 at 9:26 AM Kisselphil ***@***.***> wrote:
This is really helpful feedback @thetrashy1
<https://github.com/thetrashy1> , thanks! Would you mind if I followed up
in person?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#35 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AUBVOEIRQVFOCPDZEVURCSDTNPHRBANCNFSM44ZPV7UA>
.
--
jefflangevin.com
|
Hey @thetrashy1 thanks for working with us - following up with your data. You can now access the data that we pulled back from this first event here |
Beta Testing
Equipment Details
Scenario Details
Beta Test Version
Estimated Time
Qualtrics Code
Training Decision on Pulling the Switch
Training Decision on Stopping the Train with the Barrel
Moral Control Decision
For EVEN survey code (Switch Study)
For ODD survey code (Push Study)
Test Study Decision
For EVEN survey code (Switch Study)
For ODD survey code (Push Study)
System Crash
Additional Comments & Details
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.
The text was updated successfully, but these errors were encountered: