Skip to content

Commit d0b6e68

Browse files
kleinermkleinerm
committed
Documentation update for 3.0.19.16 release.
1 parent 57efaf1 commit d0b6e68

File tree

4 files changed

+58
-54
lines changed

4 files changed

+58
-54
lines changed

‎docs/PsychGLImageProcessing.md‎

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -61,6 +61,8 @@ soon with more useful infos...
6161
[MakeTextureDrawShader](MakeTextureDrawShader) - Create GLSL shader for use with [Screen](Screen)('DrawTexture') and [Screen](Screen)('MakeTexture')
6262
to apply on-the-fly texture filtering operations during texture draw.
6363

64+
[PsychColorCorrection](PsychColorCorrection) - Routines for gpu accelerated color correction via [PsychImaging](PsychImaging)().
65+
6466
[PsychHDR](PsychHDR) - Support and control stimulus display to HDR "High dynamic range" displays.
6567

6668
[PsychImaging](PsychImaging) - Generic setup routine for the imaging pipeline. Allows to setup

‎docs/PsychImaging.md‎

Lines changed: 9 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -683,13 +683,15 @@ actions:
683683
with 10 bit precision per color channel (10 bpc / 30 bpp / "Deep color")
684684
on graphics hardware that supports native 10 bpc framebuffers.
685685

686-
Under Linux, all AMD graphics cards since at least 2007, [NVidia](NVidia) graphics cards
687-
since 2008, and Intel graphics chips since at least 2010 do support native
688-
10 bit framebuffers. Intel graphics chips must use the X11 "intel" video driver
689-
to output their 10 bit framebuffers with actual 10 bit precision, the alternative
690-
"modesetting" video driver does not support output with more than 8 bit yet.
691-
[XOrgConfCreator](XOrgConfCreator) will take care of this Intel quirk when creating a custom xorg.config
692-
for such 10 bpc setups under Intel.
686+
Under Linux, AMD graphics cards since at least the year 2007, [NVidia](NVidia) graphics
687+
cards since 2008, and Intel graphics chips since at least 2010 do support native
688+
10 bit framebuffers. Intel graphics chips must use the legacy X11 "intel" video driver
689+
to output their 10 bit framebuffers with actual 10 bit precision on Ubuntu
690+
20.04 LTS or earlier, as old "modesetting" video drivers do not support output
691+
with more than 8 bit. On Ubuntu 22.04-LTS and later, the modern modesetting driver
692+
can deal with 10 bpc output on all Intel graphics, so at least Ubuntu 22.04-LTS is
693+
recommended. [XOrgConfCreator](XOrgConfCreator) will take care of these Intel quirks when creating a
694+
custom xorg.config for such 10 bpc setups under Intel.
693695

694696
Under MS-Windows, many graphics cards of the professional class AMD/ATI Fire/Pro
695697
series (2008 models and later), and all current models of the professional class

‎docs/RenderDemo.md‎

Lines changed: 46 additions & 46 deletions
Original file line numberDiff line numberDiff line change
@@ -1,64 +1,64 @@
11
# [RenderDemo](RenderDemo)
22
##### >[Psychtoolbox](Psychtoolbox)>[PsychDemos](PsychDemos)
33

4-
[RenderDemo](RenderDemo)
4+
[RenderDemo](RenderDemo)
55

6-
Illustrates calibration interface for simple task of producing a uniform
7-
color patch of desired CIE xyY coordinates.
6+
Illustrates calibration interface for simple task of producing a uniform
7+
color patch of desired CIE xyY coordinates.
88

9-
The calculation is done with respect to the current PTB demonstration
10-
calibration file.
9+
The calculation is done with respect to the current PTB demonstration
10+
calibration file.
1111

12-
The demo shows multiple different ways to implement this, starting with a
13-
purely Matlab based method, progressing to more advanced methods. The
14-
final demonstration shows how to do it automatically and graphics
15-
hardware accelerated.
12+
The demo shows multiple different ways to implement this, starting with a
13+
purely Matlab based method, progressing to more advanced methods. The
14+
final demonstration shows how to do it automatically and graphics
15+
hardware accelerated.
1616

17-
### Demo 1:
17+
### Demo 1:
1818

19-
The RGB values are gamma corrected and live in the range [0,1]. If they
20-
contain 0 or 1, the xyY coordinates requested may have been out of gamut.
19+
The RGB values are gamma corrected and live in the range [0,1]. If they
20+
contain 0 or 1, the xyY coordinates requested may have been out of gamut.
2121

22-
A uniform color patch is displayed in the MATLAB figure window. This is
23-
not a well-controlled display method, but does give a sense of the patch
24-
color if the calibration file is a reasonable description of the display.
22+
A uniform color patch is displayed in the MATLAB figure window. This is
23+
not a well-controlled display method, but does give a sense of the patch
24+
color if the calibration file is a reasonable description of the display.
2525

26-
Immediately afterwards, the same color patch is shown in a PTB onscreen
27-
window, with the same gamma table loaded which was used during
28-
calibration measurements. This should render an accurate stimulus.
26+
Immediately afterwards, the same color patch is shown in a PTB onscreen
27+
window, with the same gamma table loaded which was used during
28+
calibration measurements. This should render an accurate stimulus.
2929

