The hardware and bandwidth for this mirror is donated by METANET, the Webhosting and Full Service-Cloud Provider.
If you wish to report a bug, or if you are interested in having us mirror your free-software or open-source project, please feel free to contact us at mirror[@]metanet.ch.
survival package to bring in the
strata and cluster functions (#141)..lm.fit() within slm.fit.csr.fixed
given breaking changes in SparseM::chol() (#134)xtable.xbal() to match the
generic. (#131)balanceplot() plots when using
absolute=TRUE. (#129)bibentry() in citation to address
deprecation.broom::glance() and
broom::tidy() methods for balance test objects, a work in
progress (#90).This was an internal release not placed on CRAN.
This is a maintenance release.
This is a maintenance release.
This is a maintenance release.
This is a maintenance release.
data.table related global options (#69)This version was submitted to CRAN prematurely and ultimately was not released.
xBalance(), you can now specify strata “foo” and
“bar” by including “+ strata(foo) + strata(bar)” in the
fmla argument, without need to give a separate
strata argument (eg
strata=list(foo=~foo, bar=~bar)).balanceplot() function to handle plotting
matrices, not just xbal objects.xbal objects.post.alignment.transform argument to
xBalance() allows modifying the data after per-stratum
centering.subset method for xbal objects.report="all" provides all relevant statisticsargs(xBalance) is now useful as a reminder of
report= options.impfn=mean.default.strata=NULL to xBalance() is
depracated, as it can be easy to do inadvertently, with a misspelling of
a non-null intended argument. For no stratification, use
list(unstrat=NULL), as is now the default.display, align, etc arguments to
xtable.xbal() have been enabled.xBalance(), when specifying a stratification using a
formula with several variables, as in ~x+y, the
stratification you get is now interaction(x,y) rather than just y.These binaries (installable software) and packages are in development.
They may not be fully stable and should be used with caution. We make no claims about them.