Skip to content

Standard Accesses

Description

Creates an access on an object.

(make-access ... )

Syntax and Default Values

A generic access can be created using the following Lisp syntax:

(make-access object_reference controller direction)

Parameters

the make-access function requires the following arguments:

  • object_reference: name of the object on which the access will be located.
  • controller: describes the location of the access on the object.
  • direction: chooses one of the possible directions of movement of the access.

Controllers

The dimension of the controller provided as an argument depends on the type of object being accessed. For example, for a string, the controller should have one dimension, and be a value between 0 and 1 (representing the endpoints of the string). For a circular membrane, however, a two-dimensional controller is necessary; the first dimension is a distance from the center (0-1), and the second dimension is an angle in degrees. Details about the accesses on specific objects can be found in the object reference page entries themselves.

Directions of Movement

Different objects use different directions of movement. The following is a list of possible direction types:

  • 'trans0 - transversal along the X axis - used for mono- and bi-directional strings and masses
  • 'trans1 - transversal along the Y axis - used for bi-directional strings and masses
  • 'long - longitudinal - used for tubes
  • 'normal - used for 2D surfaces such as plates, membranes and bars
  • 'top-vertical - specific to the violin and cello bridges
  • 'top-horizontal - specific to the violin and cello bridges
  • 'base - specific to the violin and cello bridges
  • 'decoded - direct access to any and all of the object's points on a modal point-by-point basis.
  • 'xyz - used for finite-element objects. Modalys will locate the closest point on the mesh relative to the one defined by the 3 coordinates given in the controller.

Details about the direction in which an object can be accessed can be found in the object reference page entries themselves. For each type of object, a subset of these directions of movement is appropriate. For example, a bi-string can have accesses in either the 'trans0 or 'trans1 direction (first and second transverse directions). A closed-closed-tube or closed-open-tube can only be accessed in the long (longitudinal) direction. Membranes and plates are accessed in the normal direction (this is “normal” in the mathematical sense, i.e. at right angles to both dimensions of the membrane). The 'decoded direction is explained in the access options, below.

Options

Decoded Accesses

All objects can additionally be accessed using “decoded” accesses. To understand these, you need to know that internally, Modalys discretizes objects in space. Imagine a membrane covered with discrete points. Modalys can really only compute accesses on a per-point basis. When you say you'd like an access at (0.3 0.4) on a membrane, this location is probably not exactly on a point, so Modalys actually takes a weighting of four points to approximate your access. Using “decoded” accesses permits you to bypass this “point translation phase” (PTP) and directly say how much of each point you would like. So if you want to access the middle of a mono-dimensional string with 10 modes and 9 points, you could write either of these two statements:

(make-access my-string (const .5) 'trans0)
or:

(make-access my-string (const 0 0 0 0 1 0 0 0 0) 'decoded)
As you can see, using a decoded accesses allows you to do some slightly weird things, like being able to “spread” your access over half of the string by typing:

(make-access my-string (const .2 .2 .2 .2 .2 0 0 0 0) 'decoded)
Unfortunately, the disadvantage to all of this is that in most cases, you can't know exactly how many points Modalys used for a given object, and you also can't know exactly how the points are laid out on the object surface. So what's the use of this? Well, in two cases you do know the number of points — when you used compiled accesses (see the make-compiled-access explanation) and when you use (make-object 'read-from-file ...) to create your model.

Shared Accesses

Accesses can be shared - in other words, one access can be used for multiple connections. Beware though that in some cases the physical equations might not subsequently be solvable and error messages will be issued during synthesis. This is often the case if you try to impose a certain position at a certain access, with a 'position connection for example, and at the same time trying to impose a certain speed to the same location, with a 'strike interaction, for example.

Generally, however, it can be safer (and conceptually easier, even though slightly more computationally expensive) to create an access for each use, such as an access for a point-output at the same location as an input force, etc....