You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In chapter 7.5.2 of Procrustes Problems by J. C. Gower and G. G. Dijksterhuis an algorithm for 2-sided orthogonal Procrustes is presented. This generalizes the current treatment, which requires that the matrices being matched be symmetric and square. This is also explained in section 3.3 of Pythagoras Papadimitriou's Ph.D. thesis at the Univ. of Manchester. papad93.pdf
Right now, the object is to find an orthogonal matrices, Q1 and Q2, such that || Q1 A Q2 - B || is minimized, where A and B are symmetric square matrices and have the same shape (i.e., both are mxm matrices). However, this reference shows that this can work even as long as A and B have the same shape; they need not be square or symmetric.
This could be an embellishment on the existing method (it contains the old method as a special case) or it could be implemented as a separate method. I'd tend to do the latter, and leave the easy case as a routine that can be used where applicable.
The text was updated successfully, but these errors were encountered:
In chapter 7.5.2 of Procrustes Problems by J. C. Gower and G. G. Dijksterhuis an algorithm for 2-sided orthogonal Procrustes is presented. This generalizes the current treatment, which requires that the matrices being matched be symmetric and square. This is also explained in section 3.3 of Pythagoras Papadimitriou's Ph.D. thesis at the Univ. of Manchester.
papad93.pdf
Right now, the object is to find an orthogonal matrices, Q1 and Q2, such that || Q1 A Q2 - B || is minimized, where A and B are symmetric square matrices and have the same shape (i.e., both are mxm matrices). However, this reference shows that this can work even as long as A and B have the same shape; they need not be square or symmetric.
This could be an embellishment on the existing method (it contains the old method as a special case) or it could be implemented as a separate method. I'd tend to do the latter, and leave the easy case as a routine that can be used where applicable.
The text was updated successfully, but these errors were encountered: