I have also another question regarding the command resize for a a distributed matrix. I would expect it to work similarly to matlab, I mean if you have a 3 x3 matrix and try to resize to a 9x1 matrix, the command would stack the columns of the matrix. Is this what I should expect? I believe that in some of the col and row aligns it was not working like that.
the Gemm calls can be replaced with std::function calls similar to the way I implemented FGMRES
ah, that would be reshape
which does not exist in Elemental
at least, I don't think I ever implemented it
err, actually I did implement Reshape
I implemented using bind, instead of function, but the code is very similar
The CIRC,CIRC distribution puts the entire matrix on one process
Thanks I will do that, and it also saves me some trouble in having to change the distribution.
please feel free to ask any questions if you run into anymore road blocks
thank you very much.
i started working on it last year but didn't find much material online.
Hi! I'm trying to install Elemental into an Anaconda environment python 3.5. After succesfully checking the python options building and installing with CMAKE, the Elemental python module seems to not be there. Any ideas on this? Thanks!
This is good motivation to push out the Anaconda package being discussed at elemental/Elemental#207
What CMake configuration flags did you use?
the usual issue is that you need to make sure your PYTHONPATH includes the Python installation directory
Thanks for the response. I did set up the PYTHONPATH and I tried on a linux machine and OSX. In both cases the installation of the python package did not work
The python files were not installed in the right folder as a package under python3.5/site-packages but in the top-level folder
Ryan H. Lewis
You can control where most elements of the install go. Look at the redhat/elemental-spec for an example
Hi Jack, thanks for merging my PR. I've got some issues with COMPACT_SVD. In https://github.com/elemental/Elemental/blob/master/src/lapack_like/spectral/SVD.cpp#L75, the default tol is used to cull 'low enough but not necessarily zero' singular values. Is this the intended behaviour? Lines 277, 469, 771 and 1126 of src/lapack_like/spectral/BidiagSVD.cpp seem to contradict this, and do not make use of the APosterioriThreshold function.
Also, would you know what I can do if an SVD does not converge? I am trying to build with ScaLAPACK to see if I have problems there, but I'm running into issues building with ScaLAPACK and 64-bit ints.