Jörg F. Unger

Is there an update on this, we are also interested in visualizing nested sampling results from dynesty with arviz.

Another comment - style back to the roots :) This logger was used in the case where FE² type multiscale models are used, i.e. there was a separate structure for...

I agree that the renaming of Hessian0,1,2 into stiffness, damping and mass would make the code better to understand, though this would somehow limit the generality. In the Newmark branch,...

I personally see no downsides, but many simplifications. However, I would keep the DofVector (at least now) to store the current state (that might include dof_types currently not solved for)....

I think we should enforce a consistent numbering of the elements, thus enforcing detJac>0 for the gmsh import as well as for the element creation. If we don't enforce this,...

I also prefer to completely remove constraints as much as possible from all classes such as time integration schemes or the build gradient/hessian stuff. Currently, I feel that we have...

@potto1 and I have discussed, where and how the constraint application should be modified. Mygeneral idea is to have a class LinearConstraintApplicator (naming is not fixed yet) that does all...

Any reasons why we do not just check all det(J)>0?

I also support the idea, some remarks from my side. Why do you say "They should all be orthogonal to the assembler?". IMO, similar to #194, the assembler would just...

The new version looks much simpler than the original boost version. I very much like the idea, since it would generalize to any dimension. The only remaining ingredient to make...