Comments (9)
That's not the only one. Also a table in 7.3 (Collective Cormack-Jolly-Seber Model) and one in 8.1 (Sparse Data Structures) missing. In all cases they use a Latex tabular (these are the only cases in the user's guide).
I've rewritten the table of 9.4 as a standard markdown table: the result in pdf is almost identical as the previous version (barring an extra horizontal line above the table and the lack of a vertical line after the first column). The html version is ok, perhaps it could be improved with a bit of css, but at least it's there now. If it's fine I could try to convert also the other ones (although one of them uses minipages, which I don't know if they would be rendered in html).
from docs.
@mcol: converting more of these would be great. I'm embarassed I missed so many of them. I'm not sure how you can work from @enbrown's branch, but these don't all need to be fixed in the same PR.
from docs.
I think that these will come in through the same PR. Here's the HTML I came up with for the sparse data structure table:
https://github.com/enbrown/stan-docs/blob/cd453fc8075445d7db3f5409aceb8448e0373240/src/stan-users-guide/sparse-ragged.Rmd#L33-L66
And here's the HTML for the latent-discrete Rmd file:
https://github.com/enbrown/stan-docs/blob/cd453fc8075445d7db3f5409aceb8448e0373240/src/stan-users-guide/latent-discrete.Rmd#L488-L510
Of course, this isn't the only way of doing it. So if someone has a better idea, that's fine with me.
from docs.
I didn't see that these were being fixed in the other PR. It's a matter of deciding whether there should be two specialized implementations of the same table (html and latex) or a plain one in markdown. My preference would be the unified approach for maintainability, but I can see that @enbrown's approach may look better.
from docs.
from docs.
The problem is that markdown syntax for tables is very limited. There is no markdown syntax to have cells span multiple columns or rows and none of the table borders/lines can be adjusted. So having column headers that span multiple columns (to group related columns) or doing something simple like having a border between the first and second columns (such as in the otherwise simple table in section 9.4) isn't possible. Even the many RMarkdown table-making packages seem to sometimes skip the markdown code and instead directly output HTML code to make a presentable table.
So I see three options (not mutually exclusive):
- Use limited markdown tables that don't look good in either HTML or PDF but are easier to make
- Use an R package that would generate each based on the output format (maybe xtable?)
- Create markup in both HTML and LaTeX for the tables
Any other ideas?
from docs.
If we go the package way, we could use knitr::kable
and the kableExtra package (https://cran.r-project.org/web/packages/kableExtra/vignettes/awesome_table_in_html.html).
from docs.
from docs.
I've pushed another approach in #61 which allows nice formatting for both html and pdf documents based on kable. This avoids duplication of the code while making the tables still readable also when unformatted. It requires a bit of knitr magic in order to put tables side by side, as html_document doesn't show at all Latex minipages, while pdf_document completely ignores the html table markup.
from docs.
Related Issues (20)
- add Survival models chapter to Stan User's Guide TOC
- Stan User's Guide Efficiency Tuning Section - beta_binomial? HOT 1
- add links to pdfs from docs homepage and overview pages
- add dark mode for website
- Problem searching the functions reference HOT 3
- Incorrect equation for wiener pdf
- [User Guide] Stan Translation efforts HOT 3
- Add more in-depth description of Pathfinder to the reference-manual HOT 1
- Functions Refernce: return type of `bernoulli_rng` - `R` or `ints`? HOT 1
- Functions Reference - Array reductions contain vector-only signatures HOT 2
- needs updating: Efficiency-tuning/standardizing-predictors-and-outputs HOT 6
- Update documentation for "Missing Data: Sliced missing" data to new array syntax HOT 1
- Incorrect equation in the truncated data section HOT 1
- replace "sampling statement" with "target augmentation statement" HOT 2
- document normal sufficient stats in User's Guide efficiency chapter HOT 1
- Document that non-data variables are not allowed in top level size declarations - consequences for `generated quantities` block HOT 6
- Document new overloads of `wiener_lpdf`
- question - mismatch between SUG chapters
- Add to Stan CSV format doc that the number of digits can be changed
- document minimal hardware, OS requirements
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
π Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. πππ
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google β€οΈ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from docs.