[cgma-dev] Fwd: Multiple "TopologyBridge"s under one merged "RefEntity"

[Jane Hu]

FYI

---------- Forwarded message ----------
From: Jane Hu <janejhu at gmail.com>
Date: Thu, Sep 1, 2011 at 12:01 PM
Subject: Re: [cgma-dev] Multiple "TopologyBridge"s under one merged
"RefEntity"
To: Hong-Jun Kim <hongjun at mcs.anl.gov>


I just chatted with Jason and learned two things:

Jason, Please correct me if I understood wrong.

1. When getting one of the merged geometries, cubit10.2 kept the RefEntity
and its sense for both geometries. So you can do keep your mesh. While
cubit12 use their own RefEntities and senses for each geometry, so you may
end up with reversed mesh loops. Each geometry entity or TopologyBridge
remain the same, hopefully your mesh won't need to know details about them.

2. Our https://svn.mcs.anl.gov/repos/ITAPS/cgm/branches/cubit/ directory is
now cubit code for version 12, we don't have a clean branch for cubit10.2.
Although we need all our code for 10.2, when make with --with-cubit option,
it only used limited stuff from our code, mainly the header files. r4775 is
the one we merged our code to cubit12, so before it should be all cubit10
code. Please use code changes before r4775 for your build.

Jane


On Thu, Sep 1, 2011 at 10:49 AM, Hong-Jun Kim <hongjun at mcs.anl.gov> wrote:

> Tim recommended to use CGM with cubit 10.2 for this problem because it is
> hard to fix it not modifying core part of CGM.
>
> So, it looks CGM r5026 is the latest version with cubit 10.2 and then is it
> the best way to use this revision?
> Otherwise, is there any branch for cubit 10.2 in repository?
> Thanks.
>
> Hong-Jun
>
>
> ----- Original Message -----
> > From: "Jane Hu" <janejhu at gmail.com>
> > To: "Hong-Jun Kim" <hongjun at mcs.anl.gov>
> > Sent: Wednesday, August 31, 2011 9:50:52 AM
> > Subject: Re: [cgma-dev] Multiple "TopologyBridge"s under one merged
> "RefEntity"
> > Before you send to different processors, can you detect the sense
> > difference, and give a correct loop direction for it?
> >
> > Jane
> >
> >
> > On Tue, Aug 30, 2011 at 12:33 PM, Hong-Jun Kim < hongjun at mcs.anl.gov >
> > wrote:
> >
> >
> > My parallel mesher pre-meshs interface shared region and sends the
> > mesh information to proper places in processors.
> > If the shared geometries in different processors have different
> > geometry directions, their mesh loop directions are confused.
> >
> > This problem happens only for "scatter" geometry distribution method
> > not for other methods like "broadcast and delete", then I am comparing
> > where the problems come from.
> >
> > Thanks for your comment.
> >
> > Hong-Jun
> >
> >
> >
> >
> > ----- Original Message -----
> > > From: "Jane Hu" < janejhu at gmail.com >
> > > To: "Hong-Jun Kim" < hongjun at mcs.anl.gov >
> > > Sent: Tuesday, August 30, 2011 10:55:25 AM
> > > Subject: Re: [cgma-dev] Multiple "TopologyBridge"s under one merged
> > > "RefEntity"
> > > Can I ask you why do you want to make the TopologyBridges still
> > > using
> > > the same edge direction? My 2-cent opinion is that each geometry by
> > > itself is consistent for its own senses, and for mesh purpose, I
> > > think
> > > you may go ahead mesh each one, just make sure the merged entity has
> > > the same mesh setting. Then when the meshed parts are going to be
> > > put
> > > together, you need to take special care if the TopoBridges are
> > > opposite senses, the parameters you are going to be merged should
> > > reverse too, or in other word, I think after parallel mesh, we need
> > > to
> > > rematch the nodes and connectivity on merged curves and faces.
> > >
> > > Jane
> > >
> > >
> > >
> > >
> > > On Mon, Aug 29, 2011 at 3:16 PM, Hong-Jun Kim < hongjun at mcs.anl.gov
> > > >
> > > wrote:
> > >
> > >
> > > Hi, all
> > >
> > > When I scatter geometries in parallel meshing, I need the merged
> > > geometry edges have the same geometry directions in every processor.
> > >
> > > However, since there are multiple "TopologyBridge"s under one merged
> > > "RefEntity", different TopologyBridge entities are scattered to
> > > processors and it makes inconsistent geometry edge direction.
> > >
> > > So, can I ask if there is any way forcing to export the same
> > > TopologyBridge entities for all merged entities?
> > >
> > > Moreover, "CAMergePartner" attribute is not used any more?
> > >
> > > Thanks.
> > >
> > > -----------------------------
> > > Hong-Jun Kim
> > > Post-doc researcher
> > > MCS, Argonne National Laboratory
> > > 9700 S. Cass Ave. B240/R2147
> > > Argonne, IL 60439
> > > 630-252-4791
> > > hongjun at mcs.anl.gov
> > > -----------------------------
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mcs.anl.gov/pipermail/cgma-dev/attachments/20110901/eb213d2f/attachment.htm>