Programmer Guide/Command Reference/EVAL: Difference between revisions

From STX Wiki
Jump to navigationJump to search
Line 464: Line 464:
  // Result: the path of the GDX file containing the spectrogram
  // Result: the path of the GDX file containing the spectrogram
  //---
  //---
     #path := [[Programmer_Guide/Command_Reference/UNIQUE|unique^]] '$@work' gdx 1 8        // get unique output file name
     #path := [[Programmer_Guide/Command_Reference/UNIQUE|unique]] '$@work' gdx 1 8        // get unique output file name
     #lfft := eval [[Programmer_Guide/Command_Reference/EVAL/fft|fft]]($#len)                // compute transformation length
     #lfft := eval [[Programmer_Guide/Command_Reference/EVAL/fft|fft]]($#len)                // compute transformation length
     #nfrm := int $#wave[!length] / $#hop    // compute number of frames
     #nfrm := int $#wave[!length] / $#hop    // compute number of frames

Revision as of 15:20, 25 April 2014

The EVAL command implements the evaluation of numerical expressions. These expressions may be built up from numerical constants, from scalar, vector, and matrix variables, and from a large number of functions and operators.

The EVAL command was added to the STx language in version 3.7. It replaces and extends the old EVALUATE command.

See also INT (INTCHECK) and NUM (NUMCHECK) for commands evaluating simpler forms of expressions.

Syntax

General

The EVAL command uses the following general syntax:

target := eval expression

or

target := evalcheck expression
target
This is the target to be assigned with the result of the evaluation of the numerical expression. The result can be a shell variable or a numerical object.
expression
The numerical expression to be evaluated. The expression consists of numerical objects, functions and operators.

The return value of the EVAL is a numerical object which is the result of the expression evaluation.

If the evaluation fails, the return value of EVAL and EVALCHECK is the empty string ('') and the variables RC and EMSG are set to the numerical error code and error description. Here EVAL and EVALCHECK differ in that EVAL will consider a failed evaluation an error (and treat it as such), whereas EVALCHECK will only return a numerical warning code in its description in RC and EMSG, respectively.

Examples

result := eval (5 * 10) % 3          // remainder of 50 divided by 3
result := eval init(10,1,2)          // matrix of 10 rows and 1 column
                                     // (i.e., a column vector), each element set to 2
result := eval 5+max(fill(6,1,1))

EBNF

The following list shows the syntax of EVAL expression using the EBNF notation. The expressions are listed in the reverse order of priority (lowest first). The operators with lower priority are evaluated after that with higher priority.

assignment
Value = Or [ "?" Or ":" Or ]
logical or
Or = And { "||" And }
logical and
And = Comparison { "&&" Comparison }
comparison
Comparison = AddSub { "<" | "<=" | "==" | "!=" | ">=" | ">" AddSub }
add, subtract
AddSub = MulDiv { "+" | "-" MulDiv }
multiply, divide
MulDiv = Pwr [ "*" | "/" | "%" Pwr ]*
power
Pwr = NegInv [ "^" NegInv ]
negate
NegInv = [ "-" | "!" ] Atom 
brackets, functions,
numerical objects
Atom = "(" expression ")"  |  "|" expression "|" | 
        functionName "(" [ expression { "," expression } ] ")" | 
        numericalObject

If the expression is syntactically ill-formed an error (EVAL) or warning (EVALCHECK) is reported and the assignment is not performed (content of result is not changed). See the example script expression_check.sts for details. Note that a good place to try out the EVAL command is the Programmer_Guide/BScript console.

Note: The special bracket |expression| implements a short form to compute the absolute value of expression. The result is always a number (scalar).

  • |xS| → the absolute value of number xS
  • |xV| → the length of the vector xV
  • |xM| → the determinant of the square matrix xM

The functions abs(x) and det(x) can be used as aliases for |expression|.

Numerical objects

The following numerical objects are known to the EVAL command.

