Open stueller opened 1 year ago
makeData
override with $makeData(y0atyMean=F)
fitDist
issue is fixed changing is01 <- min(dv, na.rm=TRUE) >= 0 & max(dv, na.rm=TRUE) <= 1
to is01 <- min(dv, na.rm=TRUE) >= 0 & max(dv, na.rm=TRUE) <= 1 & !isBin
cutY
inutils.r
is a wrapper for thecut
function that cleans the output into a numeric variable.polyICT
there is an error for cutting y into more than five categories because 5 is the maximum supported by multinomial regression.rNBI
orrnbinom
cutY
codeas.numeric(factor(u, labels = 1:length(yCut))) - 1
, the categorization is correct but the values are non-integer (the code looks correct, check for downstream bugs).polyICT
object can generate categorical data (up to 5 categories for now) using$makeData()
, but$designCheck()
has an error whenyCut
is notNULL
.PersonAlytic
fails with the error "x must be between 0 and 1", something must be going wrong in the call to thegamlss
functionfitDist
inPalytic.r
, most likely the optionreal0to1
is being included when it should not be. This would happen when the parameteris01
on line 1447 in thePersonAlytics
Palytic$set()
definition in thePalytic.r
file. SetautoSelect = list()
inPersonAlytic()
as a temporary workaround.ICTpower()
generates data with apolyICT
object whereyCut!=NULL
butyCut
is ignored. Passing afamily
parameter throws the errorformal argument "family" matched by multiple actual arguments
.