estimatr::lm_robust() for
clustering and standard errors.reshape_projoint() overhaul: now robust to arbitrary
base-task orders, infers the repeated base task from the first base
outcome, and requires the repeated outcome to be the last element of
.outcomes.bibentry(), avoid
install-time lookups).Author: alongside
Authors@R..irr is
user-specified..irr is
fixed.Author: exactly with CRAN’s
derived Authors@R format (names and ORCID link formatting)
to remove NOTE.Author and
Authors@R fields, as requested by CRAN.pj_estimate() to automatically set the
appropriate standard-error option (se_type) depending on
clustering and estimation method.\value{} sections
describing return values.DESCRIPTION to highlight both
profile-level and choice-level estimators, IRR correction, and
visualization.reshape_projoint() docs
(\textrightarrow macro removed).summary(),
plot(), and print() methods to match CRAN
policies.This release addresses all issues raised in the CRAN review and includes several small improvements and documentation updates.
authors (year) <https://...>.projoint_data()) with
runnable toy examples.projoint_tau(),
plot_projoint_profile_level()) using
@noRd.plot.projoint_results.Rd.R CMD check --as-cran runs cleanly with 0 errors, 0
warnings, and 2 expected NOTES (package size and timestamps).reshape_projoint()'' to handle repeated-task reshaping more robustly when tasks/outcomes are not in a simple 1..T order. The function now standardizes the mapping between the last outcome (the repeated measure) and the inferred base task, reducing misalignment in thetask’’
variable for some inputs.reshape_projoint()'' into a dedicated source file (R/reshape_projoint.R’’)
with no changes to the exported function name or arguments.organize_data() where profile-varying
columns (e.g., selected_repeated) were incorrectly included
in pivot_wider(id_cols), which could drop respondent-level
covariates (e.g., weights) and cause .weights_2 to fail in
choice_level estimation..weights_1 and
.weights_2.
Need a high-speed mirror for your open-source project?
Contact our mirror admin team at info@clientvps.com.
This archive is provided as a free public service to the community.
Proudly supported by infrastructure from VPSPulse , RxServers , BuyNumber , UnitVPS , OffshoreName and secure payment technology by ArionPay.