History log of /petsc/src/dm/dt/tests/ex8.c (Results 26 – 32 of 32)
Revision Date Author Comments
# 98921bda 28-Jan-2022 Jacob Faibussowitsch <jacob.fai@gmail.com>

SETERRQ[1-9]+ begone


# 940e4fdf 12-Jan-2022 Satish Balay <balay@mcs.anl.gov>

Merge branch 'jacobf/2021-12-09/attribute-format-mat' into 'main'

Feature: Attribute Format - Mat

See merge request petsc/petsc!4634


# 546078ac 10-Dec-2021 Jacob Faibussowitsch <jacob.fai@gmail.com>

remove trailing newline from SETERRQ


# 2c7de515 06-Apr-2020 Satish Balay <balay@mcs.anl.gov>

Merge branch 'tisaac/feature-dubiner-basis' into 'master'

PetscDT: PKD (Dubiner) basis

See merge request petsc/petsc!2691


# fbdc3dfe 01-Apr-2020 Toby Isaac <tisaac@cc.gatech.edu>

Add PetscDTPDKEvalJet(), PetscDTJacobiEvalJet(), PetscDTIndexToGradedOrder(), and PetscDTGradedOrderToIndex()

The Proriol-Koordwinder-Dubiner basis (PKD) is orthonormal on the
reference simplex, so

Add PetscDTPDKEvalJet(), PetscDTJacobiEvalJet(), PetscDTIndexToGradedOrder(), and PetscDTGradedOrderToIndex()

The Proriol-Koordwinder-Dubiner basis (PKD) is orthonormal on the
reference simplex, so we should make it available as a stable basis of
evaluation.

The recursive definition allows for a straightforward and stable
calculation of all derivatives, not just first and second.

`src/dm/dt/tests/ex9.c` tests that the basis is orthonormal
and compares the derivatives against the derivatives computed by
tensor-product Legendre polynomials.

I thought about how to make an interface that would handle that,
and I decided returning the jet in the same kind of graded
representation that makes sense for multivariate polynomial spaces was a
good choice.

To facilitate this, I also added indexing functions for figuring out
where a tuple (either of exponents in a monomial or orders in a partial
derivatives) is in this ordering.

Along the way I made PetscDTStroudConicalQuadrature() handle arbitrary
dimensions instead of just 1--3.

We have a variety of dimensional orderings in PetscDT, related to how we
order points of evaluation, components of the jet, and basis functions.

I thought that:
- downstream users concerned with performance might prefer points of
evaluation as the fastest varying index to facilitate vectorization
of numerical integration, and
- having basis functions as one of the outer dimensions (first or last)
would simplify computing the matrix-matrix product of
a [basis function x evaluation point] matrix with a Vandermonde
inverse matrix

So I ordered the output dimensions of PetscDTPKDEvalJet() as
[basis function, jet component (derivative), evaluation point]. I am
seeking comment as to whether this is good, and whether it might be a
good convention to adopt elsewhere in PetscDT.

undo extern

Fix complex type issue in dm/dt/tests/ex9.c

squashme: fix scaling in PetscDTStroudConicalQuadrature()

squashme: loosen tolerance for single precision

squashme: cast to double before printing

squashme: remove unused static functions

show more ...


# 8bb017ff 30-Mar-2020 Satish Balay <balay@mcs.anl.gov>

Merge branch 'tisaac/feature-dual-space-rework' into 'master'

Rework PetscDualSpace

See merge request petsc/petsc!2399


# d4afb720 26-Mar-2020 Toby Isaac <tisaac@cc.gatech.edu>

Add PetscDTIndexToBary, PetscDTBaryToIndex, and PetscDTNodeType

Move tests that missed the example excision

Add enum lists for PetscDTNodeTypes


12