Stats

  • State Not Answered
  • Replies 3
  • Subscribers 8
  • Views 1089
  • Members are here 0
More Content

FineTurbo: Solver gets stuck

Delfim Sa

I am using FineTurbo 18, and when I put in a simulation, most of the time, it gets stuck on this:

BLOCK 47 : Transfer initial solution for turbomachinery
BLOCK 4 : Transfer initial solution for turbomachinery
BLOCK 31 : Transfer initial solution for turbomachinery
BLOCK 43 : Transfer initial solution for turbomachinery
BLOCK 37 : Transfer initial solution for turbomachinery
BLOCK 42 : Transfer initial solution for turbomachinery
BLOCK 11 : Transfer initial solution for turbomachinery
BLOCK 28 : Transfer initial solution for turbomachinery
BLOCK 14 : Transfer initial solution for turbomachinery

Then, I need to stop it and rerun it until it passes this phase.

What do I do to avoid this?

I am planning on doing an optimization, and I don't want this type of problem.

What do I do?

Regards and Merry Christmas and a Happy New Year,

Delfim Sá

  • 0

    Based on the block index, the project has a log of blocks. It could be a multi-stage machine with a large mesh. You can isolate the issue by running each row separately to see which takes more time.

  • 0 in reply to Gaurav

    Sorry for the late reply. But that is not what is happening here. The solver just gets stuck. If I stop the solver and restart it a few times, it doesn't get stuck anymore. The problem is that the solver gets stuck. I don't know if I made my point clear.

  • 0

    Hi Delfin,

    Some of my colleagues, who primarily use the legacy Fine/Turbo tools (but the newer versions), occasionally experience similar issues. They often have to restart the simulation to get it running properly.

    Are you working on a Windows system? Running the simulations on Linux might help avoid such problems. Personally, I mainly work with Fidelity and haven’t encountered these issues.

    I agree—getting this kind of error during an optimization run is really inconvenient.

    Here’s what I would suggest:

    • Periodically check the log file where the output is written (is that the .std file, perhaps?). If the last entry doesn’t change for a certain amount of time, abort the simulation and restart it.

    • Alternatively, you could monitor the size of the .std file. If it doesn’t increase over time (as it should while more entries are being added), take that as a sign to abort and restart the simulation.

Cadence Guidelines

Community Guidelines

The Cadence Design Communities support Cadence users and technologists interacting to exchange ideas, news, technical information, and best practices to solve problems and get the most from Cadence technology. The community is open to everyone, and to provide the most value, we require participants to follow our Community Guidelines that facilitate a quality exchange of ideas and information. By accessing, contributing, using or downloading any materials from the site, you agree to be bound by the full Community Guidelines.