labpython-users — LabPython users mailing list

[LabPython-Users] FW: Importing Modules

[Rolf K. <r.k...@hc...>]

Gustav Montgomerie [mailto:gu...@gm...] wrote:

>I have just started using LabView (8.2) and LabPython and I am having
trouble importing >modules. My code essentially looks like this:
>
>
>import socket

Before you can do any import you need to set the module path in the Python
session that you created. That is the path where the Python loader can find
the modules.

LabPython interfaces to the Python core and makes it available to a LabVIEW
application but does not setup anything explicitedly itself. Anything that
is not hardwired in the Python DLL will have to be setup by you when
creating the Python session. For your case you want to add the path where
your socket module is found to the sys.path variable before attempting to
issue an import command.

Rolf Kalbermatter

Re: [LabPython-Users] Importing Modules

[Rolf K. <r.k...@hc...>]

Gustav Montgomerie [mailto:gu...@gm...] wrote:

>I have just started using LabView (8.2) and LabPython and I am having
trouble importing >modules. My code essentially looks like this:
>
>
>import socket

Before you can do any import you need to set the module path in the Python
session that you created. That is the path where the Python loader can find
the modules.

LabPython interfaces to the Python core and makes it available to a LabVIEW
application but does not setup anything explicitedly itself. Anything that
is not hardwired in the Python DLL will have to be setup by you when
creating the Python session. For your case you want to add the path where
your socket module is found to the sys.path variable before attempting to
issue an import command.

Rolf Kalbermatter

[LabPython-Users] Numpy and labpython bug

[Christopher R. <Chr...@no...>]

I've just installed LabPython on LabVIEW 8.5 but I'm having trouble. I've changed the Python version to 2.6, and I can import any other package (pyglet, sys, csv for example) but if I try to import numpy or any other package that is dependent on it (scipy or matplotlib for example) it throws an error:

Runtime error!

Program: C...

R6034
An application has made an attempt to load the C runtime library incorrectly. Please contact the application's support team for more information.

I can load numpy fine in a python shell, or using idle. I'm using the Enthought package on Windows if that is of any use. Any help will be most gratefully received.

Chris
This message and any attachment are intended solely for the addressee and may contain confidential information. If you have received this message in error, please send it back to me, and immediately delete it.   Please do not use, copy or disclose the information contained in this message or in any attachment.  Any views or opinions expressed by the author of this email do not necessarily reflect the views of the University of Nottingham.

This message has been checked for viruses but the contents of an attachment
may still contain software viruses which could damage your computer system:
you are advised to perform your own checks. Email communications with the
University of Nottingham may be monitored as permitted by UK legislation.

[LabPython-Users] Importing Modules

[Gustav M. <gu...@gm...>]

Hi,

I have just started using LabView (8.2) and LabPython and I am having
trouble importing modules. My code essentially looks like this:


import socket

class CLASS:

    def __init__(self,attribute):
        self.item = socket.socket()
        [...]

When running the code in LabView (filename Test2.vi), via New Session -> Set
Script -> Compile -> Execute Script, I get the following error message:


Error 1050 occurred at PYTHON Execute Script__ogtk.vi
->Test2.vi:<type 'exceptions.NameError'>,
global name 'socket' is not defined


The code works just fine outside of LabView. Is there some barrier I am
unaware of, and is there a way to avoid/cirumvent it?

Thanks!

Gustav

[LabPython-Users] What happened to script node?

[Seth B. <se...@te...>]

I was wondering what happened to the python scripting node which appears
in the instructions on this website in step 3:

http://labpython.sourceforge.net/scriptnode.html

I cant seem to find it in the openg distribution of labpython!

Re: [LabPython-Users] dependency doesn't make sense

[Jim K. <jim...@gm...>]

Hi Mark,

I would just disregard this error message. The declared dependency is wrong
in labpython and should have stated >= 0.2 instead of >= 2.0.

-Jim

On Mon, Nov 16, 2009 at 3:51 PM, Mark Garnett <mcg...@gm...> wrote:

