• 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. Optimization
  3. Design3D Screening error: No mesh quality report file found...

Stats

  • Replies 8
  • Subscribers 5
  • Views 7113
  • Members are here 0
More Content

Design3D Screening error: No mesh quality report file found or readable

JosephSmith
JosephSmith over 3 years ago

Hi everyone,

I have been trying to set up an optimization project in Design3D. It is for a centrifugal impeller with a blunt trailing edge (its a constant dmr blunt type). I had run an initial simulation in fine turbo and made a parametric model of the geometry in Autoblade. I used the geomturbo file from the Autogrid mesh as the target model for the Autoblade modelling.

My problem lies when I try running the Screening operation in Design3D. I get the following error seen in image 1 which appears after STEP 4 Mesh quality failed in the Task manager tab

Opening view computations info shows the following information:




The quality report file was missing from the above directory. It was only in the directory where I saved the Autogrid mesh files. So, I then pasted the MKS.quality report file in the above directory ( \_trk\_flow\_mesh). The same error still appeared even after adding the quality file to the directory. I suspect maybe its the ''not being readable'' error now.

I am not quite sure how to resolve this error and would appreciate any help. This error did not occur when I did the desgin3d tutorial 1

  • Sign in to reply
  • Cancel
  • domen
    domen over 3 years ago

    Hello, the error may be a little misleading, but generally, this happens if the mesh generation fails thus the quality report is not created.

    Examples of the failure are:

    - "negative cells" in the mesh generation, if the new parametric blade is not suitable for the Autogrid template

    - if the blade was replaced by a shorter geometry that doesn't intersect the hub and/or shroud

    - possible mistake or error in case of a multirow optimization

    My advice is to open the *.igg file with IGG and check if the mesh looks ok. If it doesn't, go to the design directory, open the job_autogrid and you should be able to find out what's gone wrong.

    Let me know how it goes, please!

    • Cancel
    • Vote Up +1 Vote Down
    • Sign in to reply
    • Cancel
  • JosephSmith
    JosephSmith over 3 years ago in reply to domen

    Hi Domen,

    Thanks for the helpful advice. I opened the autogrid file within that directory and got an intersection error between blade and hub shown below. It seems it is as you say in the second point. In your 2nd point, how does the blade being replaced by a shorter geometry occur?

    In this file, I then went to expand the blade to intersect the hub. However, expanding the blade resulted in an unusual shape near the hub. It did not end up fully intersecting the hub either.


    Expanding only the hub also gave an ''adapt units'' suggestion (Although the parasolids geometry that I linked the initial mesh had units in metres). I increased the sewing tolerance and adjusted the expansion ratio but still did not fully intersect the hub. 



    Expanding both hub and shroud did not work either:


    In addition to the intersection error, the job file also mentioned that there is a self-intersecting  error:

    Not quite sure how that occurred.

    So far, the only possible solution I can think of is to adjust the blade geometry in Solidworks to intersect the hub, and restart from the beginning. Is there maybe an easier solution to this problem?


    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Cancel
  • domen
    domen over 3 years ago in reply to JosephSmith

    Just to be sure: this geometry comes from AutoBlade, right? The objective is to optimize the impeller while the volute is unchanged. 

    If this is correct, I would double-check the parametrization in Autoblade. Where are the sections positioned span-wise?

    • Cancel
    • Vote Up +1 Vote Down
    • Sign in to reply
    • Cancel
  • JosephSmith
    JosephSmith over 3 years ago in reply to domen

    I think so, I shall get back to you on that one. Yes, after optimizing the impeller I was going to do manual adjustments on the volute.

    Initially, the target geometry (geomturbo file from autogrid) did not have sectionally data so I used the slicing option in Autoblade to make three slices at 0.01 0.5 and 0.99 in the spanwise direction for this design.

    In the Stream surfaces tab of the model editor, I used 3 primary sections, and their spanwise locations after fitting were at 0 0.49 1

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Cancel
  • domen
    domen over 3 years ago in reply to JosephSmith

    OKOK.

    One trick is to let Autoblade extend the blade, you can do that in this menu:

    0.05 should be enough. If Autogrid is not able to mesh, then my suggestion would be to check the stream surfaces: if they make a "knot" or they are not following well the endwalls, you can shorten them up and have a proper surface to use to build the section. For example here, I reduced the shroud flow path, the section is built on a shorter surface and it's easier to control.

    • Cancel
    • Vote Up +1 Vote Down
    • Sign in to reply
    • 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