Open cmp5cg opened 8 years ago
My overall experience to use vistasoft on Windows was not good. I have tested few times in almost two years before in Windows 7, but as I recall I finally gave up (as you mentioned, there are many issues for compiling mex files, which are not trivial). This may not be a specific issue with dtiInit (presumably it is true for mrVista; not sure how much Jon has thought about it). I am using Ubuntu 14.04 now for running analysis. In general, I think that we don't have enough number of vistasoft users working in Windows computer to wrap up these dependency issues. I have no experience with Windows 10.
There are several ways to handle it. First idea is using virtual machine environment in your Windows machine to use Ubuntu in there. This may be easier but computationally inefficient. Second idea is installing Ubuntu in your computer. Third way is using Docker container in your windows, to solve some environmental dependency. In my case, I finally chose a second option.
I do not have any Windows machines in my lab and have not tested any vistasoft code on Windows. At some point, probably 5 years ago, it generally worked. Might not anymore. If someone does have a Windows machine and can run mrvTest and share the report, that would be informative. I am not optimistic, though, and do not have the ability to support Windows issues myself.
On Tue, Jul 18, 2017 at 9:44 PM, Hiromasa Takemura <notifications@github.com
wrote:
My overall experience to use vistasoft on Windows was not good. I have tested few times in almost two years before in Windows 7, but as I recall I finally gave up (as you mentioned, there are many issues for compiling mex files, which are not trivial). This may not be a specific issue with dtiInit (presumably it is true for mrVista; not sure how much Jon has thought about it). I am using Ubuntu 14.04 now for running analysis. In general, I think that we don't have enough number of vistasoft users working in Windows computer to wrap up these dependency issues. I have no experience with Windows 10.
There are several ways to handle it. First idea is using virtual machine environment in your Windows machine to use Ubuntu in there. This may be easier but computationally inefficient. Second idea is installing Ubuntu in your computer. Third way is using Docker container in your windows, to solve some environmental dependency. In my case, I finally chose a second option.
— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/vistalab/vistasoft/issues/171#issuecomment-316247859, or mute the thread https://github.com/notifications/unsubscribe-auth/ACBX3nthxVKAdsf7VOPjYZt_BPQSDQmUks5sPV-KgaJpZM4IYiP8 .
-- Jonathan Winawer Assistant Professor of Psychology and Neural Science
New York University 6 Washington Place New York, NY, 10003 (212) 998-7922 (phone) (212) 995-4018 (fax) jonathan.winawer@nyu.edu http://psych.nyu.edu/winawer/
From my experience matlab has a problem compiling 64bit The solution is check MATLAB\bin\mex.pl: look for $v7_compat. Change from "yes" to "no" Then try again to compile ditFitTensor mex -O dtiFitTensor.c and path to libmwlapack.lib
Hi Vistasoft community,
Has anyone been able to run dtiInit all the way through on Windows? I cannot get either dtiRawFitTensorMex or dtiRawFitTensorRobust to run without causing Matlab fatal errors and forcing it to close. I have tried compiling the necessary C files using the notes in dtiFitTensor and other files, but that does not work. I am currently working in Matlab 2016a (Windows 10), but I also tried in Matlab 2013a and was unsuccessful.
Thanks for your help!