History log of /petsc/src/dm/impls/moab/dmmbvec.cxx (Results 151 – 159 of 159)
Revision Date Author Comments
# a4920a59 24-Aug-2013 Vijay Mahadevan <vijay.m@gmail.com>

Some bug fixes for the ghosted exchange of tag data during Get/Restore Array for DMMoabVec


# 5dc0bdae 20-Nov-2013 Vijay Mahadevan <vijay.m@gmail.com>

Adding an extra API functionality to use the local DOF to assemble vectors and matrices.

- This should generally be faster than using VecSetValues. Use DMMoabGetLocalFieldDofs for these operations.

Adding an extra API functionality to use the local DOF to assemble vectors and matrices.

- This should generally be faster than using VecSetValues. Use DMMoabGetLocalFieldDofs for these operations.
- Should work with MatSetValuesLocal, VecSetValuesLocal also (untested).

show more ...


# b251b9b3 13-Aug-2013 Vijay Mahadevan <vijay.m@gmail.com>

Fixed a possible bug when restoring array.


# d5cc4873 20-Nov-2013 Vijay Mahadevan <vijay.m@gmail.com>

Fix the NNZ computation by removing the old methods and implemented a more rigorous traversal to find nnz and onz. Other minor cleanups in DMMoab - remove prints, debug statements etc.


# 874a40fe 20-Nov-2013 Vijay Mahadevan <vijay.m@gmail.com>

Bug fixes for deciphering leading dimension/DMCreateLocalVector_Moab and data output feature additions.

9cb894f: Adding some options for writing MOAB output files.
1e30170: Fixed a bug with leading

Bug fixes for deciphering leading dimension/DMCreateLocalVector_Moab and data output feature additions.

9cb894f: Adding some options for writing MOAB output files.
1e30170: Fixed a bug with leading dimension specification. MOAB->set_dimension should not be used. Miscellaneous fixes for DOF of fields: making global DOF index list as part of DM private data.
70830f3: Remove redundant use of gsindices and reuse global DOF list from DM. Fixed a bug in DMCreateLocalVector_Moab.

show more ...


# d20bd513 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 ...


# 54f3a419 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 ...


# 6668135e 20-Nov-2013 Vijay Mahadevan <vijay.m@gmail.com>

Add important ltog and gtol routines apart from documentation and cleanup of code.


# 1b083bf1 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 ...


1234567