> Hi everyone!
>
> I am using VIPM to install LabPython 1.2. However, VIPM indicates a
> broken dependency, saying it needs an open g library,
> ogrsc_dynamicpalette, to be version 2.0 or later. As far as I know,
> the current version of this library is 0.17, as indicated by the OpenG
> software portal, while VIPM indicates that it is 0.18.  What is going
> on here? I haven't had to import external code in labview before or
> use VIPM, so please forgive me if this question has been asked a
> million times before. I would very much appreciate some help though.
>
> Regards,
>
> Mark Garnett
>
>
> ------------------------------------------------------------------------------
> Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
> trial. Simplify your report design, integration and deployment - and focus
> on
> what you do best, core application coding. Discover what's new with
> Crystal Reports now.  http://p.sf.net/sfu/bobj-july
> _______________________________________________
> LabPython-Users mailing list
> Lab...@li...
> https://lists.sourceforge.net/lists/listinfo/labpython-users
>

[LabPython-Users] dependency doesn't make sense

[Mark G. <mcg...@gm...>]

Hi everyone!

I am using VIPM to install LabPython 1.2. However, VIPM indicates a
broken dependency, saying it needs an open g library,
ogrsc_dynamicpalette, to be version 2.0 or later. As far as I know,
the current version of this library is 0.17, as indicated by the OpenG
software portal, while VIPM indicates that it is 0.18.  What is going
on here? I haven't had to import external code in labview before or
use VIPM, so please forgive me if this question has been asked a
million times before. I would very much appreciate some help though.

Regards,

Mark Garnett

Re: [LabPython-Users] 64-bit python26.dll incompatibility?

[Rolf K. <r.k...@hc...>]

Vladimir Brik [mailto:no...@gm...] wrote:

> Is it possible to get LabPython to work with 64-bit Python?

It's certainly possible but I'm not setup to do that since I do
not have a 64 bit system nor have I planned to install that anytime
soon.
 
> LabPython 1.2 doesn't work with 64-bit python26.dll (Python 
> 2.6.2) on Vista. VIs fail saying that Python server cannot be 
> found. Everything seems to work fine with the 32-bit dll.

I would expect it to be a bit more work than just recompiling in
a Windows 64 Bit OS and a Visual C version that supports 64 Bit
compilation.

First I use mainly Visual C 6.0 for all LabVIEW related C projects
which does certainly not support 64 Bit creation. Porting of the
project files will be therefore necessary.

Second while the code is written in a way to be fairly platform
independent I had at the time of creation no ideas of how 64 Bit
programming would look like nor what intrinsicacies it would have
when writing C code. So I would expect some minor C source code
modifications to be necessary to make it both compile and work
correctly under 64 Bit.

If you feel up for the task you can go and grab the C sources
from sourceforge and try on your own. Certainly don't hold your
breath for me to do it as you would likely suffer from lack of
oxygene :-)

Rolf Kalbermatter

[LabPython-Users] 64-bit python26.dll incompatibility?

[Vladimir B. <no...@gm...>]

Hello,

Is it possible to get LabPython to work with 64-bit Python?

LabPython 1.2 doesn't work with 64-bit python26.dll (Python 2.6.2) on
Vista. VIs fail saying that Python server cannot be found. Everything
seems to work fine with the 32-bit dll.


Thanks,

Vladimir

Re: [LabPython-Users] Source code

[Kenneth M. <xke...@gm...>]

Jim,

     The latest version of LabPython seems to work pretty well.

Regards,
Ken

On Feb 4, 2009, at 7:30 PM, Glen Shennan wrote:

> Hi all,
>
> I'm worried that I'm missing something really simple here but where  
> is the source code for LabPython?  Can't find it on the labpython  
> site or on the download page on sourceforge...
>
> Glen
> ------------------------------------------------------------------------------
> Create and Deploy Rich Internet Apps outside the browser with  
> Adobe(R)AIR(TM)
> software. With Adobe AIR, Ajax developers can use existing skills  
> and code to
> build responsive, highly engaging applications that combine the  
> power of local
> resources and data with the reach of the web. Download the Adobe AIR  
> SDK and
> Ajax docs to start building applications today-http://p.sf.net/sfu/adobe-com_______________________________________________
> LabPython-Users mailing list
> Lab...@li...
> https://lists.sourceforge.net/lists/listinfo/labpython-users

