Package Jitter

jit.linden

Lindenmayer string expansion (L-systems)

Description

The jit.linden object interprets an incoming 1-dim, 1-plane char matrix as a Lindenmayer System (L-system).

Discussion

Named after Aristid Lindenmayer (1925-1989), L-systems work on an interpreted grammar model wherein a syntax is defined for replacing individual elements of the incoming string with a replacement string. These models (called production rules, or just productions ), can be context-dependent. L-systems can also support multiple modes of branching (only one dimension of branching is supported here, though branches can be nested). Generally speaking, L-systems get larger (not smaller) through successive productions (or generations of the grammar); the size of the Jitter matrix used by the object determines the maximum length of the string, so a large matrix is advisable, even if the axiom (starting string) is very small.

The jit.linden object treats the incoming matrix as ASCII, and certain values are reserved to indicate wildcards ( * by default) and branching ( [ and ] by default). These can be set by the wildcard, leftbranch, and rightbranch attributes.

The arguments to the ignore and production attributes should be lists of ASCII characters, e.g.:

ignore F C A tells the jit.linden object to ignore the ASCII characters F , C , and A when checking context during a production match.

typically ignored symbols are characters which describe geo-spatial information (e.g. turtle graphics) and aren't included in the grammar of the production.

production * F * +F[F] tells the object to take every instance of the ASCII character F found in the input matrix and replace it with the string +F[F] . The output string is lengthened as a result, so that the first four generations of an L-system with an axiom of F (as a starting point) would look like this:

+F[F]

++F[F][+F[F]]

+++F[F][+F[F]][++F[F][+F[F]]]

More complex models can be created by adding multiple productions, or by introducing context matching into the L-system grammar. For example:

The message production G F * +F instructs the jit.linden object to replace values of F with +F only if the character preceding the F is a G . Otherwise, the F is simply echoed to the output string unchanged. If you were to give jit.linden the message:

production G F * +F * G * G-

multiple productions are defined. F is replaced as in the example above, but the character G is now replaced by G- as well. Up to 50 productions in the format [left_context] [strict_predecessor] [right_context] [successor_string] can be sent to jit.linden. The predecessor symbol and the left and right contexts must be single characters (though this is not necessarily true for all L-system interpreters). The successor (or replacement string) can be as long as you like.

Typically, the output of the jit.linden object will then be interpreted by an object which scans the string and interprets the symbols as commands. The jit.turtle object interprets L-systems as turtle graphics, so that characters such as F , + , and - acquire special meaning. You could easily use a jit.iter object (or a holding jit.matrix object polled by getcell messages) to access the Lindenmayer string in Max. You can then use the select object against certain ASCII values and use those values to generate any kind of graphical or sonic data you like. The example patches in the Jitter distribution called 'Lindenmayer Examples' give examples of generating 2-D graphics with L-systems within Max/Jitter.

Matrix Operator

matrix inputs:1, matrix outputs:1
Name IOProc Planelink Typelink Dimlink Plane Dim Type
out n/a 1 1 1 1 1 char

More about Matrix Operators

The Jitter MOP

Since the matrix is Jitter's focus, it is not surprising that the majority of Jitter objects fall in this category of Matrix Operators. Every Matrix operator has some number of matrix inputs and some number of matrix outputs. Matrix inputs are referred to by the names "in", "in2", "in3", etc., from left to right, and matrix outputs are referred to by the names "out", "out2", "out3", etc., from left to right--i.e. the names are appended by the input/output number except for the first (leftmost) input and first (leftmost) output which are simply named "in" and "out". We will refer to the input or output name names as the "I/O-name".

