Reference Guide

3-232 Full Command and Function Reference
The spectral radius of a matrix is a measure of the size of the matrix, and is equal to the absolute
value of the largest eigenvalue of the matrix.
Access: !Ø OPERATIONS L L SRAD (Ø is the left-shift of the 5key).
!´ MATRIX NORMALIZE SRAD ( ´ is the left-shift of the Pkey).
Input/Output:
Level 1/Argument 1 Level 1/Item 1
[[ matrix ]]
n×n
→
x
spectralradius
See also: COND, SNRM, TRACE
SRB
Type: Command
Description: Shift Right Byte Command: Shifts a binary integer one byte to the right.
The least significant byte is shifted out to the right and lost, while the most significant byte is
regenerated as zero. SRB is equivalent to binary division by 2
8
(or executing SR eight times).
Access: !´ BASE L BYTE SRB ( ´ is the left-shift of the Pkey).
…ã L BYTE SRB (ã is the right-shift of the 3key).
Flags: Binary Integer Wordsize (–5 through –10), Binary Integer Base (–11, –12)
Input/Output:
Level 1/Argument 1 Level 1/Item 1
#n
1
→
#n
2
See also: ASR, SL, SLB, SR
SRECV
Type: Command
Description: Serial Receive Command: Reads up to n characters from the serial input buffer and returns them
as a string, along with a digit indicating whether errors occurred.
SRECV does not use Kermit protocol.
If n characters are not received within the time specified by STIME (default is 10 seconds),
SRECV “times out”, returning a 0 to level 1 and as many characters as were received to level 2.
If the level 2 output from BUFLEN is used as the input for SRECV, SRECV will not have to
wait for more characters to be received. Instead, it returns the characters already in the input
buffer.
If you want to accumulate bytes in the input buffer before executing SRECV, you must first open
the port using OPENIO (if the port isn’t already open).
SRECV can detect three types of error when reading the input buffer:
• Framing errors and UART overruns (both causing "Receive Error" in ERRM).
• Input-buffer overflows (causing "Receive Buffer Overflow" in ERRM).
• Parity errors (causing "Parity Error" in ERRM).
SRECV returns 0 if an error is detected when reading the input buffer, or 1 if no error is detected.
Parity errors do not stop data flow into the input buffer. However, if a parity error occurs,
SRECV stops reading data after encountering a character with an error.
Framing, overrun, and overflow errors cause all subsequently received characters to be ignored
until the error is cleared. SRECV does not detect and clear any of these types of errors until it
tries to read the byte where the error occurred. Since these three errors cause the byte where the
error occurred and all subsequent bytes to be ignored, the input buffer will be empty after all
previously received good bytes have been read. Therefore, SRECV detects and clears these errors
when it tries to read a byte from an empty input buffer.