2008/11/12 Keren Lasker kerenl@salilab.org: > Javi - I think that there is some confusion here. > The Matrix3D is a rotation matrix, maybe we should rename the class to > RotationMatrix3D for clarity.
Yesssss!
> It has nothing to do with grids for storing data. > Today we store the image as a one array with access function for specific > voxels depending on the grid dimensions.
Yes, that's what we do in EMBed is for 3D. But now I need the 2D version, that needs tons of specifics.
> Are you going to change this basic representation now or just have an access > class for Xmipp?
I am NOT changing anything, just building the 2D version compatible with Xmipp.
> On Nov 12, 2008, at 7:32 PM, Javier Ángel Velázquez Muriel wrote: > >> Actually, on second thought, what I am working on is not necessary a >> Matrix in 2D or 3D as Keren has wrote in her class. I am working in a >> template array able to store different types of data and then access >> to them in a 1D, 2D or 3D fashion. It is the way images and volumes >> are treated in Xmipp, and it is very efficient. Your point of view, >> guys, is more of storing points, and therefore compatible with what I >> am doing. >> >> J >> _______________________________________________ >> IMP-dev mailing list >> IMP-dev@salilab.org >> https://salilab.org/mailman/listinfo/imp-dev > >