Mesh unite¶
Commands of the mesh_unite chapter of the database, 3 entries. The status words are defined once, on the compatibility matrix, which says what each rests on and what the script builder does with it. Read it before this page: broken and removed are refusals, so a row here can be telling you the emitter will not write that command for that version.
BOOLEAN_UNITE_GEOMETRY¶
Phase geometry, layout keyword_block. Manual: SRC-749 p.272.
Boolean-unites CAD GEOMETRY bodies, where BOOLEAN_UNITE_MESH unites mesh bodies. The two are siblings on the same page of the 25.000 edition and only the mesh one survives: no edition from 25.100 on prints this name. The unite is not performed by FlightStream. Both commands call out to an external OpenVSP executable for the CompGeom operation, and OPENVSP_PATH is where that executable is, which is why a path belongs in a geometry command at all. A wrong path is an environment failure and not a modelling one. BODIES takes a count followed by one line per body pairing the body index with POSITIVE or NEGATIVE, the sign being whether that body adds volume or subtracts it. A count of -1 means every body with a positive volume, which is the additive unite, and then no body lines follow.
| Argument | Specification |
|---|---|
bodies |
int |
body_unite_types |
str_list |
openvsp_path |
path |
| Version | Status | Evidence |
|---|---|---|
| 25.000 | documented | SRC-749 p.272, this edition documents it |
| 25.100 | removed | SRC-748 pp.271-347, the whole scripting reference of the 25.100 edition, does not print this command. That is a fact about the document rather than a measurement of the solver, which is the weakest of the three ways a removal is recorded here; no probe has asked this build whether it still answers the name. |
| 26.000 | removed | SRC-747 pp.270-346, the whole scripting reference of the 26.000 edition, does not print this command. That is a fact about the document rather than a measurement of the solver, which is the weakest of the three ways a removal is recorded here; no probe has asked this build whether it still answers the name. |
| 26.100 | removed | SRC-741 pp.275-369, the whole scripting reference of the 26.100 edition, does not print this command. That is a fact about the document rather than a measurement of the solver, which is the weakest of the three ways a removal is recorded here; no probe has asked this build whether it still answers the name. |
| 26.101 | removed | SRC-725 pp.280-375, the whole scripting reference of the 26.101 edition, does not print this command. That is a fact about the document rather than a measurement of the solver, which is the weakest of the three ways a removal is recorded here; no probe has asked this build whether it still answers the name. |
| 26.120 | removed | SRC-003 pp.281-376, the whole scripting reference of the 26.120 edition, does not print this command. That is a fact about the document rather than a measurement of the solver, which is the weakest of the three ways a removal is recorded here; no probe has asked this build whether it still answers the name. |
| 26.121 | removed | SRC-740 pp.284-379, the whole scripting reference of the 26.121 edition, does not print this command. That is a fact about the document rather than a measurement of the solver, which is the weakest of the three ways a removal is recorded here; no probe has asked this build whether it still answers the name. |
BOOLEAN_UNITE_MESH¶
Phase geometry, layout payload_lines. Manual: SRC-003 p.316.
Intersects and unites several mesh bodies into one. The count sits on the command line and the indices follow on the next. THE INDICES ARE SPACE SEPARATED HERE AND COMMA SEPARATED IN THE MESH OPERATIONS CHAPTER. Both samples on this page print spaces, where SURFACE_COMBINE and WRAPPER_SET_INPUT print commas for the same kind of payload. The separator is emitted literally, so the difference is recorded per command rather than harmonised. -1 UNITES EVERY BODY and takes no index line, which is why the list is optional. The manual states this as a note under the count. These are MESH BODY indices, not the mesh boundary indices the rest of the database cites, so nothing resolves or range checks them: the script builder tracks boundaries and has no inventory of bodies.
| Argument | Specification |
|---|---|
num_bodies |
int |
body_indices |
int_list (optional) |
| Version | Status | Evidence |
|---|---|---|
| 25.000 | documented | SRC-749 p.272, this edition's own grammar; see the note below |
| 25.100 | documented | SRC-748 p.290, this edition's own grammar; see the note below |
| 26.000 | documented | SRC-747 p.289, this edition's own grammar; see the note below |
| 26.100 | documented | SRC-741 p.311, same grammar as 26.120 |
| 26.101 | documented | SRC-725 p.315, same grammar as 26.120 |
| 26.120 | documented | SRC-003 p.316 |
| 26.121 | documented | SRC-740 p.319, same grammar as 26.120 |
| 26.123 | documented | SRC-751 p.320, unchanged from SRC-750 p.320 |
| 26.124 | documented | SRC-752 p.320, the SRC-751 file, carried from 26.123; not run on 26.124 |
BOOLEAN_UNITE_PATH¶
Phase geometry, layout keyword_block. Manual: SRC-003 p.316.
Location of the OpenVSP executable used for the unite. The manual states it must be called BEFORE BOOLEAN_UNITE_MESH, which is the one ordering rule the chapter has and which nothing here enforces: the phase system orders commands by phase, and both of these are geometry. The sample writes a directory rather than an executable, and the parameter row calls it a path to the executable. Which of the two the solver wants is not settled by the page, so nothing here constrains the value beyond it being a path.
| Argument | Specification |
|---|---|
openvsp_path |
path |
| Version | Status | Evidence |
|---|---|---|
| 25.000 | documented | SRC-749 p.272, same grammar as 26.120 |
| 25.100 | documented | SRC-748 p.290, same grammar as 26.120 |
| 26.000 | documented | SRC-747 p.289, same grammar as 26.120 |
| 26.100 | documented | SRC-741 p.311, same grammar as 26.120 |
| 26.101 | documented | SRC-725 p.315, same grammar as 26.120 |
| 26.120 | documented | SRC-003 p.316 |
| 26.121 | documented | SRC-740 p.319, same grammar as 26.120 |
| 26.123 | documented | SRC-751 p.320, unchanged from SRC-750 p.320 |
| 26.124 | documented | SRC-752 p.320, the SRC-751 file, carried from 26.123; not run on 26.124 |