Syntax Description Data type
constant a scalar constant. Any number (17, 4.5, 2.5e-6, ...) or one of the following strings:
pi (3.14159...), e (2.71828...), true (1) or false (0)
scalar
table the content of the whole table vector, matrix
table[i,*]
table[i,]
the i-th row of the table scalar, vector
table[*,j]
table[,j]
the j-th column of the table scalar, vector
table[i,j] the value of the i-th row and j-th column of the table scalar
value the content of the value item scalar, vector, matrix
value[i,*]
value[i,]
the i-th row of the value item scalar, vector
value[*,j]
value[,j]
the j-th column of the value item scalar, vector
value[i,j] the value of the i-th row and j-th column of the value item scalar
wave[!signal,*]
wave[!signal,]
the signal from all channels vector, matrix
wave[!signal,ch] the signal from channel ch (=1,2,...) vector
wave[!signal,*,b,l] the signal from all channels from sample b (0 <= b < wave[!length]) to sample b+l-1 (l > 0)
If b is lower than 0 or b+l is greater than wave[!length] zero padding is applied to the result
vector, matrix
wave[!signal,ch,b,l] the signal from channel ch from sample b to sample b+l-1 vector
gdxfile[!data] all columns of the GDX file item vector, matrix
gdxfile[!data,icol,ncol] the columns of icol to icol+ncol-1 of the GDX file item vector, matrix
  • The fields of the table item table are all numeric (extended table or parameter table).
  • The value item value can contain numbers, vectors or matrices.
  • The wave item wave is any wave item. It must address a (part of a) soundfile if wave is used as target.
  • The file item gdxfile must be of type GDX. This is a special form of the binary files, which can be used as numerical object and can also be connected to an input of a graph item. A GDX file item may contain one vector or one matrix.

row and column vectors

In STx it is not possible to differentiate between row vectors and column vectors. Normally a vector is a row vector, but it depends on the context (the operator or function used) which type of vector is supposed.

complex numbers

The current versions of STx do not implement the datatype complex, but a lot of functions take complex arguments and/or return complex results. Therefore the following convention for numerical objects holding complex numbers is used:
  • complex number: A vector with two elements. If the number is stored in the cartesian format, the first element is the real part and the second the imaginary part. If it is stored in polar format, the first element is the magnitude (or length) and the second the phase.
  • complex vector: A vector of N complex numbers consists of 2N elements. The element 2i is the real part (or magnitude) and the element 2i+1 is the imaginary part (or phase) of the i-th complex number (i = 0..N-1).
  • complex matrix: A matrix of N x M complex numbers consists of 2N rows and M. Each row is formatted like a complex vector described above.
The EVAL implements a set of functions for complex arithmetic and special handling of complex numbers.

polygons

The EVAL command implements a set of functions to manipulate 2-dimensional polygons. These functions are using specially formatted matrices to store information about one or more polygons. Some examples for the use of polygon functions and data types can be found in the example script scripts\examples\polygon_examples.sts.
closed point-list (pg_cplist)
Is a list of N points Pi in a 2-dimensional plane. Each pair (Pi , Pi+1) builds one edge of a polygon. The list is called closed, because PN-1 is connected to P0. A pg_cplist is stored in a matrix PL with N rows and 2 columns. The coordinates of point Pi are stored in PL[i,0] (xi) and PL[i,1] (yi).
simple-polygon (pg_simple)
Is a closed point-list (pg_cplist) defining a polygon without crossing edges.
polygon-stream (pg_stream)
Is a packed format to store the point-list and some additional information for one or more simple-polygons. This format is created by the initialisation function and used as argument and/or result by the most other polynom processing functions. A pg_stream is stored in a matrix with 2 columns and 8M+N0+..+NM-1 rows, where M means the number of polynoms stored in the stream and Ni the number of points of the i-th polynom. The data for the i-th polygon are stored in the matrix in the following format:
row
index
value of
column 0
value of
column 1
comment
oi+0 Ni: number of points reserved (set to 0)
oi+1 IXi: the index of the leftmost/lowest point (used for computations y=f(x)) IYi: the index of the lowest/leftmost point (used for computations x=f(y))
oi+2 XMINi: minimum x of all points YMINi: minimum y of all points The point (XMINi,YMINi) is the lower left corner of the bounding rectangle
oi+3 XMAXi: maximum x of all points YMAXi: maximum y of all points The point (XMAXi,YMAXi) is the upper right corner of the bounding rectangle
oi+4 XCi: x value of the center of gravity YCi: y value of the center of gravity The point (XCi,YCi) is the center of gravity of the polygon
oi+5 Ai: area Li: circumference
oi+6 1 if the center of gravity is inside the polygon,
0 otherwise
1 if the polygon is convex,
0 otherwise
oi+7 reserved (set to 0) reserved (set to 0)
oi+8
..
oi+Ni-1
x values of points y values of points the coordinates of the points (corners) of the (simple) polygon
with: oi is the first row index of the i-th polynum; o0=0, oi=oi-1+8+Ni-1 (i = 1..M-1)

