1. 14 May, 2020 1 commit
  2. 19 Feb, 2020 1 commit
  3. 18 Feb, 2020 1 commit
    • Mark Olesen's avatar
      ENH: improvements to IOstreamOption · 33f9ae50
      Mark Olesen authored
      * Support default values for format/compress enum lookups.
      
        - Avoids situations where the preferred default format is not ASCII.
          For example, with dictionary input:
      
              format binar;
      
          The typing mistake would previously have caused formatEnum to
          default to ASCII. We can now properly control its behaviour.
      
              IOstream::formatEnum
              (
                  dict.get<word>("format"), IOstream::BINARY
              );
      
          Allowing us to switch ascii/binary, using BINARY by default even in
          the case of spelling mistakes. The mistakes are flagged, but the
          return value can be non-ASCII.
      
      * The format/compression lookup behave as pass-through if the lookup
        string is empty.
      
        - Allows the following to work without complaint
      
            IOstream::formatEnum
            (
                dict.getOrDefault("format", word::null), IOstream::BINARY
            );
      
        - Or use constructor-like failsafe method
      
            IOstream::formatEnum("format", dict, IOstream::BINARY);
      
        - Apply th...
      33f9ae50
  4. 31 Oct, 2019 1 commit
  5. 13 Mar, 2019 1 commit
    • Mark Olesen's avatar
      ENH: surface writers now track their own write status · 1a35a3ef
      Mark Olesen authored
      - instead of deciding beforehand if a surface format requires a separate
        geometry file (or if a geometry file should be written if no fields were
        written) now determine afterwards if something was written.
      
        This improves the overall reliability (consistency) and is more
        convenient for the caller as well.
      1a35a3ef
  6. 22 Feb, 2019 2 commits
  7. 07 Feb, 2019 1 commit
    • Mark Olesen's avatar
      ENH: improved sample surfaces and surface writers (#1206) · 181c974b
      Mark Olesen authored
      - The writers have changed from being a generic state-less set of
        routines to more properly conforming to the normal notion of a writer.
        These changes allow us to combine output fields (eg, in a single
        VTK/vtp file for each timestep).
      
        Parallel data reduction and any associated bookkeeping is now part
        of the surface writers.
        This improves their re-usability and avoids unnecessary
        and premature data reduction at the sampling stage.
      
        It is now possible to have different output formats on a per-surface
        basis.
      
      - A new feature of the surface sampling is the ability to "store" the
        sampled surfaces and fields onto a registry for reuse by other
        function objects.
      
        Additionally, the "store" can be triggered at the execution phase
        as well
      181c974b