Repository navigation
redundant paragraphs about automatic differentiation in documentation #110
Description
Activity
Elements.html describes what any element developer needs to know.
- understand the basic idea
- don't overspecialise function interface
- take care with type stability
With these techniques, if R is good, K, C, M, dR/dU, dR/dA will be good.
Adiff.html is for the developer of advanced elements (Beam), and introduces
- motion
- chainrule
With these advanced techniques, it's fully possible to evaluate the matrices wrong.
So there is a logic. Is it a good logic? Should it be announced more clearly?
Redundant content:
https://sintef.github.io/Muscade.jl/dev/Elements.html
https://sintef.github.io/Muscade.jl/dev/Adiff.html
Point to the (more complete) https://github.com/SINTEF/Muscade.jl/blob/dev/docs/src/Adiff.md when describing the implementation of new element