Bayesian Mixture Log-Normal Survival Model

Bayesian Survival models via the mixture of Log-Normal distribution extends the well-known survival models and accommodates different behaviour over time and considers higher censored survival times. The proposal combines mixture distributions Fruhwirth-Schnatter(2006) , and data augmentation techniques Tanner and Wong (1987) .

Log Binomial Regression Model in Exact Method

Fit the log binomial regression model (LBM) by Exact method. Limited parameter space of LBM causes trouble to find admissible estimates and fail to converge when MLE is close to or on the boundary of space. Exact method utilizes the property of boundary vectors to re-parametrize the model without losing any information, and fits the model on the standard fitting algorithm with no convergence issues.

Learning Sparse Log-Ratios for Compositional Data

In the context of high-throughput genetic data, CoDaCoRe identifies a set of sparse biomarkers that are predictive of a response variable of interest (Gordon-Rodriguez et al., 2021) . More generally, CoDaCoRe can be applied to any regression problem where the independent variable is Compositional (CoDa), to derive a set of scale-invariant log-ratios (ILR or SLR) that are maximally associated to a dependent variable.

Log-Multiplicative Models, Including Association Models

Functions to fit log-multiplicative models using 'gnm', with support for convenient printing, plots, and jackknife/bootstrap standard errors. For complex survey data, models can be fitted from design objects from the 'survey' package. Currently supported models include UNIDIFF (Erikson & Goldthorpe, 1992), a.k.a. log-multiplicative layer effect model (Xie, 1992) , and several association models: Goodman (1979) row-column association models of the RC(M) and RC(M)-L families with one or several dimensions; two skew-symmetric association models proposed by Yamaguchi (1990) and by van der Heijden & Mooijaart (1995) Functions allow computing the intrinsic association coefficient (see Bouchet-Valat (2022) ) and the Altham (1970) index , including via the Bayes shrinkage estimator proposed by Zhou (2015) ; and the RAS/IPF/Deming-Stephan algorithm.

Saturated Model Log-Likelihood for Multinomial Outcomes

When the response variable Y takes one of R > 1 values, the function 'glsm()' computes the maximum likelihood estimates (MLEs) of the parameters under four models: null, complete, saturated, and logistic. It also calculates the log-likelihood values for each model. This method assumes independent, non-identically distributed variables. For grouped data with a multinomial outcome, where observations are divided into J populations, the function 'glsm()' provides estimation for any number K of explanatory variables.

Compare Models with Cross-Validated Log-Likelihood

An implementation of the cross-validated difference in means (CVDM) test by Desmarais and Harden (2014) (see also Harden and Desmarais, 2011 ) and the cross-validated median fit (CVMF) test by Desmarais and Harden (2012) . These tests use leave-one-out cross-validated log-likelihoods to assist in selecting among model estimations. You can also utilize data from Golder (2010) and Joshi & Mason (2008) that are included to facilitate examples from real-world analysis.

Send Log Messages to Remote 'syslog' Server

Send 'syslog' protocol messages to a remote 'syslog' server specified by host name and TCP network port.

Produces Markdown Log File with a Built-in Function Call

Produces clean and neat Markdown log file and also provide an argument to include the function call inside the Markdown log.

Analyze Download Logs from the CRAN RStudio Mirror

Analyze download logs from the CRAN RStudio mirror (< http://cran.rstudio.com/>). This CRAN mirror is the default one used in RStudio. The available data is the result of parsed and anonymised raw log data from that CRAN mirror.

Dynamic Logging for R Inspired by Configuration Driven Development

A comprehensive and dynamic configuration driven logging package for R. While there are several excellent logging solutions already in the R ecosystem, I always feel constrained in some way by each of them. Every project is designed differently to solve it's domain specific problem, and ultimately the utility of a logging solution is its ability to adapt to this design. This is the raison d'être for 'dyn.log': to provide a modular design, template mechanics and a configuration-based integration model, so that the logger can integrate deeply into your design, even though it knows nothing about it.