'parpool' fails in deployed application
10 Ansichten (letzte 30 Tage)
Ältere Kommentare anzeigen
Vinayak Phalke am 29 Okt. 2018
Beantwortet: Stefanie Schwarz am 9 Aug. 2022
I am building a parallel for loop (parfor) based deployed application. I have a parpool command before the parfor loop:
parfor a = 1:N ....
The code works within MATLAB, but in the deployed application, it errors out at the parpool line:
Error using parpool (line 113)
The specified superclass 'parallel.internal.customattr.CustomPropTypes' contains a parse error,
cannot be found on MATLAB's search path, or is shadowed by another file with the same name.
Great. That's mean for MATLAB compiler, it need to do the same way as MATLAB Compiler SDK.
To use parallel computing for standalone application (MATLAB Compiler SDK/MATLAB Compiler) , you may need to configure/change your code as below:
Kristoffer Walker am 26 Jun. 2019
Bearbeitet: Kristoffer Walker am 26 Jun. 2019
It would be great if this answer could be improved. I am having this issue now I believe, but I do not understand what a "local profile" is, how to generate such a settings file, and why I should bundle it for deployment in a completely different remote machine that will have a different number of cores and may not share any similarities with the local profile that was deployed with it. I have read the website links above.
Kevin Chng am 28 Jun. 2019
Let me provide some documentation here for your reading:
Similar question has been asked in the past:
I tried it before personally, it is working for deployed application. For your question about :
Different remote machine that will have a different number of cores and may not share any similarities with the local profile that was deployed with it.
Frankly speaking, i'm not sure about it, but i think the local setting file should working for different machine.
follow the documentation to get your local pc work with your deployed standalone application with parallel computing first.
later, we can try to execute the standalone application in different pc. I think it should be working. Let me know, i'm interested to know it as well.
If you still encouter any issue, let me know, then i try spend some time to try it out.
Kristoffer Walker am 1 Jul. 2019
Bearbeitet: Kristoffer Walker am 1 Jul. 2019
So I've looked more carefully at this and created a simple example to demo the problem. Just create a script "testApp.m". Include in it a call to function testAppFunc(), which inside it only does a "parpool(2)". Put some fprintf statements in there for correlation purposes. Then compile it with Application Compiler and test the testApp.exe in for_redistribution_files_only directory by launching from a PowerShell. You will hear the beep. Why does this happen and how can I stop it? This only happens the first time parpool is executed from a deployed app. It does not happen during subsequent calls to parpool in the same instance of the deployed app. It also does not happen in the non-deployed app at any time.
BTW, saving the settings.local file did not help (but thanks for those links to the instructions).
Stefanie Schwarz am 9 Aug. 2022
See the MATLAB Answers post below - it could also just be a problem of running the executable against an incorrect version of MATLAB Runtime:
Find more on Parallel Computing Fundamentals in Help Center and File Exchange
Community Treasure Hunt
Find the treasures in MATLAB Central and discover how the community can help you!Start Hunting!