(To add notes: log in, click on the pencil-looking icon to the right to edit, and then just start typing …)
James had made a folder
…/VNLab/Blender Tracking/ to hold useful Blender files. Today Anthony changed the folder's name to
blender and moved it to a new location:
[taken by Daijreous Poole (?)]
[Headings represent AC's attempt to organize comments into themes.]
Specify first set of tasks with target dates.
SR (2015.10.24): Downloaded and tried MouseTracker (http://www.mousetracker.org/)
[AC's notes ahead of meeting:]
Define keyboard functions: up/down/L/R arrows control panning mouse wheel controls zooming [should be default:] mouse x/y controls cursor location Begin trial loop Display entire image (maximally zoomed out). Overlay thumbnail of entire image in small pane. Move cursor to center of display. Begin display update loop (infinite) Check keyboard state Change both images as needed Check mouse state Change cursor location as needed if maximally zoomed in Allow mouse click Check mouse button state if mouse button down record x/y location continue to next trial end end save all keyboard, mouse, button states end display update loop end trial loop
The base distribution of MATLAB includes functions for automatically generating a second panel that shows an overview with a rectangle that shows the visible part of the main image:
AC made a new directory on uniqua:
“lsnd” stands for “Learning in Small Non-interactive Displays,” which is meant to mean the opposite of the abbreviation of the overall study (LLID = Learning in Large Interactive Displays).
Made 3 matlab scripts by copying code from websites:
This is a function that sets up an image overview pane.
This is a script that calls the above function and displays an image.
This is a function/script that demonstrates how to assign a function to the scroll wheel. The function is a pretty useless one for our purposes: it resets the scale of the x-axis.
OLD TODO: Integrate scroll_wheel.m function into scroll_display_TEST.m script, and change scroll wheel function to do zooming in and out.
The goal for this semester was to figure out how to track cursor movement on the small screen. To do this we have been learning how to use a software called Blender. On the other hand, Anthony has been trying to do the same using MATLAB. By the end of the semester, we hope to figure out soon which software to use for the final study.
Exact notes on Blender as follows-
-Record Video of participant.
-Find tracking points to track zooming: Zooming can be tracked and quantified based on the screen recording inside of blender.
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).
Priya & Dale: working on boundaries and game physics. Still a work in progress.
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.
Finishing coding before SONA pool closes.
Figure out remaining game physics and looping issues.
NOTE FROM JAMES:
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/respawning over spring break. I'll also work on the game physics.
Special thanks to Stephanie for the demo today (everything looks really great and has a polished feel). Good job so far everyone!
Found http://sourceforge.net/projects/minimousemacro/ This is a mouse macro Recorder. Determined not to be ideal – ruled out
The seemingly random links I posted below reflect my attempt to make zoom/scaled distances on a screen congruent with actually moving up to an object in real-life. This approach is sort of a hybrid of the two different ways I was working on and is the most promising; the others would work, but individually they have pieces that can be successfully integrated to do what we want! I can explain more in a lab meeting/or in person.
There are two or three approaches to tracking cursor behavior (including panning/zooming) using blender.
Stephanie found this page with instructions on how to extract raw object tracking data on 11/16/15:
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.
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
NOTE: the lists below are automatically generated based on searching the rest of the page above. Add new “to do” items in the main body of the page (above here), not here.