| 7023aa44 | 20-Nov-2013 |
Vijay Mahadevan <vijay.m@gmail.com> |
Updates to the 2-D example and additional options for reading mesh from file.
51ee65e: Adding new public interface functions to simplify user assembly code. Added methods to get connectivity of an e
Updates to the 2-D example and additional options for reading mesh from file.
51ee65e: Adding new public interface functions to simplify user assembly code. Added methods to get connectivity of an element, coordinates of vertices, and to check if given vertices lie on the boundary. 866cea9: Updating some RW options for MOAB and enabling command-line control. fd2859a: Remove the DA related routines and references in 2-D example.
show more ...
|
| ffb678cd | 20-Nov-2013 |
Vijay Mahadevan <vijay.m@gmail.com> |
Add the 2-D FEM example poisson solver in SS.
2d7ab24: Adding the first draft of MOAB based 2-D FEM computation using both DMDA and DMMoab 2b0793a: Updating some RW options for MOAB and enabling com
Add the 2-D FEM example poisson solver in SS.
2d7ab24: Adding the first draft of MOAB based 2-D FEM computation using both DMDA and DMMoab 2b0793a: Updating some RW options for MOAB and enabling command-line control of how the mesh gets loaded from file../../dmmbutil.cxx
show more ...
|
| 0df6e276 | 31-Jul-2013 |
Vijay Mahadevan <vijay.m@gmail.com> |
A first draft version of getting hte connectivity right. It still overpredicts in the current method based on edge adjacencies. Need to refine to do a second pass over local mesh to remove duplicates
A first draft version of getting hte connectivity right. It still overpredicts in the current method based on edge adjacencies. Need to refine to do a second pass over local mesh to remove duplicates in order to get the NNZ accurately.
show more ...
|
| 1cec0304 | 31-Jul-2013 |
Vijay Mahadevan <vijay.m@gmail.com> |
Several interface level changes to DMMoab implementation.
1) Compute the skin and store entities in DMMoab 2) Use PetscSection to propagate the DOF indices for various fields transparently through D
Several interface level changes to DMMoab implementation.
1) Compute the skin and store entities in DMMoab 2) Use PetscSection to propagate the DOF indices for various fields transparently through DM interface 3) Use filesets to perform local computations instead of always on the root set 4) Changing interface implementation of DMMoabGetLocalElements, DMMoabGetLocalVertices, DMMoabSetLocalElements 5) Adding interface implementation for DMMoabSetFields, DMMoabGetFieldDofs, DMMoabOutput, DMMoabSetFieldVector, DMMoabGetBoundaryEntities 6) Need to add better documentation for public interface functions
show more ...
|
| 9088682f | 20-Nov-2013 |
Vijay Mahadevan <vijay.m@gmail.com> |
Private interface changes in DMMoab.
d64c012: Adding storage for holding the boundary vertices and faces for easier traversal during FEM assembly calculations. Could move it somewhere else if need b
Private interface changes in DMMoab.
d64c012: Adding storage for holding the boundary vertices and faces for easier traversal during FEM assembly calculations. Could move it somewhere else if need be. d7dd518: Adding more public interface methods to Output the mesh+solution fields, to set a Vec for a field handled by DMMoab and accessors for getting the boundary entities. bdfc3ff: Fix a bug in checking whether a tag is valid.
show more ...
|
| 5eb88e9d | 20-Nov-2013 |
Vijay Mahadevan <vijay.m@gmail.com> |
Squashing multiple commits related to simplification of public interfaces and internal bug-fixes.
1b14864: Adding new public interface functions for DMMoab. Fixed a compiler error in MBERRVM. Interf
Squashing multiple commits related to simplification of public interfaces and internal bug-fixes.
1b14864: Adding new public interface functions for DMMoab. Fixed a compiler error in MBERRVM. Interface now supports the ability to create DM from a box-mesh in memory or load from file. Also, preliminary field manipulation interfaces in place. 994bad9: Adding variables to store Field data to make DMMoab little more whole. d0a4170: Use a fileset to categorize DM entities. Useful when mutiple DMs are intiialized. 08af2fa: Renaming Set/Get Range routines to be more descriptive: Get/Set vertices. Also adding a getter for local elements.
show more ...
|
| efd17f3e | 18-Jun-2013 |
Vijay Mahadevan <vijay.m@gmail.com> |
Add MOAB specific Vector array get/restore methods for both write and read-only operations to ease the use of MoabVec in FEM based computations. The arrays typically have a ghosted representation if
Add MOAB specific Vector array get/restore methods for both write and read-only operations to ease the use of MoabVec in FEM based computations. The arrays typically have a ghosted representation if the MOAB mesh is ghosted itself, else represents a truly distributed array.
show more ...
|
| 20b94d24 | 20-Nov-2013 |
Vijay Mahadevan <vijay.m@gmail.com> |
Modifying Brusselator solver with various options to assemble the operators via Block routines, local/ghost forms etc that give various performance options. Needs further profiling, removal of commen
Modifying Brusselator solver with various options to assemble the operators via Block routines, local/ghost forms etc that give various performance options. Needs further profiling, removal of comments, and more documentation.
show more ...
|
| 032b8ab6 | 20-Nov-2013 |
Vijay Mahadevan <vijay.m@gmail.com> |
Several essential feature additions and internal modifications for DMMoab.
1) Petscify the DMMoab implementation and separate out the Mat and Vec handling parts to separate files. 2) Private data st
Several essential feature additions and internal modifications for DMMoab.
1) Petscify the DMMoab implementation and separate out the Mat and Vec handling parts to separate files. 2) Private data structure definitions moved to petsc-private. 3) Other feature additions include clean ways to perform local-global and global-local scatters. 4) Now there is a separate SetUp routine that handles consistency checks and initialization all necessary data for DMMoab. 5) The Matrix creation from DMMoab can handle AIJ and BAIJ type matrix creations based on how the user defined a tag. This assumes that the primary solution is defined as a single tag in MOAB and hence block size is set in DMMoab globally. This should change in order to allow more flexibility to create block matrices for single solution fields or combinations of them. Similar changes for Vec can be provided based on tag structure. Perhaps taking in a MoabVec input can resolve this to maintain consistency.
show more ...
|