Re: [LabPython-Users] Source code

[Rolf K. <rol...@ci...>]

There is no source code package to download. You use CVS to check out the
source code from sourceforge.
 
Informations as to how you can do that are visible in the Code->CVS menu of
the lappython project on sourceforge.
You may see at first a condensed menu with a "More" menu at the end. Select
More to see the Code and other additional menus.
 

Rolf Kalbermatter


 


  _____  

From: Glen Shennan [mailto:gle...@gm...] 
Sent: Thursday, February 05, 2009 2:30 AM
To: Lab...@li...
Subject: [LabPython-Users] Source code


Hi all,

I'm worried that I'm missing something really simple here but where is the
source code for LabPython?  Can't find it on the labpython site or on the
download page on sourceforge...

Glen

[LabPython-Users] Source code

[Glen S. <gle...@gm...>]

Hi all,

I'm worried that I'm missing something really simple here but where is the
source code for LabPython?  Can't find it on the labpython site or on the
download page on sourceforge...

Glen

Re: [LabPython-Users] Source

[Glen S. <gle...@gm...>]

Great!

I'm on holidays from now until the 7th of January (I'm at an internet cafe
right now) so won't be able to do much until then but if you can perhaps get
together an idea of what might be involved then I can begin to get a picture
of what I can contribute.  I have some C/C++ experience, some Python and a
reasonable amount of LabView experience, though virtually all of that comes
from the algorithm implementation perspective, I have very little systems
programming experience, though I am keen to learn.  I'm running Ubuntu 8.04,
64 bit version but have access to Windows machines with LabView and Python
(and C/C++ if needs be) at uni.  I really don't know what the first step
might be so the ball's very much in your court at the moment so let me know
what needs to be done and I'll get back to you within the week.

Cheers,
Glen

2009/1/2 Kenneth Miller <xke...@gm...>

> Glen,
>    I'm in, let's talk.
>
> Regards,
> Ken
>
>  On Jan 1, 2009, at 11:14 PM, Glen Shennan wrote:
>
>  Hi all,
>
> I have no idea of the magnitude of what I'm proposing and not being much of
> programmer I don't know how much help I can be but I have significant
> interest in using LabPython with the numpy and scipy libraries.  If
> LabPython is to be updated then can this be made to happen?  If this is a
> do-able thing then I'd certainly be interested in helping out with testing
> and documentation, and I'd be keen to learn what I can of the programming
> side along the way.
>
> Glen
>
> 2009/1/1 Rolf Kalbermatter <rol...@ci...>
>
>>  Hi Jim,
>>
>> It's available in CVS, here:
>>
>> http://sourceforge.net/cvs/?group_id=61043
>>
>> Do you know how to do a CVS checkout?
>>
>> Also, what updates were you considering?
>>
>> Probably he wants to make it link to Python 2.6 or 3.0 by default.
>> While 2.6 most likely will work I have no idea if 3.0 would work at all.
>>
>> But there is no strict need to change the LabPython sources to link to
>> different shared library version.
>> The function PYTHON Set Server Path.vi can be used to set a DLL name, with
>> or without the full path,
>> to link to a specific Pythin shared library implementation.
>>
>> It would be the first thing to try out if LabPython even works with a new
>> version of Python. And the setting
>> for the Python DLL to use will be added to the labview.ini file (or your
>> <app>.ini file for a build application)
>> and persist between restarts.
>>
>> Rolf Kalbermatter
>>
>>
>> ------------------------------------------------------------------------------
>>
>> _______________________________________________
>> LabPython-Users mailing list
>> Lab...@li...
>> https://lists.sourceforge.net/lists/listinfo/labpython-users
>>
>>
>
> ------------------------------------------------------------------------------
> _______________________________________________
> LabPython-Users mailing list
> Lab...@li...
> https://lists.sourceforge.net/lists/listinfo/labpython-users
>
>
>
>
> ------------------------------------------------------------------------------
>
> _______________________________________________
> LabPython-Users mailing list
> Lab...@li...
> https://lists.sourceforge.net/lists/listinfo/labpython-users
>
>