Operators

Numerical operators

Syntax Description Data type of
Result
-x Negate all elements of x. same as x
y+xS
xS+y
Add the scalar xS to all elements of y. same as y
x+y Add elements of x to the elements of y. Both operands must be of the same type. same as x and y
y-xS Subtract the scalar xS from each element in y. same as y
xSy Subtract all elements of y from the scalar xS. same as y
x-y Subtract elements of x from the elements of y. Both operands must be of the same type. same as x and y
y*xS
xS*y
Multiply all elements of y with the scalar xS. same as y
xV*yV The inner (or dot) product of the vectors xV and yV. The length of both vectors must be the same. scalar
xM*yV The product of the matrix xM and the vector yV. The length of the vector yV must be the same as the number of columns in the matrix xM. vector with nrow(xM) elements
xM*yM The product of the matrix xM and yM. The number of rows in yM must be equal to the number of columns in xM. matrix with nrow(xM) rows and ncol(yM)) columns
y/xS Divide all elements of y through the scalar xS. The value of xM may not be 0. same as y
xS/yM Multiply all elements of the inverse matrix of yM with the scalar xS. The matrix yMmust be a square matrix.The special case 1/yM returns the inverse matrix. Note that the function inv(y) can also be used to invert scalars and matrices. same as yM
y%xS The rest of the division of every element in y through the scalar xS (modulo) same as y
y^xS Raise every element of y to the power of the scalar xS.
Special cases: y^-1 is calculated like 1/y and y^2 is calculated like this y*y
same as y

If one of the numerical operands has the prefix ? then the operation is carried out element per element. Example:

#dotprod := eval $#x * $#y // dot product of vectors #x and #y
#winsig := eval $#x ?* $#y // multiply elements of #x and #y (e.g. to apply signal windowing)

Comparison operators

Syntax Description
x<y x less than y
x>y x greater than y
x<=y x less than or equal to y
x>=y x greater than or equal to y
x==y x equal to y.
x!=y x not equal to y.

The result of a comparison of two numerical expressions is (logical) true (numerical 1), if the condition is fulfilled, otherwise it is (logical) false (numerical 0). Normally it make only sense to compare scalars or, more generally, numerical objects with equal dimensions. The following rules applies to a comparison:

  • The numerical objects x and y are equal (x==y is true), if (and only if) the dimensions of x and y are the same and all pairs of elements (xi,j , yi,j) are numerically equal.
  • The numerical objects x and y are not equal (x!=y is true), if the dimensions of x and y are different or at least one element pair (xi,j , yi,j) is numerically not equal.
  • For all other comparisons the dimensions of x and y must be the same, otherwise the comparison failes. The result is true, if the condition is fulfilled for all pairs of elements (xi,j , yi,j).

Logical operators

Syntax Description
x||y logical or
x&&y logical and
!x unary not

The result of a logical operation is true (numerical 1) or false (numerical 0). The arguments x and y can be any numerical type. It is also possible to use arguments with different types. The following rules are used to convert logical (boolean) to numerical values and vice versa:

The numerical result of a logical operation is the value ...

  • 1 if the logical expression is true
  • 0 if the logical expression is false

The logical value of a numerical object (or expression) is ...

  • true if one of its elements is not equal to 0.
  • false if all of its elements are equal to 0.

Selection operator

