Closed GegznaV closed 3 years ago
Regarding chk.hy
also take a look at #130 and the cross-references there-in. I think all these concerns can be fixed at once.
Regarding decomposition
I authored #144 so I agree this should be renamed.
Somewhat related: decomposition
will create a hyperSpec
object containing loadings or scores. If loadings, then plotspc
should be used, but if scores, plotc
should be used. plotc
also has other uses. I have not looked at this in detail, but from a user-friendliness point of view, it would be nice if plotc
and plotspc
were merged, made generic and employed the formula interface like plotc
does to specify what should be plotted. Some careful checking of dimensions would be needed to intercept user errors like calling for a plot that does not make sense with the matrix dimensions.
This discussion moved and reopen as:
This issue complements https://github.com/cbeleites/hyperSpec/issues/208#issuecomment-684085699.
These functions may also be renamed. But extension or modification of functionality should also be introduced.
decomposition
as.hyperSpec(<matrix>)
,as_hyperSpec(<matrix>)
scores2hyperSpec()
loadings2hyperSpec()
as.hyperSpec()
,as_hyperSpec()
. See discussion in #144. Related #289chk.hy
is.hyperSpec()
,is_hyperSpec()
validObject()
as well.2. To keep current functionality (failure in case of non-
hyperSpec
object), argumentfail = TRUE
may be added. Default should befail = FALSE
to returnFALSE
.