Nothing
editor_options: markdown: wrap: 72
gh1
(GSED-HH, JAN 2023) to builtin_itemtable
and builtin_itembank
as part of key gsed2212
sample_sf
, sample_lf
and sample_hf
gl1
instruments as: aa --> gm, bb --> lg, cc --> fmgl1aad001
--> gl1gmd001
, and so onselect()
and pivot_longer()
to conform to tidyselect 1.2.0
grammargsed2206
and gsed2208
, as well as analyses that rely on correct LF item labels. Version 1.7.0 corrects these problems.LF1
, corrected using RedCAP comparisons from
Phase_1_master_data_dictionary_V1.0_29_11_2022.xlsx
;LF2
, from
GSED LF Item Guide_October22_FINAL_clean_27Nov22.docx
and
manually matched to LF1
.gsed2212
gs1
(GSED SF V1.0) and gl1
(GSED LF V1.0)gto
labels with correct ordergsed2212
. This key repairs problems in gsed2206
and gsed2208
. get_labels()
now returns the labels in the same order as items
gsed2212
with 18 ECDI items using Phase 1 validation databuiltin_itemtable
and builtin_itembank
with correct LF
item orderdscore::count_mu_phase1(t)
when t
is a
vector containing NA
sgsample
with 10 cases with SF and LF scoresorder
argument to get_itemnames()
sort_itemnames()
exampledscore.cpp
sirt
packagegsed2208
and 293_0
) using the Phase 1
validation data for the GSED SF and GSED LF.293_0
as the GSED core model and extended it to include
the 818 items that fitted the previous model ("gsed2206").phase1
), based on LF and SF data from
cohorts GSED-BGD, GSED-PAK and GSED-TZA studies.gsed2208
and default population
to "phase1".**. If you want the old behavior, specify
key =
"gsed1912"or
key =
"gsed2206"to functions that accept the
keyargument (
dscore(),
dscore_posterior(),
get_age_equivalent(),
get_tau()`).get_age_equivalent()
and get_tau()
consistent
with dscore()
phase1
reference to get_reference()
zad()
and daz()
count_mean_phase1()
for setting prior mean equal to the GSED
Phase 1 referencecount_mean_phase1()
dscore()
prior_mean functionality to deal with the
to-be-implemented new reference as "phase1"count_mean_phase1()
functiongsed2206
and 294_0
population
when key is 294_0
.294_0
to the builtin_itembank
.relevance
argument to dscore()
and dscore_posterior()
to restrict calculation of D-scores to those items that have their
tau
within this relevance interval around the dynamic EAP
estimate.builtin_itembank
that inherits old (gsed1912) tau's
into new key (gsed2206) for instruments gto
and gpa
. As a
consequence, D-score were incorrectly calculated when gto
and
gpa
item names were used.get_age_equivalent()
that resulted in age
interval estimates that were too narrow on the D-score scale.gsed2206
, lf2206
and sf2206
) that
incorporate Phase 1 validation data for the GSED SF, GSED LF and
BSID.gsed2206
. If you want the old
behavior, specify key = "gsed1912"
to functions that accept the
key
argument (dscore()
, dscore_posterior()
,
get_age_equivalent()
, get_tau()
).builtin_itemtable
with names and labels for gpa
(SF),
gto
(LF) and gsd
(novel SF) items.metric = "logit"
and transform
parameters specified.
The D-scores calculated under different transforms are now linear
transformations of each other.D-score/dscore
for
increased visibilitydata-raw/data/bds)edited.csv
ddata
package to
builtin_itemtable
itemtable_20200424.txt
with minimal item definitionsddata
packagebuiltin_itemtable
get_itemtable()
function gets a new argument decompose
for
adding info from decomposed item namesget_itemtable()
when itemtable
argument is
specifieddrop = TRUE
to account for new behavior in
tibble 3.0.0
get_itemtable()
.dscore
and clopus
packages. The dscore
package now first
rounds the D-score and then calculate DAZ.dscore()
function now automatically select the
prior_mean = ".dutch"
option when the user specifies
key == "dutch"
. This change repair an error in the D-score
calculation that occurs when only key == "dutch"
was given.dscore()
function now silently handles warnings that may
result from taking the log of negative ages.dscore 1.0.0
! For the development history, see
https://github.com/D-score/dscoreNEWS.md
file to track changes to the package.Any scripts or data that you put into this service are public.
Add the following code to your website.
For more information on customizing the embed code, read Embedding Snippets.