When running the above scenario with coe 1.0.10, I had the name of a scalar variable wrong, and got the following message:
The message in bold should have been something like "The instance {Dut}.dut does not have a scalar variable named in_torque".
Instead the message seems to indicate that y is the variable missing, but that's incorrect and misleading.
PS C:\work\gitlab\project_digit-bench-dlte\claudio\distributed_model_tunning_example\decoupled_model_cosim\maestro_cli\local_cosim_coe_v1> java -jar .\coe-1.0.10.jar -o -c .\local_cosim_noloop.json --starttime 0 --endtime 10
Version: 1.0.10
ERROR [main] (RequestProcessors.java:320) - Internal error in initialization
org.intocps.orchestration.coe.AbortSimulationException: Failure in input calculation.
()
()
()
()
()
**{Dut}.dut.in_torque does not have a scalar variable named: y**
at org.intocps.orchestration.coe.scala.CoeInitialize$.constructOuputInputMaps(CoeInitialize.scala:277)
at org.intocps.orchestration.coe.scala.CoeInitialize$.initialize(CoeInitialize.scala:87)
at org.intocps.orchestration.coe.scala.Coe.initialize(Coe.scala:140)
at org.intocps.orchestration.coe.httpserver.RequestProcessors.processInitialize(RequestProcessors.java:311)
at org.intocps.orchestration.coe.httpserver.RequestHandler.initialize(RequestHandler.java:362)
at org.intocps.orchestration.coe.httpserver.RequestHandler.handleRequest(RequestHandler.java:212)
at org.intocps.orchestration.coe.util.SimulationExecutionUtil.callHttpAny(SimulationExecutionUtil.java:166)
at org.intocps.orchestration.coe.util.SimulationExecutionUtil.run(SimulationExecutionUtil.java:200)
at org.intocps.orchestration.coe.CoeMain.runOneShotSimulation(CoeMain.java:213)
at org.intocps.orchestration.coe.CoeMain.main(CoeMain.java:159)
Simulation failed Failure in input calculation.
()
()
()
()
()
{Dut}.dut.in_torque does not have a scalar variable named: y
maestro_cli.zip
When running the above scenario with coe 1.0.10, I had the name of a scalar variable wrong, and got the following message:
The message in bold should have been something like "The instance {Dut}.dut does not have a scalar variable named in_torque". Instead the message seems to indicate that
y
is the variable missing, but that's incorrect and misleading.