CFD Online Logo CFD Online URL
www.cfd-online.com
[Sponsors]
Home > Forums > Mesh Generation & Pre-Processing Software > Pointwise & Gridgen

Pink vs grayish color of database after import

Register Blogs Members List Search Today's Posts Mark Forums Read

Reply
 
LinkBack Thread Tools Search this Thread Display Modes
Old   March 29, 2022, 07:19
Default Pink vs grayish color of database after import
  #1
Senior Member
 
Pay D.
Join Date: Aug 2011
Posts: 164
Blog Entries: 1
Rep Power: 13
pdp.aero is on a distinguished road
Hi there,

Have a quick question. What is the difference when a database appears to be kinda grayish but still a model and a pinkish when it is imported into PW?

What do these colors indicate?

I see that two protocols of STEP files are supported.

"STEP file types supported for import are protocols AP 203, configuration controlled 3D designs of 3D mechanical parts and assemblies, and AP 214, core data for automotive mechanical design processes."

So how come when I import a STEP file exported like:

STEP AP214
AUTOMOTIVE_DESIGN

I get grayish model but if I import like:

STEP AP203
CONFIG_CONTROL_DESIGN

I get pinkish model. I would appreciate if you could help me understand the difference and how to avoid incompatible formats of STEPs.

Cheers, Pay.
__________________
since every contribution counts, always good ones are appreciated!
pdp.aero is offline   Reply With Quote

Old   March 30, 2022, 13:37
Default
  #2
Senior Member
 
David Garlisch
Join Date: Jan 2013
Location: Fidelity Pointwise, Cadence Design Systems (Fort Worth, Texas Office)
Posts: 307
Rep Power: 12
dgarlisch is on a distinguished road
Import of STEP (and all database files) are assigned the color specified in the imported file. If no color is defined, then PW defaults to pink.

See also attributes, display docs.
dgarlisch is offline   Reply With Quote

Old   March 31, 2022, 11:43
Default
  #3
Senior Member
 
Pay D.
Join Date: Aug 2011
Posts: 164
Blog Entries: 1
Rep Power: 13
pdp.aero is on a distinguished road
Quote:
Originally Posted by dgarlisch View Post
Import of STEP (and all database files) are assigned the color specified in the imported file. If no color is defined, then PW defaults to pink.

See also attributes, display docs.
Thanks David. So they are just STEP with colors.

Do you have any idea why sometimes a step files imports with no quilts? Just curves.

More information maybe helps. A step file had a boolean operation in ESP and then the result in egads format imported in PW but there is no quilt just hidden curves. Same step file is showing to be OK in esp and OK in PW alone. But after the boolean operation and export in egads format in PW quilts fail to be there. Re-export of the same file with protocol AP203 solved the issue though. I am just trying to figure out what happened and if this kinda issues can be detected beforehand.

Interestingly, I tried freeCAD to re-export the same file but didn't solve the issue. It's a mystery
__________________
since every contribution counts, always good ones are appreciated!
pdp.aero is offline   Reply With Quote

Old   March 31, 2022, 13:13
Default
  #4
Senior Member
 
David Garlisch
Join Date: Jan 2013
Location: Fidelity Pointwise, Cadence Design Systems (Fort Worth, Texas Office)
Posts: 307
Rep Power: 12
dgarlisch is on a distinguished road
I'd be guessing.

Attach a simple, ZIPPED STEP file that demonstrates the problem.

Or contact Pointwise support for help.

STEP files are ASCII. Zipping them makes them much smaller.
dgarlisch is offline   Reply With Quote

Old   March 31, 2022, 15:26
Default
  #5
Senior Member
 
Pay D.
Join Date: Aug 2011
Posts: 164
Blog Entries: 1
Rep Power: 13
pdp.aero is on a distinguished road
Quote:
Originally Posted by dgarlisch View Post
I'd be guessing.

Attach a simple, ZIPPED STEP file that demonstrates the problem.

Or contact Pointwise support for help.

STEP files are ASCII. Zipping them makes them much smaller.
Funny thing is that particular step file that I cannot share is showing this problem. I have tried to re-produce the problem but I couldn't.

Yep I did vimdiff but nothing seems to be much different between the one showing that problem and the one that had been re-exported, except the header that includes the protocol.
__________________
since every contribution counts, always good ones are appreciated!
pdp.aero is offline   Reply With Quote

Old   April 1, 2022, 11:53
Default
  #6
Senior Member
 
David Garlisch
Join Date: Jan 2013
Location: Fidelity Pointwise, Cadence Design Systems (Fort Worth, Texas Office)
Posts: 307
Rep Power: 12
dgarlisch is on a distinguished road
Quote:
Originally Posted by pdp.aero View Post
Funny thing is that particular step file that I cannot share is showing this problem. ...
Of course you can't share it.

Without a file, there is not much more I can offer.
dgarlisch is offline   Reply With Quote

Old   April 1, 2022, 11:57
Default
  #7
Senior Member
 
David Garlisch
Join Date: Jan 2013
Location: Fidelity Pointwise, Cadence Design Systems (Fort Worth, Texas Office)
Posts: 307
Rep Power: 12
dgarlisch is on a distinguished road
One quick thought just jumped in my head.

You said the model was "grayish".

Do you have hidden ents shown by any chance (View, Show Hidden)?

All hidden entities, when displayed, are "grayish".
dgarlisch is offline   Reply With Quote

Old   April 4, 2022, 04:44
Default
  #8
Senior Member
 
Pay D.
Join Date: Aug 2011
Posts: 164
Blog Entries: 1
Rep Power: 13
pdp.aero is on a distinguished road
Quote:
Originally Posted by dgarlisch View Post
One quick thought just jumped in my head.

You said the model was "grayish".

Do you have hidden ents shown by any chance (View, Show Hidden)?

All hidden entities, when displayed, are "grayish".
I am aware of hidden entities. Those are dark grayish. This one is bright grayish. As you said the bright gray is just color of stp file.

The thing is when the stp file gets imported alone everything is fine. Quilts are there.

But when it is imported into ESP first and have an operation, and then the egads result gets imported into PW, that particular region associated with stp file completely lose their quilts. Everything gets hidden and by showing hidden, there are only curves there. The problem is the stp file but I was wondering how can I find out what exactly makes the stp file incompatible.

If I re export the same stp file from some CAD software then everything is fine either importing alone or even after having an operation in ESP and getting the egads imported. No problem at all.

If I discover this mystery I would update here or would contact the customer services to have their opinion. Thanks a lot.
__________________
since every contribution counts, always good ones are appreciated!
pdp.aero is offline   Reply With Quote

Reply

Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are Off
Pingbacks are On
Refbacks are On


Similar Threads
Thread Thread Starter Forum Replies Last Post
[PyFoam] Using pyFoamPlotWatcher.py To Plot Residuals m_ridzon OpenFOAM Community Contributions 22 January 26, 2021 19:48
I developed an FEM toolkit in Java: FuturEye nkliuyueming Main CFD Forum 7 January 29, 2016 14:28
[PyFoam] library import error 00Sibbe OpenFOAM Community Contributions 5 October 15, 2014 12:41
[OpenFOAM] Annoying issue of automatic "Rescale to Data Range " with paraFoam/paraview 3.12 keepfit ParaView 60 September 18, 2013 04:23
Errors running allwmake in OpenFOAM141dev with WM_COMPILE_OPTION%3ddebug unoder OpenFOAM Installation 11 January 30, 2008 21:30


All times are GMT -4. The time now is 18:53.