Our efforts to move the analysis from column-based to row-based is incomplete. Consequently, the code is in an inconsistent state, resulting in random crashes depending on whether P > T or T > P. For now, we are assuming the data are row-based; therefore, the matrix S should be P x T, and the corresponding u and v vectors should be the correct size and multiply with S on the correct side.
As per #52, we'll be refactoring this a bit to allow either row or columnar data, but this issue is critical in that it can cause the program to crash.
Our efforts to move the analysis from column-based to row-based is incomplete. Consequently, the code is in an inconsistent state, resulting in random crashes depending on whether
P > T
orT > P
. For now, we are assuming the data are row-based; therefore, the matrixS
should beP x T
, and the correspondingu
andv
vectors should be the correct size and multiply withS
on the correct side.As per #52, we'll be refactoring this a bit to allow either row or columnar data, but this issue is critical in that it can cause the program to crash.