[SciPy-user] Scipy + Vision = LabView ?

Stef Mientki s.mientki@ru...
Thu Nov 1 13:16:54 CDT 2007

Matthieu Brucher wrote:
> 2007/10/31, Paul Barrett <pebarrett@gmail.com 
> <mailto:pebarrett@gmail.com>>:
>     No, you are not dreaming.  I also commented on this possibility
>     several years ago to some people in the SciPy community.
>     Unfortunately, I have not had the time or motivation to act on it.  It
>     would certainly be nice to have a basic package to show people.
>     You'll need to create a set of APIs so that you can connect to
>     instrumentation.  It shouldn't be too hard now that the interfaces
>     have been standardized.
> Sorry, it was in fact Vision and Viper I saw in the past as well.
Where can I find Viper ?
Google hates those common names ;-)
> The idea is great but the application, IMHO, is not quite optimal :
> - even for the tutorial, the rotate bloc should have two inputs, the 
> image and the rotation angle (this last factor could be given by the 
> result of another algorithm)
maybe 3, also one for the interpolation method ?
I would also make the major controls (for models with not too many 
in this case the rotation angle directly available with a small slider 
on the visual component.
> - what about multithreading in this model ?
> - what about flow control ? (which is really a huge issue that is 
> lacking in ITK for instance)
> - is there a way to create a bunch of blocks easily ?
Does LabView supports these ?
> All this has consequences on the interface. Besides, it would be very 
> great to use Traits as input and output blocks.
I Don't know Traits, so can't judge that.


More information about the SciPy-user mailing list