Read LS-Dyna databases (d3plot) More...
#include <vtkLSDynaReader.h>
Detailed Description
Read LS-Dyna databases (d3plot)
This filter reads LS-Dyna databases.
The Set/GetFileName() routines are actually wrappers around the Set/GetDatabaseDirectory() members; the actual filename you choose is irrelevant -- only the directory name is used. This is done in order to accommodate ParaView.
Note that this reader produces 7 output meshes. These meshes are required as several attributes are defined on subsets of the mesh. Below is a list of meshes in the order they are output and an explanation of which attributes are unique to each mesh:
- solid (3D) elements: number of integration points are different than 2D
- thick shell elements: number of integration points are different than planar 2D
- shell (2D) elements: number of integration points are different than 3D
- rigid surfaces: can't have deflection, only velocity, accel, etc.
- road surfaces: have only a "segment ID" (serves as material ID) and a velocity.
- beam elements: have Frenet (TNB) frame and cross-section attributes (shape and size)
spherical particle hydrodynamics (SPH) elements: have a radius of influence, internal energy, etc. Because each mesh has its own cell attributes, the vtkLSDynaReader has a rather large API. Instead of a single set of routines to query and set cell array names and status, one exists for each possible output mesh. Also, GetNumberOfCells() will return the sum of all the cells in all 7 meshes. If you want the number of cells in a specific mesh, there are separate routines for each mesh type.
- Attention:
- LSDyna files contain 3 different types of sections: control, data, and state. Control sections contain constants that describe the type of simulation data in a file or group of files. Data sections contain simulation information that is invariant across individual time steps (but can vary when a mesh adaptation occurs). This information includes material, connectivity, and undeformed geometry. Finally, state data is information that varies with each time step. Unless a mesh adaptation occurs, there will be a single control and data section, and they will be located at the start of the database (the first file).
- In their infinite wisdom, LSDyna developers decided to split simulation data into multiple files, each no larger than some predetermined limit. Each file can contain one section, a partial section (if it would not fit into a single file), or multiple sections. Files are padded with zeros so that their lengths will be multiples of 512*512. The size of each section is determined by constants in the control and data sections, which means that these must be parsed carefully in order to correctly locate desired information. Unfortunately, the constants are not terribly well-documented and in some cases the documentation is in error.
- Open Issues
- : The LS-Dyna file format document leaves a good bit open to interpretation. In addition to the "documentation vs. files in the wild" issues there are also implementation problems.
- Open Issues
- :
- Where exactly may breaks to a new file occur in the pre-state information? At each section?
- Will state data sections (node/cell data, element deletion, sph data, rigid body motion) be moved to the beginning of a new file if their data will be too large for a given file, or are all the sections counted together as a single state (makes more sense for keeping time word at start of every file). The questions above arise because the docs (p. 3) state "There are 3 sections in this database." but then call many smaller pieces of data "sections". Should they be subsections? The docs are quiet about whether the second section (of 3) is ever split across multiple files and, if so, whether it is done at (sub)section boundaries when possible or just wherever it needs to occur.
- How many components does Eddy Viscosity have? It's shown as 7 bits in NCFDV1 which makes no sense at all.
- Why is NARBS larger than 10+NUMNP+NEL8+NEL2+NEL4+NELT (which is the value specified by the documentation)? Obviously, NARBS is definitive, but what are the extra numbers at the end?
- Is there a difference between rigid body elements NUMRBE and rigid road surfaces? It appears that the nodes and connectivity of the road surface are given separately (p.13) while on p.7 the Material Type Data subsection says that shells in a rigid body will just have a certain material ID but be interspersed among deformable shell elements.
- Word 37 of the control section serves two possible purposes... it can mean NMSPH or EDLOPT. I assume that different versions of the code use that word differently. How do we know the difference?
- It's unclear how much state isn't stored when a shell element is marked as rigid. Specifically, is element deletion data stored for rigid shells? Page 21 of the spec is mute on this.
The loop to read cell User IDs won't work if Rigid Body and Shell elements are interleaved (which I now believe they are).
- Open Issues
- : On the VTK side of things:
- Berk has nudged me towards multiblock outputs but hasn't committed to exactly how things can be made efficient for a parallel version of the reader.
- This reader will eventually need to respond to a second output port for "small spatial, large temporal" queries.
- The reader doesn't handle crack files (d3crck)
- The reader doesn't handle interface force files (no default name)
- The reader doesn't handle time history (abbreviated output) files (d3thdt)
- The reader doesn't handle dynamic relaxation files (d3drfl)
- The reader doesn't handle reduced parts (state for a subset of parts) files (d3part)
- The reader doesn't handle mode shape files (d3eigv)
- The reader doesn't handle equilibrium iteration files (d3iter)
- The reader doesn't handle extra time data files (d3xtf)
- The reader doesn't handle printer files (d3hsp)
- The reader doesn't handle modal neutral files (d3mnf)
- The reader doesn't handle packed connectivity.
- The reader doesn't handle adapted element parent lists (but the 2002 specification says LSDyna doesn't implement it).
- All the sample datasets have MATTYP = 0. Need something to test MATTYP = 1.
- I have no test datasets with rigid body and/or road surfaces, so the implementation is half-baked.
It's unclear how some of the data should be presented. Although blindly tacking the numbers into a large chuck of cell data is better than nothing, some attributes (e.g., forces & moments) lend themselves to more elaborate presentation. Also, shell and thick shell elements have stresses that belong to a particular side of an element or have a finite thickness that could be rendered. Finally, beam elements have cross sections that could be rendered. Some of these operations require numerical processing of the results and so we shouldn't eliminate the ability to get at the raw simulation data. Perhaps a filter could be applied to "fancify" the geometry.
- Tests:
- vtkLSDynaReader (Tests)
Definition at line 166 of file vtkLSDynaReader.h.
Member Typedef Documentation
Reimplemented from vtkMultiBlockDataSetAlgorithm.
Reimplemented in vtkPLSDynaReader.
Definition at line 169 of file vtkLSDynaReader.h.
Constructor & Destructor Documentation
| vtkLSDynaReader::vtkLSDynaReader | ( | ) | [protected] |
| virtual vtkLSDynaReader::~vtkLSDynaReader | ( | ) | [protected, virtual] |
Member Function Documentation
| static int vtkLSDynaReader::IsTypeOf | ( | const char * | name | ) | [static] |
Return 1 if this class type is the same type of (or a subclass of) the named class. Returns 0 otherwise. This method works in combination with vtkTypeMacro found in vtkSetGet.h.
Reimplemented from vtkMultiBlockDataSetAlgorithm.
Reimplemented in vtkPLSDynaReader.
| virtual int vtkLSDynaReader::IsA | ( | const char * | name | ) | [virtual] |
Return 1 if this class is the same type of (or a subclass of) the named class. Returns 0 otherwise. This method works in combination with vtkTypeMacro found in vtkSetGet.h.
Reimplemented from vtkMultiBlockDataSetAlgorithm.
Reimplemented in vtkPLSDynaReader.
| static vtkLSDynaReader* vtkLSDynaReader::SafeDownCast | ( | vtkObjectBase * | o | ) | [static] |
Reimplemented from vtkMultiBlockDataSetAlgorithm.
Reimplemented in vtkPLSDynaReader.
| virtual vtkObjectBase* vtkLSDynaReader::NewInstanceInternal | ( | ) | const [protected, virtual] |
Reimplemented from vtkMultiBlockDataSetAlgorithm.
Reimplemented in vtkPLSDynaReader.
| vtkLSDynaReader* vtkLSDynaReader::NewInstance | ( | ) | const |
Reimplemented from vtkMultiBlockDataSetAlgorithm.
Reimplemented in vtkPLSDynaReader.
| virtual void vtkLSDynaReader::PrintSelf | ( | ostream & | os, |
| vtkIndent | indent | ||
| ) | [virtual] |
Methods invoked by print to print information about the object including superclasses. Typically not called by the user (use Print() instead) but used in the hierarchical print process to combine the output of several classes.
Reimplemented from vtkMultiBlockDataSetAlgorithm.
Reimplemented in vtkPLSDynaReader.
| static vtkLSDynaReader* vtkLSDynaReader::New | ( | ) | [static] |
Create an object with Debug turned off, modified time initialized to zero, and reference counting on.
Reimplemented from vtkMultiBlockDataSetAlgorithm.
Reimplemented in vtkPLSDynaReader.
| void vtkLSDynaReader::Dump | ( | ostream & | os | ) |
Print out more complete information about the dataset (and less complete information about the VTK hierarchy) than PrintSelf.
| void vtkLSDynaReader::DebugDump | ( | ) |
A routine to call Dump() from within a lame debugger that won't properly pass a C++ iostream object like cout.
| virtual int vtkLSDynaReader::CanReadFile | ( | const char * | fname | ) | [virtual] |
Determine if the file can be readed with this reader.
Reimplemented in vtkPLSDynaReader.
| virtual void vtkLSDynaReader::SetDatabaseDirectory | ( | const char * | ) | [virtual] |
Get/Set the directory containing the LS-Dyna database and determine whether it is valid.
| const char* vtkLSDynaReader::GetDatabaseDirectory | ( | ) |
Get/Set the directory containing the LS-Dyna database and determine whether it is valid.
Get/Set the directory containing the LS-Dyna database and determine whether it is valid.
| virtual void vtkLSDynaReader::SetFileName | ( | const char * | ) | [virtual] |
Get/Set the filename. The Set/GetFileName() routines are actually wrappers around the Set/GetDatabaseDirectory() members; the actual filename you choose is irrelevant -- only the directory name is used. This is done in order to accommodate ParaView.
| const char* vtkLSDynaReader::GetFileName | ( | ) |
Get/Set the filename. The Set/GetFileName() routines are actually wrappers around the Set/GetDatabaseDirectory() members; the actual filename you choose is irrelevant -- only the directory name is used. This is done in order to accommodate ParaView.
| char* vtkLSDynaReader::GetTitle | ( | ) |
The title of the database is a 40 or 80 character text description stored at the front of a d3plot file. Do not call this function before setting the database directory and calling UpdateInformation().
Retrieve the dimension of points in the database. This should return 2 or 3. Do not call this function before setting the database directory and calling UpdateInformation().
Retrieve the number of points in the database. Do not call this function before setting the database directory and calling UpdateInformation().
Retrieve the number of cells of a given type in the database. Do not call this function before setting the database directory and calling UpdateInformation(). Note that GetNumberOfCells() returns the sum of GetNumberOfContinuumCells() and GetNumberOfParticleCells().
Retrieve the number of cells of a given type in the database. Do not call this function before setting the database directory and calling UpdateInformation(). Note that GetNumberOfContinuumCells() returns the sum of GetNumberOfSolidCells(), GetNumberOfThickShellCells(), GetNumberOfShellCells(), GetNumberOfRigidBodyCells(), GetNumberOfRoadSurfaceCells(), and GetNumberOfBeamCells().
Retrieve the number of cells of a given type in the database. Do not call this function before setting the database directory and calling UpdateInformation().
Retrieve the number of cells of a given type in the database. Do not call this function before setting the database directory and calling UpdateInformation().
Retrieve the number of cells of a given type in the database. Do not call this function before setting the database directory and calling UpdateInformation().
Retrieve the number of cells of a given type in the database. Do not call this function before setting the database directory and calling UpdateInformation().
Retrieve the number of cells of a given type in the database. Do not call this function before setting the database directory and calling UpdateInformation().
Retrieve the number of cells of a given type in the database. Do not call this function before setting the database directory and calling UpdateInformation().
Retrieve the number of cells of a given type in the database. Do not call this function before setting the database directory and calling UpdateInformation().
Retrieve information about the time extents of the LS-Dyna database. Do not call these functions before setting the database directory and calling UpdateInformation().
| virtual void vtkLSDynaReader::SetTimeStep | ( | vtkIdType | ) | [virtual] |
Retrieve information about the time extents of the LS-Dyna database. Do not call these functions before setting the database directory and calling UpdateInformation().
Retrieve information about the time extents of the LS-Dyna database. Do not call these functions before setting the database directory and calling UpdateInformation().
Retrieve information about the time extents of the LS-Dyna database. Do not call these functions before setting the database directory and calling UpdateInformation().
| virtual int* vtkLSDynaReader::GetTimeStepRange | ( | ) | [virtual] |
Retrieve information about the time extents of the LS-Dyna database. Do not call these functions before setting the database directory and calling UpdateInformation().
| virtual void vtkLSDynaReader::GetTimeStepRange | ( | int & | , |
| int & | |||
| ) | [virtual] |
Retrieve information about the time extents of the LS-Dyna database. Do not call these functions before setting the database directory and calling UpdateInformation().
| virtual void vtkLSDynaReader::GetTimeStepRange | ( | int | [2] | ) | [virtual] |
Retrieve information about the time extents of the LS-Dyna database. Do not call these functions before setting the database directory and calling UpdateInformation().
| virtual void vtkLSDynaReader::SetTimeStepRange | ( | int | , |
| int | |||
| ) | [virtual] |
Retrieve information about the time extents of the LS-Dyna database. Do not call these functions before setting the database directory and calling UpdateInformation().
| void vtkLSDynaReader::SetTimeStepRange | ( | int | [2] | ) |
Retrieve information about the time extents of the LS-Dyna database. Do not call these functions before setting the database directory and calling UpdateInformation().
These methods allow you to load only selected subsets of the nodal variables defined over the mesh.
| const char* vtkLSDynaReader::GetPointArrayName | ( | int | ) |
These methods allow you to load only selected subsets of the nodal variables defined over the mesh.
| virtual void vtkLSDynaReader::SetPointArrayStatus | ( | int | arr, |
| int | status | ||
| ) | [virtual] |
These methods allow you to load only selected subsets of the nodal variables defined over the mesh.
| void vtkLSDynaReader::SetPointArrayStatus | ( | const char * | arrName, |
| int | status | ||
| ) | [inline, virtual] |
These methods allow you to load only selected subsets of the nodal variables defined over the mesh.
Definition at line 593 of file vtkLSDynaReader.h.
These methods allow you to load only selected subsets of the nodal variables defined over the mesh.
| int vtkLSDynaReader::GetPointArrayStatus | ( | const char * | arrName | ) | [inline] |
These methods allow you to load only selected subsets of the nodal variables defined over the mesh.
Definition at line 606 of file vtkLSDynaReader.h.
These methods allow you to load only selected subsets of the nodal variables defined over the mesh.
| int vtkLSDynaReader::GetNumberOfComponentsInPointArray | ( | const char * | arrName | ) | [inline] |
These methods allow you to load only selected subsets of the nodal variables defined over the mesh.
Definition at line 619 of file vtkLSDynaReader.h.
| int vtkLSDynaReader::GetNumberOfCellArrays | ( | int | cellType | ) |
Routines that allow the status of a cell variable to be adjusted or queried independent of the output mesh. The cellType parameter should be one of: LS_POINT, LS_BEAM, LS_SHELL, LS_THICK_SHELL, LS_SOLID, LS_RIGID_BODY, or LS_ROAD_SURFACE
| const char* vtkLSDynaReader::GetCellArrayName | ( | int | cellType, |
| int | arr | ||
| ) |
Routines that allow the status of a cell variable to be adjusted or queried independent of the output mesh. The cellType parameter should be one of: LS_POINT, LS_BEAM, LS_SHELL, LS_THICK_SHELL, LS_SOLID, LS_RIGID_BODY, or LS_ROAD_SURFACE
| virtual void vtkLSDynaReader::SetCellArrayStatus | ( | int | cellType, |
| int | arr, | ||
| int | status | ||
| ) | [virtual] |
Routines that allow the status of a cell variable to be adjusted or queried independent of the output mesh. The cellType parameter should be one of: LS_POINT, LS_BEAM, LS_SHELL, LS_THICK_SHELL, LS_SOLID, LS_RIGID_BODY, or LS_ROAD_SURFACE
| void vtkLSDynaReader::SetCellArrayStatus | ( | int | cellType, |
| const char * | arrName, | ||
| int | status | ||
| ) | [inline, virtual] |
Routines that allow the status of a cell variable to be adjusted or queried independent of the output mesh. The cellType parameter should be one of: LS_POINT, LS_BEAM, LS_SHELL, LS_THICK_SHELL, LS_SOLID, LS_RIGID_BODY, or LS_ROAD_SURFACE
Definition at line 632 of file vtkLSDynaReader.h.
| int vtkLSDynaReader::GetCellArrayStatus | ( | int | cellType, |
| int | arr | ||
| ) |
Routines that allow the status of a cell variable to be adjusted or queried independent of the output mesh. The cellType parameter should be one of: LS_POINT, LS_BEAM, LS_SHELL, LS_THICK_SHELL, LS_SOLID, LS_RIGID_BODY, or LS_ROAD_SURFACE
| int vtkLSDynaReader::GetCellArrayStatus | ( | int | cellType, |
| const char * | arrName | ||
| ) | [inline] |
Routines that allow the status of a cell variable to be adjusted or queried independent of the output mesh. The cellType parameter should be one of: LS_POINT, LS_BEAM, LS_SHELL, LS_THICK_SHELL, LS_SOLID, LS_RIGID_BODY, or LS_ROAD_SURFACE
Definition at line 645 of file vtkLSDynaReader.h.
| int vtkLSDynaReader::GetNumberOfComponentsInCellArray | ( | int | cellType, |
| int | arr | ||
| ) |
Routines that allow the status of a cell variable to be adjusted or queried independent of the output mesh. The cellType parameter should be one of: LS_POINT, LS_BEAM, LS_SHELL, LS_THICK_SHELL, LS_SOLID, LS_RIGID_BODY, or LS_ROAD_SURFACE
| int vtkLSDynaReader::GetNumberOfComponentsInCellArray | ( | int | cellType, |
| const char * | arrName | ||
| ) | [inline] |
Routines that allow the status of a cell variable to be adjusted or queried independent of the output mesh. The cellType parameter should be one of: LS_POINT, LS_BEAM, LS_SHELL, LS_THICK_SHELL, LS_SOLID, LS_RIGID_BODY, or LS_ROAD_SURFACE
Definition at line 658 of file vtkLSDynaReader.h.
These methods allow you to load only selected subsets of the cell variables defined over the mesh.
| const char* vtkLSDynaReader::GetSolidArrayName | ( | int | ) |
These methods allow you to load only selected subsets of the cell variables defined over the mesh.
| virtual void vtkLSDynaReader::SetSolidArrayStatus | ( | int | arr, |
| int | status | ||
| ) | [virtual] |
These methods allow you to load only selected subsets of the cell variables defined over the mesh.
| void vtkLSDynaReader::SetSolidArrayStatus | ( | const char * | arrName, |
| int | status | ||
| ) | [inline, virtual] |
These methods allow you to load only selected subsets of the cell variables defined over the mesh.
Definition at line 671 of file vtkLSDynaReader.h.
These methods allow you to load only selected subsets of the cell variables defined over the mesh.
| int vtkLSDynaReader::GetSolidArrayStatus | ( | const char * | arrName | ) | [inline] |
These methods allow you to load only selected subsets of the cell variables defined over the mesh.
Definition at line 684 of file vtkLSDynaReader.h.
| int vtkLSDynaReader::GetNumberOfComponentsInSolidArray | ( | const char * | arrName | ) | [inline] |
Definition at line 697 of file vtkLSDynaReader.h.
These methods allow you to load only selected subsets of the cell variables defined over the mesh.
| const char* vtkLSDynaReader::GetThickShellArrayName | ( | int | ) |
These methods allow you to load only selected subsets of the cell variables defined over the mesh.
| virtual void vtkLSDynaReader::SetThickShellArrayStatus | ( | int | arr, |
| int | status | ||
| ) | [virtual] |
These methods allow you to load only selected subsets of the cell variables defined over the mesh.
| void vtkLSDynaReader::SetThickShellArrayStatus | ( | const char * | arrName, |
| int | status | ||
| ) | [inline, virtual] |
These methods allow you to load only selected subsets of the cell variables defined over the mesh.
Definition at line 710 of file vtkLSDynaReader.h.
These methods allow you to load only selected subsets of the cell variables defined over the mesh.
| int vtkLSDynaReader::GetThickShellArrayStatus | ( | const char * | arrName | ) | [inline] |
These methods allow you to load only selected subsets of the cell variables defined over the mesh.
Definition at line 723 of file vtkLSDynaReader.h.
| int vtkLSDynaReader::GetNumberOfComponentsInThickShellArray | ( | const char * | arrName | ) | [inline] |
Definition at line 736 of file vtkLSDynaReader.h.
These methods allow you to load only selected subsets of the cell variables defined over the mesh.
| const char* vtkLSDynaReader::GetShellArrayName | ( | int | ) |
These methods allow you to load only selected subsets of the cell variables defined over the mesh.
| virtual void vtkLSDynaReader::SetShellArrayStatus | ( | int | arr, |
| int | status | ||
| ) | [virtual] |
These methods allow you to load only selected subsets of the cell variables defined over the mesh.
| void vtkLSDynaReader::SetShellArrayStatus | ( | const char * | arrName, |
| int | status | ||
| ) | [inline, virtual] |
These methods allow you to load only selected subsets of the cell variables defined over the mesh.
Definition at line 749 of file vtkLSDynaReader.h.
These methods allow you to load only selected subsets of the cell variables defined over the mesh.
| int vtkLSDynaReader::GetShellArrayStatus | ( | const char * | arrName | ) | [inline] |
These methods allow you to load only selected subsets of the cell variables defined over the mesh.
Definition at line 762 of file vtkLSDynaReader.h.
| int vtkLSDynaReader::GetNumberOfComponentsInShellArray | ( | const char * | arrName | ) | [inline] |
Definition at line 775 of file vtkLSDynaReader.h.
These methods allow you to load only selected subsets of the cell variables defined over the mesh.
| const char* vtkLSDynaReader::GetRigidBodyArrayName | ( | int | ) |
These methods allow you to load only selected subsets of the cell variables defined over the mesh.
| virtual void vtkLSDynaReader::SetRigidBodyArrayStatus | ( | int | arr, |
| int | status | ||
| ) | [virtual] |
These methods allow you to load only selected subsets of the cell variables defined over the mesh.
| void vtkLSDynaReader::SetRigidBodyArrayStatus | ( | const char * | arrName, |
| int | status | ||
| ) | [inline, virtual] |
These methods allow you to load only selected subsets of the cell variables defined over the mesh.
Definition at line 866 of file vtkLSDynaReader.h.
These methods allow you to load only selected subsets of the cell variables defined over the mesh.
| int vtkLSDynaReader::GetRigidBodyArrayStatus | ( | const char * | arrName | ) | [inline] |
These methods allow you to load only selected subsets of the cell variables defined over the mesh.
Definition at line 879 of file vtkLSDynaReader.h.
| int vtkLSDynaReader::GetNumberOfComponentsInRigidBodyArray | ( | const char * | arrName | ) | [inline] |
Definition at line 892 of file vtkLSDynaReader.h.
These methods allow you to load only selected subsets of the cell variables defined over the mesh.
| const char* vtkLSDynaReader::GetRoadSurfaceArrayName | ( | int | ) |
These methods allow you to load only selected subsets of the cell variables defined over the mesh.
| virtual void vtkLSDynaReader::SetRoadSurfaceArrayStatus | ( | int | arr, |
| int | status | ||
| ) | [virtual] |
These methods allow you to load only selected subsets of the cell variables defined over the mesh.
| void vtkLSDynaReader::SetRoadSurfaceArrayStatus | ( | const char * | arrName, |
| int | status | ||
| ) | [inline, virtual] |
These methods allow you to load only selected subsets of the cell variables defined over the mesh.
Definition at line 905 of file vtkLSDynaReader.h.
These methods allow you to load only selected subsets of the cell variables defined over the mesh.
| int vtkLSDynaReader::GetRoadSurfaceArrayStatus | ( | const char * | arrName | ) | [inline] |
These methods allow you to load only selected subsets of the cell variables defined over the mesh.
Definition at line 918 of file vtkLSDynaReader.h.
| int vtkLSDynaReader::GetNumberOfComponentsInRoadSurfaceArray | ( | const char * | arrName | ) | [inline] |
Definition at line 931 of file vtkLSDynaReader.h.
These methods allow you to load only selected subsets of the cell variables defined over the mesh.
| const char* vtkLSDynaReader::GetBeamArrayName | ( | int | ) |
These methods allow you to load only selected subsets of the cell variables defined over the mesh.
| virtual void vtkLSDynaReader::SetBeamArrayStatus | ( | int | arr, |
| int | status | ||
| ) | [virtual] |
These methods allow you to load only selected subsets of the cell variables defined over the mesh.
| void vtkLSDynaReader::SetBeamArrayStatus | ( | const char * | arrName, |
| int | status | ||
| ) | [inline, virtual] |
These methods allow you to load only selected subsets of the cell variables defined over the mesh.
Definition at line 788 of file vtkLSDynaReader.h.
These methods allow you to load only selected subsets of the cell variables defined over the mesh.
| int vtkLSDynaReader::GetBeamArrayStatus | ( | const char * | arrName | ) | [inline] |
These methods allow you to load only selected subsets of the cell variables defined over the mesh.
Definition at line 801 of file vtkLSDynaReader.h.
| int vtkLSDynaReader::GetNumberOfComponentsInBeamArray | ( | const char * | arrName | ) | [inline] |
Definition at line 814 of file vtkLSDynaReader.h.
These methods allow you to load only selected subsets of the cell variables defined over the mesh.
| const char* vtkLSDynaReader::GetParticleArrayName | ( | int | ) |
These methods allow you to load only selected subsets of the cell variables defined over the mesh.
| virtual void vtkLSDynaReader::SetParticleArrayStatus | ( | int | arr, |
| int | status | ||
| ) | [virtual] |
These methods allow you to load only selected subsets of the cell variables defined over the mesh.
| void vtkLSDynaReader::SetParticleArrayStatus | ( | const char * | arrName, |
| int | status | ||
| ) | [inline, virtual] |
These methods allow you to load only selected subsets of the cell variables defined over the mesh.
Definition at line 827 of file vtkLSDynaReader.h.
These methods allow you to load only selected subsets of the cell variables defined over the mesh.
| int vtkLSDynaReader::GetParticleArrayStatus | ( | const char * | arrName | ) | [inline] |
These methods allow you to load only selected subsets of the cell variables defined over the mesh.
Definition at line 840 of file vtkLSDynaReader.h.
| int vtkLSDynaReader::GetNumberOfComponentsInParticleArray | ( | const char * | arrName | ) | [inline] |
Definition at line 853 of file vtkLSDynaReader.h.
| void vtkLSDynaReader::SetDeformedMesh | ( | int | ) |
Should deflected coordinates be used, or should the mesh remain undeflected? By default, this is true but its value is ignored if the nodal "Deflection" array is not set to be loaded.
| virtual int vtkLSDynaReader::GetDeformedMesh | ( | ) | [virtual] |
Should deflected coordinates be used, or should the mesh remain undeflected? By default, this is true but its value is ignored if the nodal "Deflection" array is not set to be loaded.
| virtual void vtkLSDynaReader::DeformedMeshOn | ( | ) | [virtual] |
Should deflected coordinates be used, or should the mesh remain undeflected? By default, this is true but its value is ignored if the nodal "Deflection" array is not set to be loaded.
| virtual void vtkLSDynaReader::DeformedMeshOff | ( | ) | [virtual] |
Should deflected coordinates be used, or should the mesh remain undeflected? By default, this is true but its value is ignored if the nodal "Deflection" array is not set to be loaded.
| virtual void vtkLSDynaReader::SetRemoveDeletedCells | ( | int | ) | [virtual] |
Should dead cells be removed from the mesh? Cells are marked dead by setting the corresponding entry in the cell array "Death" to 0. Cells that are not dead have the corresponding entry in the cell array "Death" set to their material ID. By default, this is true but its value is ignored if the cell "Death" array is not set to be loaded. It is also ignored if the database's element deletion option is set to denote points (not cells) as deleted; in that case, "Death" will appear to be a point array.
| virtual int vtkLSDynaReader::GetRemoveDeletedCells | ( | ) | [virtual] |
Should dead cells be removed from the mesh? Cells are marked dead by setting the corresponding entry in the cell array "Death" to 0. Cells that are not dead have the corresponding entry in the cell array "Death" set to their material ID. By default, this is true but its value is ignored if the cell "Death" array is not set to be loaded. It is also ignored if the database's element deletion option is set to denote points (not cells) as deleted; in that case, "Death" will appear to be a point array.
| virtual void vtkLSDynaReader::RemoveDeletedCellsOn | ( | ) | [virtual] |
Should dead cells be removed from the mesh? Cells are marked dead by setting the corresponding entry in the cell array "Death" to 0. Cells that are not dead have the corresponding entry in the cell array "Death" set to their material ID. By default, this is true but its value is ignored if the cell "Death" array is not set to be loaded. It is also ignored if the database's element deletion option is set to denote points (not cells) as deleted; in that case, "Death" will appear to be a point array.
| virtual void vtkLSDynaReader::RemoveDeletedCellsOff | ( | ) | [virtual] |
Should dead cells be removed from the mesh? Cells are marked dead by setting the corresponding entry in the cell array "Death" to 0. Cells that are not dead have the corresponding entry in the cell array "Death" set to their material ID. By default, this is true but its value is ignored if the cell "Death" array is not set to be loaded. It is also ignored if the database's element deletion option is set to denote points (not cells) as deleted; in that case, "Death" will appear to be a point array.
| virtual void vtkLSDynaReader::SetDeletedCellsAsGhostArray | ( | int | ) | [virtual] |
Instead of removing the cells that are dead, hide them by setting the array as the ghost levels arrays
| virtual int vtkLSDynaReader::GetDeletedCellsAsGhostArray | ( | ) | [virtual] |
Instead of removing the cells that are dead, hide them by setting the array as the ghost levels arrays
| virtual void vtkLSDynaReader::DeletedCellsAsGhostArrayOn | ( | ) | [virtual] |
Instead of removing the cells that are dead, hide them by setting the array as the ghost levels arrays
| virtual void vtkLSDynaReader::DeletedCellsAsGhostArrayOff | ( | ) | [virtual] |
Instead of removing the cells that are dead, hide them by setting the array as the ghost levels arrays
| virtual void vtkLSDynaReader::SetInputDeck | ( | const char * | ) | [virtual] |
The name of the input deck corresponding to the current database. This is used to determine the part names associated with each material ID. This file may be in two formats: a valid LSDyna input deck or a short XML summary. If the file begins with "<?xml" then the summary format is used. Otherwise, the keyword format is used and a summary file will be created if write permissions exist in the directory containing the keyword file. The newly created summary will have ".k" or ".key" stripped from the end of the keyword filename and ".lsdyna" appended.
| virtual char* vtkLSDynaReader::GetInputDeck | ( | ) | [virtual] |
The name of the input deck corresponding to the current database. This is used to determine the part names associated with each material ID. This file may be in two formats: a valid LSDyna input deck or a short XML summary. If the file begins with "<?xml" then the summary format is used. Otherwise, the keyword format is used and a summary file will be created if write permissions exist in the directory containing the keyword file. The newly created summary will have ".k" or ".key" stripped from the end of the keyword filename and ".lsdyna" appended.
These methods allow you to load only selected parts of the input. If InputDeck points to a valid keyword file (or summary), then part names will be taken from that file. Otherwise, when arbitrary material numbering is used, parts will be named "PartXXX (MatlYYY)" where XXX is an increasing sequential number and YYY is the respective material ID. If no input deck is specified and arbitrary arbitrary material numbering is not used, parts will be named "PartXXX" where XXX is a sequential material ID.
| const char* vtkLSDynaReader::GetPartArrayName | ( | int | ) |
These methods allow you to load only selected parts of the input. If InputDeck points to a valid keyword file (or summary), then part names will be taken from that file. Otherwise, when arbitrary material numbering is used, parts will be named "PartXXX (MatlYYY)" where XXX is an increasing sequential number and YYY is the respective material ID. If no input deck is specified and arbitrary arbitrary material numbering is not used, parts will be named "PartXXX" where XXX is a sequential material ID.
| virtual void vtkLSDynaReader::SetPartArrayStatus | ( | int | arr, |
| int | status | ||
| ) | [virtual] |
These methods allow you to load only selected parts of the input. If InputDeck points to a valid keyword file (or summary), then part names will be taken from that file. Otherwise, when arbitrary material numbering is used, parts will be named "PartXXX (MatlYYY)" where XXX is an increasing sequential number and YYY is the respective material ID. If no input deck is specified and arbitrary arbitrary material numbering is not used, parts will be named "PartXXX" where XXX is a sequential material ID.
| void vtkLSDynaReader::SetPartArrayStatus | ( | const char * | partName, |
| int | status | ||
| ) | [inline, virtual] |
These methods allow you to load only selected parts of the input. If InputDeck points to a valid keyword file (or summary), then part names will be taken from that file. Otherwise, when arbitrary material numbering is used, parts will be named "PartXXX (MatlYYY)" where XXX is an increasing sequential number and YYY is the respective material ID. If no input deck is specified and arbitrary arbitrary material numbering is not used, parts will be named "PartXXX" where XXX is a sequential material ID.
Definition at line 944 of file vtkLSDynaReader.h.
These methods allow you to load only selected parts of the input. If InputDeck points to a valid keyword file (or summary), then part names will be taken from that file. Otherwise, when arbitrary material numbering is used, parts will be named "PartXXX (MatlYYY)" where XXX is an increasing sequential number and YYY is the respective material ID. If no input deck is specified and arbitrary arbitrary material numbering is not used, parts will be named "PartXXX" where XXX is a sequential material ID.
| int vtkLSDynaReader::GetPartArrayStatus | ( | const char * | partName | ) | [inline] |
These methods allow you to load only selected parts of the input. If InputDeck points to a valid keyword file (or summary), then part names will be taken from that file. Otherwise, when arbitrary material numbering is used, parts will be named "PartXXX (MatlYYY)" where XXX is an increasing sequential number and YYY is the respective material ID. If no input deck is specified and arbitrary arbitrary material numbering is not used, parts will be named "PartXXX" where XXX is a sequential material ID.
Definition at line 957 of file vtkLSDynaReader.h.
| int vtkLSDynaReader::ReadHeaderInformation | ( | int | currentAdaptLevel | ) | [protected] |
This function populates the reader's private dictionary with information about the database. It is called once from RequestInformation() and once any time the adaptation level changes. The adaptation level can change any time the current state(time) is modified. Upon success, -1 is returned. "Soft" failures return 0 and "hard" failures return 1.
| int vtkLSDynaReader::ScanDatabaseTimeSteps | ( | ) | [protected] |
This function scans the list of files in the database and bookmarks the start of each time step's state information. Before this function is called: - The database directory name must be set, - ReadHeaderInformation must have been called for adaptation level 0, and - The "read head" must be placed at the end of the first adaptation's geometry section. Upon success, -1 is returned. "Soft" failures return 0 and "hard" failures return 1.
| virtual int vtkLSDynaReader::RequestInformation | ( | vtkInformation * | , |
| vtkInformationVector ** | , | ||
| vtkInformationVector * | |||
| ) | [protected, virtual] |
This is called by the superclass. This is the method you should override.
Reimplemented from vtkMultiBlockDataSetAlgorithm.
Reimplemented in vtkPLSDynaReader.
| virtual int vtkLSDynaReader::RequestData | ( | vtkInformation * | , |
| vtkInformationVector ** | , | ||
| vtkInformationVector * | |||
| ) | [protected, virtual] |
This is called by the superclass. This is the method you should override.
Reimplemented from vtkMultiBlockDataSetAlgorithm.
Reimplemented in vtkPLSDynaReader.
| virtual int vtkLSDynaReader::ReadTopology | ( | ) | [protected, virtual] |
These functions read various parts of the database. The functions that take a vtkIdType argument must be passed the current timestep. Functions that do not take a timestep must have the read head positioned to the start of their data sections. These functions should only be called from within RequestData() since they require the various output meshes to exist.
Reimplemented in vtkPLSDynaReader.
| virtual int vtkLSDynaReader::ReadNodes | ( | ) | [protected, virtual] |
These functions read various parts of the database. The functions that take a vtkIdType argument must be passed the current timestep. Functions that do not take a timestep must have the read head positioned to the start of their data sections. These functions should only be called from within RequestData() since they require the various output meshes to exist.
| virtual int vtkLSDynaReader::ReadPartSizes | ( | ) | [protected, virtual] |
These functions read various parts of the database. The functions that take a vtkIdType argument must be passed the current timestep. Functions that do not take a timestep must have the read head positioned to the start of their data sections. These functions should only be called from within RequestData() since they require the various output meshes to exist.
| virtual int vtkLSDynaReader::ReadConnectivityAndMaterial | ( | ) | [protected, virtual] |
These functions read various parts of the database. The functions that take a vtkIdType argument must be passed the current timestep. Functions that do not take a timestep must have the read head positioned to the start of their data sections. These functions should only be called from within RequestData() since they require the various output meshes to exist.
| virtual int vtkLSDynaReader::ReadUserIds | ( | ) | [protected, virtual] |
These functions read various parts of the database. The functions that take a vtkIdType argument must be passed the current timestep. Functions that do not take a timestep must have the read head positioned to the start of their data sections. These functions should only be called from within RequestData() since they require the various output meshes to exist.
| virtual int vtkLSDynaReader::ReadState | ( | vtkIdType | ) | [protected, virtual] |
These functions read various parts of the database. The functions that take a vtkIdType argument must be passed the current timestep. Functions that do not take a timestep must have the read head positioned to the start of their data sections. These functions should only be called from within RequestData() since they require the various output meshes to exist.
| virtual int vtkLSDynaReader::ReadNodeStateInfo | ( | vtkIdType | ) | [protected, virtual] |
These functions read various parts of the database. The functions that take a vtkIdType argument must be passed the current timestep. Functions that do not take a timestep must have the read head positioned to the start of their data sections. These functions should only be called from within RequestData() since they require the various output meshes to exist.
| virtual int vtkLSDynaReader::ReadCellStateInfo | ( | vtkIdType | ) | [protected, virtual] |
These functions read various parts of the database. The functions that take a vtkIdType argument must be passed the current timestep. Functions that do not take a timestep must have the read head positioned to the start of their data sections. These functions should only be called from within RequestData() since they require the various output meshes to exist.
| virtual int vtkLSDynaReader::ReadDeletion | ( | ) | [protected, virtual] |
These functions read various parts of the database. The functions that take a vtkIdType argument must be passed the current timestep. Functions that do not take a timestep must have the read head positioned to the start of their data sections. These functions should only be called from within RequestData() since they require the various output meshes to exist.
| virtual int vtkLSDynaReader::ReadSPHState | ( | vtkIdType | ) | [protected, virtual] |
These functions read various parts of the database. The functions that take a vtkIdType argument must be passed the current timestep. Functions that do not take a timestep must have the read head positioned to the start of their data sections. These functions should only be called from within RequestData() since they require the various output meshes to exist.
| virtual void vtkLSDynaReader::ResetPartInfo | ( | ) | [protected, virtual] |
Resets the Part information to the default state
| virtual int vtkLSDynaReader::ReadInputDeck | ( | ) | [protected, virtual] |
Called from within ReadHeaderInformation() to read part names associated with material IDs.
| virtual int vtkLSDynaReader::ReadPartTitlesFromRootFile | ( | ) | [protected, virtual] |
Called from within ReadHeaderInformation to read part names from the end of the first d3plot file. Used if ReadInputDeck fails.
| virtual int vtkLSDynaReader::ReadUserMaterialIds | ( | ) | [protected, virtual] |
Called from within ReadHeaderInformation() to read arbitrary material IDs (if present) or manufacture sequential material IDs (if not present).
| int vtkLSDynaReader::ReadInputDeckXML | ( | ifstream & | deck | ) | [protected] |
ReadInputDeck determines the type of file (keyword or XML summary) and calls one of these two routines to read the file.
| int vtkLSDynaReader::ReadInputDeckKeywords | ( | ifstream & | deck | ) | [protected] |
ReadInputDeck determines the type of file (keyword or XML summary) and calls one of these two routines to read the file.
| int vtkLSDynaReader::WriteInputDeckSummary | ( | const char * | fname | ) | [protected] |
ReadInputDeckKeywords calls this function if it was successful in reading part names for materials.
| virtual void vtkLSDynaReader::ReadDeletionArray | ( | vtkUnsignedCharArray * | arr, |
| const int & | pos, | ||
| const int & | size | ||
| ) | [protected, virtual] |
Read an array of deletion data. This is used by ReadDeletion to actually read the data from the file (as opposed to attach it to the proper place in the VTK dataset) depending on the value of "MDLOPT". The array passed to this routine is filled with ones if deleted, zero it is not deleted The number of tuples must be set on the array previous to calling this routine. Note: pos is the position in the size that the death value is store at
| virtual void vtkLSDynaReader::ReadCellProperties | ( | const int & | type, |
| const int & | numTuples | ||
| ) | [protected, virtual] |
Read all the cell properties of a given part type
| void vtkLSDynaReader::ResetPartsCache | ( | ) | [protected] |
Member Data Documentation
vtkLSDynaPartCollection* vtkLSDynaReader::Parts [protected] |
Definition at line 468 of file vtkLSDynaReader.h.
int vtkLSDynaReader::DeformedMesh [protected] |
Should deflected coordinates be used, or should the mesh remain undeflected? By default, this is true.
Definition at line 472 of file vtkLSDynaReader.h.
int vtkLSDynaReader::RemoveDeletedCells [protected] |
Should cells marked as deleted be removed from the mesh? By default, this is true.
Definition at line 477 of file vtkLSDynaReader.h.
int vtkLSDynaReader::DeletedCellsAsGhostArray [protected] |
Should cells marked as deleted be removed from the mesh? By default, this is true.
Definition at line 478 of file vtkLSDynaReader.h.
int vtkLSDynaReader::TimeStepRange[2] [protected] |
The range of time steps available within a database. Only valid after UpdateInformation() is called on the reader.
Definition at line 483 of file vtkLSDynaReader.h.
char* vtkLSDynaReader::InputDeck [protected] |
The name of a file containing part names and IDs.
Definition at line 486 of file vtkLSDynaReader.h.
LSDynaMetaData* vtkLSDynaReader::P [protected] |
Definition at line 569 of file vtkLSDynaReader.h.
The documentation for this class was generated from the following file:
- /Users/kitware/Dashboards/MyTests/VTK_BLD_Release_docs/Utilities/Doxygen/dox/IO/LSDyna/vtkLSDynaReader.h
