Package semantics

Applies fn to arg by creating a FunctionApplication and returns the result. This is used for formalism-unspecific access to this feature.

Returns the concatenation of the two lists. Uses existing instances passed in, so make sure they're copies if you don't want your original objects modified.

Produces a list of (x,y) coordinates in the tonal space, given a List or CoordinateList.

Parameters:

• lst (List) - list from the semantics representing constraints on a TS path
• start_block (pair of ints) - enharmonic block to start in (if other than the default (0,0))

Returns:

2D coordinates of the path through the tonal space and the times at which they were reached.

Like list_lf_to_coordinates, but produces a list of (function,time) pairs instead of (coordinate,time).

Parameters:

• lst (List) - list from the semantics representing constraints on a TS path

Returns:

function strings of points on the path through the tonal space and the times at which they were reached.

Generates a list of (coordinates,time) tuples given a parse result.

Raises:

• ValueError - if the result can't produce a list of coordinates.

Generates a list of (function,time) tuples given a parse result.

Raises:

• ValueError - if the result can't produce a list of coordinates.

Builds a logical form given a list of states and the chords they were assigned to. Accepts a list of labels,time and return a logical form for the formalism (a Semantics in this case).

This uses the special logical form classes CoordinateList and PathCoordinate.

Builds a Semantics instance from a string representation of the logical form. This is mainly for testing and debugging and shouldn't be used in the wild (in the parser, for example). This is not how we construct logical forms out of the lexicon: they're specified in XML, which is a safer way to build LFs, though more laborious to write.

The strings may be constructed as follows.

Tonic semantics: "<x,y>". This will build an EnharmonicCoordinate.

List: "[ITEM0, ITEM1, ...]". This will build a List.

List concatenation: "LIST0+LIST1", that is with infix notation. This will build a ListCat.

Variable: "$x0". Begin every variable with a $, as if you're writing PHP or Bash, or something. Use any variable name and, optionally, a number. If no number is given, 0 will be used by default.

Predicates - leftonto, rightonto: "leftonto(...)", etc. Builds a FunctionApplication with the predicate as its functor.

Now: "now@x(...)". Works like the other predicates, but has the special "@x" value to give it a time.

Lambda abstraction: "\$x.EXPR". Use a backslash to represent a lambda. You can have multiple abstracted variables, which will result in multiple nested abstractions. EXPR can be any expression.

Function application: "(FUNCTOR ARGUMENT)". Always enclose a function application in brackets, even if you wouldn't write them.

Note that the output is not beta-reduced.

INTERVAL_TO_NN

Value:

{0: (0, 0), 1: (-1, -1), 2: (2, 0), 3: (1, -1), 4: (0, 1), 5: (-1, 0), 6: (-2, -1), 7: (1, 0), ...