Re: [LabPython-Users] Source

[Kenneth M. <xke...@gm...>]

Glen,

    I'm in, let's talk.

Regards,
Ken

On Jan 1, 2009, at 11:14 PM, Glen Shennan wrote:

> Hi all,
>
> I have no idea of the magnitude of what I'm proposing and not being  
> much of programmer I don't know how much help I can be but I have  
> significant interest in using LabPython with the numpy and scipy  
> libraries.  If LabPython is to be updated then can this be made to  
> happen?  If this is a do-able thing then I'd certainly be interested  
> in helping out with testing and documentation, and I'd be keen to  
> learn what I can of the programming side along the way.
>
> Glen
>
> 2009/1/1 Rolf Kalbermatter <rol...@ci...>
> Hi Jim,
> It's available in CVS, here:
>
> http://sourceforge.net/cvs/?group_id=61043
>
> Do you know how to do a CVS checkout?
>
> Also, what updates were you considering?
> Probably he wants to make it link to Python 2.6 or 3.0 by default.
> While 2.6 most likely will work I have no idea if 3.0 would work at  
> all.
>
> But there is no strict need to change the LabPython sources to link  
> to different shared library version.
> The function PYTHON Set Server Path.vi can be used to set a DLL  
> name, with or without the full path,
> to link to a specific Pythin shared library implementation.
>
> It would be the first thing to try out if LabPython even works with  
> a new version of Python. And the setting
> for the Python DLL to use will be added to the labview.ini file (or  
> your <app>.ini file for a build application)
> and persist between restarts.
>
> Rolf Kalbermatter
>
> ------------------------------------------------------------------------------
>
> _______________________________________________
> LabPython-Users mailing list
> Lab...@li...
> https://lists.sourceforge.net/lists/listinfo/labpython-users
>
>
> ------------------------------------------------------------------------------
> _______________________________________________
> LabPython-Users mailing list
> Lab...@li...
> https://lists.sourceforge.net/lists/listinfo/labpython-users

Re: [LabPython-Users] Source

[Glen S. <gle...@gm...>]

Hi all,

I have no idea of the magnitude of what I'm proposing and not being much of
programmer I don't know how much help I can be but I have significant
interest in using LabPython with the numpy and scipy libraries.  If
LabPython is to be updated then can this be made to happen?  If this is a
do-able thing then I'd certainly be interested in helping out with testing
and documentation, and I'd be keen to learn what I can of the programming
side along the way.

Glen

2009/1/1 Rolf Kalbermatter <rol...@ci...>

>  Hi Jim,
>
> It's available in CVS, here:
>
> http://sourceforge.net/cvs/?group_id=61043
>
> Do you know how to do a CVS checkout?
>
> Also, what updates were you considering?
>
> Probably he wants to make it link to Python 2.6 or 3.0 by default.
> While 2.6 most likely will work I have no idea if 3.0 would work at all.
>
> But there is no strict need to change the LabPython sources to link to
> different shared library version.
> The function PYTHON Set Server Path.vi can be used to set a DLL name, with
> or without the full path,
> to link to a specific Pythin shared library implementation.
>
> It would be the first thing to try out if LabPython even works with a new
> version of Python. And the setting
> for the Python DLL to use will be added to the labview.ini file (or your
> <app>.ini file for a build application)
> and persist between restarts.
>
> Rolf Kalbermatter
>
>
> ------------------------------------------------------------------------------
>
> _______________________________________________
> LabPython-Users mailing list
> Lab...@li...
> https://lists.sourceforge.net/lists/listinfo/labpython-users
>
>

Re: [LabPython-Users] Source

[Rolf K. <rol...@ci...>]

