Move xtable and network to Imports? #22
Unanswered
TomSnijders
asked this question in
General
Replies: 1 comment 1 reply
-
|
On the tables, I wonder whether it might be an idea to offer siena model support to other popular tabulating packages, such as stargazer? |
Beta Was this translation helpful? Give feedback.
1 reply
-
|
Might be a good idea. What are the requirements for stargazer to use a results object? The basic stuff now is in the components ans$theta, ans$se, ans$fixed, ans$requestedEffects$effectName. What kind of additional structure would be required for stargazer? |
Beta Was this translation helpful? Give feedback.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Package xtable is used for functions effectsDocumentation and (of course) xtable.sienaFit.
Package network is used for sienaGOF. Perhaps also for sienaDataCreate; but I'm not sure. Does anybody know?
But these packages are now both mentioned only as "Suggests". Wouldn't it be better to have them under "Imports"?
(If network is used in sienaDataCreate, then of course this should be the case.)
Beta Was this translation helpful? Give feedback.
All reactions