Movement Module¶
This module is used to code the movement components of a sign. As many instances of this module as necessary can be called for any given sign coding. For more discussion on the use of modules in SLP-AA to encode information about signs, see Modularity.
Select the hand(s) involved in this instance of the module. For movements involving both hands, you can also optionally specify whether the movement described in this instance of the module is in phase or out of phase. If the hands are not out of phase, you can also choose to select if the hands are moving as a connected unit.
Note
Phasing
Movements should be selected to be in phase if the hands have the same specifications for Movement at the same time, and they should be selected as out of phase if the specifications are the same for each hand but with different timing. In either case, choose the specifications that apply to H1, and the specifications for H2 will be predictable from the indication of phasing.
For instance, a two-handed joint-specific movement (like POPCORN) may use one category of movement (like Closing/Opening) for both hands, though the specification for each hand within that category is out of phase with the other (as in, one hand is closing while the other one is opening).
A two-handed perceptual shape movement is out of phase if the hands reach different points of the perceptual shape at the same time, as in PACK or THEATER. Conversely, the movement is in phase if both hands reach the same point of the perceptual shape at the same time, as in ROW or BLANKET.
In the following sample coding of the movement in ROW, all specifications for both hands are identical and the movement is in phase:
The movement of both hands can easily be described together in one instance of Movement.
The following sample coding of the movement in THEATER is similar except that the hands are indicated to be out of phase, since they reach the top of the circle at different times:
The movements of both hands can still be described together in one module instance as long as they are indicated to be out of phase. This allows for quicker sign coding while retaining key information for searching and analysis.
Note
Connectedness
(Add short description here): reference Morgan’s dissertation and/or book. Link to glossary term for connected.
Module instances link to generic x-slots to record information about their timing relative to any others within a sign. For more information on the use of x-slots in SLP-AA, consult Timing & X-Slots.
1. Movement type¶
Select the movement type for the current module. The three movement types are mutually exclusive within an instance of a module; that is, a single instance of the module can be specified for only one of these three types of movement.
Note
No movement
If any portion of a sign includes a prominent moment of intended stillness (for instance, MISS or ONE), select the ‘No movement’ option. When applicable, this is the only selection within the module as it is mutually exclusive with all other movement options. This selection can apply for only one portion of a sign which otherwise does have movement, which is what makes it useful above and beyond the ‘no movement’ options in Sign Type.
Movement type options include:
perceptual shape, as in NORTH
joint-specific movement, as in APPLE
handshape change, as in HIGH_SCHOOL
Note that in SLP-AA, we do not require users to classify movements into the traditional categories of ‘path’ / ‘major’ / ‘primary’ vs. ‘local’ / ‘minor’ / ‘secondary’ movements. Instead, we have classifications for “perceptual shape movements” (e.g., straight, circle, arc), “joint-specific movements” (e.g., twisting, closing), and “handshape changes” (e.g., fingerspelling). As Napoli et al. (2011: 19) point out, “the actual distinction between primary and secondary movement is not uncontroversial and is far from simple.” For example, while wrist movements are typically considered local movements according to articulatory definitions of path and local movement categories (e.g., Brentari, 1998), some of them have been categorized as path movements (van der Kooij, 2002: 229; Sehyr et al., 2021: 269). Furthermore, forcing the choice between path and local movements at the level of phonetic transcription could mask empirical phenomena such as proximalization and distalization (Brentari, 1998), in which both path and local movements can be articulated by non-canonical joints.
In response to these issues, our system allows any movement in which the hand or arm draws a perceptual shape in space to be classified as perceptual movement, with optional manual specifications of the exact (combination of) joints executing the movement under a separate “joint activity” section. For example, the sign NORTH is canonically signed as a straight perceptual movement that is articulated at the shoulder. A distalized version of this sign might be produced with an “un-nodding” wrist movement. In such a case, one could code this either as a joint-specific wrist-nod movement OR one could preserve the ‘phonological intention’ of the perceptual straight movement and simply add the fact that it is articulated with wrist flexion in the joint activity section.
Traditional local movements (relating to particular joints) defined in the literature are listed under the joint-specific movement section, with the associated joint activities optionally autofilled (e.g., the joint-specific movement of “closing” can autofill to flexion of finger joints in the “joint activity” section).
Note that after the movement type selections have been made, there are separate additional sections for coding the joint activity and the movement characteristics.
Note
There is often some flexibility as to whether different components of movement can be counted as separate modules or part of the same one. See Modularity for more in-depth discussion of this idea.
At minimum, for signs with multiple (simultaneous and/or sequential) movements, give each movement type its own module. That is, code any joint-specific movement separately from any movement with perceptual shape as well as any handshape change, as these are mutually exclusive by definition. You can then adjust the timing of each module with respect to the others in the x-slot visualization window.
This means that signs with complex movements like MILK_2 and EVERY_YEAR require at least two movement modules, including a perceptual shape and a joint-specific movement.
The number of modules needed to describe a movement may also depend on your choices in terms of movement characteristics (e.g., how repetitions are coded).
I. Perceptual shape¶
Make your selections from this section if you are coding a movement with perceptual shape. This could be the only movement in a sign, as in NORTH, or a single component of a more complex sign, like the path movements in MILK_2.
Note
As with the other movement types, a module with this specification cannot be combined with the selections for a handshape change or a movement with joint-specific movement. To code any information about other movements in the sign, add additional movement module(s) with the appropriate movement type(s). You can then adjust the timing of each module with respect to the others in the x-slot visualization window. For example, to code the sign MILK_2, one would need two separate instances of the movement module, one for the straight (perceptual shape) movement of the hands and one for the joint-specific opening and closing movements.
a) Shape¶
Select the shape of the movement.
Only one shape option can be specified per module. When you want to indicate multiple perceptual shapes in one sign, as you could for SIGN_LANGUAGE, one way to code the full set of movements is to add as many modules as there are distinct shapes. The timing of each movement with respect to the others can then be seen in the x-slot visualization window. The default list of perceptual shapes can also be edited by the user [ADD REF TO EDITING INFO], so another way to capture the full movement of a new shape is to create a shape label. This may be a useful option for shapes that reappear in many signs.
For the special case of shape combinations where multiple straight movements are signed in a connected sequence, as in CANCEL or SEMESTER, you have the option to select whether any given straight shape interacts with a subsequent straight movement, and then to code each of the straight lines using a separate module. Some signs may include multiple straight shapes that do not form a connected sequence, as in ROOM, in which case you can indicate that the first straight movement does not interact with a subsequent straight movement. This latter option is also used for signs that have only a single straight movement, such as NORTH, and for the final straight movement in a connected sequence.
The default list of shape options is:
Straight
Interacts with a subsequent straight movement
Movement contours cross, for cases of “X”-type shapes, as in CANCEL or HOSPITAL
Subsequent movement starts at end of first, for cases of continuous / connected “V”-, “Z”-, or “7”-type shapes, as in SEMESTER or TRIANGLE (Note that there is also a separate ‘zigzag’ movement option, so care should be taken in terms of deciding when a movement is interpreted as a series of separate, connected straight movements vs. a single multiple-component movement.)
Subsequent movement starts in same location as first, as in the second set of movements of DAISY
Subsequent movement ends in same location as first, as in the first set of movements of SNOWSTORM
Doesn’t interact with a subsequent straight movement, as in NORTH or SCROLL_DOWN (Note that this option would also be used when coding the final movement of a series of interacting straight lines.)
Circle, as in DECORATE_2 or REASON
None of these
b) Axis direction¶
Select an axis direction (or a combination of axis directions) that describe the direction of movement. It is also possible to select an axis without a specific direction.
This section is automatically specified by the program as not relevant when the module includes a circle perceptual shape.
If the hands have opposite specifications for axis direction within every applicable axis, select the checkbox for H1 and H2 move in opposite directions and continue to fill out the instance of the module as it applies to H1. The axis direction for H2 can then be defined implicitly without coding another instance of Movement for each hand. This selection does not apply for signs where the hands move along different (sets of) axes, like TAPE <https://asl-lex.org/visualization/?sign=tape>.
Note
Opposite horizontal directions
Take care in consideration of the horizontal axis, since SLP-AA allows users to select whether the horizontal axis is defined in absolute (toward H1/H2) or relative (ipsilateral/contralateral) terms for each module, where the default for Movement is set as relative directions. (Consult the Global Settings for information on changing these options for each module.)
This means that the interpretation of what is considered the “opposite” direction may depend on the user’s preferences for the horizontal axis. If Movement is defined in terms of relative directions, the movement in FREE has the same axis direction for both hands, as they move in the same relative way (contralaterally or ipsilaterally) at the same time. If Movement is defined in terms of absolute directions, the movement in WINDSHIELD WIPERS has the same axis direction for both hands, as they move in the same absolute way (toward the H1 or H2 side) at the same time. See Symmetry for more information.
Keep in mind that a single instance of the module is meant to convey only one direction of movement, so selecting a combination of axes should be interpreted as a diagonal or angled movement with all of the selected directions applying simultaneously. See the section on Angled axes for a visual description of how this works. To instead indicate a sequence of movements in different planes or directions, create multiple instances of the Movement module, associate them with separate (and sequential) timing values, and select the appropriate direction for each one.
At most one direction can be selected for each axis, so that a total maximum of three directions can apply at once within a module. For a movement that travels back and forth along both directions for a given axis, as in WINDSHIELD_WIPERS, you can either create a new module for each successive change in direction, or you can select that the movement is bidirectional in the movement characteristics options. In the case of bidirectional movements, you should establish a convention for selecting axis direction consistently, such as always selecting the first direction of motion.
The directions for the horizontal axis as they appear in the movement module depend on the preferences of the user as set in the Global Settings. These adhere to one of two models, relative (ipsi/contra) or absolute (toward H1/H2), and these are described in greater detail in Symmetry. By default, the relative set of options apply for Movement:
Horizontal axis: relative [Default]
OR
Horizontal axis: absolute
The endpoints for the vertical and sagittal axes are consistent wherever they appear.
Vertical axis
Sagittal axis
Not relevant, as in ROW. Axis direction is not relevant for this sign because the perceptual shape is circle, whereas axis direction is only relevant for other perceptual shapes.
See Symmetry, Planes & Axes for a visual representation of these options.
Warning
(For Kathleen and Oksana) - relevant to the note below
From the ‘to mention’ doc: One example of where right-left rather than ipsi-contra distinction is useful, if not necessary, is indicating (referential?) signs, as described in Johnson & Liddell 2021 (p. 136-138). Maybe give this example?
Resolved by giving examples of EAST and WEST? Reference J&L.
(We don’t use right and left for the absolute directions anymore, but the reference could still be helpful - Nico)
Note
Left and right vs. H1 and H2 side
In some circumstances, the direction of movement is lexically encoded to be towards a side of the body independent of the signer’s handedness. This is the case for WEST, where the direction of movement is towards the signer’s left (regardless of the signer’s dominant hand), and EAST, where the direction of movement is towards the signer’s right.
Both of the models for the horizontal axis used in SLP-AA can describe the articulated movement in these (and any other) signs, but neither one can capture the the full implications of the lexical definition using only the phonetic descriptors available in Movement. For signs like this, it may be helpful to indicate the definition elsewhere in the sign coding, like in the notes of the Sign Level Information.
c) Plane¶
In some cases, it is useful to specify not just the axis but also the plane (or combination of planes) that is relevant to describe the movement being coded. For each selected plane, you can also choose a circular direction if desired.
This section is automatically specified by the program as not relevant when the module includes a straight perceptual shape.
If the hands have opposite specifications for circular direction within every applicable plane, select the checkbox for H1 and H2 move in opposite directions and continue to fill out the instance of the module as it applies to H1. The circular direction for H2 can then be defined implicitly without coding another instance of Movement for each hand.
Note
Opposite horizontal directions
Take care in consideration of what the “opposite” direction means in the horizontal and vertical planes. SLP-AA allows users to select whether the horizontal axis is defined in absolute (toward H1/H2) or relative (ipsilateral/contralateral) terms for each module, where relative directions are the default for Movement. (Consult the Global Settings for information on changing these options for each module.)
This means that the interpretation of what is considered the “opposite” direction depends in some cases on the user’s preferences for the horizontal axis. If Movement is defined in terms of relative directions, the movement in CLOUD_1 has the same circular direction for both hands, as they move in the same relative way (contralaterally or ipsilaterally) at the same time and share the same specification. If Movement is defined in terms of absolute directions, the movement in DECORATE_2 has the same circular direction for both hands, as they move in the same absolute way (toward the H1 or H2 side) at the same time and share the same specification.
See Symmetry for more information.
This option could also apply in cases that do not involve the horizontal axis, which means both hands move in circles in opposite directions in only the sagittal plane. We do not know of any such cases, as they are biomechanically difficult.
Keep in mind that a single instance of the module is meant to convey only one direction of movement, so a selection of a combination of planes is interpreted as a diagonal or angled movement with all of the selected planes (and circular directions, if applicable) applying simultaneously. See the sections on Angled planes and Angled circular directions for a visual description of how this works. To instead indicate a sequence of movements in different planes or directions, create multiple instances of the Movement module, associate them with separate (and sequential) timing values, and select the appropriate direction for each one.
At most one circular direction can be selected for each plane, so that a total maximum of three directions can apply at once within a module. For a movement that travels back and forth along both circular directions for a given plane, as in WINDSHIELD_WIPERS, you can either create a new module for each successive change in direction, or you can select that the movement is bidirectional in the movement characteristics options. In the case of bidirectional movements, you should establish a convention for selecting circular direction consistently, such as always selecting the first direction of motion.
As with Axis direction, the options for circular directions in planes involving the horizontal axis (which are the horizontal and vertical planes) depend on the user preferences for the movement module as set in the Global Settings. The relative (ipsi/contra) and absolute (toward H1/H2) models for the horizontal axis are described in greater detail in Symmetry. By default, the relative set of options apply for the movement module.
See Circular directions for a description of what we define to be the ‘top of a circle’ for each plane.
Horizontal plane: relative [Default]
Ipsilateral from the top of the circle, as in SWIM or the left hand of DECORATE_2
Contralateral from the top of the circle, as in CELEBRATE or the right hand of DECORATE_2
OR
Horizontal plane: absolute
Toward H1 side from the top of the circle, as in the left hand of CELEBRATE
Toward H2 side from the top of the circle, as in DECORATE_2 or the right hand of CELEBRATE
Vertical plane: relative [Default]
OR
Vertical plane: absolute
Sagittal plane
Not relevant, as in VALIDATE. Plane is not relevant for this sign because the perceptual shape is straight, whereas plane is only relevant for perceptual shapes that are not straight.
See Symmetry, Planes & Axes for a visual representation of these options.
II. Joint-specific movements¶
Make your selections from this section if you are coding a joint-specific movement. This may be the only movement in a sign, as in APPLE, or a single component of a more complex sign, like the closing and opening motions in MILK_2.
Note
As with the other movement types, a module with this specification cannot be combined with the selections for a handshape change or a movement with perceptual shape. To code any information about other movements in the sign, add additional movement module(s) with the appropriate movement type(s). You can then adjust the timing of each module with respect to the others in the x-slot visualization window. For example, to code the sign MILK_2, one would need two separate instances of the movement module, one for the straight (perceptual shape) movement of the hands and one for the joint-specific opening and closing movements.
Each joint-specific movement has two sub-options, which correspond to the two directions a movement can occur in. It is possible to use separate instances of the movement module for each direction, or to use one instance of the module and then code that movement as being ‘bidirectional’ in the movement characteristics section. In the latter case, you would need to establish a convention such as explicitly selecting the direction that the movement starts with. All of our examples below assume this convention.
As with all menus, selecting the sub-option will automatically select the broader option, saving a step of coding. Alternatively, the system does not require that you specify a sub-option, if for any reason it is preferable to leave the direction unspecified or if it is unknown. The appropriate joint activity can optionally be autofilled in the joint activity section once you have selected a sub-option for direction. Autofilling can be turned off in global settings.
The joint-specific movement options are as follows:
Nodding should be selected if the movement begins with a flexion of the wrist, such as CORN_3. This is an example of a sign that contains both nodding and un-nodding, however this option should also be selected for signs where there is only a single nodding motion, such as CAN, or signs where there is a repeated, unidirectional nodding, such as YES. The joint activity section will be autofilled to flexion of the wrist.
Un-nodding should be selected if the movement begins with an extension of the wrist, or if it is the only movement involved, for example GIVE_UP. The joint activity section will be autofilled to extension of the wrist.
To ulnar should be selected if the movement begins with a pivot in the direction of the ulnar surface of the hand, as in COOKIE, or if it is the only direction involved. The joint activity section will be autofilled to radial deviation of the wrist.
To radial should be selected if the movement begins with a pivot in the direction of the radial surface of the hand, or if it is the only direction involved. The joint activity section will be autofilled to ulnar deviation of the wrist.
Pronation should be selected if the movement begins with pronation, or if it is the only direction involved, such as the subordinate hand of DIE. Selecting this will autofill to proximal radioulnar pronation in the joint activity section.
Supination should be selected if the movement begins with supination, or if it is the only direction involved, such as CLAUSE and the dominant hand of DIE. Selecting this will autofill to proximal radioulnar supination in the joint activity section.
Closing should be selected if the movement begins with flexion of all joints of the selected finger(s), or if this is the only direction involved, such as MILK_2. The joint activity section will be autofilled to flexion of [selected finger, all joints].
Opening should be selected if the movement begins with extension of all joints of the selected finger(s), or if this is the only direction involved, such as BOWTIE. The joint activity section will be autofilled to extension of [selected finger, all joints].
Pinching should be selected if the movement begins with adduction of the thumb base joint, such as TURTLE, or if it is the only direction involved. The joint activity section will be autofilled to adduction of thumb base joint.
Un-pinching should be selected if the movement begins with abduction of the thumb base joint, or if it is the only direction involved, such as DELETE. The joint activity section will be autofilled to abduction of thumb base joint.
Flattening should be selected if the movement begins with flexion of the base joints of the selected fingers, such as HORSE, or if it is the only direction involved. The joint activity section will be autofilled to flexion of [selected finger base joints].
Straightening should be selected if the movement begins with extension of the base joints of the selected fingers, or if it is the only direction involved. The joint activity section will be autofilled to extension of [selected finger base joints].
Hooking, or “clawing”, should be selected if the movement begins with flexion of the non-base joints of the selected fingers, or if it is the only direction involved, such as CLAUSE. The joint activity section will be autofilled to flexion of [selected finger non-base joints].
Un-hooking should be selected if the movement begins with extension of the non-base joints of the selected fingers, or if it is the only direction involved, such as UPLOAD. The joint activity section will be autofilled to extension of [selected finger non-base joints].
Spreading should be selected if the movement begins with the abduction of the base joints of the selected fingers, or if it is the only direction involved, such as SEND. The joint activity section will be autofilled to abduction of [selected finger base joints].
Un-spreading should be selected if the movement begins with the adduction of the base joints of the selected fingers, or if it is the only direction involved, such as RUN_OUT_OF or SCISSORS. The joint activity section will be autofilled to abduction of [selected finger base joints].
Thumb crosses over the palm should be selected if the thumb crosses over the palm, as in FEW. The joint activity section will be autofilled to [complex/multi-joint].
Thumb moves away from palm should be selected if the thumb moves away from the palm, as in DOG. The joint activity section will be autofilled to [complex/multi-joint].
Wiggling/Fluttering should be selected if the selected fingers wiggle or flutter, such as in the signs DIRTY, SALT, or BEACH. The joint activity section will be autofilled to both flexion and extension of the selected fingers’ base joints.
The none of these option should be selected for a joint-specific movement that does not seem to correspond with any (single or combination) of the movements in the list above.
III. Handshape change¶
Make your selections from this section if you are coding a handshape change.
Note
As with the other movement types, a module with this specification cannot be combined with the selections for a joint-specific movement or a movement with perceptual shape. To code any information about other movements in the sign, add additional movement module(s) with the appropriate movement type(s). You can then adjust the timing of each module with respect to the others in the x-slot visualization window. For example, to code the sign WORKSHOP, one would need two separate instances of the movement module, one for the circular (perceptual shape) movement of the hands and one for the handshape change from W to S.
No further details of the handshape change itself need to be provided in this section, because they can be better coded in the Hand Configuration Module. It is left to the discretion of the user as to how exactly these two modules interact with each other. For example, in STYLE, one could code five movements (one perceptual shape of the circle that lasts the whole duration of the sign, plus one handshape change movement for each change between letters, S → T, T → Y, Y → L, L → E, each aligned with a timepoint within the whole duration of the sign), or code two movements (one perceptual shape of the circle that lasts the whole duration of the sign, plus one generic handshape change movement that also encompasses the duration of the sign). In either case, there would be five different hand configuration modules instantiated, one for each letter.
2. Joint activity¶
Use the joint activity section to add more fine-grained detail about any joint movements related to the current module. If the module describes a joint-specific movement, then the program can autofill the joint movements that are predictable from the selections made earlier within its movement type section. See the Global Settings for how to change the program’s default autofill behaviour.
(A note on user flexibility: this section can encode the phonetics of proximalization/distalization, differences in sizes of the same perceptual shape based on the joints involved, etc.)