Closed tpyork closed 7 years ago
I modified this design slightly to make the results more explicitly mirror the user's input:
Input | Sections in produced report |
---|---|
mxReport(AdeFit) |
Section 1 (AdeFit ), Section 2 (AdeFit ) |
mxReport(list(AdeFit, AeFit) |
Section 1 (AdeFit ), Section 2 (AdeFit ), Section 2 (AeFit ) |
mxReport(AdeFit, c(AdeFit, AeFit)) |
Section 1 (AdeFit ), Section 2 (AdeFit ), Section 3 (AdeFit vs AeFit ) |
mxReport(AdeFit, AeFit, c(AdeFit, AeFit)) |
Section 1 (AdeFit ), Section 2 (AdeFit ), Section 2 (AeFit ), Section 3 (AdeFit vs AeFit ) |
So the rules are:
MxModel
produce an Observed Data Summary Section and an Expected Data Summary SectionMxModel
, produce an Expected Data Summary SectionMxModel
s, produce a Model Comparison SectionDoes that make sense?
This looks a lot nicer ! Not sure where you're at but there are a few things I did not see:
ADE
or AE
(Section 2)Fixed in 7f1f076b.
cool that the timestamp is based on when the model was fit. i'm wondering if we should add a timestamp for when the report was generated
possible to sharpen up the Free Parameters and Goodness of Fit Statistics tables ? Using
kable()
for this ?need to reorder output i think to make more general. 3 main sections. add link to each.
OBSERVED DATA SUMMARIES; this reported only once.
SUMMARIES FOR EACH MODEL FIT; each should have its own link.
SUMMARY FOR
mxCompare()
; this should be a single table