source: trunk/third/xscreensaver/hacks/critical.man @ 15683

Revision 15683, 3.2 KB checked in by ghudson, 24 years ago (diff)
This commit was generated by cvs2svn to compensate for changes in r15682, which included commits to RCS files with non-trunk default branches.
Line 
1.TH XScreenSaver 1 "08 Feb 2000" "X Version 11"
2.SH NAME
3critical - Draw a system showing self-organizing criticality
4.SH SYNOPSIS
5.B critical
6[\-display \fIhost:display.screen\fP] [\-foreground \fIcolor\fP] [\-background \fIcolor\fP] [\-window] [\-root] [\-mono] [\-install] [\-visual \fIvisual\fP] [\-delay \fIseconds\fP] [\-random \fIboolean\fP] [\-ncolors \fIint\fP] [\-offset \fIint\fP]
7.SH DESCRIPTION
8The \fIcritical\fP program displays a self-organizing critical system
9that gradually emerges from chaos.
10
11\fIcritical\fP performs a simulation on a two-dimensional array of
12integers.  The array is initialized to random values.  On each
13iteration, it draws a line to the array position with the greatest
14value.  It then replaces that location and the eight neighboring
15locations with randomly-selected values.
16
17The lines are initially random, but over time a chaotic
18self-organizing system evolves: areas of the screen which happen to
19have lower values are less likely to be updated to new values, and so
20the line tends to avoid those areas.  Eventually, the histogram of
21changes approaches the power-law curve typical of such systems.
22
23The simplest documented self-organizing system is the one-dimensional
24equivalent of \fIcritical\fP.
25
26I heard about this algorithm second-hand: apparently there was an
27article in \fIScientific American\fP describing it sometime in 1997.
28.SH OPTIONS
29.I critical
30accepts the following options:
31.TP 8
32.B \-window
33Draw on a newly-created window.  This is the default.
34.TP 8
35.B \-root
36Draw on the root window.
37.TP 8
38.B \-mono
39If on a color display, pretend we're on a monochrome display.
40.TP 8
41.B \-install
42Install a private colormap for the window.
43.TP 8
44.B \-visual \fIvisual\fP
45Specify which visual to use.  Legal values are the name of a visual class,
46or the id number (decimal or hex) of a specific visual.
47.TP 8
48.B \-delay \fIusecs\fP
49Number of microseconds to wait after drawing each line.
50.TP 8
51.B \-random \fIboolean\fP
52Whether to use randomly selected colours rather than a cycle around
53the colour wheel.
54.TP 8
55.B \-offset \fIinteger\fP
56The maximum random radius increment to use.
57.TP 8
58.B \-ncolors \fIinteger\fP
59How many colors should be allocated in the color ramp (note that this
60value interacts with \fIoffset\fP.)
61.TP 8
62.B \-trail \fIinteger\fP
63Length of the trail: between 5 and 100 is nice.
64.SH ENVIRONMENT
65.PP
66.TP 8
67.B DISPLAY
68to get the default host and display number.
69.TP 8
70.B XENVIRONMENT
71to get the name of a resource file that overrides the global resources
72stored in the RESOURCE_MANAGER property.
73.SH SEE ALSO
74.BR X (1),
75.BR xscreensaver (1)
76.BR xscreensaver-command (1)
77.BR xscreensaver-demo (1)
78.SH COPYRIGHT
79Copyright \(co 1998 by Martin Pool.
80
81Permission to use, copy, modify, distribute, and sell this software
82and its documentation for any purpose is hereby granted without fee,
83provided that the above copyright notice appear in all copies and that
84both that copyright notice and this permission notice appear in
85supporting documentation.  No representations are made about the
86suitability of this software for any purpose.  It is provided "as is"
87without express or implied warranty.
88.SH AUTHOR
89Martin Pool <mbp@humbug.org.au>, 1998-2000.  Based in part on the
90XScreenSaver code by Jamie Zawinski <jwz@jwz.org>.
Note: See TracBrowser for help on using the repository browser.