- Jul 30, 2008
-
-
Andrew Heather authored
-
-
Mattijs Janssens authored
-
Mattijs Janssens authored
-
- Jul 29, 2008
-
-
Mattijs Janssens authored
-
Mattijs Janssens authored
-
Mattijs Janssens authored
-
Mattijs Janssens authored
-
Mattijs Janssens authored
-
Mark Olesen authored
-
henry authored
-
-
henry authored
-
henry authored
-
Mark Olesen authored
-
Mark Olesen authored
-
Mark Olesen authored
-
- Jul 28, 2008
-
-
Mattijs Janssens authored
-
Mattijs Janssens authored
-
Mattijs Janssens authored
-
Mark Olesen authored
- vtkPV3Foam get PrintSelf (reduces number of methods) - move output data member from vtkPV3Foam -> PV3FoamReader in preparation for rewriting output method - roughed in code to track mesh/field changes in preparation for rewriting output method - progress bar with arbitrary values to give the user something to watch
-
Mark Olesen authored
-
- Jul 27, 2008
-
-
-
henry authored
-
- Jul 25, 2008
-
-
Andrew Heather authored
-
Mark Olesen authored
-
Mark Olesen authored
- Remove paraFoam/Allwmake leftover junk - Always attempt make of libccmio to ensure lnInclude/ exists
-
Mark Olesen authored
- avoid code duplication in vtkPV3Foam.C and checkTimeOption.H - can also be used in Time::findClosestTime(), but didn't touch that
-
Mattijs Janssens authored
-
Mattijs Janssens authored
-
Mattijs Janssens authored
-
Mattijs Janssens authored
-
Mark Olesen authored
- On the first call, select 'internalMesh' and the 'p', 'U' fields. This corresponds to a fairly common default case without loading all possible fields etc. - Include zones should now work without issuing a FatalError when the corresponding files are missing. I must have tried too many things at once and didn't notice this before. - Use ZoneMesh for zone names if the fvMesh is already cached (skips re-reading the same files). - Change reader description to "OpenFOAM Reader" to distinguish it a bit from the vtkOpenFOAMReader built into paraview/vtk - Misc. file and method names reorganized - Remaining problem: mixing internalMesh and cellZones is clunky since there aren't yet interpolated point values for cellSets/cellZones. Paraview complains about the mismatch, but extracting a block is still okay. TODO: - multi-port output for Lagrangian - hold all the vtk mesh parts (including multiblock) and just pass the reference. With this, the pipeline might notice that the geometry is actually identical and skip the PVGeometryFilter that takes so long.
-
- Jul 24, 2008
-
-
-
henry authored
-
Mark Olesen authored
-
andy authored
-
Mattijs Janssens authored
-
Mattijs Janssens authored
-
Mattijs Janssens authored
-