On Tue, 2018-03-27 at 18:38 -0700, William Hack wrote:
> That sounds reasonable. One positive, it should allow for using
> different
> PCA algorithms depending on the data set size (maybe).
>
> Would an example how to use it still be possible to add?
Sure.
> May I ask what is the reason for "minimal API change[s]"? (Just
> curious.)
> Is it due to the maintenance tail for new changes... or is it to
> limit
> changes due to a release schedule... or keep the API as stable as
> possible?
I guess it should be s/change/addition/. To completely replicate the
PCA API for MCA would give us a new type and several new function that
just call the relevant PCA methods. We prefer to make things
composable, so since you can do for example
```
var pc stat.PC
ok := pc.PrincipalComponents(stat.TransformCDT(x), nil)
```
to get the behaviour you want, that feels nicer.
I'd like to get input from other about where this "stat.TransformCDT"
by some name would actually go though.