Opened 11 years ago

Closed 7 years ago

Last modified 7 years ago

#2694 closed discussion (invalid)

Simulate thermopower pump error code -1

Reported by: Félicia Owned by: Lennart Ochel
Priority: high Milestone: never
Component: Backend Version: 1.9.0Beta
Keywords: Cc:

Description (last modified by Lennart Ochel)

I want to developp a simulation of power plant. At the beginning, I simulate each components of the power plant power (condenser, turbine, pump...).

For the pump, I use source pressure and masse flow and sink pressure.
I initalized pressure and enthalpy.

And I have a error message :

stdout | warning | While solving non-linear system an assertion failed.
| | | | | The non-linear solver tries to solve the problem that could take some time.
| | | | | It could help to provide better start-values for the iteration variables.
| | | | | For more information simulate with -lv LOG_NLS
LOG_NLS | warning | nonlinear system fails: Nonlinear function (residualFunc10, size 3) at t=0 Debug more
| | | | | proper start-values for some of the following iteration variables might help
| | | | | | [1] Real pump1.inletFluidState.p(start=100000, nominal=100000)
| | | | | | [2] Real pump1.rho(start=1000, nominal=1)
| | | | | | [3] Real pump1.s(start=1, nominal=1)
stdout | warning | While solving non-linear system an assertion failed.
| | | | | The non-linear solver tries to solve the problem that could take some time.
| | | | | It could help to provide better start-values for the iteration variables.
| | | | | For more information simulate with -lv LOG_NLS
LOG_NLS | warning | Error solving nonlinear system Nonlinear function (residualFunc26, size 3) at time 0 Debug more
stdout | warning | Error in initialization. Storing results and exiting.

Use -lv=LOG_INIT -w for more information.

Process crashed

Simulation process exited with code -1

I don't understand why it doesn't work.

Could you help me for this error?

Where can I have information about error compilation and about model of thermopower library?

Thank you

Best regards
Dubret Félicia

Change History (14)

comment:1 by Adeel Asghar, 11 years ago

Component: OMEditBackend
Owner: changed from Adeel Asghar to lochel, wbraun
Status: newassigned

comment:2 by Martin Sjölund, 10 years ago

Milestone: 1.9.11.9.2

This ticket was not closed for 1.9.1, which has now been released. It was batch modified for milestone 1.9.2 (but maybe an empty milestone was more appropriate; feel free to change it).

comment:3 by Martin Sjölund, 10 years ago

Milestone: 1.9.21.9.3

Milestone changed to 1.9.3 since 1.9.2 was released.

comment:4 by Martin Sjölund, 9 years ago

Milestone: 1.9.31.9.4

Moved to new milestone 1.9.4

comment:5 by Lennart Ochel, 9 years ago

Owner: changed from lochel, wbraun to Lennart Ochel

Is this issue still present?

comment:6 by Lennart Ochel, 9 years ago

Description: modified (diff)

comment:7 by Martin Sjölund, 9 years ago

Milestone: 1.9.41.9.5

Milestone pushed to 1.9.5

comment:8 by Martin Sjölund, 9 years ago

Milestone: 1.9.51.10.0

Milestone renamed

comment:9 by Lennart Ochel, 9 years ago

I think the pump component should work in the meanwhile. Is this issue still up-to-date?

comment:10 by Martin Sjölund, 8 years ago

Milestone: 1.10.01.11.0

Ticket retargeted after milestone closed

comment:11 by Martin Sjölund, 8 years ago

Milestone: 1.11.01.12.0

Milestone moved to 1.12.0 due to 1.11.0 already being released.

comment:12 by Francesco Casella, 7 years ago

Milestone: 1.12.0Future

The milestone of this ticket has been reassigned to "Future".

If you think the issue is still valid and relevant for you, please select milestone 1.13.0 for back-end, code generation and run-time issues, or 2.0.0 for front-end issues.

If you are aware that the problem is no longer present, please select the milestone corresponding to the version of OMC you used to check that, and set the status to "worksforme".

In both cases, a short informative comment would be welcome.

comment:13 by Christoph Buchner <buchner@…>, 7 years ago

Resolution: invalid
Status: assignedclosed

I think without repro code, and with no feedback from the reporter, this should be closed. If you still experience the issue we can open it again.

comment:14 by Christoph Buchner <buchner@…>, 7 years ago

Milestone: Futurenever
Note: See TracTickets for help on using tickets.