Unable to run compiled function that uses parallel toolbox
2 visualizaciones (últimos 30 días)
Mostrar comentarios más antiguos
The direct error messagebox I get is:
"Failed to start a parallel pool. (For information in addition to the causing error, validate the profile 'local' in the Cluster Profile Manager.)"
Validating the local cluster profile succeeds.
The MatlavDesktopCreateError.log reads:
java.lang.Error: ActionData AbstractNamedUniqueID object with unique ID 'close-genome-desktop' and user-visible name 'Exit NGS Browser'. is already registered.
com.mathworks.mwswing.binding.KeyBindingManager.throwError(KeyBindingManager.java:623)
com.mathworks.mwswing.binding.KeyBindingManager.addAction(KeyBindingManager.java:201)
com.mathworks.mwswing.binding.KeyBindingManager.parseAndRegisterActions(KeyBindingManager.java:71)
at com.mathworks.services.binding.MatlabKeyBindings.<clinit>(MatlabKeyBindings.java:618)
at com.mathworks.widgets.action.BaseAbstractAction.<init>(BaseAbstractAction.java:24)
at com.mathworks.widgets.action.AbstractNewAction.<init>(AbstractNewAction.java:24)
at com.mathworks.hg.peer.FiguresGroup$NewFigureAction.<init>(FiguresGroup.java:78)
at com.mathworks.hg.peer.FiguresGroup.createToolBar(FiguresGroup.java:68)
at com.mathworks.hg.peer.FiguresGroup.<init>(FiguresGroup.java:43)
at com.mathworks.hg.peer.FiguresGroup.getInstance(FiguresGroup.java:52)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at com.mathworks.widgets.desk.DTGroup.createPropertyProvider(DTGroup.java:253)
at com.mathworks.widgets.desk.DTGroup.getPropertyProvider(DTGroup.java:190)
at com.mathworks.widgets.desk.DTOccupant.getProperty(DTOccupant.java:748)
at com.mathworks.widgets.desk.DTOccupant.getToolstripTabs(DTOccupant.java:520)
... (the stack continues a bit further down, but this post space seems limited).
I've tried the compiler-pragma workaround mentioned here and the explicit parpool instantiation mentioned here, with no results. Calling setSchedulerMessageHandler as mentioned here didn't shed any more light.
Any insight would be greatly appreciated!
-Ofek
1 comentario
Thomas Ibbotson
el 27 de Abr. de 2016
What is your compiled app doing?
The stack trace has nothing related to the Parallel Computing toolbox in it. It appears to be something to do with the MATLAB desktop which is odd for a parallel application.
Respuestas (0)
Ver también
Categorías
Más información sobre Parallel Computing Fundamentals en Help Center y File Exchange.
Community Treasure Hunt
Find the treasures in MATLAB Central and discover how the community can help you!
Start Hunting!