30-
Demo 2: As demo 1, but displaying in a onscreen window and performing the
31-
gamma correction via proper inverse gamma lookup tables loaded into the
32-
graphics card, thereby presenting on a linearized display, instead of
33-
using the [SensorToSettings](SensorToSettings)() routine to adapt the stimulus to a
34-
non-linearized display.
30+
Demo 2: As demo 1, but displaying in a onscreen window and performing the
31+
gamma correction via proper inverse gamma lookup tables loaded into the
32+
graphics card, thereby presenting on a linearized display, instead of
33+
using the [SensorToSettings](SensorToSettings)() routine to adapt the stimulus to a
34+
non-linearized display.
3535

36-
The last two demos Demo 3 and Demo 4 require a recent graphics card and
37-
perform all color space conversions and calibrated display automatically
38-
and hardware accelerated on the graphics card. Any [NVidia](NVidia) [GeForce](GeForce)-8000 or
39-
later, AMD Radeon X-1000 or later, or Intel HD graphics card should be
40-
able to support these demos.
36+
The last two demos Demo 3 and Demo 4 require a recent graphics card and
37+
perform all color space conversions and calibrated display automatically
38+
and hardware accelerated on the graphics card. Any [NVidia](NVidia) [GeForce](GeForce)-8000 or
39+
later, AMD Radeon X-1000 or later, or Intel HD graphics card should be
40+
able to support these demos.
4141

42-
Demo 3: The stimulus is defined in XYZ tristimulus color space and
43-
converted automatically by [Screen](Screen)() into RGB output format, taking the
44-
calibration data in 'cal' into account.
42+
Demo 3: The stimulus is defined in XYZ tristimulus color space and
43+
converted automatically by [Screen](Screen)() into RGB output format, taking the
44+
calibration data in 'cal' into account.
4545

46-
Demo 4: The stimulus is directly defined in xyY chromacity + luminance
47-
format and all conversions and calibrations are done automatically by
48-
[Screen](Screen)().
46+
Demo 4: The stimulus is directly defined in xyY chromacity + luminance
47+
format and all conversions and calibrations are done automatically by
48+
[Screen](Screen)().
4949

50-
4/26/97 dhb Wrote it.
51-
7/25/97 dhb Better initialization.
52-
3/12/98 dgp Use [Ask](Ask).
53-
3/14/02 dhb Update for [OpenWindow](OpenWindow).
54-
4/03/02 awi Merged in Windows changes. On Windows we do not copy the result to the clipboard.
55-
4/13/02 awi Changed "[SetColorSpace](SetColorSpace)" to new name "[SetSensorColorSpace](SetSensorColorSpace)".
56-
Changed "[LinearToSettings](LinearToSettings)" to new name "[SensorToSettings](SensorToSettings)".
57-
12/21/02 dhb Remove reliance on now obsolete [OpenWindow](OpenWindow)/[CloseWindow](CloseWindow).
58-
11/16/06 dhb Start getting this to work with PTB-3.
59-
11/22/06 dhb Fixed except that [Ask](Ask)() needs to be fixed.
60-
6/16/11 dhb The PTB display section was out of date and didn't work. I removed it.
61-
1/26/13 mk Add standard PTB display, but also imaging pipeline based methods.
50+
4/26/97 dhb Wrote it.
51+
7/25/97 dhb Better initialization.
52+
3/12/98 dgp Use [Ask](Ask).
53+
3/14/02 dhb Update for [OpenWindow](OpenWindow).
54+
4/03/02 awi Merged in Windows changes. On Windows we do not copy the result to the clipboard.
55+
4/13/02 awi Changed "[SetColorSpace](SetColorSpace)" to new name "[SetSensorColorSpace](SetSensorColorSpace)".
56+
Changed "[LinearToSettings](LinearToSettings)" to new name "[SensorToSettings](SensorToSettings)".
57+
12/21/02 dhb Remove reliance on now obsolete [OpenWindow](OpenWindow)/[CloseWindow](CloseWindow).
58+
11/16/06 dhb Start getting this to work with PTB-3.
59+
11/22/06 dhb Fixed except that [Ask](Ask)() needs to be fixed.
60+
6/16/11 dhb The PTB display section was out of date and didn't work. I removed it.
61+
1/26/13 mk Add standard PTB display, but also imaging pipeline based methods.
6262

6363

6464

‎docs/Screen-FrameOval.md‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,7 @@
11
# [Screen('FrameOval')](Screen-FrameOval)
22
##### [Psychtoolbox](Psychtoolbox)>[Screen](Screen).{mex*} subfunction
33

4-
Screen('FrameOval', windowPtr [, color] [, rect] [, penWidth] [, penHeight] [, penMode]);
4+
Screen('FrameOval', windowPtr [,color] [,rect] [,penWidth] [,penHeight] [,penMode]);
55

66
Draw the outline of an oval inscribed in "rect". "color" is the clut index
77
(scalar or [r g b] triplet) that you want to poke into each pixel; default

0 commit comments

Comments
 (0)