![]() So there might be hope I'll report back after I've implemented C code), as I had expected. ![]() ![]() In R, as in most modern languages except Matlab, square brackets are used for indexing see Sect.2.3.4. Do you reckon with an SSD (to tackle IO) and a GPU (to tackle huge number of pixels) - some headway could be made? Just ran the profiler, and the most amount of time is indeed spent on the Fourier transform (not a mex btw. In R, assignment statements do not print their value, so there is no need for the Matlab convention of using for silencing an assignment. Profiling states that the fft loop is indeed taking up a huge chunk of the time, but ofcourse the IO is also a bottleneck. Usually, I would run my loop over 50 to 1000 (ideal) iterations, with each iteration having between 4 and 20 fft's. (Is the best way to convert it into a series of functions first, and then somehow use a C compiler?) Part 2: so just a quick edit to update my question based on the responses I've gotten so far (and thank you very much for those): So I've got like 212 x 212 (4096 x 4096 or 16million) pixels 'images' taht I'm manipulating at the moment, and with an 8GB ram, I can't go any higher than that, though ideally I want to be able to manipulate 8192 x 8192 (or 64million) pixels. How do I go about converting such an m file to a C code.
0 Comments
Leave a Reply. |