On Fri, 10 Jun 2011, Cody Permann wrote:
> I just commited an app (r4583) to update subdomain, sideset, and
> nodeset IDs on existing meshes.
Thanks!
> By the way, I think there is a
> small corner case you are missing in the app you committed
> yesterday. On line 151 of meshbcid.C you are usi
Roy,
I just commited an app (r4583) to update subdomain, sideset, and nodeset IDs on
existing meshes. By the way, I think there is a small corner case you are
missing in the app you committed yesterday. On line 151 of meshbcid.C you are
using the "scalar" version of the boundary_id function.
On Jun 9, 2011, at 4:49 PM, Roy Stogner wrote:
>
> On Thu, 9 Jun 2011, Cody Permann wrote:
>
>> If you don't mind, could you get the ID updater tool committed or
>> otherwise sent to us? I'd like to use it to do some testing with
>> the patch before we commit something.
>
> I don't mind, but
On Thu, 9 Jun 2011, Cody Permann wrote:
> If you don't mind, could you get the ID updater tool committed or
> otherwise sent to us? I'd like to use it to do some testing with
> the patch before we commit something.
I don't mind, but I also don't have it. Sorry I wasn't clear:
meshbcid just wor
On Jun 9, 2011, at 4:23 PM, Roy Stogner wrote:
>
> On Thu, 9 Jun 2011, Derek Gaston wrote:
>
>> We'll let them know about it...
>
> Thanks.
>
>> I say we check the changes into libMesh... and if we ever get the
>> Exodus guys to incorporate the changes we can then update the
>> sources in lib
On Thu, 9 Jun 2011, Derek Gaston wrote:
> We'll let them know about it...
Thanks.
> I say we check the changes into libMesh... and if we ever get the
> Exodus guys to incorporate the changes we can then update the
> sources in libMesh. But for now at least things will work
> sanely.
Unles
On Jun 9, 2011, at 3:22 PM, Roy Stogner wrote:
> Have you sent those changes upstream, to see what they think? If we
> can upgrade to future Exodus versions without having to apply our own
> patches each time, then I'd be thrilled to no longer be applying an
> ugly hack to our Exodus subdomain I
On Jun 9, 2011, at 3:22 PM, Roy Stogner wrote:
>
> On Thu, 9 Jun 2011, Cody Permann wrote:
>
>> The final impacts of this change center around the Seacas tools from
>> Sandia. It turns out that some of those tools make assumptions that
>> IDs inside of exodus are positive which might cause a f
On Thu, 9 Jun 2011, Cody Permann wrote:
> The final impacts of this change center around the Seacas tools from
> Sandia. It turns out that some of those tools make assumptions that
> IDs inside of exodus are positive which might cause a few issues
> going forward. I already created a patch to f
Developers and Exodus users,
Instead of doing all this odd mapping and un-mapping I started digging into the
underlying reason why we weren't writing zero IDs to the exodus files. It
turns out that when the exodus files are constructed through the normal API, a
number of "mesh-related" field
On Jun 8, 2011, at 1:07 PM, John Peterson wrote:
> On Wed, Jun 8, 2011 at 1:02 PM, Cody Permann wrote:
>>
>> On Jun 8, 2011, at 12:56 PM, Roy Stogner wrote:
>>
>>>
>>> On Wed, 8 Jun 2011, John Peterson wrote:
>>>
On Wed, Jun 8, 2011 at 8:49 AM, Cody Permann wrote:
> I've just about
On Wed, Jun 8, 2011 at 1:02 PM, Cody Permann wrote:
>
> On Jun 8, 2011, at 12:56 PM, Roy Stogner wrote:
>
>>
>> On Wed, 8 Jun 2011, John Peterson wrote:
>>
>>> On Wed, Jun 8, 2011 at 8:49 AM, Cody Permann wrote:
I've just about finished up the patch to allow us to configure
subdomain_id
On Jun 8, 2011, at 12:56 PM, Roy Stogner wrote:
>
> On Wed, 8 Jun 2011, John Peterson wrote:
>
>> On Wed, Jun 8, 2011 at 8:49 AM, Cody Permann wrote:
>>> I've just about finished up the patch to allow us to configure
>>> subdomain_id_type with ./configure. The current syntax I'm using
>>> is
On Wed, 8 Jun 2011, John Peterson wrote:
On Wed, Jun 8, 2011 at 8:49 AM, Cody Permann wrote:
I've just about finished up the patch to allow us to configure
subdomain_id_type with ./configure. The current syntax I'm using
is "--with-subdomain-id-bytes=<1|2|4>" defaulting to "2".
This looks
On Wed, Jun 8, 2011 at 8:49 AM, Cody Permann wrote:
> I've just about finished up the patch to allow us to configure
> subdomain_id_type with ./configure. The current syntax I'm using is
> "--with-subdomain-id-bytes=<1|2|4>" defaulting to "2".
> I'm running into an issue now with our regressio
I've just about finished up the patch to allow us to configure
subdomain_id_type with ./configure. The current syntax I'm using is
"--with-subdomain-id-bytes=<1|2|4>" defaulting to "2".
I'm running into an issue now with our regression test suite where I'm getting
diffs on tests that use the m
16 matches
Mail list logo
