1. 11 Nov, 2016 1 commit
  2. 05 Aug, 2016 1 commit
  3. 25 Apr, 2016 1 commit
  4. 24 Apr, 2016 1 commit
  5. 16 Apr, 2016 1 commit
  6. 10 Feb, 2016 1 commit
  7. 10 Jan, 2016 1 commit
  8. 25 Jan, 2016 1 commit
    • mattijs's avatar
      ENH: glboal file handling: initial commit · a644a9f4
      mattijs authored
      Moved file path handling to regIOobject and made it type specific so
      now every object can have its own rules. Examples:
      - faceZones are now processor local (and don't search up anymore)
      - timeStampMaster is now no longer hardcoded inside IOdictionary
        (e.g. uniformDimensionedFields support it as well)
      - the distributedTriSurfaceMesh is properly processor-local; no need
        for fileModificationChecking manipulation.
      a644a9f4
  9. 17 Jun, 2013 1 commit
  10. 05 Apr, 2013 1 commit
  11. 17 Dec, 2012 1 commit
  12. 06 Dec, 2012 1 commit
  13. 11 Jun, 2012 1 commit
  14. 06 Dec, 2011 1 commit
  15. 14 Aug, 2011 1 commit
  16. 14 Jan, 2011 1 commit
  17. 06 Sep, 2010 1 commit
  18. 02 Jun, 2010 2 commits
  19. 19 May, 2010 1 commit
  20. 30 Apr, 2010 1 commit
  21. 29 Mar, 2010 1 commit
  22. 24 Feb, 2010 1 commit
  23. 23 Nov, 2009 1 commit
    • Mark Olesen's avatar
      Commit Paraview enhancements - quit working on sets/zones frills · 4b82f942
      Mark Olesen authored
      - Include Sets/Zones now scans immediately to refresh the list of available
        mesh parts. Unfortunately, this also causes the object panel to be
        modified, even although the selection doesn't acutally need to change.
        This seems to be due to how the pqNamedWidgets are getting the information
        from the proxy properties. I can't figure if it's possible to acheive what
        I want, but we can probably live with the current implementation.
      
        After IncludeZones, simply us 'Reset' to undo the spurious GUI changes.
        Works fine - just looks a bit silly.
      
      - Added 'Refresh' button to rescan for new times/fields.  Good for
        post-processing ongoing calculations without exiting the reader.
      
      - Added 'Skip Zero Time' checkbox: many (some) calculations have
        data missing at time=0 (eg, rho, lagrangian, etc). This provides
        a convenient way to skip over this time.
      
      - Future?:
        We could probably pick up favourite default values for these switches from
        ~OpenFOAM/controlDict, from a case system/paraview, or simply by making
        the casename.OpenFOAM also be an OpenFOAM dictionary with the settings.
      4b82f942
  24. 27 Nov, 2009 1 commit
    • Mark Olesen's avatar
      coding style adherence · 6d9d6262
      Mark Olesen authored
      - markup codingStyleGuide.org examples so they actually indent correctly
      
      - use 'Info<<' as per codingStyleGuide instead of 'Info <<'
      6d9d6262
  25. 18 Oct, 2009 1 commit
    • Mark Olesen's avatar
      Cleanup/fixup paraview readers · 7b6547ba
      Mark Olesen authored
      - remove patch/point text labels upon deletion
      
      - combined client/server plugin instead of separate .so files
        first experiment with adding panel decorations
      
      - directory reorganization
      7b6547ba
  26. 05 Oct, 2009 1 commit
  27. 22 Jul, 2009 1 commit
  28. 20 May, 2009 1 commit
  29. 23 Mar, 2009 2 commits
  30. 04 Mar, 2009 1 commit
  31. 20 Feb, 2009 1 commit
  32. 02 Feb, 2009 1 commit
  33. 31 Dec, 2008 1 commit
  34. 21 Nov, 2008 1 commit
  35. 10 Aug, 2008 1 commit
  36. 08 Aug, 2008 1 commit
    • Mark Olesen's avatar
      PV3FoamReader gets (single) mesh region handling · d8369415
      Mark Olesen authored
        - handling multiple regions require multiple readers
        - a region is currently recognized by the file name, anything after the
          '=' delimiter (eg, "case=region.OpenFOAM") is used to determine the
          mesh region, but might be changed in the future
          eg, 'case%region', 'case^region', 'case~region', 'case{region}' ...
      
      Note:
        - Having a separate reader for each region instead attempting to handle
          all the mesh regions in a single reader is the better solution.
          It is not only simpler, but allows distinct field selections for
          each region
      Todo:
        - Haven't a test for Lagrangian and multi-regions.
      d8369415
  37. 05 Aug, 2008 1 commit
    • Mark Olesen's avatar
      PV3FoamReader - minor changes · d20b6fe6
      Mark Olesen authored
        - remove TimeRange property from XML. Not needed for discrete time data
        - represent Lagrangian data as VTK_VERTEX for simple visualization
      d20b6fe6
  38. 04 Aug, 2008 1 commit