Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

REMDOUBL# returns a Telitab subset from which multiple ocurring cases are removed

Syntax

  1. REMDOUBL#(Mode%, Telitab$,Deviation,[ArgPar_1$,..,ArgPar_n$])
  2. REMDOUBL#(Telitab$,[ArgPar_1$,..,ArgPar_n$])

...

  • Mode% = -2 inverse remove, will only leave the double values, keeping Deviation into account
  • Mode% = -1 standard remove of double values, removing all double values, keeping Deviation into account
  • Mode% = 0 standard remove of double values, leaving one case (the very first one...), keeping Deviation into account
  • Mode% > 0 standard remove of double values (comparable to Mode% = 0 ) but returning only the column with a number equal to Mode%, keeping Deviation into account
  • Telitab$ is Telitab$ is a string expression containing table to be analysed.
  • Deviation is a very small value required for instance in order to compensate errors due to internal rounding
  • ArgPar_1$,,,,ArgPar_n$ is an optional list of parameter names in Telitab$ to base the REMDOUBL# on. 

Remarks

...

When we use the relation:

REMDOUBL#(Telitab$, "SPEED", "RPM")

for Telitab$:


6 "RUN" "SPEED" "RPM" "TORQUE" "THRUST" 
"1" 5607401001 0.00 803.00 132.27 -39.32 
"2" 5607401002 0.35 835.69 133.02 -39.08 
"3" 5607401003 0.70 877.99 135.47 -39.23 
"4" 5607401004 1.39 903.04 118.85 -32.78 
"5" 5607401005 0.35 835.69 133.02 -39.08 
"6" 5607401006 2.10 902.16 92.47 -23.55 
"7" 5607401007 0.35 860.41 133.02 -39.08

...

Case 5 (row 5) is removed because SPEED and RPM are the same as in case 2.

Please noteREMDOUBL#(Telitab$) would return the complete Telitab$ as result due to the difference RUN numbers (also for cases 2 and 5).

...