PyRAT icon indicating copy to clipboard operation
PyRAT copied to clipboard

Does not compile on Windows

Open birgander2 opened this issue 5 years ago • 4 comments

Currently, there are several problems when running (better: compiling) PyRAT on Windows:

  • The current MSVC compiler seems to have a particular implementation of complex data structures, not compatible with the C99 standard. As a consequence, despeckle.pyx and nlsar don't compile on Windows.
  • Python multiprocessing seems not to work well (mean: very slow) on Windows 10. This seems to be related to the inability of Windows to fork processes.

I'll try to find solutions, but for the moment don't expect too much when using Windows. We somehow need a Windows expert.

birgander2 avatar Jan 27 '20 09:01 birgander2

WSL gives us much of the native speed functionality in windows and should be the recommended solution. I have PyRAT working successfully in windows under WSL. Are there any functions you would like me to benchmark ?

whatnick avatar Jan 27 '20 09:01 whatnick

You're lucky. On my company-locked Windows machine, I have no WSL and cannot install it...

birgander2 avatar Jan 27 '20 12:01 birgander2

No worries similar situation with my machine. But in that case I don't have a compiler and Python either. So most work is done in a cloud hosted Jupyter Hub environment. I can have a go at this issue once my short-term analysis goals around Sentinel-1 are closed.

whatnick avatar Jan 27 '20 19:01 whatnick

No worries similar situation with my machine. But in that case I don't have a compiler and Python either. So most work is done in a cloud hosted Jupyter Hub environment. I can have a go at this issue once my short-term analysis goals around Sentinel-1 are closed.

@whatnick could you show a sample notebook on how to run PyRAT on the cloud?

khanfarhan10 avatar Dec 24 '20 09:12 khanfarhan10