Hi,
you may have noticed that http://sfepy.org, that should point to [1], either
does not work, or points to the main google site. That's because something
changed, and my old DNS settings (ip 69.56.173.218) do not work anymore.
I have tried changing the ip to 209.85.227.100 which is what I found to be the
new ip of code.google.com (one of many), but that just redirects to google.com.
Is there anyone experienced more with those issues around?
r.
[1] http://code.google.com/p/sfepy/
Hi,
could this be useful? I do not see license at the package site...
r.
-------- Original Message --------
Subject: [SciPy-User] Announcement: Self-contained Python module to write
binary VTK files.
Date: Mon, 29 Nov 2010 09:45:29 +0100
From: Paulo Herrera <pauloa....(a)gmail.com>
Reply-To: SciPy Users List <scipy...(a)scipy.org>
To: scipy...(a)scipy.org
Hello everyone,
This is my first post to this list.
I would like to announce the first release of a Python module I wrote to export
scientific data to binary VTK files. The source code for the module can be
downloaded from its Mercurial repository at bitbucket. To get a copy, type on
terminal window:
hg clone https://pauloh@bitbucket.org/pauloh/pyevtk
PyEVTK (Python Export VTK) package allows exporting data to binary VTK files for
visualization and data analysis with any of the visualization packages that
support VTK files, e.g. Paraview, VisIt and Mayavi. EVTK does not depend on any
external library (e.g. VTK), so it is easy to install in different systems.
The package is composed of a set of Python files and a small C/Cython library
that provides performance critical routines. PyEVTK provides low and high level
interfaces. While the low level interface can be used to export data that is
stored in any type of container, the high level functions make easy to export
data stored in Numpy arrays. In addition, it provides a helper class to create
pvd files that can be imported into Paraview to visualize time dependent data
series.
PyEVTK is released under the GPL 3 open source license. A copy of the license is
included in the src directory.
Please see below for an example of how to use the high level routines. More
examples
are included in the package.
I hope you will find this package useful and I look forward to getting your
feedback.
Paulo
High-level interface example:
=============================
from evtk.hl import imageToVTK
import numpy as np
# Dimensions
nx, ny, nz = 6, 6, 2
ncells = nx * ny * nz
npoints = (nx + 1) * (ny + 1) * (nz + 1)
# Variables
pressure = np.random.rand(ncells).reshape( (nx, ny, nz), order = 'C')
temp = np.random.rand(npoints).reshape( (nx + 1, ny + 1, nz + 1))
imageToVTK("./image", cellData = {"pressure" : pressure}, pointData = {"temp" :
temp} )
_______________________________________________
SciPy-User mailing list
SciPy...(a)scipy.org
http://mail.scipy.org/mailman/listinfo/scipy-user
FYI: I have regenerated the development docs with the latest Sphinx, which has
a cool extension (viewcode) than can link the docstrings to the actual code,
see [1].
r.
[1] http://docs.sfepy.org/doc-devel
FYI: there is now a very interesting discussion going on
numpy-di...(a)scipy.org that resulted in [1], see also the forwarded
message below. Shall we create a similar document for sfepy?
r.
[1] http://docs.scipy.org/doc/numpy/dev/gitwash/index.html
---------- Forwarded message ----------
Date: Tue, 12 Oct 2010 11:55:04 -0700
From: Fernando Perez <fpere...(a)gmail.com>
Reply-To: Discussion of Numerical Python <numpy-di...(a)scipy.org>
To: Discussion of Numerical Python <numpy-di...(a)scipy.org>
Subject: Re: [Numpy-discussion] Development workflow
On Tue, Oct 12, 2010 at 6:51 AM, Vincent Davis <vin...(a)vincentdavis.net> wrote:
> Lots of good reading :) Just thought I'd put a plug in for the
> contributor that may make only a few contributions and needs a simple
> workflow to do so. It would be great if they could just..
> make there own fork
> clone the branch of interest
> make changes
> push to there own fork
> request pull.
>
> I think part of the point of moving to git was to make these types of
> contributions easier. Ideally there would be instructions here
> http://www.numpy.org/
>
Matthew Brett has prepared a document with much of this in ready-to-digest form:
http://github.com/matthew-brett/gitwash
It's meant for easy inclusion in other projects (if they agree with
the worfklow it presents), here it is for example rendered with the
urls pointing to ipython repos:
http://ipython.scipy.org/doc/nightly/html/development/gitwash/index.html
Cheers,
f
_______________________________________________
NumPy-Discussion mailing list
NumPy-Di...(a)scipy.org
http://mail.scipy.org/mailman/listinfo/numpy-discussion
