Jump to content

Search the Community

Showing results for tags 'labpython'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • Software & Hardware Discussions
    • LabVIEW Community Edition
    • LabVIEW General
    • LabVIEW (By Category)
    • Hardware
  • Resources
    • LabVIEW Getting Started
    • GCentral
    • Code Repository (Certified)
    • LAVA Code on LabVIEW Tools Network
    • Code In-Development
    • OpenG
  • Community
    • LAVA Lounge
    • LabVIEW Feedback for NI
    • LabVIEW Ecosystem
  • LAVA Site Related
    • Site Feedback & Support
    • Wiki Help

Categories

  • *Uncertified*
  • LabVIEW Tools Network Certified
  • LabVIEW API
    • VI Scripting
    • JKI Right-Click Framework Plugins
    • Quick Drop Plugins
    • XNodes
  • General
  • User Interface
    • X-Controls
  • LabVIEW IDE
    • Custom Probes
  • LabVIEW OOP
  • Database & File IO
  • Machine Vision & Imaging
  • Remote Control, Monitoring and the Internet
  • Hardware

Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


Personal Website


Company Website


Twitter Name


LinkedIn Profile


Facebook Page


Location


Interests

Found 11 results

  1. I'm seeing a slightly weird (and inconvenient) bug with LabPython... I've a Windows 7 64bit machine with 32bit LabVIEW 2012 and 32 bit LabVIEW2013 and both 64bit and 32bit Python 2.7 installed (the former I use standalone, the latter is just for linking to some LabVIEW code that makes use of LabPython). My 32bit python27.dll therefore lives in C:\Windows\SysWOW64\ and I point LabPython to it (for both versions of LabVIEW) and can see in both labview.ini files that the correct key has been added. On LabVIEW 2012, everything work s absolutely fine. On LabVIEW 2013, if I load a VI containi
  2. I have installed LabPython successfully few days ago. My goal is to experiment the possibility of calling machine learning library from python into the labview environment. So I want to run a LabPython script node that will read two local csv files for the inputs of random forest classifier. The output of the python script is the final predicted class in string format. What I did to make this work: I have set the server path to where my python27.dll located. The script is running fine until it comes through machine learning library. It ran but struck forever to run. I can ran this exactly
  3. Hi there, I wonder anyone out there having issue installing the latest LabPython v4.0.04. The Laview system i have is 2015 32 bit, windows 10, python 2.7. I tried to install the vip package from sourceforge using VI package manager. Then it showed me error code 8 saying the installation was not completed. Any thoughts anyone as to what's going on ? Could someone who has similar experience help me out on getting Labpython installed in my LV?
  4. Hello there: I have a big project, pretty much already coded in Labview, designed to perform monte-carlo analysis on a set of applications that use data from time synchronized measurements across the electrical power system. The project is designed to be open source and distributable using both built .exe and vipm. Therefore I include ONLY libraries that either come with LV or are OpenG (no third party tools that need to be purchased, and no TestStand). A part I have yet to code is the monte-carlo engine which needs to be end-user programmable. I have an idea for creating my o
  5. Hi, I try to use LabPython with Python 2.7.8. After some difficulties in the beginning I am now able to run simple scripts and also import certain modules, for example the following: import numpy sampling = 1/timestep millivoltage = numpy.std(voltage)*1000 But if I now try to add a def statement (like the one below) to the script, the VI gets stuck at PYTHON Execute Script (if it is called) or throws a ZeroDivisionError (if it is just added but not called in the script): def test(): return 0 Are there certain things that are forbidden when using LabPython like certain statements?
  6. I want to develop a C++ script server or C++ script node which it works like LabPython. So I want to run my C++ code in text mode in the block diagram of LabVIEW. Now I can run my C++ code in C++ interpreter of CERN's ROOT which can run without compilation. ROOT is good at data analysis, and LabVIEW does well in the data acqisition. I hope the two can be work together. So instead of data processing offline by using ROOT after LabVIEW finish getting the experiment data, I hope that data processing online when LabVIEW getting data. That means I must corporate my ROO
  7. I want to use the Python extension libs such as ROOT (http://root.cern.ch/drupal/content/how-use-use-python-pyroot-interpreter and http://root.cern.ch/drupal/content/production-version-528), but it is strange for me to use the labpython. I write a demo.py to import ROOT(just like this "from ROOT import gROOT, TCanvas, TF1") which is running in LabPython, but it seems to crash for LabVIEW, but it can be used outside of LabVIEW if python it in the command line. And If I run the python script without ROOT lib, it is normal in LabPython. How can I solve it? My python version is 2.6, th
  8. I was requested to provide Labview bindings for an app written in mostly in python and I've found LabPython tobe a blessing. However, I run into a nasty problem and I can't really figure who is to blame. In a nutshell: LabPython does not unload python server dll and dll of imported modules (python27.dll and *.pyd) after "PYTHON Close Session.vi" have been executed and VI stopped . For most cases it causes no problem, but numpy module causes LabView to hang when "import numpy" is executed on the second run. I'll greatly appreciate any help with the matter, because I can't even tell who
  9. This package will be available for download through VIPM in a few days. This release and covers a request for the LabPython package to be view-able under the new 4.x Top Level Menus, and to fix a dependency issue (related to this thread). This package was tested with Python 2.5 on both Windows 7 x86 and Windows XP x86. If any developers want to continue to work on the Labpython project or any other OpenG project just PM me. Kind regards Jonathon Green OpenG Manager
  10. Hi All, On a system we're working on, we are allowing the operator to enter a python script. The script is executed with LabPython, which seems to work well. We implemented the script editing with ScintillaNET (http://scintillanet.codeplex.com/) We also implemented pre-execution script checking (I don’t know the right term for this) with pylint (http://pypi.python.org/pypi/pylint) Attached is an example of our implementation. I’m posting this in case anyone might find it useful. A couple of items that could be improved 1) This implementation used system exec to run pylint, could pyl
  11. Hi all, I'm a beginer, and I'm french, so sorry formy mystake in programing and in english. I have to use a python script into labview 2010. I use Vi Package Manager to instal Labpython find in OpenG source. It seems that I have a problem if initialisation of Labpython The example box of Labpython doesn't work has you can see on this Print Screen. Thank you for your futur reply. Thibault Menard
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.