Skip to content

Increase size of MapperContainer mappers_.

Samuel Burbulla requested to merge bugfix/twist-provider-mappercontainer into master

In a script where I combined several Galerkin schemes on different spaces on different grids I ran into the issue that the assertion

assert( quad.id() < MapperContainer::instance().size() );

in twistprovider.cc:50 fails as quad.id() == 111 and MapperContainer::instance().size() == 100.

Increasing the initialisation size of the MapperContainer fixes the issue. I choose 200 to not increase too much.

Is it expected that the MapperContainer might be too small? Or, do have to have a look where the unexpected high quadrature id came from?

Actually, is there a reasonable bound? Do we have to check dynamically?

Merge request reports