How do I suppress this warning from spmd?
3 Ansichten (letzte 30 Tage)
Ältere Kommentare anzeigen
Dom
am 14 Jan. 2014
Beantwortet: Peiyuan Zhai
am 20 Mär. 2022
I have an spmd statement running in a loop where one worker will use labBroadcast to send a message to the other workers. Occasionally the other workers will finish what they're doing before they receive the message. This isn't a problem except that when spmd finishes Matlab gives an warning of the form:
Lab 1:
Warning: An incoming message was discarded from lab 2 (tag: 400003)
I've tried using lastwarn to identify the warning after stopping execution, but it gives no output. I've also tried
pctRunOnAll warning('off','all')
outside the spmd statement and warning('off','all') inside the statement and yet the warning keeps being thrown. Because the spmd statement is in a loop, this message can appear hundreds of times during the execution of the script. How do I suppress these warnings?
3 Kommentare
Niklas Nylén
am 14 Jan. 2014
I also run 2011b and warnings appear in orange text. You can set the color in the matlab preferences.
By the looks of the output you provided, the message is not a usual matlab warning, and even if it is it does not have an identifier, which means you can not turn it off, if it does not work with the 'all' input.
Akzeptierte Antwort
Edric Ellis
am 14 Jan. 2014
I believe you can only hit this warning if you don't ensure that all workers call labBroadcast together. So, rather than suppress this warning, you should ensure that all workers make the same labBroadcast calls.
2 Kommentare
Edric Ellis
am 14 Jan. 2014
Bearbeitet: Edric Ellis
am 14 Jan. 2014
You've already encountered the first detrimental effect - the warning. However, there's a more serious problem which you might encounter later. labBroadcast is built on top of MPI, and the MPI standard doesn't define when a method such as broadcast will block and when it will use buffering. Because you're using the default error-detecting mode of lab* communication, labBroadcast is using the implementation based on labSend and labReceieve; and fortunately for you the labSend portion is able to complete without the matching labReceive because of buffering.
If you ever get to the point where labSend cannot buffer the message because it's too large, you'll get deadlock (which may or may not be detected) or an erroring communication mismatch. In R2013b, this gives me an error:
parpool('local', 2);
spmd
if labindex == 1
labBroadcast(1, rand(1000));
end
end
Weitere Antworten (2)
Ammar
am 21 Apr. 2017
Hi guys, I have the same problem, any suggestion ?
This is the message:
Warning: An incoming message was discarded from lab 3 (tag: 0)
Kind regards Ammar
0 Kommentare
Peiyuan Zhai
am 20 Mär. 2022
Try to add
warning('off','all')
after
spmd
but not before it. This works for me.
0 Kommentare
Siehe auch
Kategorien
Mehr zu Parallel Computing Fundamentals finden Sie in Help Center und File Exchange
Produkte
Community Treasure Hunt
Find the treasures in MATLAB Central and discover how the community can help you!
Start Hunting!