My bad, I had not merged my libmesh version. Sorry.
Miguel
On Sep 22, 2015 2:42 PM, "John Peterson" wrote:
>
>
> On Tue, Sep 22, 2015 at 10:18 AM, John Peterson
> wrote:
>
>>
>>
>> On Tue, Sep 22, 2015 at 10:11 AM, Miguel Angel Salazar de Troya <
>> salazardetr...@gmail.com> wrote:
>>
>>> Hello
On Tue, Sep 22, 2015 at 10:18 AM, John Peterson
wrote:
>
>
> On Tue, Sep 22, 2015 at 10:11 AM, Miguel Angel Salazar de Troya <
> salazardetr...@gmail.com> wrote:
>
>> Hello
>>
>> I'm trying to install libmesh with vtk 6.3, but it cannot detect it. This
>> is the problem:
>>
>> configure:34048: /o
Hello
I'm trying to install libmesh with vtk 6.3, but it cannot detect it. This
is the problem:
configure:34048: /opt/local/bin/mpicxx -o conftest -std=gnu++11
-I/Users/salazardetro1/VTKInstall/include/vtk-6.3/ conftest.cpp
-Wl,-rpath,/Users/salazardetro1/VTKInstall/lib/
-L/Users/salazardetro
On Tue, Sep 22, 2015 at 10:11 AM, Miguel Angel Salazar de Troya <
salazardetr...@gmail.com> wrote:
> Hello
>
> I'm trying to install libmesh with vtk 6.3, but it cannot detect it. This
> is the problem:
>
> configure:34048: /opt/local/bin/mpicxx -o conftest -std=gnu++11
> -I/Users/salazardetro1/
Hi Antonio,
this is exactly the kind of functionality I needed; thanks for your help. It
would be great if this extension of vtkio would make it into one of the next
releases and/or release candidates.
Cheers
Erich
Am 28.02.2014 um 15:57 schrieb Antonio Cervone :
> i implemented this in
i implemented this in a branch here
https://github.com/capitalaslash/libmesh/tree/vtkio_extended
it is intended to be used like this
https://gist.github.com/capitalaslash/9272522
i will make a PR after adding some documentation and fixing indentation.
cheers
On Thu, Feb 27, 2014 at 4:02 PM, Ki
Can't speak for the others, but I wouldn't have any objection to
functionality along these lines being added (in fact, this might plug in
well for a proposal I just submitted). That said, none of the core
developers really use the VTK format (we all seem to use ExodusII), so you
(or someone else) w
I'd think you could easily refactor the current class and then derive from it
to implement your specialization, right? If that works for you I'd happily
accept a patch for it!
> On Feb 27, 2014, at 7:39 AM, "Erich Gaertig" wrote:
>
> I'm currently testing a workaround for the solution array f
I'm currently testing a workaround for the solution array fill you mentioned
below. Just as a general comment, from my point of view it would be great to
have a convenience method that similar to VTKIOs write_equation_systems fills
the _vtk_grid - variable with mesh and solution data and makes t
this is working for me
https://gist.github.com/capitalaslash/9246262
after making public a couple of functions and the _vtk_grid member.
in practice, what you need is a new method that sets up the vtk
structure, as it is done in the first part of
VTKIO::write_nodal_data().
in order to restore all
Am 26.02.2014 um 17:11 schrieb Kirk, Benjamin (JSC-EG311)
:
> On Feb 26, 2014, at 9:59 AM, John Peterson wrote:
>
>> This sounds like an interesting idea, but as you have discovered, VTKIO is
>> pretty far away from being able to do that as it stands.
>>
>> At the very least, you might be abl
On Feb 26, 2014, at 9:59 AM, John Peterson wrote:
> This sounds like an interesting idea, but as you have discovered, VTKIO is
> pretty far away from being able to do that as it stands.
>
> At the very least, you might be able to use it for inspiration to do what
> you want...
Agreed. An optio
On Wed, Feb 26, 2014 at 8:53 AM, Erich Gaertig wrote:
> If you, for example, want to visualize time-evolution, then after each
> time step, I would write data out, read it in and display it. I want to
> circumvent this cicle of writing/reading files to/from disk. This is why I
> was hoping, that
BTW - VTK reads Exodus files just fine if you would rather stick to a
format that is a little more mature in libMesh
Derek
Hi Derek,
but the problem is that, according to the ExodusII_IO documentation in libmesh,
there's no way of getting pointer access to the exodus-datastructure. As far
BTW - VTK reads Exodus files just fine if you would rather stick to a
format that is a little more mature in libMesh
Derek
On Wed, Feb 26, 2014 at 5:17 AM, Roy Stogner wrote:
>
> On Wed, 26 Feb 2014, Erich Gaertig wrote:
>
> > vtkUnstructuredGrid *grid;
> > grid = VTKIO (mesh).get_vtk_grid(
On Wed, 26 Feb 2014, Erich Gaertig wrote:
> vtkUnstructuredGrid *grid;
> grid = VTKIO (mesh).get_vtk_grid();
This constructs a temporary VTKIO object, gets a pointer to a grid
object from it, then *destructs the temporary*. If this code *didn't*
give you a segfault it would mean we had a memory
Hello, folks at libmesh;
I have an issue with the libmesh integration of VTK output. Maybe it's trivial
to solve and I just don't get it so I apologize already if my question is so
simple... The problem is the following: I am writing a little visualization
program with VTK which takes as input
17 matches
Mail list logo
