
Hi,
I just wanted to share a simple code that I wrote:
http://certik.github.com/visit_writer/
which uses Visit's VTK writer (written in C, wrapped in Python). I wrote a pcolor() function, that works just like the one in matplotlib, only it produces a vtk file (resp. data that you then pass to the vtk writer). See the pictures and demos on the webpage above.
With this, it's very easy to write VTK files, no need to fiddle with the ASCII format --- btw, the module can produces a binary VTK file too, so it really saved me lots of troubles.
Ondrej

Hi Ondrej,
Ondrej Certik wrote:
Hi,
I just wanted to share a simple code that I wrote:
http://certik.github.com/visit_writer/
which uses Visit's VTK writer (written in C, wrapped in Python). I wrote a pcolor() function, that works just like the one in matplotlib, only it produces a vtk file (resp. data that you then pass to the vtk writer). See the pictures and demos on the webpage above.
With this, it's very easy to write VTK files, no need to fiddle with the ASCII format --- btw, the module can produces a binary VTK file too, so it really saved me lots of troubles.
Nice! So the Visit's license (LLNL stuff) is compatible with the new BSD license, right?
r.

On Mon, Jul 13, 2009 at 5:20 AM, Robert Cimrman<cimr...@ntc.zcu.cz> wrote:
Hi Ondrej,
Ondrej Certik wrote:
Hi,
I just wanted to share a simple code that I wrote:
http://certik.github.com/visit_writer/
which uses Visit's VTK writer (written in C, wrapped in Python). I wrote a pcolor() function, that works just like the one in matplotlib, only it produces a vtk file (resp. data that you then pass to the vtk writer). See the pictures and demos on the webpage above.
With this, it's very easy to write VTK files, no need to fiddle with the ASCII format --- btw, the module can produces a binary VTK file too, so it really saved me lots of troubles.
Nice! So the Visit's license (LLNL stuff) is compatible with the new BSD license, right?
Ah, I forgot to check this, I just saw BSD, but you are right, they added some stuff in there too:
https://wci.llnl.gov/codes/visit/copyright.html
But it's just the "Additional BSD Notice" and it doesn't say what you should or should not do. It only says that "we are not doing any warranty".
So I think it is just BSD.
Ondrej
participants (2)
-
Ondrej Certik
-
Robert Cimrman