Fix "Available Models" table in user docs (!211) · Merge Requests · dorie / dorie

Fix "Available Models" table in user docs

What does this MR do?

Fix the malformed table in the "Available Models" user docs. This reverts commit 358ed887.

@sospinar: Notice that the information you added in 358ed887 is incorrect: There are targets defined with transport.numerics.FEorder greater than richards.numerics.FEorder, but they are not compiled and hence not available by default. Only the targets with the same order for both models are added to the default target, see DorieCompileInstance.cmake#L114.

Is there something that needs to be double checked?

Table is not malformed and appears in docs output

Can this MR be accepted?

Added/Updated documentation
Pipeline passing
Squash option set
Delete branch option set
~~[ ] Added entry to CHANGELOG.md~~

Assignee: If the Squash option is set, check/update the commit message right before merging!

Related issues

!209 (merged)

### What does this MR do?
Fix the malformed table in the "Available Models" user docs. This reverts commit 358ed88723a76fe86b94135f106e0b7aba1e70a5.

@sospinar: Notice that the information you added in 358ed88723a76fe86b94135f106e0b7aba1e70a5 is incorrect: There are *targets* defined with `transport.numerics.FEorder` greater than `richards.numerics.FEorder`, but they are not compiled and hence not available by default. Only the targets with the same order for both models are added to the default target, see [`DorieCompileInstance.cmake#L114`](https://ts-gitlab.iup.uni-heidelberg.de/dorie/dorie/-/blob/master/cmake/modules/DorieCompileInstance.cmake#L114).

### Is there something that needs to be double checked?
- [x] Table is not malformed and appears in docs output

### Can this MR be accepted?
- [x] Added/Updated documentation
- [ ] Pipeline passing 
- [x] Squash option set 
- [x] Delete branch option set 
- ~~[ ] Added entry to `CHANGELOG.md`~~

_**Assignee:** If the Squash option is set, check/update the commit message right before merging!_

### Related issues

!209

<!--
PLEASE READ THIS!

A Merge Request should be associated to a certain task or issue.
Its changes are supposed to be merged into the master branch.

Briefly explain __how__ you achieved the proposal of the task.

IMPORTANT: Make sure to set the merge request WIP if you are not finished yet.
-->

Edited Aug 24, 2020 by Lukas Riedel