Hi Jim,

It's available in CVS, here:

http://sourceforge.net/cvs/?group_id=61043

Do you know how to do a CVS checkout?

Also, what updates were you considering?

Probably he wants to make it link to Python 2.6 or 3.0 by default.
While 2.6 most likely will work I have no idea if 3.0 would work at all.
 
But there is no strict need to change the LabPython sources to link to
different shared library version.
The function PYTHON Set Server Path.vi can be used to set a DLL name, with
or without the full path,
to link to a specific Pythin shared library implementation.
 
It would be the first thing to try out if LabPython even works with a new
version of Python. And the setting
for the Python DLL to use will be added to the labview.ini file (or your
<app>.ini file for a build application)
and persist between restarts.
 
Rolf Kalbermatter

Re: [LabPython-Users] Source

[Jim K. <jim...@gm...>]

Hi Ken,

It's available in CVS, here:

http://sourceforge.net/cvs/?group_id=61043

Do you know how to do a CVS checkout?

Also, what updates were you considering?

-Jim


On Wed, Dec 31, 2008 at 2:03 PM, Kenneth Miller <xke...@gm...> wrote:

> Is the LabPython source available? I'd like to consider updating it.
>
> Regards,
> Ken
>
>
> ------------------------------------------------------------------------------
> _______________________________________________
> LabPython-Users mailing list
> Lab...@li...
> https://lists.sourceforge.net/lists/listinfo/labpython-users
>

[LabPython-Users] Source

[Kenneth M. <xke...@gm...>]

Is the LabPython source available? I'd like to consider updating it.

Regards,
Ken

Re: [LabPython-Users] LabPython with rpy problem

[Christian C. <chr...@em...>]

Thanks it works..

On Mon, 20 Oct 2008 20:11:51 +0200, Rolf Kalbermatter  
<r.k...@hc...> wrote:

> Hello Christian,
>
>> I tried to use rpy through labpyhton. But the enclosed
>> rpy_simple.vi allows just one execution. It's not possible to
>> rerun rpy a second time without a restart of LabView. It
>> seems that LabPython doesn't clean/close/disconnect correctly
>> after executing once.
>>
>> I have installed:
>>
>> LabPyton 1.2.2 (LabPython is part of OpenG lib for LabView)
>> numpy 1.2.0-win32 ActivePython 2.5.2.2-win32x86 (in order to
>> get rpy using Mark Hammond's py
>> extensions)
>> rpy-1.0.3-R-2.7.0-win32-py2.5.exe
>> Python 2.5.2
>> R 2.7.0
>> LabView 2.5
>
> I'm not sure about the exact interactions here and why this happens but  
> am
> currently not working with Python nor do I have time to look into  
> LabPython.
>
> Workaround is to not close the Python session but instead just open it  
> once
> in the beginning and then keep it open, optionally setting a new  
> expression,
> and then executing that expression repeatedly using the same session.
>
> And you are right LabPython does not close completely from the python  
> kernel
> once it connects. It does however clean all resources it allocated but  
> that
> might be not enough in case of external modules that might expect some
> special throw out of memory after use.
>
> LabVIEW restarting shouldn't really be necessary as it should be enough  
> to
> close all LabVIEW VIs making use of LabPython. If that is not enough the
> issue is even more obscure than I would expect.
>
> Rolf Kalbermatter
>
>
> -------------------------------------------------------------------------
> This SF.Net email is sponsored by the Moblin Your Move Developer's  
> challenge
> Build the coolest Linux based applications with Moblin SDK & win great  
> prizes
> Grand prize is a trip for two to an Open Source event anywhere in the  
> world
> http://moblin-contest.org/redirect.php?banner_id=100&url=/
> _______________________________________________
> LabPython-Users mailing list
> Lab...@li...
> https://lists.sourceforge.net/lists/listinfo/labpython-users



-- 
-------
Christian Conrad
European Molecular Biology Laboratory
Meyerhofstr. 1
69117 Heidelberg
Germany
cc...@em...
room 4.53C
+49 6221 387 8855

