Skip to content
Snippets Groups Projects

Evaluated and written values may not correspond in FO

    • Closed Issue created by Mark OLESEN @mark

    Noticed with the ddt2 and zero-grad FO. It is possible to select evaluate intervals and write intervals such that the value written is actually rather out of date at the time of writing. Or even set things that the FO is never evaluated, but only written. Should add extra logic to catch this.

      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 Changed title: Evaluated and written values may not correspond → Evaluated and written values may not correspond in FO

          Changed title: Evaluated and written values may not correspond → Evaluated and written values may not correspond in FO

        • Mark OLESEN Mentioned in commit cf9000df6573ac573540a3833ab24b2744db2714

          Mentioned in commit cf9000df6573ac573540a3833ab24b2744db2714

        • Admin
          Admin @OpenFOAM-admin ·
          Maintainer

          Why not add as a general solution? e.g. see MR !79 (merged)

          By Andrew Heather on 2016-11-24T12:38:57 (imported from GitLab project)

        • Mark OLESEN
          Mark OLESEN @mark ·
          Author Maintainer

          That makes even better sense, since this problem will certainly crop up more often.

        • Admin Mentioned in commit 0cdd03474ed2ce86812a187e22a4265a72a9f9ba

          Mentioned in commit 0cdd03474ed2ce86812a187e22a4265a72a9f9ba

          By Andrew Heather on 2016-11-28T09:49:41 (imported from GitLab project)

        • Mark OLESEN Status changed to closed

          Status changed to closed

        Please register or sign in to reply