Jed Brown
Jed Brown
This has a couple conflicts with main and thus needs a rebase or merge. CI will run once that is done.
Pipeline is running now.
Looks like CPU tests fail due to large pointwise errors. https://gitlab.com/libceed/libCEED/-/pipelines/632636153/test_report
Yeah, CI tries to run those cases. Can we fix them so it passes a reasonable test? (I realize there is other good stuff in the branch, but that is...
One design decision here is how strongly typed to make these interfaces. If you do something like the following, you can eliminate a class of mistakes by compile-time errors. The...
I think qfunction variation is the hardest part. Do we need to support different arguments to the qfunction having different precisions or can they be homogeneous (all arguments in matching...
`CeedBasis` has several interfaces that take `CeedScalar *`, and I think there's no harm in making those all `double` (perhaps with complex variants at some point). It can be converted...
1. The list included internal representations (E-vectors), and I intended it to identify each place where precision can be varied in `G^T B^T D B G`. I think it's a...
I figured `CeedVectorGetArray()` and the like would be able to mirror data to any requested precision, but `CeedElemRestrictionApply` would inspect the available precisions of the input vector and the preferred...
Do you think it'll be hard to handle consistently if CeedElemRestriction is precision-agnostic (uses its arguments rather than set as state)? My concern is that when we wire up several...