Re: [LabPython-Users] LabPython with rpy problem

[Rolf K. <r.k...@hc...>]

Hello Christian,

> I tried to use rpy through labpyhton. But the enclosed 
> rpy_simple.vi allows just one execution. It's not possible to 
> rerun rpy a second time without a restart of LabView. It 
> seems that LabPython doesn't clean/close/disconnect correctly 
> after executing once.
> 
> I have installed:
> 
> LabPyton 1.2.2 (LabPython is part of OpenG lib for LabView) 
> numpy 1.2.0-win32 ActivePython 2.5.2.2-win32x86 (in order to 
> get rpy using Mark Hammond's py
> extensions)
> rpy-1.0.3-R-2.7.0-win32-py2.5.exe
> Python 2.5.2
> R 2.7.0
> LabView 2.5

I'm not sure about the exact interactions here and why this happens but am
currently not working with Python nor do I have time to look into LabPython.

Workaround is to not close the Python session but instead just open it once
in the beginning and then keep it open, optionally setting a new expression,
and then executing that expression repeatedly using the same session.

And you are right LabPython does not close completely from the python kernel
once it connects. It does however clean all resources it allocated but that
might be not enough in case of external modules that might expect some
special throw out of memory after use.

LabVIEW restarting shouldn't really be necessary as it should be enough to
close all LabVIEW VIs making use of LabPython. If that is not enough the
issue is even more obscure than I would expect.

Rolf Kalbermatter 

[LabPython-Users] labpython with rpy

[Christian C. <chr...@em...>]

Hi,

I tried to use rpy through labpyhton. But the enclosed rpy_simple.vi  
allows just one execution. It's not possible to rerun rpy a second time  
without a restart of LabView. It seems that LabPython doesn't  
clean/close/disconnect correctly after executing once.

I have installed:

LabPyton 1.2.2 (LabPython is part of OpenG lib for LabView)
numpy 1.2.0-win32
ActivePython 2.5.2.2-win32x86 (in order to get rpy using Mark Hammond's py  
extensions)
rpy-1.0.3-R-2.7.0-win32-py2.5.exe
Python 2.5.2
R 2.7.0
LabView 2.5

Does anyone have a workaround/solution for this?


Regards

Christian

-- 
-------
Christian Conrad
European Molecular Biology Laboratory
Meyerhofstr. 1
69117 Heidelberg
Germany
cc...@em...
room 4.53C
+49 6221 387 8855

Re: [LabPython-Users] Numpy and Scipy

[Jim K. <jim...@gm...>]

Hello All,

I'm sure that Rolf would happily accept purchase orders for any new features
that you would like ;)

Cheers,

-Jim


On Thu, Jun 5, 2008 at 3:40 PM, Glen Shennan <gle...@gm...> wrote:

