• Skip to main content
  • Skip to search
  • Skip to footer
Cadence Home
  • This search text may be transcribed, used, stored, or accessed by our third-party service providers per our Cookie Policy and Privacy Policy.

  1. Community Forums
  2. Online CFD Course
  3. Module 1: Simulation produces error: Mass is not a numb...

Stats

  • State Verified Answer
  • Replies 10
  • Subscribers 11
  • Views 6639
  • Members are here 0
More Content

Module 1: Simulation produces error: Mass is not a number

SimonGohle
SimonGohle over 2 years ago

The problem I have with the first challenge might be a problem with my PC. When ever I start the simulation of the in the handout specified numbers, the simulation ends after some time and gives out the error message

 - S_Simulation 1 Error: ERROR: residual of Mass is Not A Number: the solver has been stopped

and the message

 - The simulation Simulation 1 has failed: some NaN have been detected during the computation.<br> ERROR: residual of Mass is Not A Number: the solver has been stopped

I don´t know if my PC´s CPU is maybe not good enough or if there might be a problem with my pre-processing in this challenge.

What worked is to set the CFL Number to 1.5 instead of 3.0, but the challenge requires running the simulation with a CFL of 3.0.

  • Sign in to reply
  • Cancel
Parents
  • Kathrin
    0 Kathrin over 2 years ago
    Hi Simon,

    I assume you are using Omnis v5.2? Good news is: this problem does not originate from your CPU! This is what we call a diverging/crashing simulation. You did the proof yourself: By setting CFL to 1 the simulation does not converge anymore. Please try the following: Set the CFL to 3 and the CFL number (for CGI) to 1 as shown in the screenshot below.
    IF you are in essential mode, you just see the CFL number, which shall be put to 3. We were assuming that you would remain in essential mode.

    Could you please check if that solves the problem and give us a quick feedback? If that helps we would quickly update the hand-out.

    Best regards,
    Kathrin
    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Verify Answer
    • Cancel
Reply
  • Kathrin
    0 Kathrin over 2 years ago
    Hi Simon,

    I assume you are using Omnis v5.2? Good news is: this problem does not originate from your CPU! This is what we call a diverging/crashing simulation. You did the proof yourself: By setting CFL to 1 the simulation does not converge anymore. Please try the following: Set the CFL to 3 and the CFL number (for CGI) to 1 as shown in the screenshot below.
    IF you are in essential mode, you just see the CFL number, which shall be put to 3. We were assuming that you would remain in essential mode.

    Could you please check if that solves the problem and give us a quick feedback? If that helps we would quickly update the hand-out.

    Best regards,
    Kathrin
    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Verify Answer
    • Cancel
Children
  • SimonGohle
    0 SimonGohle over 2 years ago in reply to Kathrin

    Yes, I am using Omnis v5.2 . It is the other way around, if I set the CFL number on 3.0 it will produce the error, but if I set it on 1.5 it works. I looked into the program and CFL number is at 3 and CFL number (for CGI) is already at 1. I tried it also with lower speeds of 0.5 m/s, and then it worked fine with a CFL number of 3. So that is unfortunately not the solution I am searching

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Verify Answer
    • Cancel
  • Kathrin
    0 Kathrin over 2 years ago in reply to SimonGohle

    I am trying to find out which solver setting might differ from the handout. So far I only get a crash of the simulation when I do not activate "Low speed flow".
    Could you please check if "Low speed flow (M>0.3)" is activated and the characteristic speed is set to 1.2m/s?

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Verify Answer
    • Cancel
  • SimonGohle
    0 SimonGohle over 2 years ago in reply to Kathrin

    Yes, I have laminar Flow on and a tip at Low speeds with the correct velocity when the Error is produced.

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Verify Answer
    • Cancel
  • SimonGohle
    0 SimonGohle over 2 years ago in reply to SimonGohle

    *And a tick at the low speeds not tip

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Verify Answer
    • Cancel
  • SimonGohle
    +1 SimonGohle over 2 years ago in reply to SimonGohle

    I found my error. There is a tab in the mesharea exactly looking the same for the viscos layers. Instead of setting it up in at the wall I set it up in the mesh set up in the tab local. That producet the error. Now my Solution converges. Thank you very much for your help :)

    • Cancel
    • Vote Up +2 Vote Down
    • Sign in to reply
    • Reject Answer
    • Cancel
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.

© 2025 Cadence Design Systems, Inc. All Rights Reserved.

  • Terms of Use
  • Privacy
  • Cookie Policy
  • US Trademarks
  • Do Not Sell or Share My Personal Information