-
Notifications
You must be signed in to change notification settings - Fork 17
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Design decision on the output tables #145
Comments
One thing I would suggest as a default is to include the standard errors or CIs in the table. I would also expand the table title to say what the numbers are, e.g., Parameter estimates from a two-factor model. A: additive genetic; C: common environment; E: unique environment. |
hI @lf-araujo Markdown output in So... yes: definitely scope for improvements now with kable extras and rmarkdown/pandoc etc. to build on. I see pandoc supports the PS: Have a play with |
I modified umxSummary for umxCP umxACE and umxRAM. Captions work in the online pandoc converter to generate latex code with table captions. If you have example output from RAM model (nb: GitHub markdown doesn't grok the captions) require(umx)
data(demoOneFactor)
manifests = names(demoOneFactor)
m2 = umxRAM("One Factor", data = demoOneFactor, type = "cov",
umxPath("G", to = manifests),
umxPath(var = manifests),
umxPath(var = "G", fixedAt = 1)
)
umxSummary(m2, digits=3)
?umxSummary std=T|F', digits, report= 'html', filter= 'NS' & more
Model Fit: χ²(5) = 7.39, p = 0.193; CFI = 0.999; TLI = 0.999; RMSEA = 0.031 |
* IMPROVED: `umxSummary` tables have pandoc captions (see #145)
Now using the caption = facility of Table: Standardized parameter estimates from a 1-factor Cholesky ACE model. A: additive genetic; C: common environment; E: unique environment.
Table: Means and (raw) betas from model$top$intercept and model$top$meansBetas
|
|
I think is mostly up-to-spec now. re-open if there are more opportunities to improve |
Dear Tim,
Perhaps is too late on the design of this package. It is great that it displays results in markdown directly, however I think that by adding
## Titles
you are missing an opportunity (or I completely misunderstand how to use rmarkdown, either of the two).So if I allow a chunk to print out the resulting output as is, with
results = "asis"
the symbol##
may include the text in the wrong section level, if for example it is supposed to be printed in part of the text that already is in the second level and the table is meant to be within the section, not in a separate section.Have you ever considered adding a legend line instead of a section marker, like in the pandoc documentation.
The default looks like this (also note the lack of spacing btw the table and the following section):
My suggestion is that perhaps it would play nicer with rmarkdown chunks if they were:
Here is how code like the above is presented in LaTEX, these are supported in other pandoc writers too:
The text was updated successfully, but these errors were encountered: