Hi Martin,
On 03/06/2014 02:08 AM, Martin Luethi wrote:
> Hi David
>
> David Knezevic writes:
>> I've found a case where ExodusII_IO::write_discontinuous_exodusII has a
>> weird bug. The example is here (on dropbox):
> visit shows the same problem (missing elements in exo) for
> discontinuous_pl
Thanks Roman, I'm hoping to set up the PR today. Could you tell me what
version of libMesh you created this patch from? That'll help a lot. It
*almost* applies cleanly on 0.9.3, but there are a few failures:
$ patch -p1 < ~/Desktop/0001-Add-Loop-subdivision-surface-elements.patch
--dry-run
pa
Thank you, Ben. I've created the patch from the commit with short hash
59fc67cf39.
-Roman
Am 2014-03-06 14:56 , schrieb Kirk, Benjamin (JSC-EG311):
> Thanks Roman, I'm hoping to set up the PR today. Could you tell me what
> version of libMesh you created this patch from? That'll help a lot.
I've got this set up on
https://github.com/libMesh/libmesh/tree/subdivision_surfaces
(subdivision_surfaces branch)
the new example, misc11, runs. I applied the patch as-is and then needed to
make some small tweaks to avoid duplicate symbols from template functions,
these tend to show up on OS
On Thu, Mar 6, 2014 at 10:06 AM, Kirk, Benjamin (JSC-EG311) <
benjamin.k...@nasa.gov> wrote:
> I've got this set up on
> https://github.com/libMesh/libmesh/tree/subdivision_surfaces
>
> (subdivision_surfaces branch)
>
> the new example, misc11, runs. I applied the patch as-is and then needed
> to
The only real collision I think might be in there is in DofMap, I believe Derek
just extended the API and this does as well.
Thanks John!
-Ben
On Mar 6, 2014, at 11:21 AM, "John Peterson"
mailto:jwpeter...@gmail.com>> wrote:
On Thu, Mar 6, 2014 at 10:06 AM, Kirk, Benjamin (JSC-EG311)
mai
On Thu, Mar 6, 2014 at 10:34 AM, Kirk, Benjamin (JSC-EG311) <
benjamin.k...@nasa.gov> wrote:
> The only real collision I think might be in there is in DofMap, I
> believe Derek just extended the API and this does as well.
>
> Thanks John!
>
OK, just finished the rebasing and pushed the result u
On Thu, Mar 6, 2014 at 12:02 PM, John Peterson wrote:
>
>
>
> On Thu, Mar 6, 2014 at 10:34 AM, Kirk, Benjamin (JSC-EG311) <
> benjamin.k...@nasa.gov> wrote:
>
>> The only real collision I think might be in there is in DofMap, I
>> believe Derek just extended the API and this does as well.
>>
>>
> On Mar 6, 2014, at 3:15 PM, "John Peterson" wrote:
>
> Just running 'make run' didn't seem to do this linking step.
Hmm... 'make check' would do the trick, I'm not even sure what 'make run' is -
is that perhaps some backwards compatible syntactic sugar of ours that's
malfunctioning??
--
On Thu, Mar 6, 2014 at 2:18 PM, Kirk, Benjamin (JSC-EG311) <
benjamin.k...@nasa.gov> wrote:
>
> > On Mar 6, 2014, at 3:15 PM, "John Peterson"
> wrote:
> >
> > Just running 'make run' didn't seem to do this linking step.
>
> Hmm... 'make check' would do the trick, I'm not even sure what 'make run
On 03/06/2014 06:44 AM, David Knezevic wrote:
Hi Martin,
On 03/06/2014 02:08 AM, Martin Luethi wrote:
Hi David
David Knezevic writes:
I've found a case where ExodusII_IO::write_discontinuous_exodusII has a
weird bug. The example is here (on dropbox):
visit shows the same problem (missing
I'd like to write out element-based data to an exodus file (again
related to discontinuous visualization). There is a function
ExodusII_IO::write_element_data in ExodusII_IO, but it's not clear to me
how to use it?
I'd like to use it in the same way as ExodusII_IO::write_nodal_data, but
it doe
On Thu, Mar 6, 2014 at 9:12 PM, David Knezevic
wrote:
> I'd like to write out element-based data to an exodus file (again
> related to discontinuous visualization). There is a function
> ExodusII_IO::write_element_data in ExodusII_IO, but it's not clear to me
> how to use it?
>
> I'd like to use i
On 03/06/2014 11:30 PM, John Peterson wrote:
On Thu, Mar 6, 2014 at 9:12 PM, David Knezevic
mailto:dkneze...@seas.harvard.edu>> wrote:
I'd like to write out element-based data to an exodus file (again
related to discontinuous visualization). There is a function
ExodusII_IO::wri
On Thu, Mar 6, 2014 at 9:35 PM, David Knezevic
wrote:
>
> On 03/06/2014 11:30 PM, John Peterson wrote:
>
>
>
>
> On Thu, Mar 6, 2014 at 9:12 PM, David Knezevic > wrote:
>
>> I'd like to write out element-based data to an exodus file (again
>> related to discontinuous visualization). There is a fu
On 03/06/2014 11:40 PM, John Peterson wrote:
On Thu, Mar 6, 2014 at 9:35 PM, David Knezevic
mailto:dkneze...@seas.harvard.edu>> wrote:
On 03/06/2014 11:30 PM, John Peterson wrote:
On Thu, Mar 6, 2014 at 9:12 PM, David Knezevic
mailto:dkneze...@seas.harvard.edu>>
wrote:
On Thu, Mar 6, 2014 at 9:53 PM, David Knezevic
wrote:
>
> On 03/06/2014 11:40 PM, John Peterson wrote:
>
>
>
>
> On Thu, Mar 6, 2014 at 9:35 PM, David Knezevic > wrote:
>
>>
>> On 03/06/2014 11:30 PM, John Peterson wrote:
>>
>>
>>
>>
>> On Thu, Mar 6, 2014 at 9:12 PM, David Knezevic <
>> dkneze..
I put this at the end of the main function in
systems_of_equations_ex6:
ExodusII_IO exo_io(mesh);
exo_io.write_timestep("test.exo", equation_systems, 0, 0.);
exo_io.write_element_data(equation_systems);
and I got this error:
Error writing nodal values.
18 matches
Mail list logo