> Hi again,
>
> I would like voice my thanks for labpython as well, it's generally a great
> piece of software, it's just unfortunate that numpy support is not there
> since I was, as Luc said, using python/numpy/matplotlib as a matlab
> replacement.
>
> Cheers,
> Glen
>
> 2008/6/5 Luc Estebanez <luc...@en...>:
>
> Hi all,
>>
>> I would like to add my vote to support the idea to add a numpy interface
>> for Labpython! This would enhance greatly this piece of software since
>> numpy has really become the standard for numerical stuff in python, and I
>> suppose many users of Labpython are using python as a 'matlab'
>> replacement.
>>
>> Thank you for all the hard work,
>>
>> Gratefully,
>>
>> luc
>>
>> > Hi Glen
>> >
>> > So numpy and scipy functions can be used as long as native data types
>> are
>> > used?  That may cause some problems since I am trying to perform matrix
>> > operations.  I am using LabVIEW 8.20 with python 2.5.2 and labpython
>> 1.2.2
>> > on Windows XP.  I am trying to pass a 2D array of floats to python.
>> >
>> > It should be possible. The way I solved arrays in LabPython was to treat
>> > them as lists. Consequently 2D arrays are lists of lists. It is not very
>> > efficient but Python does even in 2.5 not give you an exported array C
>> API
>> > with which I could retrieve any information from a numpy array, despite
>> > the
>> > fact that the Python core does know an array datatype.
>> >
>> > It would be possible to add something like that to LabPython by making
>> use
>> > of the numpy extension and its exported C API but at the time I was
>> > developing LabPython numpy was just in its infancy taking over from its
>> > predecessor the numerical library. That API seemed not at all stable to
>> me
>> > at that point and making LabPython depend only softly on it (meaning it
>> > would still work but without support of numpy datatypes) would also be
>> > some
>> > serious thinkering.
>> >
>> > I may take a look how numpy interfaces with Python to solve the array
>> > interface issue but to do it right would be a majour undertaking and I
>> > have
>> > a real job to do that pays the bills.
>> >
>> > Rolf Kalbermatter
>> >
>> -------------------------------------------------------------------------
>> > Check out the new SourceForge.net Marketplace.
>> > It's the best place to buy or sell services for
>> > just about anything Open Source.
>> >
>> http://sourceforge.net/services/buy/index.php_______________________________________________
>> > LabPython-Users mailing list
>> > Lab...@li...
>> > https://lists.sourceforge.net/lists/listinfo/labpython-users
>> >
>>
>>
>>
>> -------------------------------------------------------------------------
>> Check out the new SourceForge.net Marketplace.
>> It's the best place to buy or sell services for
>> just about anything Open Source.
>> http://sourceforge.net/services/buy/index.php
>> _______________________________________________
>> LabPython-Users mailing list
>> Lab...@li...
>> https://lists.sourceforge.net/lists/listinfo/labpython-users
>>
>
>
> -------------------------------------------------------------------------
> Check out the new SourceForge.net Marketplace.
> It's the best place to buy or sell services for
> just about anything Open Source.
> http://sourceforge.net/services/buy/index.php
> _______________________________________________
> LabPython-Users mailing list
> Lab...@li...
> https://lists.sourceforge.net/lists/listinfo/labpython-users
>
>

Re: [LabPython-Users] Numpy and Scipy

[Glen S. <gle...@gm...>]

Hi again,

I would like voice my thanks for labpython as well, it's generally a great
piece of software, it's just unfortunate that numpy support is not there
since I was, as Luc said, using python/numpy/matplotlib as a matlab
replacement.

Cheers,
Glen

2008/6/5 Luc Estebanez <luc...@en...>:

> Hi all,
>
> I would like to add my vote to support the idea to add a numpy interface
> for Labpython! This would enhance greatly this piece of software since
> numpy has really become the standard for numerical stuff in python, and I
> suppose many users of Labpython are using python as a 'matlab'
> replacement.
>
> Thank you for all the hard work,
>
> Gratefully,
>
> luc
>
> > Hi Glen
> >
> > So numpy and scipy functions can be used as long as native data types are
> > used?  That may cause some problems since I am trying to perform matrix
> > operations.  I am using LabVIEW 8.20 with python 2.5.2 and labpython
> 1.2.2
> > on Windows XP.  I am trying to pass a 2D array of floats to python.
> >
> > It should be possible. The way I solved arrays in LabPython was to treat
> > them as lists. Consequently 2D arrays are lists of lists. It is not very
> > efficient but Python does even in 2.5 not give you an exported array C
> API
> > with which I could retrieve any information from a numpy array, despite
> > the
> > fact that the Python core does know an array datatype.
> >
> > It would be possible to add something like that to LabPython by making
> use
> > of the numpy extension and its exported C API but at the time I was
> > developing LabPython numpy was just in its infancy taking over from its
> > predecessor the numerical library. That API seemed not at all stable to
> me
> > at that point and making LabPython depend only softly on it (meaning it
> > would still work but without support of numpy datatypes) would also be
> > some
> > serious thinkering.
> >
> > I may take a look how numpy interfaces with Python to solve the array
> > interface issue but to do it right would be a majour undertaking and I
> > have
> > a real job to do that pays the bills.
> >
> > Rolf Kalbermatter
> > -------------------------------------------------------------------------
> > Check out the new SourceForge.net Marketplace.
> > It's the best place to buy or sell services for
> > just about anything Open Source.
> >
> http://sourceforge.net/services/buy/index.php_______________________________________________
> > LabPython-Users mailing list
> > Lab...@li...
> > https://lists.sourceforge.net/lists/listinfo/labpython-users
> >
>
>
>
> -------------------------------------------------------------------------
> Check out the new SourceForge.net Marketplace.
> It's the best place to buy or sell services for
> just about anything Open Source.
> http://sourceforge.net/services/buy/index.php
> _______________________________________________
> LabPython-Users mailing list
> Lab...@li...
> https://lists.sourceforge.net/lists/listinfo/labpython-users
>

