Error Messages in Clash Detection Mode

The following error messages are those that are specific to Design’s Clash Detection mode.

(69:4) May only specify tube on piping or hanger components

You have tried to specify implied tube connected to an inappropriate type of element (see Defining the Obstruction List for examples of the syntax).

(69:5) Must be a BRANCH or HANGER to specify HEAD or TAIL tube

You have tried to specify a head or tail tube connected to an inappropriate type of element (see Defining the Obstruction List for examples of the syntax).

(69:7) name/refno has not been fully mapped

The specified element has not had its positional data updated in the spatial map.

(69:8) name/refno is already in the obstruction list

You have tried to add an element to the obstruction list that is already present in the list. Use the Q CLASH OBSTRUCTION command to check the current list if necessary.

(69:9) name/refno is not in the spatial map

The specified element has not had its positional data updated in the spatial map.

(69:11) name/refno is not in the obstruction list

You have tried to remove or exclude an element from the obstruction list that is not present in the list. Use the Q CLASH OBSTRUCTION command to check the current list if necessary.

(69:12) Approved clash number integer is not in approval list

You have tried to remove or reapprove a clash by referring to an approved clash id that is not present in the list. Use the OUTPUT APPROVED command if necessary to check the current list.

(69:13) Element type word is not currently a section header

You have tried to remove a section from the main body of the report that is not present in the list of sections. Use the Q CLASH REPORT MAIN command to check the current sections if necessary.

(69:16) Maximum number of element types for the NOCHECK option exceeded

The maximum number of element types that you may specify in a NOCHECK command is 20.

(69:17) Element type word is not in the list of those set for NOCHECK

You have tried to use the WITHIN command to reinstate an element type which has not been previously specified in a NOCHECK command.

(69:18) Clearance value must be positive

You have specified a negative argument in a CLEARANCE command. You must specify either a positive value (which must be greater than the current touch gap) or zero (which switches the clearance option off).

(69:19) Clearance value must be greater than touching gap
(69:20) Touching gap must be positive
(69:21) Touching gap may not be greater than current clearance
(69:22) Touching overlap must be positive
(69:23) Invalid element type for an approved clash

See Adding Clashes to the Approval List for the valid ways of specifying approved clashes.

(69:24) Approved clash already exists

You have tried to add a clash to the approval list that is already present in the list. Use the OUTPUT APPROVED command to check the current list if necessary. See Adding Clashes to the Approval List.

(69:25) integer is not a valid approved clash number

You have tried to remove or reapprove a clash by referring to an approved clash id that is not present in the list. Use the OUTPUT APPROVED command if necessary to check the current list. See Adding Clashes to the Approval List.

(69:26) There are no items in the obstruction list

You cannot run a clash check until you have added at least one element to the obstruction list.

(69:27) Maximum number of element types for the SECT option exceeded

The maximum number of element types that you may specify in a REMOVE SECTIONS command is 20.

(69:28) Clashes cannot be saved as no clash run has been made

The SAVE CLASHES command can only save clash data currently held in memory from the most recent clash-checking run. There is no valid data in memory.

(69:29) Error in file format

You have probably tried to restore data from a file that was not written to by an Design (or CLASHER) SAVE command.

(69:33) No clash run has been made

The SAVE CLASHES command can only save clash data currently held in memory from the most recent clash-checking run. There is no valid data in memory.

(69:34) File filename already exists. Output defaulted to terminal

You can only overwrite the contents of an existing file by using either the FFILE command or the FILE ... OVER option. Your FILE command has been ignored as a protection against accidentally overwriting the named file.

(69:35) File filename is in use. Output defaulted to terminal

You have specified a file that is already open (or which is otherwise inaccessible for writing to). Your output will therefore be sent to your terminal until you specify a valid file name.

(69:36) File filename does not exist

The file from which you are trying to read is not accessible from the OS directory from which you entered Marine. Do you need to give the full pathname for the file.

(69:37) File filename already exists

You can only overwrite the contents of an existing file by using either the FFILE command or the FILE ... OVER option.

(69:38) File filename is in use

You have specified a file that is already open (or which is otherwise inaccessible for writing to).

(69:39) Page width may not be less than 50 characters

A page width of less than 50 characters will be too narrow to accommodate the clash data lines in the report.

(69:40) Page length must be between 20 and 200 lines

The page length must be of a suitable length to accommodate a sensible top and bottom margin and a reasonable number of report lines.

(69:41) Page margin must be between 0 and 20

The margin width must be positive and must allow enough remaining line length to accommodate a typical report line.

(69:43) No spatial map exists for DB containing name/refno

The specified element forms part of a DB for which a spatial map has not yet been created. The positional data for the element is therefore unavailable for clash checking.

(69:47) The leave tube for name/refno is not in the spatial map

The specified element has not had its positional data updated in the spatial map since it was connected to the next downstream component.

(69:48) No approved clashes exist between name/refno and name/refno

You have tried to reapprove one or more clashes between named items for which no approved clashes have been specified.

(69:56) Unable to open file filename

The specified file cannot be found. Check that you have specified its correct pathname and that the directory containing it is accessible from the directory from which you entered Marine.

(69:57) Line integer of macro template filename is too long

The specified command line in your template file is of such a length that, when the clash-checking keywords have been replaced by the corresponding clash data, it exceeds the maximum permitted length for a Marine command line.

(69:58) Line integer of macro template filename does not have matching dollar signs

Each keyword in a macro template file must be enclosed between a pair of $ escape characters. The $ characters in the specified file do not form properly matched pairs.

(69:59) Line integer of macro template filename has unrecognized keyword

See Creating Macro Files Incorporating Clash Data for a list of valid keywords for use in macro template files.

(69:60) Macro template filename has no keywords

There are no identifiable locations in the template to which clash data can be transferred. Design cannot check the command syntax in the template and it is most likely that the enclosing $ characters have simply been omitted from the keywords. See Creating Macro Files Incorporating Clash Data.

(69:61) Spatial map marked as incomplete ( for DB integer )

The positional data has not been updated in the spatial map since the specified DB was last accessed from a design module. Entry to a design module with map maintenance off will cause the map to be flagged as incomplete if any design change is made, even if no clashes are affected.

(69:66) No obstruction list. Use ‘OBS ALL’ or ‘OBS id1 id2 ... idn’

You cannot run a clash check until you have added at least one element to the obstruction list.

(69:67) Currently OBS ALL. Specifying additional obstructions has no effect

Since the obstruction list already comprises all relevant elements in the Design DB, there is no point in trying to add specifically named elements to the list.

(69:68) No template file has been specified for macro output

When using the REPORT MACRO option you must specify the name of the template file from which the structure of the macro is to be read. This is quite independent of the specification of the output file (FILE or FFILE command) which defines where the final macro is to be sent.

(69:79) ALL not valid for EXCLUDE command

The members of obstruction list elements that are to be excluded from the list must be individually specified. EXCLUDE ALL would effectively eliminate the entire obstruction list (use REMOVE OBSTRUCTION ALL if you really want to do this).

(69:80) name/refno is already in the exclusion list

You have tried to add an element to the exclusion list that is already present in the list. Use the Q CLASH OBSTRUCTION command to check the current list if necessary.

(69:81) name/refno is not in the exclusion list

You have tried to remove an element from the exclusion list that is not present in the list. Use the Q CLASH OBSTRUCTION command to check the current list if necessary.

(69:85) Clasher run may not be made unless the override option is used

These are errors in the Spatial Map which will cause Desclash to abort the run unless the Override On option is used.