You can subscribe to this list here.
2000 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
(4) |
Jul
(1) |
Aug
|
Sep
(15) |
Oct
(32) |
Nov
(35) |
Dec
(48) |
---|---|---|---|---|---|---|---|---|---|---|---|---|
2001 |
Jan
(46) |
Feb
(22) |
Mar
(65) |
Apr
(49) |
May
(22) |
Jun
(29) |
Jul
(51) |
Aug
(34) |
Sep
(32) |
Oct
(46) |
Nov
(30) |
Dec
(32) |
2002 |
Jan
(48) |
Feb
(4) |
Mar
(20) |
Apr
(28) |
May
(13) |
Jun
(34) |
Jul
(51) |
Aug
(15) |
Sep
(15) |
Oct
(35) |
Nov
(15) |
Dec
(20) |
2003 |
Jan
(31) |
Feb
(111) |
Mar
(41) |
Apr
(28) |
May
(36) |
Jun
(29) |
Jul
(27) |
Aug
(29) |
Sep
(47) |
Oct
(28) |
Nov
(7) |
Dec
(26) |
2004 |
Jan
(44) |
Feb
(9) |
Mar
(17) |
Apr
(26) |
May
(58) |
Jun
(13) |
Jul
(44) |
Aug
(64) |
Sep
(30) |
Oct
(11) |
Nov
(21) |
Dec
(28) |
2005 |
Jan
(29) |
Feb
(11) |
Mar
(11) |
Apr
(22) |
May
(85) |
Jun
(46) |
Jul
(17) |
Aug
(18) |
Sep
(14) |
Oct
(22) |
Nov
(1) |
Dec
(45) |
2006 |
Jan
(20) |
Feb
(36) |
Mar
(18) |
Apr
(24) |
May
(21) |
Jun
(48) |
Jul
(23) |
Aug
(20) |
Sep
(10) |
Oct
(41) |
Nov
(46) |
Dec
(40) |
2007 |
Jan
(40) |
Feb
(20) |
Mar
(13) |
Apr
(6) |
May
(24) |
Jun
(31) |
Jul
(30) |
Aug
(11) |
Sep
(11) |
Oct
(10) |
Nov
(56) |
Dec
(64) |
2008 |
Jan
(64) |
Feb
(22) |
Mar
(63) |
Apr
(28) |
May
(25) |
Jun
(36) |
Jul
(11) |
Aug
(9) |
Sep
(14) |
Oct
(41) |
Nov
(46) |
Dec
(130) |
2009 |
Jan
(95) |
Feb
(41) |
Mar
(24) |
Apr
(35) |
May
(53) |
Jun
(67) |
Jul
(48) |
Aug
(48) |
Sep
(86) |
Oct
(75) |
Nov
(64) |
Dec
(52) |
2010 |
Jan
(57) |
Feb
(31) |
Mar
(28) |
Apr
(40) |
May
(25) |
Jun
(42) |
Jul
(79) |
Aug
(31) |
Sep
(49) |
Oct
(66) |
Nov
(38) |
Dec
(25) |
2011 |
Jan
(29) |
Feb
(18) |
Mar
(44) |
Apr
(6) |
May
(28) |
Jun
(31) |
Jul
(36) |
Aug
(24) |
Sep
(30) |
Oct
(23) |
Nov
(21) |
Dec
(27) |
2012 |
Jan
(14) |
Feb
(11) |
Mar
(2) |
Apr
(48) |
May
(7) |
Jun
(32) |
Jul
(22) |
Aug
(25) |
Sep
(31) |
Oct
(32) |
Nov
(21) |
Dec
(17) |
2013 |
Jan
(44) |
Feb
(27) |
Mar
(3) |
Apr
(1) |
May
|
Jun
|
Jul
(3) |
Aug
(4) |
Sep
(1) |
Oct
(7) |
Nov
(5) |
Dec
(5) |
2014 |
Jan
|
Feb
|
Mar
|
Apr
(3) |
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
(3) |
Dec
(2) |
2015 |
Jan
|
Feb
|
Mar
|
Apr
|
May
(1) |
Jun
|
Jul
|
Aug
(1) |
Sep
|
Oct
|
Nov
|
Dec
|
2017 |
Jan
(7) |
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
2019 |
Jan
|
Feb
|
Mar
(1) |
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
From: James T. <jt...@mi...> - 2011-12-06 17:26:50
|
Another data point. I'm running LMDE (debian testing) 64-bit and I get the segfault error with the ATI proprietary driver. libgtkglextmm-x11-1.2-dev was not installed but installing it made no difference. Playing around with site_settings.py made no difference. Purge-reinstall made no difference. Seems like this is a perpetual problem I keep running into every time I come back to visual after an extended break or on a new system. Now I'm regretting not making good on my intention 2 years ago to re-implement vPython in Python (like it should be) two years ago. I have a library and a lot of simulation code that is unusable because I can't get visual to run. My last hope is to bypass the repositories and hope that a newer version or building from sources will fix this. Otherwise I'm fairly well screwed. JT |
From: Bruce S. <Bru...@nc...> - 2011-12-01 22:17:44
|
It sounds like you have a 64-bit version of Python 2.7 installed. As it says on the Windows download page at vpython.org: First, download and install Python-2.7.1 (Important: Let it install in C:\Python27)(There is not a VPython version for Windows 64-bit Python, but this 32-bit version of Python works fine on 64-bit Windows machines) Bruce Sherwood On Thu, Dec 1, 2011 at 12:52 PM, ptrottant <p.t...@fr...> wrote: > Hello, > > > > I’m trying to make run an old script using vpython (which works fine for > years). > > I’m now on windows 7 64bit, I installed VPython-Win-Py2.7-5.72.exe in > c:\python27 which is the place for python 2.7 on my computer. > > (notice that the installation process alert me about the fact it didn’t find > python 2.7 installation directory. As requested I gave it the place). > > Unfortunately it seems to have trouble with cvisual : > > > > Traceback (most recent call last): > > File "C:\3S\myprog23\pression3.py", line 3, in <module> > > import visual > > File "C:\Python27\lib\site-packages\visual\__init__.py", line 1, in > <module> > > from .visual_all import * > > File "C:\Python27\lib\site-packages\visual\visual_all.py", line 1, in > <module> > > from vis import version > > File "C:\Python27\lib\site-packages\vis\__init__.py", line 3, in <module> > > from .cvisual import (vector, dot, mag, mag2, norm, cross, rotate, comp, > proj, diff_angle, rate, waitclose) > > ImportError: DLL load failed: %1 n’est pas une application Win32 valide. > (translated by is not a valid Win32 application) > > > > I found only a cvisual.pyd file in the c:\python27\Lib\site-packages\vis > directory > > > > So, I will be very pleased if someone could help me. > > > > Thanks for your support. Don’t hesitate if you want any other information or > test result. > > > > Regards. > > > > > ------------------------------------------------------------------------------ > All the data continuously generated in your IT infrastructure > contains a definitive record of customers, application performance, > security threats, fraudulent activity, and more. Splunk takes this > data and makes sense of it. IT sense. And common sense. > http://p.sf.net/sfu/splunk-novd2d > _______________________________________________ > Visualpython-users mailing list > Vis...@li... > https://lists.sourceforge.net/lists/listinfo/visualpython-users > |
From: ptrottant <p.t...@fr...> - 2011-12-01 19:52:34
|
Hello, I'm trying to make run an old script using vpython (which works fine for years). I'm now on windows 7 64bit, I installed VPython-Win-Py2.7-5.72.exe in c:\python27 which is the place for python 2.7 on my computer. (notice that the installation process alert me about the fact it didn't find python 2.7 installation directory. As requested I gave it the place). Unfortunately it seems to have trouble with cvisual : Traceback (most recent call last): File "C:\3S\myprog23\pression3.py", line 3, in <module> import visual File "C:\Python27\lib\site-packages\visual\__init__.py", line 1, in <module> from .visual_all import * File "C:\Python27\lib\site-packages\visual\visual_all.py", line 1, in <module> from vis import version File "C:\Python27\lib\site-packages\vis\__init__.py", line 3, in <module> from .cvisual import (vector, dot, mag, mag2, norm, cross, rotate, comp, proj, diff_angle, rate, waitclose) ImportError: DLL load failed: %1 n'est pas une application Win32 valide. (translated by is not a valid Win32 application) I found only a cvisual.pyd file in the c:\python27\Lib\site-packages\vis directory So, I will be very pleased if someone could help me. Thanks for your support. Don't hesitate if you want any other information or test result. Regards. |
From: Aaron M. <mav...@gm...> - 2011-12-01 01:35:23
|
Hi all, Is there an easy way to get an axis-aligned bounding box for an object (or better yet, a frame)? The window autoscale/autocenter functionality uses this information internally, but does the Python API expose it in some way? I don't see anything in the documentation for this but I figured I'd ask before attempting an internal solution or a patch to Visual. Thanks. -- Aaron Mavrinac www.mavrinac.com |
From: Seth M. <sm...@ps...> - 2011-11-28 23:00:39
|
I am running Fedora, not Ubuntu, but I experience similar problems. When I use the nVidia drivers that come from RPMFusion, I get a segfault whenever I try to display an scene with VPython (just as I have seen described as with the latest Ubuntu). I have been experiencing this issue since Fedora 11 (current release is 15); it now seems that its made it's way over to Ubuntu. I have found that installing the driver that is downloaded directly from nVidia's web site gets rid of this issue. It seems that some of the black magic happening in the RPM (and I am assuming the .deb for Ubuntu) affects things that the binary from nVidia does not. The drawback then is that when I use nVidia's driver and then update the kernel, X windows crashes (not a VPython issue, but worthy of note). One also has to manually disable the nouveau driver that comes with Fedora. Seth On 11/28/2011 05:04 PM, Bruce Sherwood wrote: > Thanks much for this very useful information, John. > > It certainly does seem like a driver problem, though I suppose it is > possible that Visual contains some inappropriate use of OpenGL that > shows up only with new drivers. > > Bruce Sherwood > > On Mon, Nov 28, 2011 at 12:11 PM, John Zelle<joh...@wa...> wrote: >> Hi again, >> >> I've gotten my python-visual on Intel video working under Ubuntu 11.10. Installing the libgtkglextmm-x11-1.2-dev package fixed the GL error I was getting. I had to go to the site_settings.py library file and turn the shaders off. It seems to be working now without issues. >> >> It now appears to me that the seg fault issue is specific to NVIDIA graphics, which raises the possibility that it is a driver issue for NVIDIA cards. >> >> John Zelle, PhD >> Professor of Computer Science >> Wartburg College >> >> >> ________________________________________ >> From: Kevin Karplus [ka...@so...] >> Sent: Monday, November 28, 2011 12:04 PM >> To: Bru...@nc... >> Cc: vis...@li... >> Subject: Re: [Visualpython-users] Python-visual in latest Ubuntu >> >> I have, sadly, had to remove 32-bit Python from my machine, thus >> breaking Vpython. I had another package that I had to use for my >> research that only was too difficult to reconfigure to compile to >> 32-bit Python on a 64-bit machine. So I needed 64-bit Python to do my >> work. >> >> So I've had to give up on Vpython for my own use (though my son will >> still use it on the household computer, which does not need to run >> research code and can tolerate using 32-bit Python). I suppose, that >> with considerable effort I could dig up an old version of Python that >> could be compiled for a 32-bit machine, but the hassle involved is too >> large. Having both a 32-bit and 64-bit version of Python 2.7.2 on the >> same Mac seems to be very difficult to set up, as the Mac method for >> having multiple versions of python seems to rely on the version number >> to keep the directories straight. >> >> Unless the 32-bit kluge is fixed within the next year, Vpython will >> become just another good idea that disappeared because it was tied to >> obsolete technology. I suspect that Vpython will almost disappear >> within 3-5 years if it remains tied to legacy computers. >> >> Kevin Karplus >> >> ------------------------------------------------------------------------------ >> All the data continuously generated in your IT infrastructure >> contains a definitive record of customers, application performance, >> security threats, fraudulent activity, and more. Splunk takes this >> data and makes sense of it. IT sense. And common sense. >> http://p.sf.net/sfu/splunk-novd2d >> _______________________________________________ >> Visualpython-users mailing list >> Vis...@li... >> https://lists.sourceforge.net/lists/listinfo/visualpython-users >> >> ------------------------------------------------------------------------------ >> All the data continuously generated in your IT infrastructure >> contains a definitive record of customers, application performance, >> security threats, fraudulent activity, and more. Splunk takes this >> data and makes sense of it. IT sense. And common sense. >> http://p.sf.net/sfu/splunk-novd2d >> _______________________________________________ >> Visualpython-users mailing list >> Vis...@li... >> https://lists.sourceforge.net/lists/listinfo/visualpython-users >> > ------------------------------------------------------------------------------ > All the data continuously generated in your IT infrastructure > contains a definitive record of customers, application performance, > security threats, fraudulent activity, and more. Splunk takes this > data and makes sense of it. IT sense. And common sense. > http://p.sf.net/sfu/splunk-novd2d > _______________________________________________ > Visualpython-users mailing list > Vis...@li... > https://lists.sourceforge.net/lists/listinfo/visualpython-users |
From: Bruce S. <Bru...@nc...> - 2011-11-28 22:40:59
|
I verified that I have libgtkglextmm-x11-1.2-dev installed (that's one of the standard dependencies for Visual) , and I turned off shaders in site_settings.py, but I still crash. I have an NVIDIA card, so apparently the key point as you say is that you were running with Intel graphics, which again implies a problem with the NVIDIA graphics driver. However, for all I know at the moment there may be something that needs to be updated in the Visual code. Bruce Sherwood On Mon, Nov 28, 2011 at 12:11 PM, John Zelle <joh...@wa...> wrote: > Hi again, > > I've gotten my python-visual on Intel video working under Ubuntu 11.10. Installing the libgtkglextmm-x11-1.2-dev package fixed the GL error I was getting. I had to go to the site_settings.py library file and turn the shaders off. It seems to be working now without issues. > > It now appears to me that the seg fault issue is specific to NVIDIA graphics, which raises the possibility that it is a driver issue for NVIDIA cards. > > John Zelle, PhD > Professor of Computer Science > Wartburg College > > > ________________________________________ > From: Kevin Karplus [ka...@so...] > Sent: Monday, November 28, 2011 12:04 PM > To: Bru...@nc... > Cc: vis...@li... > Subject: Re: [Visualpython-users] Python-visual in latest Ubuntu > > I have, sadly, had to remove 32-bit Python from my machine, thus > breaking Vpython. I had another package that I had to use for my > research that only was too difficult to reconfigure to compile to > 32-bit Python on a 64-bit machine. So I needed 64-bit Python to do my > work. > > So I've had to give up on Vpython for my own use (though my son will > still use it on the household computer, which does not need to run > research code and can tolerate using 32-bit Python). I suppose, that > with considerable effort I could dig up an old version of Python that > could be compiled for a 32-bit machine, but the hassle involved is too > large. Having both a 32-bit and 64-bit version of Python 2.7.2 on the > same Mac seems to be very difficult to set up, as the Mac method for > having multiple versions of python seems to rely on the version number > to keep the directories straight. > > Unless the 32-bit kluge is fixed within the next year, Vpython will > become just another good idea that disappeared because it was tied to > obsolete technology. I suspect that Vpython will almost disappear > within 3-5 years if it remains tied to legacy computers. > > Kevin Karplus > > ------------------------------------------------------------------------------ > All the data continuously generated in your IT infrastructure > contains a definitive record of customers, application performance, > security threats, fraudulent activity, and more. Splunk takes this > data and makes sense of it. IT sense. And common sense. > http://p.sf.net/sfu/splunk-novd2d > _______________________________________________ > Visualpython-users mailing list > Vis...@li... > https://lists.sourceforge.net/lists/listinfo/visualpython-users > > ------------------------------------------------------------------------------ > All the data continuously generated in your IT infrastructure > contains a definitive record of customers, application performance, > security threats, fraudulent activity, and more. Splunk takes this > data and makes sense of it. IT sense. And common sense. > http://p.sf.net/sfu/splunk-novd2d > _______________________________________________ > Visualpython-users mailing list > Vis...@li... > https://lists.sourceforge.net/lists/listinfo/visualpython-users > |
From: Bruce S. <Bru...@nc...> - 2011-11-28 22:04:59
|
Thanks much for this very useful information, John. It certainly does seem like a driver problem, though I suppose it is possible that Visual contains some inappropriate use of OpenGL that shows up only with new drivers. Bruce Sherwood On Mon, Nov 28, 2011 at 12:11 PM, John Zelle <joh...@wa...> wrote: > Hi again, > > I've gotten my python-visual on Intel video working under Ubuntu 11.10. Installing the libgtkglextmm-x11-1.2-dev package fixed the GL error I was getting. I had to go to the site_settings.py library file and turn the shaders off. It seems to be working now without issues. > > It now appears to me that the seg fault issue is specific to NVIDIA graphics, which raises the possibility that it is a driver issue for NVIDIA cards. > > John Zelle, PhD > Professor of Computer Science > Wartburg College > > > ________________________________________ > From: Kevin Karplus [ka...@so...] > Sent: Monday, November 28, 2011 12:04 PM > To: Bru...@nc... > Cc: vis...@li... > Subject: Re: [Visualpython-users] Python-visual in latest Ubuntu > > I have, sadly, had to remove 32-bit Python from my machine, thus > breaking Vpython. I had another package that I had to use for my > research that only was too difficult to reconfigure to compile to > 32-bit Python on a 64-bit machine. So I needed 64-bit Python to do my > work. > > So I've had to give up on Vpython for my own use (though my son will > still use it on the household computer, which does not need to run > research code and can tolerate using 32-bit Python). I suppose, that > with considerable effort I could dig up an old version of Python that > could be compiled for a 32-bit machine, but the hassle involved is too > large. Having both a 32-bit and 64-bit version of Python 2.7.2 on the > same Mac seems to be very difficult to set up, as the Mac method for > having multiple versions of python seems to rely on the version number > to keep the directories straight. > > Unless the 32-bit kluge is fixed within the next year, Vpython will > become just another good idea that disappeared because it was tied to > obsolete technology. I suspect that Vpython will almost disappear > within 3-5 years if it remains tied to legacy computers. > > Kevin Karplus > > ------------------------------------------------------------------------------ > All the data continuously generated in your IT infrastructure > contains a definitive record of customers, application performance, > security threats, fraudulent activity, and more. Splunk takes this > data and makes sense of it. IT sense. And common sense. > http://p.sf.net/sfu/splunk-novd2d > _______________________________________________ > Visualpython-users mailing list > Vis...@li... > https://lists.sourceforge.net/lists/listinfo/visualpython-users > > ------------------------------------------------------------------------------ > All the data continuously generated in your IT infrastructure > contains a definitive record of customers, application performance, > security threats, fraudulent activity, and more. Splunk takes this > data and makes sense of it. IT sense. And common sense. > http://p.sf.net/sfu/splunk-novd2d > _______________________________________________ > Visualpython-users mailing list > Vis...@li... > https://lists.sourceforge.net/lists/listinfo/visualpython-users > |
From: Bruce S. <Bru...@nc...> - 2011-11-28 22:02:58
|
The implication is that your problem is on the Mac, not Ubuntu. The problem on the Mac is significantly more worrisome than the Ubuntu problem, because the platform-specific machinery for creating a window and handling events is currently implemented in Carbon, for which 64-bit support was dropped. It was not found possible to implement this in Cocoa, due to thread priority issues. On the other hand, if you don't require the standard Mac look and feel but are comfortable with the X11 window manager, you can run VPython with 64-bit Python on a Mac: http://comments.gmane.org/gmane.comp.python.visualpython.user/3245 Bruce Sherwood On Mon, Nov 28, 2011 at 11:04 AM, Kevin Karplus <ka...@so...> wrote: > > I have, sadly, had to remove 32-bit Python from my machine, thus > breaking Vpython. I had another package that I had to use for my > research that only was too difficult to reconfigure to compile to > 32-bit Python on a 64-bit machine. So I needed 64-bit Python to do my > work. > > So I've had to give up on Vpython for my own use (though my son will > still use it on the household computer, which does not need to run > research code and can tolerate using 32-bit Python). I suppose, that > with considerable effort I could dig up an old version of Python that > could be compiled for a 32-bit machine, but the hassle involved is too > large. Having both a 32-bit and 64-bit version of Python 2.7.2 on the > same Mac seems to be very difficult to set up, as the Mac method for > having multiple versions of python seems to rely on the version number > to keep the directories straight. > > Unless the 32-bit kluge is fixed within the next year, Vpython will > become just another good idea that disappeared because it was tied to > obsolete technology. I suspect that Vpython will almost disappear > within 3-5 years if it remains tied to legacy computers. > > Kevin Karplus > |
From: John Z. <joh...@wa...> - 2011-11-28 19:11:11
|
Hi again, I've gotten my python-visual on Intel video working under Ubuntu 11.10. Installing the libgtkglextmm-x11-1.2-dev package fixed the GL error I was getting. I had to go to the site_settings.py library file and turn the shaders off. It seems to be working now without issues. It now appears to me that the seg fault issue is specific to NVIDIA graphics, which raises the possibility that it is a driver issue for NVIDIA cards. John Zelle, PhD Professor of Computer Science Wartburg College ________________________________________ From: Kevin Karplus [ka...@so...] Sent: Monday, November 28, 2011 12:04 PM To: Bru...@nc... Cc: vis...@li... Subject: Re: [Visualpython-users] Python-visual in latest Ubuntu I have, sadly, had to remove 32-bit Python from my machine, thus breaking Vpython. I had another package that I had to use for my research that only was too difficult to reconfigure to compile to 32-bit Python on a 64-bit machine. So I needed 64-bit Python to do my work. So I've had to give up on Vpython for my own use (though my son will still use it on the household computer, which does not need to run research code and can tolerate using 32-bit Python). I suppose, that with considerable effort I could dig up an old version of Python that could be compiled for a 32-bit machine, but the hassle involved is too large. Having both a 32-bit and 64-bit version of Python 2.7.2 on the same Mac seems to be very difficult to set up, as the Mac method for having multiple versions of python seems to rely on the version number to keep the directories straight. Unless the 32-bit kluge is fixed within the next year, Vpython will become just another good idea that disappeared because it was tied to obsolete technology. I suspect that Vpython will almost disappear within 3-5 years if it remains tied to legacy computers. Kevin Karplus ------------------------------------------------------------------------------ All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity, and more. Splunk takes this data and makes sense of it. IT sense. And common sense. http://p.sf.net/sfu/splunk-novd2d _______________________________________________ Visualpython-users mailing list Vis...@li... https://lists.sourceforge.net/lists/listinfo/visualpython-users |
From: Kevin K. <ka...@so...> - 2011-11-28 18:23:50
|
I have, sadly, had to remove 32-bit Python from my machine, thus breaking Vpython. I had another package that I had to use for my research that only was too difficult to reconfigure to compile to 32-bit Python on a 64-bit machine. So I needed 64-bit Python to do my work. So I've had to give up on Vpython for my own use (though my son will still use it on the household computer, which does not need to run research code and can tolerate using 32-bit Python). I suppose, that with considerable effort I could dig up an old version of Python that could be compiled for a 32-bit machine, but the hassle involved is too large. Having both a 32-bit and 64-bit version of Python 2.7.2 on the same Mac seems to be very difficult to set up, as the Mac method for having multiple versions of python seems to rely on the version number to keep the directories straight. Unless the 32-bit kluge is fixed within the next year, Vpython will become just another good idea that disappeared because it was tied to obsolete technology. I suspect that Vpython will almost disappear within 3-5 years if it remains tied to legacy computers. Kevin Karplus |
From: John Z. <joh...@wa...> - 2011-11-28 17:13:39
|
I don't have a solution, but I can confirm 3 different systems (all I've tried) with Ubuntu 11.10 having a broken python-visual module. These are 32-bit systems with a variety of video cards (Intel and NVIDIA), so I don't think 64/32-bit or video drivers is the issues. Two of the systems report the seg fault error; the other reports glib-mm Error about not being able to load glCreateProgramObjectARB. All three of these systems got to 11.10 via upgrade. I do not have any data points for what happens with a clean install. The apparent brittleness of Vpython on Linux is troublesome. --John John Zelle, PhD Professor of Computer Science Wartburg College ________________________________ From: Andrew McCormick [agm...@gm...] Sent: Monday, November 28, 2011 10:08 AM To: Bru...@nc... Cc: Tuomas Airaksinen; vpusers Subject: Re: [Visualpython-users] Python-visual in latest Ubuntu Hi All, I'm been running vpython in Ubuntu 11.04 and then Ubuntu 11.10. I did not encounter any problems with the transition. There is a caveat though: when I installed CUDA on my system and updated my NVIDIA drivers, vpython simply stopped working. I simply could not stop it from segfaulting when any vpython object was declared. The only solution was to entirely reformat and reinstall Ubuntu and not install CUDA. My guess is that something evil is happening with the gpu drivers for the 64 bit version. Try some older drivers perhaps? Andy On Mon, Nov 28, 2011 at 10:54 AM, Bruce Sherwood <Bru...@nc...<mailto:Bru...@nc...>> wrote: I too have seen the following problem on the latest Ubuntu but thought it must be a driver problem, and I haven't had the time to look more deeply. The bug report mentioned here implies that the problem is with visual. Has someone on this list successfully run python-visual on the latest version of Ubuntu? If so, what did you have to do? Thanks. Bruce Sherwood ---------- Forwarded message ---------- From: Tuomas Airaksinen <tuo...@jy...<mailto:tuo...@jy...>> Date: Mon, Nov 28, 2011 at 2:27 AM Subject: Python-visual in ubuntu etc. Hi, Just a short question: Are you aware of any way to get python-visual work in Ubuntu Linux environment. I am using 64 bit Ubuntu 11.10, but I tried with virtual machine (virtualbox) 32 bit 11.10 and 10.04 versions, and none of them were working. There are bug reports out there https://bugs.launchpad.net/ubuntu/+source/python-visual/+bug/787932 but no fix/workaround seem to be around. I used to find this module very useful but now it just segfaults after any command like sphere(). -- Tuomas Airaksinen Post-doctoral researcher GSM (work) +358 40 805 3247<tel:%2B358%2040%20805%203247> Office: Agora AgC 423.3 University of Jyväskylä ------------------------------------------------------------------------------ All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity, and more. Splunk takes this data and makes sense of it. IT sense. And common sense. http://p.sf.net/sfu/splunk-novd2d _______________________________________________ Visualpython-users mailing list Vis...@li...<mailto:Vis...@li...> https://lists.sourceforge.net/lists/listinfo/visualpython-users -- Sincerely, Andrew McCormick |
From: Andrew M. <agm...@gm...> - 2011-11-28 16:08:15
|
Hi All, I'm been running vpython in Ubuntu 11.04 and then Ubuntu 11.10. I did not encounter any problems with the transition. There is a caveat though: when I installed CUDA on my system and updated my NVIDIA drivers, vpython simply stopped working. I simply could not stop it from segfaulting when any vpython object was declared. The only solution was to entirely reformat and reinstall Ubuntu and not install CUDA. My guess is that something evil is happening with the gpu drivers for the 64 bit version. Try some older drivers perhaps? Andy On Mon, Nov 28, 2011 at 10:54 AM, Bruce Sherwood <Bru...@nc...>wrote: > I too have seen the following problem on the latest Ubuntu but thought > it must be a driver problem, and I haven't had the time to look more > deeply. The bug report mentioned here implies that the problem is with > visual. Has someone on this list successfully run python-visual on the > latest version of Ubuntu? If so, what did you have to do? Thanks. > > Bruce Sherwood > > ---------- Forwarded message ---------- > From: Tuomas Airaksinen <tuo...@jy...> > Date: Mon, Nov 28, 2011 at 2:27 AM > Subject: Python-visual in ubuntu etc. > > Hi, > > Just a short question: Are you aware of any way to get python-visual > work in Ubuntu > Linux environment. I am using 64 bit Ubuntu 11.10, but I tried with > virtual machine (virtualbox) 32 bit > 11.10 and 10.04 versions, and none of them were working. > > There are bug reports out there > > https://bugs.launchpad.net/ubuntu/+source/python-visual/+bug/787932 > > but no fix/workaround seem to be around. > > I used to find this module very useful but now it just segfaults after > any command like > sphere(). > > -- > Tuomas Airaksinen > Post-doctoral researcher > GSM (work) +358 40 805 3247 > Office: Agora AgC 423.3 > University of Jyväskylä > > > ------------------------------------------------------------------------------ > All the data continuously generated in your IT infrastructure > contains a definitive record of customers, application performance, > security threats, fraudulent activity, and more. Splunk takes this > data and makes sense of it. IT sense. And common sense. > http://p.sf.net/sfu/splunk-novd2d > _______________________________________________ > Visualpython-users mailing list > Vis...@li... > https://lists.sourceforge.net/lists/listinfo/visualpython-users > -- Sincerely, Andrew McCormick |
From: Bruce S. <Bru...@nc...> - 2011-11-28 15:55:10
|
I too have seen the following problem on the latest Ubuntu but thought it must be a driver problem, and I haven't had the time to look more deeply. The bug report mentioned here implies that the problem is with visual. Has someone on this list successfully run python-visual on the latest version of Ubuntu? If so, what did you have to do? Thanks. Bruce Sherwood ---------- Forwarded message ---------- From: Tuomas Airaksinen <tuo...@jy...> Date: Mon, Nov 28, 2011 at 2:27 AM Subject: Python-visual in ubuntu etc. Hi, Just a short question: Are you aware of any way to get python-visual work in Ubuntu Linux environment. I am using 64 bit Ubuntu 11.10, but I tried with virtual machine (virtualbox) 32 bit 11.10 and 10.04 versions, and none of them were working. There are bug reports out there https://bugs.launchpad.net/ubuntu/+source/python-visual/+bug/787932 but no fix/workaround seem to be around. I used to find this module very useful but now it just segfaults after any command like sphere(). -- Tuomas Airaksinen Post-doctoral researcher GSM (work) +358 40 805 3247 Office: Agora AgC 423.3 University of Jyväskylä |
From: Bruce S. <Bru...@nc...> - 2011-11-22 19:52:36
|
Thanks for reporting that the documentation is incomplete. I think that the other objects that aren't pickable include extrusion and faces. Bruce Sherwood On Tue, Nov 22, 2011 at 12:48 PM, Aaron Mavrinac <mav...@gm...> wrote: > Hi all, > > The documentation for mouse events [1] says the following: > > "The nearest object in the scene which falls under the cursor, or > None. At present curve, label, and helix cannot be picked. The picked > object is scene.mouse.pick." > > Can extrusions be picked? I don't seem to get anything for them > (Visual 5.72, Linux). If not, are there other newer objects which > can't be picked? > > > [1] http://vpython.org/contents/docs/visual/mouse.html > > -- > Aaron Mavrinac > www.mavrinac.com > > ------------------------------------------------------------------------------ > All the data continuously generated in your IT infrastructure > contains a definitive record of customers, application performance, > security threats, fraudulent activity, and more. Splunk takes this > data and makes sense of it. IT sense. And common sense. > http://p.sf.net/sfu/splunk-novd2d > _______________________________________________ > Visualpython-users mailing list > Vis...@li... > https://lists.sourceforge.net/lists/listinfo/visualpython-users > |
From: Aaron M. <mav...@gm...> - 2011-11-22 19:48:43
|
Hi all, The documentation for mouse events [1] says the following: "The nearest object in the scene which falls under the cursor, or None. At present curve, label, and helix cannot be picked. The picked object is scene.mouse.pick." Can extrusions be picked? I don't seem to get anything for them (Visual 5.72, Linux). If not, are there other newer objects which can't be picked? [1] http://vpython.org/contents/docs/visual/mouse.html -- Aaron Mavrinac www.mavrinac.com |
From: Jerzy K. <jer...@un...> - 2011-11-03 21:31:19
|
Jason Morgan : > > I've had lots of success with multiprocessing, wx and visual. > > I've got a visual app which uses two multiprocessing processes as well > as a wx app with message queues between all of them and it works > perfectly. > I even get the frame rate I ask for..... > > Make your visual app run as a multiprocessing. (...) Noow, this is really interesting. The multiprocessing module is horribly heavy, but it manages (sometimes...) even to survive the bedlam which waits for the ingenuous people who try to do concurrency with TkInter... But if you use wx, tant mieux, as say the True French. Could you send me some examples? Thanks. Jerzy Karczmarczuk |
From: Bruce S. <Bru...@nc...> - 2011-11-03 16:39:14
|
I'll mention that the graph module (vis/graph.py) uses the threading module in order to implement the crosshairs for reading a point on the graph when you drag the mouse over a graph with the left button down. Bruce Sherwood On Thu, Nov 3, 2011 at 8:18 AM, Jason Morgan <j.a...@gm...> wrote: > > I've had lots of success with multiprocessing, wx and visual. > > I've got a visual app which uses two multiprocessing processes as well as a > wx app with message queues between all of them and it works perfectly. > I even get the frame rate I ask for..... > > Make your visual app run as a multiprocessing.Process, then start other > processes and/or wx as you like. > > The other process is one that creates a named pipe to allow external > programs to interact with either wx or visual using multiprocessing.Queue. > > Cheers, > jason |
From: Jason M. <j.a...@gm...> - 2011-11-03 14:18:29
|
I've had lots of success with multiprocessing, wx and visual. I've got a visual app which uses two multiprocessing processes as well as a wx app with message queues between all of them and it works perfectly. I even get the frame rate I ask for..... Make your visual app run as a multiprocessing.Process, then start other processes and/or wx as you like. The other process is one that creates a named pipe to allow external programs to interact with either wx or visual using multiprocessing.Queue. Cheers, jason ----- Original Message ----- From: Jerzy Karczmarczuk Sent: 01/11/11 11:21 PM To: vis...@li... Subject: [Visualpython-users] Threads Does anybody has some experience with multithreading and VPython? Standard examples are silent, the tutorial just mentions that the rendering thread is separate I did some simple tests (with the threading module without any locks, some "planets" wandering concurrently on the screen), no serious problems, but if somebody tried some torture example, and noticed something, I would be grateful to know. I noticed something I cannot interpret. Two objects move, and two loops running in different threads execute time.sleep(slp). Nothing wrong. I replace the sleeping by rate(1.0/slp), and the second thread waits until the first terminates. Why? Maestro Bruce? All the best. Jerzy Karczmarczuk Caen, France. ------------------------------------------------------------------------------ RSA® Conference 2012 Save $700 by Nov 18 Register now! http://p.sf.net/sfu/rsa-sfdev2dev1 _______________________________________________ Visualpython-users mailing list Vis...@li... https://lists.sourceforge.net/lists/listinfo/visualpython-users |
From: Jerzy K. <jer...@un...> - 2011-11-02 19:39:48
|
Bruce Sherwood : > I'm not sure I follow all the issues here, but I do want to emphasize > as James Mueller points out that rate is NOT an equivalent of sleep. > Its purpose is to put an upper bound on the rate (...) Alright, no point in continuing. This is my last message on this subject. I didn't say a single word about the purpose of rate()! You are right, but it doesn't change anything in my messages. However, rate()*IS* more or less based on sleep(), and if you do not agree, look at the code : rate.cpp: rate_timer::rate_timer() { origin = sclock(); } void rate_timer::delay(double delay) { float t = delay - (sclock() - origin); if (t > 0.010) { *threaded_sleep(t);* } else while (delay - (sclock() - origin) > 0); origin = sclock(); }; It simply computes the sleep time according to the specification of rate. I claimed ONLY that cvisual seems to use one shared timer, and it precludes the asynchronous animation. Moreover the last while loop suggests that for delays smaller than 0.01 sec, the handler simply enters an idle loop, doing nothing. This is not the most excellent solution, since it blocks /everything/ (only the OS preemption breaks this loop). Perhaps J. Brandmayer could say something about the possibilities to rationalize this. (His name is cited as the author of the code.) I suggested to use time.sleep() as a replacement, practically *it works*, and that's all. I believe that the handling of events by VPython could be discussed, and perhaps modernized a bit as well, but another time. Thank you, everybody. Over. Jerzy Karczmarczuk Caen, France |
From: Bruce S. <Bru...@nc...> - 2011-11-02 18:22:45
|
I'm not sure I follow all the issues here, but I do want to emphasize as James Mueller points out that rate is NOT an equivalent of sleep. Its purpose is to put an upper bound on the rate at which an animation runs, so that on a very fast computer your animation doesn't run so fast you can't see it. Bruce Sherwood On Wed, Nov 2, 2011 at 7:20 AM, Jerzy Karczmarczuk <jer...@un...> wrote: > James Mueller : > > One point is that rate and sleep have different purposes. > rate is trying to make sure that each iteration of the loop takes a time > slp. So to get the same effect from sleep, you would need to call > time.sleep(slp-delta), where delta is the amount of time taken by the > instructions in the rest of the loop. > > OK, but doesn't matter. > Some simple instructions in Python don't take much time. (And if the > rendering thread is autonomous, it doesn't waste the time of the main > process. > If in my cited program you eliminate all waiting, the process terminates > before you are able to see any movement. > > Who will need an incredibly fine tuning while programming in Python? > > You may make some variants, if you wish, e.g. introduce into a loop a timing > block which measures the time lapse since its last call, and wait until your > "rate" condition is fulfilled. > Clumsy... > > == > The problem is the thread safety. The sleep() call is a replacement for > rate(), that's all I wanted to say. > > Thank you for your reaction. > Best regards. > > Jerzy Karczmarczuk > > > ------------------------------------------------------------------------------ > RSA® Conference 2012 > Save $700 by Nov 18 > Register now! > http://p.sf.net/sfu/rsa-sfdev2dev1 > _______________________________________________ > Visualpython-users mailing list > Vis...@li... > https://lists.sourceforge.net/lists/listinfo/visualpython-users > > |
From: Jerzy K. <jer...@un...> - 2011-11-02 13:21:06
|
James Mueller : > One point is that rate and sleep have different purposes. > > rate is trying to make sure that each iteration of the loop takes a > time slp. So to get the same effect from sleep, you would need to > call time.sleep(slp-delta), where delta is the amount of time taken by > the instructions in the rest of the loop. > OK, but doesn't matter. Some simple instructions in Python don't take much time. (And if the rendering thread is autonomous, it doesn't waste the time of the main process. If in my cited program you eliminate all waiting, the process terminates before you are able to see any movement. Who will need an incredibly fine tuning while programming in Python? You may make some variants, if you wish, e.g. introduce into a loop a timing block which measures the time lapse /since its last call/, and wait until your "rate" condition is fulfilled. Clumsy... == The problem is the thread safety. The sleep() call *is* a replacement for rate(), that's all I wanted to say. Thank you for your reaction. Best regards. Jerzy Karczmarczuk |
From: James M. <mu...@pi...> - 2011-11-02 12:14:53
|
One point is that rate and sleep have different purposes. rate is trying to make sure that each iteration of the loop takes a time slp. So to get the same effect from sleep, you would need to call time.sleep(slp-delta), where delta is the amount of time taken by the instructions in the rest of the loop. On Nov 2, 2011, at 7:35 AM, Jerzy Karczmarczuk wrote: > I noticed that the use of rate(...) introduces some conflicts to threads. Bruce Sherwood answers: >> I don't feel terribly competent concerning the threading aspects of >> VPython and have no ready explanation of what you've observed about >> sleep and rate. However, I have reason to expect that generally >> speaking, using the threading module should work okay, as you've >> found, because I believe that's all within the Python machinery. In >> contrast, the rendering thread that runs about 30 times per second >> shuts down Python completely while rendering is in progress. > Thank you. > This last point is not a problem. Python itself is a dinosaur, with its GIL (Global Interpreter Lock), and it is not very suitable to make something like an operating system, or a general multiprocessed simulation program within. But threads work well. This DOES NOT mean that they must work correctly with binary modules, such as cvisual, and it seems that we have such a case here. > > The rendering doesn't show any pathologies - as far as my VERY INCOMPLETE tests show - but the function rate(...) seems buggy (from this perspective!). This is the simplified skeleton of my program, which moves the objects obj through the space > > rr=RLock() > def move(args...): > ... > for i in seq(): > # rr.acquire() > # rate(1.0/slp) > # rr.release() > obj.pos=newxyz() > obj.trail.append(pos=obj.pos) > time.sleep(slp) > ... > t1=Thread(target=move, ...) > t2=Thread(target=move, ...) # with different params, geom and timing. > t1.start() > t2.start() > # ===================== > > This program works without any problems. > 1. Comment time.sleep, uncomment rate(). Result: the thread t1 runs until completion, then the second particle starts moving. (Here the RLock is not used.) You can imagine my surprise... > > 2. Place rate() within a critical section, by uncommenting acquire() and release() of the reentrant lock, which can be released only by its owner. Ha! Try to guess what happens... (It is in principle possible, but not obvious.) > > The behaviour is funny: the two particles move concurrently, but synchronized! Despite the differences in timing (the parameter slp), now in every thread exactly one step is executed before the relinquishing of control. Notice that I didn't put in the critical section the instructions which deal with the rendering! > > Lesson to learn: if you want an asynchronous parallelism, even without race conditions or other conflicts, DON'T USE rate(), since - it seems (I looked up the file rate.cpp) - it uses one, global timer in a thread of its own, and that's it. > > My proposal for the future versions of VPython, with (probably) rather feeble priority: either remove rate() altogether, and demand that the users use the timing procedures in the kernel of Python + the time module, etc., > > or revise thoroughly the threading aspects of cvisual. > > == > Of course, it is quite possible that I am saying rubbish, it was just one hour of testing... > > +++ > > A secondary comment on a slightly different subject. Bruce Sherwood says that the rendering thread works at a speed of about 30 frames/second. But VPython offers now the stereo vision, with the possibility to use shutter glasses. > I suspect that at this speed, it might be insufficiently comfortable for everybody... Perhaps it can be boosted and/or parameterized?... > > Thank you very much, and my best regards. > > Jerzy Karczmarczuk > Caen, France > > PS. The complete version of the program if you want to check it, is here: > http://users.info.unicaen.fr/~karczma/TEACH/VPY/thr_test0.py > > > > > ------------------------------------------------------------------------------ > RSA® Conference 2012 > Save $700 by Nov 18 > Register now! > http://p.sf.net/sfu/rsa-sfdev2dev1_______________________________________________ > Visualpython-users mailing list > Vis...@li... > https://lists.sourceforge.net/lists/listinfo/visualpython-users |
From: Jerzy K. <jer...@un...> - 2011-11-02 11:35:10
|
I noticed that the use of rate(...) introduces some conflicts to threads. Bruce Sherwood answers: > I don't feel terribly competent concerning the threading aspects of > VPython and have no ready explanation of what you've observed about > sleep and rate. However, I have reason to expect that generally > speaking, using the threading module should work okay, as you've > found, because I believe that's all within the Python machinery. In > contrast, the rendering thread that runs about 30 times per second > shuts down Python completely while rendering is in progress. Thank you. This last point is not a problem. Python itself is a dinosaur, with its GIL (Global Interpreter Lock), and it is not very suitable to make something like an operating system, or a general multiprocessed simulation program within. But threads work well. This DOES NOT mean that they must work correctly with binary modules, such as cvisual, and it seems that we have such a case here. The rendering doesn't show any pathologies - as far as my VERY INCOMPLETE tests show - but the function rate(...) seems buggy (from this perspective!). This is the simplified skeleton of my program, which moves the objects obj through the space rr=RLock() def move(args...): ... for i in seq(): # rr.acquire() # rate(1.0/slp) # rr.release() obj.pos=newxyz() obj.trail.append(pos=obj.pos) time.sleep(slp) ... t1=Thread(target=move, ...) t2=Thread(target=move, ...) # with different params, geom and timing. t1.start() t2.start() # ===================== This program works without any problems. 1. Comment time.sleep, uncomment rate(). Result: the thread t1 runs until completion, then the second particle starts moving. (Here the RLock is not used.) You can imagine my surprise... 2. Place rate() within a critical section, by uncommenting acquire() and release() of the reentrant lock, which can be released only by its owner. Ha! Try to guess what happens... (It is in principle possible, but not obvious.) The behaviour is funny: the two particles move concurrently, but synchronized! Despite the differences in timing (the parameter slp), now in every thread exactly one step is executed before the relinquishing of control. Notice that I didn't put in the critical section the instructions which deal with the rendering! Lesson to learn: if you want an *asynchronous parallelism*, even without race conditions or other conflicts, DON'T USE rate(), since - it seems (I looked up the file rate.cpp) - it uses one, global timer in a thread of its own, and that's it. My proposal for the future versions of VPython, with (probably) rather feeble priority: either remove rate() altogether, and demand that the users use the timing procedures in the kernel of Python + the time module, etc., or revise thoroughly the threading aspects of cvisual. == Of course, it is quite possible that I am saying rubbish, it was just one hour of testing... +++ A secondary comment on a slightly different subject. Bruce Sherwood says that the rendering thread works at a speed of about 30 frames/second. But VPython offers now the stereo vision, with the possibility to use shutter glasses. I suspect that at this speed, it might be insufficiently comfortable for everybody... Perhaps it can be boosted and/or parameterized?... Thank you very much, and my best regards. Jerzy Karczmarczuk Caen, France PS. The complete version of the program if you want to check it, is here: http://users.info.unicaen.fr/~karczma/TEACH/VPY/thr_test0.py |
From: Bruce S. <Bru...@nc...> - 2011-11-02 02:21:14
|
I don't feel terribly competent concerning the threading aspects of VPython and have no ready explanation of what you've observed about sleep and rate. However, I have reason to expect that generally speaking, using the threading module should work okay, as you've found, because I believe that's all within the Python machinery. In contrast, the rendering thread that runs about 30 times per second shuts down Python completely while rendering is in progress. Bruce Sherwood On Tue, Nov 1, 2011 at 5:21 PM, Jerzy Karczmarczuk <jer...@un...> wrote: > Does anybody has some experience with multithreading and VPython? > Standard examples are silent, the tutorial just mentions that the > rendering thread is separate > > I did some simple tests (with the threading module without any locks, > some "planets" wandering concurrently on the screen), no serious > problems, but if somebody tried some torture example, and noticed > something, I would be grateful to know. > > I noticed something I cannot interpret. Two objects move, and two loops > running in different threads execute time.sleep(slp). Nothing wrong. I > replace the sleeping by rate(1.0/slp), and the second thread waits until > the first terminates. Why? > > Maestro Bruce? > > All the best. > > Jerzy Karczmarczuk > Caen, France. > > > ------------------------------------------------------------------------------ > RSA® Conference 2012 > Save $700 by Nov 18 > Register now! > http://p.sf.net/sfu/rsa-sfdev2dev1 > _______________________________________________ > Visualpython-users mailing list > Vis...@li... > https://lists.sourceforge.net/lists/listinfo/visualpython-users > |
From: Jerzy K. <jer...@un...> - 2011-11-01 23:40:19
|
Does anybody has some experience with multithreading and VPython? Standard examples are silent, the tutorial just mentions that the rendering thread is separate I did some simple tests (with the threading module without any locks, some "planets" wandering concurrently on the screen), no serious problems, but if somebody tried some torture example, and noticed something, I would be grateful to know. I noticed something I cannot interpret. Two objects move, and two loops running in different threads execute time.sleep(slp). Nothing wrong. I replace the sleeping by rate(1.0/slp), and the second thread waits until the first terminates. Why? Maestro Bruce? All the best. Jerzy Karczmarczuk Caen, France. |