The selection operator used in EVAL expressions works similar to the COND command.

log_expr ? true_expr : false_expr
log_expr
A logical expression which is used to select the expression to be evaluated.
true_expr
This expression is evaluated and returned as result of the selection operator, if log_expr is true.
true_expr
This expression is evaluated and returned as result of the selection operator, if log_expr is false.

In contrast to the COND command, the selection operator of the EVAL command can be nested, but must be surrounded by brackets, e.g.:

result := eval 1 > 2 ? (5 == 5 ? 5 : 0) : (4 == 5 ? 3 : 4) // result is 4

Functions

latest update: April 21, 2011 (A.N.)

abs · absmax · absmin · absv · acos · aseg1 · asin · asp2osp · atan · avr · cepstrum · complex arithmetic · corr · corrfun · cos · cvphase · dct · density · dev · dft · dist · em · exp · f0ac · f0sp · fft · fill · fir1 · floor · formants · grand · haclust · hcomb · hist · hth · hz2bark · hz2cent · hz2erb · hz2mel · ifft · iir1 · imax · imin · init · int · interp · inv · ipeak · limit · log · log2lin · lpc · map2map · mapmind · max · median · min · modclust · mul · ncol · npow2 · nrow · optmm · otrack1 · pgget · pghull · pgiline · pginit · pgitest · pgsplit · pgtrans · pgxgrid · pztf · qdet · qinterp · rand · rleqs · round · rpoly · rpolyreg · sample · select · shuffle · sig2osp · sign · sin · sinc · smooth · sort · sqrt · sum · svd · tan · ticks2f1 · trn · var · vmcol · vmrow · vsubc · vsubn · vv · vvcat · vvget · vvset · wconvert · window · wsum · ydiff · yint · zcross

Examples

The result of the evaluation returned to the script is a number, vector or matrix. Numbers are returned in a string format (as usual in STx), and vectors or matrices are stored and returned in a temporary (local) parameter table. The return value may be assigned to a variable, a shell item or an addressed part of a shell item. The following examples show some possible assignments.

Assign to a variable: Only the returned string - the value of the number or name of the temporary table - is stored.

#x := eval rand(0,100)     // generate a vector with 100 pseudo random numbers in the range -1 to 1
                           // the name of the returned temporary table is assigned to the variable #x
#y := eval $#x * (1 - $#x) // compute the dot-product of 2 vectors
                           // the returned number is assigned to variable #y

Assigning to a table item

Assign to a table item: Both the content and the definition of the table is replaced by the content and definition of the result item.

// the following code is often used to assign an eval result to a permanent item
#x := new table *          // create a dummy simple table
$#x := eval rand(0,100)    // overwrite the dummy table with the result of the evaluation

