Also, a more qualitative comment on this.
I have no way of knowing what the numbers should be after fluid.pca~, so I have no way of verifying that process other than seeing the matching I’m getting. But when I go above a certain amount of dimensions in fluid.pca~ the matching drops to nearly 0%, even when feeding it the training data back in.
Using the same patch and process that I outline in the thread about speed, it “works” at something like 152d->8d (with shitty matching percent at 44%), but the moment I move up to 152d->20d (literally only changing that in the patch), the matching drops to 0%.
It seems that either I’m getting a load of dimensions back that are garbage above a certain point, to the point that it ruins the matching, or something is happening in the maths somewhere (hence the nans, funny numbers, and negative numbers after normalization).