resources:grogu_setup
Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
| resources:grogu_setup [2024/03/06 10:10] – [Installed MATLAB] admin | resources:grogu_setup [2024/03/07 10:32] (current) – [Third Try] admin | ||
|---|---|---|---|
| Line 10: | Line 10: | ||
| ====== Third Try ====== | ====== Third Try ====== | ||
| + | |||
| + | 2024-02-20 | ||
| In summary, Second Try to install VPixx 3DPixx was doomed by having copied the wrong file to ''/ | In summary, Second Try to install VPixx 3DPixx was doomed by having copied the wrong file to ''/ | ||
| Line 366: | Line 368: | ||
| VPixx (Lindsey Fraser from technical support responding on behalf of Sophie Kenny) replied to me within an hour! Based on the detailed email instructions, | VPixx (Lindsey Fraser from technical support responding on behalf of Sophie Kenny) replied to me within an hour! Based on the detailed email instructions, | ||
| - | 1. Changed line 62 of DatapixxImagingStereoDemo.m | + | ===== 1. Changed line 62 of DatapixxImagingStereoDemo.m |
| + | |||
| Changed the argument from " | Changed the argument from " | ||
| Line 383: | Line 386: | ||
| This made it so that the LCD glasses at least started flickering. | This made it so that the LCD glasses at least started flickering. | ||
| - | 2. Deleted | + | ===== 2. Deleted / |
| + | |||
| + | ([[https:// | ||
| + | |||
| This installed everything to ''/ | This installed everything to ''/ | ||
| Line 508: | Line 514: | ||
| MATLAB was installed to ''/ | MATLAB was installed to ''/ | ||
| + | Had to do '' | ||
| ===== Installed PTB for MATLAB ===== | ===== Installed PTB for MATLAB ===== | ||
| + | |||
| + | I think when I installed the MATLAB-specific version from NeuroDebian, | ||
| + | |||
| + | I did this: | ||
| + | |||
| + | <code bash> | ||
| + | sudo apt-get install matlab-psychtoolbox-3 | ||
| + | </ | ||
| + | |||
| + | |||
| + | Instead of making symlink to Datapixx.mexa64, | ||
| + | |||
| + | |||
| + | '' | ||
| + | |||
| + | ===== Tested 3DPixx with MATLAB PTB ===== | ||
| + | |||
| + | |||
| + | Tried '' | ||
| + | |||
| + | The glasses did flicker noticeably, which is a bigger problem. | ||
| + | |||
| + | I checked the script, and this is the script that has '' | ||
| + | |||
| + | **Update** (2024-02-06 13:20): The display had become set to 85 Hz somehow. | ||
| + | |||
| + | ==== The Datapixx code lines from the script HolesCrowd_PTB_3StimCrowd_TEST.m ==== | ||
| + | |||
| + | I am 100% sure that I copied these lines from DatapixxImagingStereoDemo.m in 2014: | ||
| + | |||
| + | <code matlab> | ||
| + | % Hardware stereo buffers are a great idea, but they just seem to be broken on so many systems. | ||
| + | % Set to 1 to try it out, or set to 0 to implement software frame-alternate buffers. | ||
| + | useHardwareStereo = 0; | ||
| + | |||
| + | [... many lines later: ...] | ||
| + | |||
| + | % Prepare pipeline for configuration. This marks the start of a list of | ||
| + | % requirements/ | ||
| + | PsychImaging(' | ||
| + | | ||
| + | % Tell PTB we want to display on a DataPixx device: | ||
| + | PsychImaging(' | ||
| + | | ||
| + | % Decrease GPU workload | ||
| + | PsychImaging(' | ||
| + | | ||
| + | % Enable DATAPixx blueline support, and VIEWPixx scanning backlight for optimal 3D | ||
| + | Datapixx(' | ||
| + | %Datapixx(' | ||
| + | Datapixx(' | ||
| + | % Datapixx(' | ||
| + | | ||
| + | % | ||
| + | Datapixx(' | ||
| + | | ||
| + | % Consolidate the list of requirements (error checking etc.), open a | ||
| + | % suitable onscreen window and configure the imaging pipeline for that | ||
| + | % window according to our specs. The syntax is the same as for | ||
| + | % Screen(' | ||
| + | if useHardwareStereo == 1 | ||
| + | [w, wRect]=PsychImaging(' | ||
| + | else | ||
| + | [w, wRect]=PsychImaging(' | ||
| + | end | ||
| + | | ||
| + | % There seems to be a blueline generation bug on some OpenGL systems. | ||
| + | % SetStereoBlueLineSyncParameters(w, | ||
| + | % bug on some systems, but breaks on other systems. | ||
| + | % We'll just disable automatic blueline, and manually draw our own bluelines! | ||
| + | if useHardwareStereo == 1 | ||
| + | SetStereoBlueLineSyncParameters(w, | ||
| + | end | ||
| + | blueRectLeftOn | ||
| + | blueRectLeftOff | ||
| + | blueRectRightOn | ||
| + | blueRectRightOff = [wRect(3)*3/ | ||
| + | | ||
| + | | ||
| + | % Initially fill left- and right-eye image buffer with black background | ||
| + | % color: | ||
| + | if useHardwareStereo == 1 | ||
| + | Screen(' | ||
| + | Screen(' | ||
| + | Screen(' | ||
| + | Screen(' | ||
| + | Screen(' | ||
| + | else | ||
| + | Screen(' | ||
| + | Screen(' | ||
| + | end | ||
| + | </ | ||
| + | |||
| + | |||
| + | |||
| + | |||
| + | ==== Tinkering with HolesCrowd_PTB_3StimCrowd_TEST.m ==== | ||
| + | |||
| + | Commented out the line that skips the PTB sync tests. | ||
| + | |||
| + | The line (line 6): | ||
| + | |||
| + | <code matlab> | ||
| + | Screen(' | ||
| + | </ | ||
| + | |||
| + | Ironically, perhaps, there are now some extra flashes and flickers that seem to happen when the background of the display changes, although fortunately not when the letter stimuli appear. | ||
| + | |||
| + | I tried uncommenting-out (turning on) this line: | ||
| + | |||
| + | <code matlab> | ||
| + | | ||
| + | </ | ||
| + | |||
| + | Result: band moves around now = worse than before. | ||
resources/grogu_setup.1709737835.txt.gz · Last modified: by admin
