Skip to content
Snippets Groups Projects

ensightReadFile ignores string limits

    • Open Issue created by Mark OLESEN @mark

      Child items

      0
      Show labels

      No child items are currently assigned. Use child items to break down this issue into smaller parts.

        Activity

        • Mark OLESEN mentioned in commit a0320a03fe5f01e9c6ec1c264ace38dba62b6000

          mentioned in commit a0320a03fe5f01e9c6ec1c264ace38dba62b6000

        • Mark OLESEN closed

          closed

        • Mark OLESEN mentioned in commit bb332cf1

          mentioned in commit bb332cf1

        • Mark OLESEN reopened

          reopened

        • Mark OLESEN
          Mark OLESEN @mark ·
          Author Maintainer

          The surface reader may need to be more forgiving when handling different types of input

          • The case files may contain # comment lines
          • The geometry file may contain an optional "extents" entry
          • Currently assume that node id, element id are both "off" or "assign", which causes read failure for other values.

          Handling optional element ids is fairly trivial. Proper handling of optional node ids is much more involved. If they are simply "ignore", this is easy enough. When they are specified as "given" however, we need an entire additional layer of mapping (similar to mesh conversion routines). In many cases, the node ids are specified as "given", but are indeed contiguous 1-based values - this means that their internal connectivity will be the same as "assign", but with the possibility to use the ids in Ensight.

          The first round of fixes will treat node id "given" as being the same as "ignore" (ie, contiguous 1-based), with the option of revisiting the topic in the future.

        Please register or sign in to reply