Matrix inputs and outputs typically each have their own matrices internally where information is kept. This is necessary because Jitter is an asynchronous framework (i.e. all the matrices don't arrive at all inputs at the same time). Various aspects of matrix inputs and outputs can be set using the command [I/O-name] combined with one of the following suffixes: "_dim" which will set the dimensions of the specified I/O matrix, "_type" which will set the type of the specified matrix, "_planecount" which will set the plane of the specified matrix, or "_name" which will set the name of the specified matrix. There is one special case which does not have an internal matrix and this is the first input "in". This is the case since this special input actually triggers the calculation of the matrix operator, so it doesn't need to be cached until a calulation takes place, unlike the other inputs. Therefore there is no mechanism to set the dim, planecount, type, or name of "in".

Matrix operators accept what we'll refer to as "matrix args"--i.e. [planecount (int)] [ type (symbol)] [dim (int list)] . if these arguments are present, the adapt attribute will be turned off, otherwise it will be turned on. If adapt mode is turned on, each time a matrix is received in the first input, there will also be the equivalent of setting the dim , planecount , and type attributes to that of the input matrix. If the other inputs and outputs are linked to these attributes, this will affect their linked attributes as well. See the "MOP" table to determine which inputs and outputs will be linked to which attributes when adapt mode is turned on. For the leftmost input this is not applicable, and hence all columns are labelled "n/a".

The jit.matrix object is a named matrix which may be used to matrix data storage and retrieval, resampling, and matrix type and planecount conversion operations.

MOP Arguments

planecount[int]
optional

Explicitly sets the number of planes for the output and any righthand inputs. If this is absent, the Matrix Operator will typically adapt to the lefthand incoming matrix attributes, except for special case operators.

type[symbol]
optional

Explicitly sets the type of the matrix for the output and any righthand inputs. If this is absent, the Matrix Operator will typically adapt to the lefthand incoming matrix attributes, except for special case operators.

dimensions[list]
optional

Explicitly sets the dimensions of the matrix for the output and any righthand inputs. If this is absent, the Matrix Operator will typically adapt to the lefthand incoming matrix attributes, except for special case operators.

MOP Attributes

adapt[int]

Matrix adaptation flag (default = 0 if matrix arguments are present, otherwise 1) When the flag is set, the jit.matrix object will adapt to the incoming matrix planecount, type, and dimensions.

[in/out]_dim[32 ints]

The matrix data dimensions (default = 1 1)

[in/out]_name[symbol]

The input or output name of the matrix (default = UID)

[in/out]_planecount[int]

The number of planes in matrix input our output data. Except in special cases, this value is equal to the planecount .

[in/out]_type[symbol]

The input or output matrix data type. Except in special cases, this value is equal to type .

outputmode[int]

Output mode (default = 1 (calculate and output matrix))
0 = No output (no calculation)
1 = Calculate and output the matrix
2 = Pass input (no calculation)
3 = Pass output (no calculation)

type[int]

The matrix data type (default = char
Supported data types are char , long , float32 , or float64 .

MOP Messages

bang

Equivalent to the outputmatrix message.

clear

Sets all cell values in a matrix to zero.

exportattrs

Exports an object's current attributes values in XML format. If no filename is specified, a file dialog will open to let you choose a file.

Arguments:
  • filename [symbol]

getattributes

Sends a sequence of lists out the object's right outlet describing the object's attributes, one line per attribute. Each line listing takes the form attribute attribute-name get get-value set foo set-value data-type(s) number-of-values .

getstate

Sends a sequence of lists describing the object's state out the object's right outlet, one line per attribute. Each line listing line takes the form attribute-name attribute-value1 attribute-value2 ... attribute-valueN .

importattrs

Imports attributes specified in XML format to set the object's attributes. If no filename is specified, a file dialog will open to let you choose a file.

Arguments:
  • filename [symbol]

jit_matrix

Handles input for the named matrix. If this messages is received in the left inlet, output is typically triggered. If this message is received in any other inlet, the data is typically cached until the jit_matrix message is received in the left inlet.

Arguments:
  • matrix-name [symbol]

outputmatrix

Sends the matrix out the left outlet.

summary

Sends a sequence of lists describing the object and it attributes and messages out the rightmost outlet of the object. The first output line takes the form summary objectname object-name . The second and third lines describe the number of inlets and outlets for the object in the form summary (matrixinputcount/matrixoutletcount) number-of-(inlets/outlets) . The fourth line describes the matrixoutput in the form summary matrixoutput descriptor planelink planelink-value typelink typelink-value dimlink dimlink-value types data-type(s) . Each attribute for the object is then listed, one attribute per line. Each line listing takes the form summary attribute attribute-name attribute-value1 attribute-value2 ... attribute-valueN .

Attributes

boundmode[int]

The starting cell for production matching (0 or 1) (default = 1) Possible values:

0 = 'Start at Cell 0'
1 = 'Start at Cell 1'

ignore[128 symbols]

Characters to ignore during context matching

leftbranch[int]

The character value to be interpreted as the start of a branch in the Lindenmayer string (default = 91 (ascii '['))

production[200 symbols]

A list of symbols in the format left_context strict_predecessor right_context successor_string ... that defines the production rules of the L-system (default = none)

rightbranch[int]

The character value to be interpreted as the start of a branch in the Lindenmayer string (default = 93 (ascii ']'))

wildcard[int]

The character value to be interpreted as a wildcard in the Lindenmayer string (default = 42 (ascii '*'))

Common Box Attributes

Below is a list of attributes shared by all objects. If you want to change one of these attributes for an object based on the object box, you need to place the word sendbox in front of the attribute name, or use the object's Inspector.

annotation[symbol]

Sets the text that will be displayed in the Clue window when the user moves the mouse over the object.

background[int]: 0

Adds or removes the object from the patcher's background layer. background 1 adds the object to the background layer, background 0 removes it. Objects in the background layer are shown behind all objects in the default foreground layer.

color[4 floats]

Sets the color for the object box outline.

fontface[int]

Sets the type style used by the object. The options are:

plain
bold
italic
bold italic Possible values:

0 = 'regular'
1 = 'bold'
2 = 'italic'
3 = 'bold italic'

fontname[symbol]

Sets the object's font.

fontsize[float]

Sets the object's font size (in points). Possible values:

'8'
'9'
'10'
'11'
'12'
'13'
'14'
'16'
'18'
'20'
'24'
'30'
'36'
'48'
'64'
'72'

hidden[int]: 0

Toggles whether an object is hidden when the patcher is locked.

hint[symbol]

Sets the text that will be displayed in as a pop-up hint when the user moves the mouse over the object in a locked patcher.

ignoreclick[int]: 0

Toggles whether an object ignores mouse clicks in a locked patcher.

jspainterfile[symbol]

You can override the default appearance of a user interface object by assigning a JavaScript file with code for painting the object. The file must be in the search path.

patching_rect[4 floats]: 0. 0. 100. 0.

Sets the position and size of the object in the patcher window.

position[2 floats]
write-only

Sets the object's x and y position in both patching and presentation modes (if the object belongs to its patcher's presentation), leaving its size unchanged.

presentation[int]: 0

Sets whether an object belongs to the patcher's presentation.

presentation_rect[4 floats]: 0. 0. 0. 0.

Sets the x and y position and width and height of the object in the patcher's presentation, leaving its patching position unchanged.

rect[4 floats]
write-only

Sets the x and y position and width and height of the object in both patching and presentation modes (if the object belongs to its patcher's presentation).

size[2 floats]
write-only

Sets the object's width and height in both patching and presentation modes (if the object belongs to its patcher's presentation), leaving its position unchanged.

textcolor[4 floats]

Sets the color for the object's text in RGBA format.

textjustification[int]

Sets the justification for the object's text. Possible values:

0 = 'left'
1 = 'center'
2 = 'right'

varname[symbol]

Sets the patcher's scripting name, which can be used to address the object by name in pattr, scripting messages to thispatcher, and the js object.

See Also

Name Description
jit.conway Play Conway's game of life
jit.turtle 2-d turtle graphics interpreter