Re: [LabPython-Users] Numpy and Scipy

[Luc E. <luc...@en...>]

Hi all,

I would like to add my vote to support the idea to add a numpy interface
for Labpython! This would enhance greatly this piece of software since
numpy has really become the standard for numerical stuff in python, and I
suppose many users of Labpython are using python as a 'matlab'
replacement.

Thank you for all the hard work,

Gratefully,

luc

> Hi Glen
>
> So numpy and scipy functions can be used as long as native data types are
> used?  That may cause some problems since I am trying to perform matrix
> operations.  I am using LabVIEW 8.20 with python 2.5.2 and labpython 1.2.2
> on Windows XP.  I am trying to pass a 2D array of floats to python.
>
> It should be possible. The way I solved arrays in LabPython was to treat
> them as lists. Consequently 2D arrays are lists of lists. It is not very
> efficient but Python does even in 2.5 not give you an exported array C API
> with which I could retrieve any information from a numpy array, despite
> the
> fact that the Python core does know an array datatype.
>
> It would be possible to add something like that to LabPython by making use
> of the numpy extension and its exported C API but at the time I was
> developing LabPython numpy was just in its infancy taking over from its
> predecessor the numerical library. That API seemed not at all stable to me
> at that point and making LabPython depend only softly on it (meaning it
> would still work but without support of numpy datatypes) would also be
> some
> serious thinkering.
>
> I may take a look how numpy interfaces with Python to solve the array
> interface issue but to do it right would be a majour undertaking and I
> have
> a real job to do that pays the bills.
>
> Rolf Kalbermatter
> -------------------------------------------------------------------------
> Check out the new SourceForge.net Marketplace.
> It's the best place to buy or sell services for
> just about anything Open Source.
> http://sourceforge.net/services/buy/index.php_______________________________________________
> LabPython-Users mailing list
> Lab...@li...
> https://lists.sourceforge.net/lists/listinfo/labpython-users
>

Re: [LabPython-Users] Numpy and Scipy

[Luc E. <luc...@en...>]

Hi Rolf,

actually, it turns out that when I get the 'python' scripting node from
the OpenG panel of the 'command selector' I still get a crash (I select
the Python scripting node, open its diagram and copy the scripting panel
to my own VI).

However, I just found that if I get a 'generic' scripting node from
'math'>'scripts and formulas'>'scipting nodes'> 'matlab scripting node'
(This is a translation from the french version of Labview) and I set the
scripting engine to Python, then I don't get a crash anymore, and I obtain
the same error as you !

This is rather weird, but I think the second method solves rather well my
issues with the python scripting node.

Thank you very much for your kind help,

luc



> Hi Luc
>
>> I think I was the person who had trouble with numpy...
>> Indeed, when I cast all my variables to python 'native' types
>> such as 'list', then I don't get into trouble.
>
> I recently looked into this and I have a problem to see a crash as you
> would say it does.
>
> I tried it in LabVIEW 6.0.2 and with Python 2.5.2 as well as with
> LabVIEW 8.0.1 and I simply get an error 1048 from the script node
> back. I'm using labpython 1.2.2 as available from sourceforge download.
>
> Can you give me some more details about your system?
>
> Rolf Kalbermatter
>