Add example of enhanced and reduced connectivity

[agcapps]

Add an example of 2D and 3D multiblock grids with enhanced and reduced connectivity.

Example renderings by VisIt:

[agcapps]

Examples are copied from http://visitusers.org/index.php?title=Representing_ghost_data

[agcapps]

Still needs cleanup in the code. @cyrush , what do you think of the API style--- passing in arrays of doubles for x, y, z coordinates of corners?

[agcapps]

The 3D grid has several domains made invisible so you can see the middle. I would have made them semi-transparent but I don't know how to do that domain-by-domain.

[cyrush]

@agcapps Thanks for putting this together.

I want to void adding the std::vector based lerp functions to the public mesh blueprint interface. I am fine with them being private helpers to help implement the new example.

Also, I would prefer we don't change the base implementation of the explicit coords for braid. The prior implementation served as a simple C++ example that we could point folks at to help them learn how to create a coordset. But with the expanded version is much more complex, and leverages vectors of vectors -- folks might think all that is required to build a coordset.

Instead of unstructured topo, we want structured -- b/c that's the important case for reduced and enhanced (which also can included flipped logical indices across domains). That will be an important aspect of the example with respect to adjsets.
Changing to structured should be easy, you can replace the unstructured topo + connectivity with the structured topo def.

We should wire this up to the general examples driver. For that we will need a set of default params for the spec (opts).

See a few other suggestions (name changes, etc) in line, let me know if you have questions.

[agcapps]

@agcapps Thanks for putting this together.

I want to void adding the std::vector based lerp functions to the public mesh blueprint interface. I am fine with them being private helpers to help implement the new example.

OK, makes sense.

Also, I would prefer we don't change the base implementation of the explicit coords for braid. The prior implementation served as a simple C++ example that we could point folks at to help them learn how to create a coordset. But with the expanded version is much more complex, and leverages vectors of vectors -- folks might think all that is required to build a coordset.

Got it. I'll come up with an alternative.

Instead of unstructured topo, we want structured

Will change unstructured -> structured.

We should wire this up to the general examples driver. For that we will need a set of default params for the spec (opts). See a few other suggestions (name changes, etc) in line, let me know if you have questions.

Thanks, I'll set that up.

• structured topo
• change function names
• default for spec
• put back default coords implementation for braid
• explore using numeric leaf arrays instead of std::vector<double>
• lerp() moved into detail namespace with numeric leaf arrays replacing std::vector<double>

[agcapps]

@cyrush , I'd appreciate your further review. I think I got all the points you mentioned.