Discussion Closed This discussion was created more than 6 months ago and has been closed. To start a new discussion with a link back to this one, click here.

Hi all, I want to optimise my model using GA but I have got this error message. Would you please kindly help me solve the problem? Many thanks in advance Maleaha

Please login with a confirmed email address before reporting spam

When I wanted run the GA the following errors can be seen: Optimization running. Error running optimization. Java exception occurred: Exception: com.comsol.util.exceptions.FlException: Illegal input vector illegal entity number (rethrown as com.comsol.util.exceptions.FlException) (rethrown as com.comsol.util.exceptions.FlException) Messages: Illegal input vector illegal entity number

Illegal input vector illegal entity number

Illegal input vector, illegal entity number detected.

Stack trace: at com.comsol.clientapi.engine.c.handleException(SourceFile:27) at com.comsol.client.interfaces.g$d.e(SourceFile:533) at com.comsol.client.interfaces.g.a(SourceFile:240) at com.comsol.client.interfaces.ClientWebSocketCommandManager.a(SourceFile:468) at com.comsol.client.interfaces.g.runAndWait(SourceFile:219) at com.comsol.clientapi.engine.APIEngine.runMethod(SourceFile:235) at com.comsol.clientapi.impl.SelectionClient.set(SourceFile:108) Caused by: Exception: com.comsol.util.exceptions.FlException: Illegal input vector illegal entity number (rethrown as com.comsol.util.exceptions.FlException) Messages: Illegal input vector illegal entity number

Illegal input vector, illegal entity number detected.

at com.comsol.clientapi.engine.c.handleException(SourceFile:27) at com.comsol.client.interfaces.g.a(SourceFile:375) at com.comsol.client.interfaces.ClientWebSocketCommandManager.a(SourceFile:489) at com.comsol.client.interfaces.g.processCommandAnswer(SourceFile:331) at com.comsol.client.interfaces.g$d.e(SourceFile:531) ... 5 more Caused by: Exception: com.comsol.util.exceptions.FlException: Illegal input vector illegal entity number Messages: Illegal input vector, illegal entity number detected.

at com.comsol.model.selections.SelectionMethod.a(SourceFile:1110) at com.comsol.model.selections.SelectionMethod.set(SourceFile:756) at com.comsol.model.internal.impl.SelectionImpl.c(SourceFile:958) at com.comsol.model.internal.impl.SelectionImpl$10.a(SourceFile:613) at com.comsol.model.internal.impl.SelectionImpl$10.execute(SourceFile:1) at com.comsol.model.clientserver.ClientManager$1.call(SourceFile:169) at com.comsol.model.clientserver.ClientManager.modify(SourceFile:181) at com.comsol.model.internal.impl.SelectionImpl.set(SourceFile:605) at sun.reflect.GeneratedMethodAccessor64.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at com.comsol.bridge.command.b.a(SourceFile:138) at com.comsol.bridge.command.b.run(SourceFile:83) at com.comsol.bridge.command.h.execute(SourceFile:42) at com.comsol.bridge.command.BridgeCommandManager.d(SourceFile:675) at com.comsol.bridge.command.BridgeCommandManager.a(SourceFile:663) at com.comsol.bridge.command.BridgeCommandManager$3.a(SourceFile:572) at com.comsol.bridge.command.BridgeCommandManager$3.call(SourceFile:1) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) at java.lang.Thread.run(Thread.java:745)


0 Replies Last Post Sep 27, 2017, 5:59 a.m. EDT
COMSOL Moderator

Hello Maleaha Samin

Your Discussion has gone 30 days without a reply. If you still need help with COMSOL and have an on-subscription license, please visit our Support Center for help.

If you do not hold an on-subscription license, you may find an answer in another Discussion or in the Knowledge Base.

Note that while COMSOL employees may participate in the discussion forum, COMSOL® software users who are on-subscription should submit their questions via the Support Center for a more comprehensive response from the Technical Support team.