Skip to main content
Mar 13, 2017 2:50 PM UTC
Archived

Using ModelCHECK to flag bad density value.

Related products:Creo Parametric

This may be a repeat request (but I didn't see one when I searched).

There may also be another option than what I'm proposing here, so please be kind.

This is a request to allow ModelCHECK to flag specific density values (like an itemized list of values) that are bad.  Today, the DEF_DEFAULT setting looks for 1.00.  That's fine in some cases, but not all.  Imported vendor models will often have densities assigned that are not 1.00, a value based on the material, or even a value that's anywhere near a realistic value.  This means ModelCHECK skips them.

This request would effectively allow us to use an "OR" statement.

Here's an example:  IF density = 0 OR density = 1000 OR density = 1.2345 THEN issue an error.  Something like that.

I don't know if this would also require some sort of tolerance/accuracy, or would read the exact value including significant digits.  1.00 vs.  .999.  I realize that we'd could end up with a pretty long list, but the capability could help us today.

Thanks.

4 replies

Mar 21, 2017 11:24 PM UTC

ModelCheck will "skip" any density value that is not "1" and consider it acceptable and not provide an ERROR or Warning.

Some standard default densities I've seen are "1", "1000", and "0.000001" (have to check the number zeros, don't remember if it is 5 or 6).

There are a few types of realistic densities.  One is a density of single material objects (all AL6061 T6) or combinations of those objects which keep the density in a range between the lightest material and the highest density material.  Another type is a "fake" density which could be extremely high or extremely low to make the PRT calculate the correct mass.  A honeycomb panel that is modeled as a solid rectangle would need an extremely low density to make the PRT match the real mass of that size honeycomb panel.

So while selecting several options to reject (1, 1000, 0.000001, etc) it might be easier to reject a range of values such as a greater than or less than statement rather than listing so many individual numbers.

Apr 25, 2019 3:10 PM UTC
Status changed to: Acknowledged
Oct 19, 2021 12:23 PM UTC
olivierlp
Community Manager
Jan 4, 2022 5:07 PM UTC
Status changed to: Archived

Hello,

We are archiving your idea as part of a general review. This action is based on the age of your idea and the total number of votes received, as per this announcement.

You can always post a new idea with all the details required in the form.

Thank you for your participation.

Olivier