Opened 10 years ago

Closed 7 years ago

#2945 closed defect (fixed)

Translation error

Reported by: Adam Dershowitz <dersh@…> Owned by: wbraun
Priority: high Milestone: Future
Component: Backend Version: trunk
Keywords: Cc:

Description

I just upgraded from 22978 to 23108.
Some of my models, that worked fine in 22978, now report the following errors:
[:0:0-0:0] Error: Internal error BackendDAEOptimize.createJacobian failed
[:0:0-0:0] Error: Internal error BackendDAEOptimize.generateSymbolicJacobian failed

But, the models then seem to compile and run fine. So, I'm not sure if this is a "real" error, or it is a bug in the Messaging system? But, something is clearly different after the update. Typically, after errors, the model then stops, so I am not sure exactly what to make of the change, and the errors.

Change History (8)

comment:1 Changed 10 years ago by sjoelund.se

Well. We are able to simulate without a symbolic Jacobian (default to a numeric one instead). But I guess we should not fail, and want to produce a better solution...

comment:2 follow-up: Changed 10 years ago by Adam Dershowitz <dersh@…>

Was it failing symbolically before and then defaulting to numeric, and the only thing that is different in this version is that it is reporting it as an error now?
Or was symbolic working before, and now is failing?
In either case, yes, if it is falling back to something that works, it should probably not be an error, but a warning, I would think.

comment:3 Changed 10 years ago by lochel

  • Component changed from Unknown to Backend
  • Owner changed from somebody to wbraun
  • Status changed from new to assigned

comment:4 in reply to: ↑ 2 Changed 10 years ago by wbraun

  • Status changed from assigned to accepted

Replying to Adam Dershowitz <dersh@…>:

Was it failing symbolically before and then defaulting to numeric, and the only thing that is different in this version is that it is reporting it as an error now?
Or was symbolic working before, and now is failing?
In either case, yes, if it is falling back to something that works, it should probably not be an error, but a warning, I would think.

It's connected to #2867 and r22637. There we activated for more model to generate that symbolic jacbian, so that's perhaps the reason it didn't not fail before.
I try first to fix #2867, and then we can see if that help also to your models.

comment:5 in reply to: ↑ description Changed 10 years ago by wbraun

Replying to Adam Dershowitz <dersh@…>:

I just upgraded from 22978 to 23108.
Some of my models, that worked fine in 22978, now report the following errors:
[:0:0-0:0] Error: Internal error BackendDAEOptimize.createJacobian failed
[:0:0-0:0] Error: Internal error BackendDAEOptimize.generateSymbolicJacobian failed

Could you please try with something newer than 23216 and report if you still get the same message.
If so could you please provide a model that cause such messages?

comment:6 Changed 10 years ago by Adam Dershowitz <dersh@…>

I just built 23219, and I see the same results. It gives that error, but does does continue to run, and give results that appear to be the same as with 22978.
Perhaps, the symbolic Jacobian used to fail, and switch over to the numeric one, with no error. Now it reports that as an error, but continues anyway?
Unfortunate, this model proprietary so is not something I can post. And, I am not seeing this issue on some simplified models. Is there any other information that perhaps I can give you that might help debug this?

comment:7 Changed 10 years ago by adrpo

If the model is proprietary, if you want, you could send it
to us privately via email and we will just use it for debugging
and then delete it.

comment:8 Changed 7 years ago by wbraun

  • Resolution set to fixed
  • Status changed from accepted to closed

In the meanwhile there were quite a lot of improvements on the symbolic jacobians, therefore I assume this also fixed. If not please reopen it.

Note: See TracTickets for help on using tickets.