Logging in a parfor

3 次查看（过去 30 天）
Ben
Ben 2016-3-2
编辑： Adam 2016-3-2
So this is multithreading 101. I have a crash somewhere, I assume. I started running 500 iterations and only about 40 out of 400 of them wrote a picture to file. I can't explain why so I am looking at debugging. In any other programming language, I would open up a log file with the id of the iteration (like log_1.log) and close the file at the end of the loop. How do I do this in matlab? I don't see how "diary" can be used since it seems to open up a global file, which is obviously a terrible idea. I don't want to use fprint statements since I am trying to collect everything in the command window on that specific thread. I might be making a large assumption about how parfor works though.
Can I assume that the parfor loop essentially is a fancy "fork" command? That is, I set up the variables and it hits a parfor and there is absolutely no communication between the different threads, essentially treating them as separate processes with separate heaps and stacks?
  1 个评论
Adam
Adam 2016-3-2
编辑：Adam 2016-3-2
In a simple parfor loop every thread should be independent of every other.
I'm not sure why you specifically don't want to use fprintf statements though. If you really want to write 500 log files this seems like the simplest way. I have previously used parfor loops writing each to their own file which worked well for what I wanted.
One of the easiest first ports of call for bugs in parfor loops though is to switch out the parfor for a regular for loop and see if you have the same problem. If you do then obviously you can ignore the parallel aspect and debug normally. If you don't get the problem then you can at least be sure it is related to the parfor specifically.

请先登录，再进行评论。

请先登录，再回答此问题。

回答（0 个）

类别

在 Help Center 和 File Exchange 中查找有关 Parallel for-Loops (parfor) 的更多信息

标签

Community Treasure Hunt

Find the treasures in MATLAB Central and discover how the community can help you!

Start Hunting!

Translated by