// for those prefering compact code: the following line is equivalent to the above code
$(#x := new table *) := eval rand(0,100)
// the number of table columns is fixed (defined in the NEW command)
// the number of table rows is variable:
#y := new table * * num:x:50 /param     // create a parameter table with 50 columns (x0 .. x49)
$#y[3,*] := eval fill($#y[!ncol],1,50)  // assign a vector to row 3, the rows 0 to 2 are
                                        // automatically created and filled with zeros
$#y[$#y[!nrow]+1,*] := eval …           // append a row to a table

Assigning to a value item

Assign to a value item: The data stored in the value item is replaced by the result. The timer configuration of the value item is not changed.

// create a value item
#x := new value *

// assign a vector to the value item
$#x := eval fill(10,0,1)
conlog 'attributes: $#x[!type], $#x[!data]' // output: 'attributes: Vector, 10'

// assign a number to the value item
$#x := eval sum($#x)
conlog 'attributes: $#x[!type], $#x[!data]' // output: 'attributes: Number, 45'

// assign a string to the value item
$#x := set 'sum(x)'
conlog 'attributes: $#x[!type], $#x[!data]' // output: 'attributes: String, sum(x)'

Assigning to a matrix row or column

Assign to a row or column of a matrix. Matrices are stored in table or value items.

#x := eval init(20,20,0)       // create a 20x20 matrix
$#x[0,] := eval fill(20,0,1)   // replace row 0 of the matrix
$#x[,1] := eval fill(20,0,1)   // replace column 1 of the matrix
$#x[,2] := eval fill(100,0,1)  // error: the vector is to long!
$#x[2,] := eval fill(5,0,1)    // error: the vector is to short!

Assigning to an entry of a matrix, or a vector

Assign to an element (i.e., a cell, i.e., a field) of an item:

#x := new table * * str:a num:b // create a table with a string field a numeric field
$#x[0,a] := eval fill(10,1,1)   // the fill command returns a vector (temp. table), 
                                // the id of the returned item is assigned to the cell
$#x[0,b] := eval fill(10,1,1)   // error: a string can not be assigned to a numeric field!
$#x[0,b] := eval sum($#x[0,b])  // okay: the sum is assigned to the cell

Storing a signal in a wave item

Store signal in a wave item.

// create a soundfile (32kHz, stereo, 24bit) and store a 1s tone (440Hz, 880Hz) 
// in channel 1 and a 1s noise in channel 2
// create the soundfile and the wave item
bsf open $@work\testtone.wav; create; 32000; 2; pcm24; wave
#x := new wave * 0_1s
// initialize both channels
// the number of samples stored in x equals the length of the assigned vectors
$#x[!signal,1,0] := eval fill($#x[!length],0,2*pi*440/$#x[!srate])/2
$#x[!signal,2,0] := eval rand(0,$#x[!length],1) / 4
// its also possible to assign a matrix to a wave item
// number of columns  = must be equal to the number of channels
// number of rows     = number of samples to be written
#matrix := eval init(10000, 2, 0)
$#matrix[*,0] := fill($#matrix[!length],0,2*pi*880/$#x[!srate])/2
$#matrix[*,1] := fill($#matrix[!length],0,2*pi*660/$#x[!srate])/2
$#x[!signal,*,10000] := $#matrix
// the signal of a wave item can be modified (e.g. ramp)
$#x[!signal,1,0] := eval $#x[!signal,1,0,1000] ?* fill(1000,0,1/1000)
// now you can play the generated signal
playwave $#x ; Signal generation test!
delete $#x
bsf close $@work\testtone.wav

Using GDX files

GDX file items are special binary files which can be used directly in a numerical expression and which can also be connected to an input of a graph item. One matrix can be stored per GDX file.

[macro computeSpectrogram #wave #len=1024 #hop=256]
// Compute a spectrogram and store it in a GDX file
// Args:   #wave       a mono wave item
//         #len, #hop  the analysis window length and the hopsize in samples
// Result: the path of the GDX file containing the spectrogram
//---
    #path := unique '$@work' gdx 1 8        // get unique output file name
    #lfft := eval fft($#len)                // compute transformation length
    #nfrm := int $#wave[!length] / $#hop    // compute number of frames
    #file := new file * '$#path' 4 $#nfrm $(int $#lfft/2+1) // create GDX file
    // compute and save one log. amplitude spectrum / frame
    for #i := 0 to $#i < $#nfrm step #i := int $#i+1
        #pos := int $#i * $#hop - $#len/2
        $#file[!data,$#i] := eval fft($#wave[!signal,1,$#pos,$#len] ?* whanning($#len) , $#lfft, 4)
    end
    delete /Var #file  // close the file
    exit 1 set '$#path'
[macro computeAvrPowerspectrum #path]
// Compute the average powerspectrum of a spectrogram stored in a GDX file
// Args:   #path       the path of the GDX file containing the spectrogram
// Result: the average log. powerspectrum (a temp. numeric table item)
//---
    #file := new file * '$#path' // open GDX file
    // compute average spectrum
    #avr := eval fill($#file[!nrow],0,0)
    for #i := 0 to $#i < $#file[!ncol] step #i := int $#i+1
        $#avr := eval $#avr + log2lin($#file[!data,$#i,1], 1, 10) / $#file[!ncol]
    end
    delete /Var #file  // close the file
    exit 1 eval lin2log($#avr, 1, 20)

Script examples

The following script shows some examples how to use the EVAL command.

[Macro eval_example]
// force this macro to be run in the debugger
message debug on
message debug init /Step
// note: use the script debugger to view the results

// assign constants
#a := 0
#b := 1
#c := 2
#d := 3

// simple numerical expressions
#e1 := eval $#d*$#c+$#b
#e2 := eval $#b+$#d*$#c
#e3 := eval $#d*($#c+$#b)

// simple logical expressions
#c1 := eval $#a || $#b || $#c
#c2 := eval $#a && $#b && $#c
#c3 := eval $#a && $#b || $#c
#c4 := eval $#c || $#a && $#b
#c5 := eval ($#c || $#a) && $#b
#c6 := eval ! $#a || ! $#b
#c7 := eval ! $#a && ! $#b

// compare numbers
#c1 := eval $#a > $#b
#c2 := eval $#a >= $#b
#c3 := eval $#a < $#b
#c4 := eval $#a <= $#b
#c5 := eval $#a == $#b
#c6 := eval $#a != $#b

// selection operator (conditional assignment)
#c1 := eval $#a < $#b ? $#a+$#b : $#a-$#b
#c2 := eval $#a > $#b ? $#a+$#b : $#a-$#b
#c3 := eval $#a == $#b ? $#a+$#b : $#a-$#b
#c4 := eval $#a != $#b ? $#a+$#b : $#a-$#b

// nested "? :" statements may be hard to read
#c := eval $#a > $#b ? ($#a == $#b ? 1 : 2) : ($#a == $#b ? 3 : 4)
// ...especially if you leave out readability blanks...
#c := eval $#a>$#b?($#a==$#b?1:2):($#a==$#b?3:4)

// using "? :" to select a function argument
#c1 := eval sin( $#a > $#b ? $#a : $#b )
#c2 := eval sin( $#a < $#b ? $#a : $#b )

// initialize vectors
#v1 := eval fill( 10, 0.1, 0.2 ) 	// ten elements
#v2 := eval fill( 10, 0.2, 0.1 )  	// also ten elements
#v3 := eval fill( 5,  0.2, 0.1 )	// only five elements

// ten elements each of which is larger than the corresponding element in #v1
#v4 := eval $#v1 + 1

// compare vectors
#c1 := eval $#v1 == $#v2
#c2 := eval $#v1 != $#v2
#c3 := eval $#v1 >  $#v2
#c4 := eval $#v1 <  $#v2
#c5 := eval $#v1 >  $#v4
#c6 := eval $#v1 <  $#v4

// the "element-wise" operator
#x1 := eval $#v4 ^  2	// normal operation
#x2 := eval $#v4 ?^ 2	// element-wise operation

// vectors of different size are trivially unequal
#c1 := eval $#v1 == $#v3
#c2 := eval $#v1 != $#v3
// illegal comparisons due to different size
#c3 := eval $#v1 < $#v3	// illegal!
#c4 := eval $#v1 > $#v3	// illegal!

// replace the vector v1
$#v1 := eval fill( 11, -5, 1 )

// limit all values to be >= -1 and <= 2
$#v2 := eval limit( $#v1, -2, 2 )
// set lowest bound only
$#v2 := eval limitLow( $#v1, -2 )
// set highest bound only
$#v2 := eval limitHigh( $#v1, 2 ) 

// this works with a number (as opposed to vectors and matrices), too
#c1 := 123.5
#c2 := eval limit($#c1,0,100)
#c2 := eval limitlow( $#c1, 100 )
#c2 := eval limithigh( $#c1, 100 )

// pick out the smallest/largest value from vec1, vec2 and a number of numbers
#min := eval min($#v1, $#v2, 100, 20)
#max := eval max($#v1,$#v2, 100, 20)

// merge vectors and numbers
$#v3 := eval vv($#v1, $#c1, $#v2, $#c2)

In the directory scripts\examples of the STx installation, you can find a lot of script files using EVAL for differnt purposes (dsp_examples.sts, eval_example.sts, expression_checks.sts, matrix_algebra_examples.sts, parameter_table_example.sts, plot_sample.sts, polygon_examples.sts, ...)

Navigation menu

Personal tools