C

E-CBUF, Write error block <Integer>
LAS, Input/Output routines : an error occurred during a write operation to the output file. This may be due to a large number of reasons (for example the disk may be off line, write locked or damaged) but is more or less fatal.
User action : See ``Recovering Corrupted Data Files''

E-CHECK, Flag > 4
ANALYSE, LINES command : the input values contained an invalid flag.
User action : reenter valid values.

W-CHECK, Line <Integer> alone in a <String> Group
ANALYSE, LINES command. Input values were entered for dependent lines, but no lines depend on the one specified by <Integer>.
User action : although this is just a warning, it is likely that you made a typing mistake. Verify your input values and codes.

E-CHECK, No Independent <String>
ANALYSE, LINES command : input values were entered for dependent lines, but there is no independent line in VELOCITY, AREA or WIDTH (as specified by <String>.
User action : correct typing error.

E-CHECK, Several groups in <String>
ANALYSE, LINES command : input values were entered for dependent lines, but all lines must be dependent of a single one in this case. This may be due to a typing error, but also to a problem which cannot be solved by the current minimization routine.
User action : Correct typing error if any.

E-COBS, Observation not open for write nor modify
LAS, Input/Output routine : an observation is being closed after or write or modify operation, but has never been opened for such operation.
User action : Submit an SPR. The output file may have been corrupted, see ``Recovering Corrupted Data Files''

W-CONVERT, Earth velocity not converted
LAS, GET command or other observation reading routine. The velocity of the source was relative to Earth, and has not been converted to the current velocity system.
User action : None, but remember the velocity is wrong...

W-CONVERT, Velocity type was unknown, Set to <String>
LAS, GET command or other observation reading routine. The velocity type was undefined, and has been (arbitrarily) declared as <String> (LSR, Helio, etc...), but no velocity conversion was done.

W-CONVER, label too long, truncated
LAS, plotting routines. A label was too long to be drawn.
User action : None. Submit an SPR if you wish, with the label of course.

F-COX, Output file not opened
LAS, Input/Output routine : an operation was requested on the output file, but no such file has been opened.
User action : open the output file, and resubmit the command.

F-COX, Write error block <Integer>
LAS, Input/Output routines : an error occurred during a write operation to the output file. This may be due to a large number of reasons (for example the disk may be off line, write locked or damaged) but is more or less fatal.
User action : Notify your system manager. The output file may have been corrupted, see ``Recovering Corrupted Data Files''

E-CUBE, Cannot create output image
ANALYSE, CUBE command. The output image could not be created. This message is followed by a message 'E-GDF_CRIMAG, ....' which gives the reason of the failure. The most likely reason is an exceeded quota (either disk or virtual memory)
User action : if this is due to a disk quota, delete unwanted files and retry. If this is due to a virtual memory quota, clear any plot, run the program without parallel sub-processes, and if none of these solution works, ask your system manager.

E-CUBE, Cannot write output image header
ANALYSE, CUBE command. The output image header could not be written. This error is due to an hardware error on the disk.
User action : Notify the system manager, and retry again later.

I-CUBE, Check tolerance (SET MATCH) please
ANALYSE, CUBE command. The output cube is too large, possibly because of roundoff errors in the offsets.
User action : increase the SET MATCH to overcome roundoff errors.

E-CUBE, Continuum data not supported
ANALYSE, CUBE Command. Spectral line data is required to make a data cube. Use command STRIP to build a continuum map from a set of scans.

E-CUBE, Cube too large, <Integer> by <Integer>
ANALYSE, CUBE command. The output cube is too large, most likely because of roundoff errors in the offsets.
User action : see ``I-CUBE, Check tolerance (SET MATCH) please''

W-CUBE, Incoherent axis scale for scan <Integer>
ANALYSE, CUBE command. One of the spectra in the index has an axis scale which does not match the cube definition. The spectrum has been written to the cube nevertheless, and the cube command proceeds.
User action : May be this spectrum should not be placed in the cube, so drop it from the current index and rebuild the cube. If spectra have been obtained under slightly different conditions (for example with different sidebands) you must bring them on a common axis scale (use RESAMPLE) before combining them in a cube.

E-CUBE, Incoherent number of channels for scan <Integer>
ANALYSE, CUBE command. One of the spectra has a number of channels different from the cube definition. The spectrum is not written to the cube, and the cube command aborts.
User action : drop this spectrum from the current index and restart command.

E-CUBE, Incoherent offset type for scan <Integer>
ANALYSE, CUBE command. The coordinate system of the scan differs from the one of the cube. The scan is not written, and command CUBE aborts.
User action : drop the scan from the index, and restart command.

E-CUBE, Index is empty
ANALYSE, CUBE command. A cube is being build from nothing...
User action : define your current index before by using command FIND.

E-CUBE, Missing file name
ANALYSE, CUBE command. The output cube name has not been specified
User action : specify file name

E-CUBE, No input file connected
ANALYSE, CUBE command. No input file is opened.
User action : open input file and define the current index before using command CUBE.