research:internal_small_version
Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
| research:internal_small_version [2016/11/04 14:54] – anthony | research:internal_small_version [2019/05/22 16:08] (current) – external edit 127.0.0.1 | ||
|---|---|---|---|
| Line 254: | Line 254: | ||
| Exact notes on Blender as follows- | Exact notes on Blender as follows- | ||
| - | Blender Tasks: | + | ==== Blender Tasks: |
| -Record Video of participant. | -Record Video of participant. | ||
| Line 269: | Line 270: | ||
| __**James & Agilay**__: working on tracking participant responses and programming loops. Still a work in progress. | __**James & Agilay**__: working on tracking participant responses and programming loops. Still a work in progress. | ||
| - | Stephanie: working on character movements within virtual environment. Significant progress made here! We can now make a character capable of crouching, however a little more work needs to be done specifying game physics (e.g. object and character physical boundaries). | + | __**Stephanie**__: working on character movements within virtual environment. Significant progress made here! We can now make a character capable of crouching, however a little more work needs to be done specifying game physics (e.g. object and character physical boundaries). |
| - | __ | + | |
| - | **Priya & Dale**__: working on boundaries and game physics. Still a work in progress. | + | |
| - | WHAT'S HAPPENING NEXT: | + | __**Priya & Dale**__: working on boundaries and game physics. Still a work in progress. |
| + | |||
| + | |||
| + | \\ | ||
| + | |||
| + | ==== WHAT'S HAPPENING NEXT: ==== | ||
| We came to the conclusion that it's time to start sourcing our work into one working draft. Anthony believes the solution is to use Git. Git will allow us to concatenate our Blender files with the goal of creating a version of the Blender game that we can use for the actual study. | We came to the conclusion that it's time to start sourcing our work into one working draft. Anthony believes the solution is to use Git. Git will allow us to concatenate our Blender files with the goal of creating a version of the Blender game that we can use for the actual study. | ||
| - | GOAL(S): | + | === GOAL(S): |
| Finishing coding before SONA pool closes. | Finishing coding before SONA pool closes. | ||
| Line 287: | Line 291: | ||
| I definitely think the remaining issues can be figured out before the SONA pool closes. I anticipate having figured out all of the remaining kinks in the looping/ | I definitely think the remaining issues can be figured out before the SONA pool closes. I anticipate having figured out all of the remaining kinks in the looping/ | ||
| - | Special thanks to Stephanie for the demo today (everything looks really great and has a polished feel). Good job so far everyone! | + | Special thanks to __**Stephanie**__ for the demo today (everything looks really great and has a polished feel). Good job so far everyone! |
| + | \\ | ||
| __**Agilay**__: | __**Agilay**__: | ||
| Line 310: | Line 315: | ||
| There are two or three approaches to tracking cursor behavior (including panning/ | There are two or three approaches to tracking cursor behavior (including panning/ | ||
| - | Way one: | + | == Way one: == |
| - | *render video images in blender with shading | + | |
| - | *use that shading to emulate 3d (panning/ | + | |
| - | Way two: | + | * render video images in blender with shading |
| - | *translate | + | * use that shading to emulate 3d (panning/ |
| - | and one for a reference frame. | + | |
| - | *problem; figure out how to deal with movie image being cutoff (this stops the tracking and makes | + | |
| - | mars reference frame tracking judgments made with blender...still figuring out the solution to this. | + | |
| - | + | ||
| - | To Do List: | ||
| - | get everyone up to speed on blender tracking. | + | == Way two: == |
| - | figure out if 3d shading render is a viable option | + | * translate panning/ |
| + | * problem; figure out how to deal with movie image being cutoff | ||
| + | |||
| + | |||
| + | === To Do List: === | ||
| - | be able to obtain coordinates from python text file. | + | * get everyone up to speed on blender tracking. |
| + | * figure out if 3d shading render is a viable option for cursor tracking (panning/ | ||
| + | * be able to obtain coordinates from python text file. | ||
| \\ | \\ | ||
| Line 348: | Line 352: | ||
| There is also an option in Blender under File -> Export -> COLLADA (.dae) that will create a COLLADA file. Wikipedia describes this format as a 3D interchange file format, and says python has a module called pycollada that will read this data. The link above suggests you can use python to export this data into .csv if needed. | There is also an option in Blender under File -> Export -> COLLADA (.dae) that will create a COLLADA file. Wikipedia describes this format as a 3D interchange file format, and says python has a module called pycollada that will read this data. The link above suggests you can use python to export this data into .csv if needed. | ||
| - | |||
| \\ | \\ | ||
| + | ===== 02/15/2017 Lab meeting: Re-introduction to study and Task List ===== | ||
| + | |||
| + | 1. Aesthetics: Presence and characteristics of floor, ceiling, walls, other computers, etc. | ||
| + | |||
| + | 2. Make Blender file an executable module. | ||
| + | |||
| + | 3. Putting words on the screen (one image with words and one image with just boxes) | ||
| + | |||
| + | 4. Generating and exporting the data file | ||
| + | |||
| + | 5. Making poison-boxes for all the words | ||
| + | |||
| + | 6. Blender tracking (Stephanie and James posted links about how to do this above) | ||
| + | |||
| + | 7. Writing IRB | ||
| + | 8. Assigning experimenter roles to everyone | ||
| Line 372: | Line 391: | ||
| ~~TODOLIST showdate: | ~~TODOLIST showdate: | ||
| - | |||
research/internal_small_version.1478285692.txt.gz · Last modified: 2019/05/22 16:08 (external edit)