Menu
▾
▴
visualpython-users
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: Jonathan B. <jbr...@ea...> - 2006-08-12 18:28:07
|
On Sat, 2006-08-12 at 18:47 +0200, Jaap Spies wrote: > Bruce Sherwood wrote: > > 4.beta5 is now downloadable from > > http://sourceforge.net/projects/visualpython > > > > Trying to install the 4.beta5 under SAGE (Software for Algebra and Geometry > Experimentation), see http://modular.math.washington.edu/sage/index.html > > SAGE comes with its own Python, so I did the following configure: > > >> [root@paix buildbeta]# PYTHON=/usr/local/sage/local/bin/python ../visual-4.beta5/configure --prefix=/usr/local/sage/local > >> > >> [...] > >> > > But the following make failed: > > >> [root@paix buildbeta]# make > >> Making all in site-packages/visual > >> make[1]: Entering directory `/home/jaap/work/downloads/buildbeta/site-packages/visual' > >> make[1]: Nothing to be done for `all'. > >> make[1]: Leaving directory `/home/jaap/work/downloads/buildbeta/site-packages/visual' > >> Making all in src > >> make[1]: Entering directory `/home/jaap/work/downloads/buildbeta/src' > >> Compiling ../../visual-4.beta5/src/core/arrow.cpp ... > >> Compiling ../../visual-4.beta5/src/core/axial.cpp ... > >> Compiling ../../visual-4.beta5/src/core/box.cpp ... > >> Compiling ../../visual-4.beta5/src/core/cone.cpp ... > >> Compiling ../../visual-4.beta5/src/core/cylinder.cpp ... > >> Compiling ../../visual-4.beta5/src/core/display_kernel.cpp ... > >> Compiling ../../visual-4.beta5/src/core/ellipsoid.cpp ... > >> Compiling ../../visual-4.beta5/src/core/frame.cpp ... > >> Compiling ../../visual-4.beta5/src/core/label.cpp ... > >> Compiling ../../visual-4.beta5/src/core/mouseobject.cpp ... > >> Compiling ../../visual-4.beta5/src/core/primitive.cpp ... > >> Compiling ../../visual-4.beta5/src/core/pyramid.cpp ... > >> Compiling ../../visual-4.beta5/src/core/rectangular.cpp ... > >> Compiling ../../visual-4.beta5/src/core/renderable.cpp ... > >> Compiling ../../visual-4.beta5/src/core/ring.cpp ... > >> Compiling ../../visual-4.beta5/src/core/sphere.cpp ... > >> Compiling ../../visual-4.beta5/src/python/convex.cpp ... > >> Compiling ../../visual-4.beta5/src/python/curve.cpp ... > >> Compiling ../../visual-4.beta5/src/python/cvisualmodule.cpp ... > >> Compiling ../../visual-4.beta5/src/python/faces.cpp ... > >> Compiling ../../visual-4.beta5/src/python/num_util.cpp ... > >> Compiling ../../visual-4.beta5/src/python/num_util_impl_numarray.cpp ... > >> make[1]: *** [num_util_impl_numarray.lo] Error 1 > >> make[1]: Leaving directory `/home/jaap/work/downloads/buildbeta/src' > >> make: *** [all-recursive] Error 1 > >> [root@paix buildbeta]# > >> Did configure properly detect the existence and availability of numarray? What is the actual error (it should be in src/build.log)? -Jonathan |
|
From: Jaap S. <j....@hc...> - 2006-08-12 16:47:57
|
Bruce Sherwood wrote: > 4.beta5 is now downloadable from > http://sourceforge.net/projects/visualpython > Trying to install the 4.beta5 under SAGE (Software for Algebra and Geometry Experimentation), see http://modular.math.washington.edu/sage/index.html SAGE comes with its own Python, so I did the following configure: >> [root@paix buildbeta]# PYTHON=/usr/local/sage/local/bin/python ../visual-4.beta5/configure --prefix=/usr/local/sage/local >> >> [...] >> But the following make failed: >> [root@paix buildbeta]# make >> Making all in site-packages/visual >> make[1]: Entering directory `/home/jaap/work/downloads/buildbeta/site-packages/visual' >> make[1]: Nothing to be done for `all'. >> make[1]: Leaving directory `/home/jaap/work/downloads/buildbeta/site-packages/visual' >> Making all in src >> make[1]: Entering directory `/home/jaap/work/downloads/buildbeta/src' >> Compiling ../../visual-4.beta5/src/core/arrow.cpp ... >> Compiling ../../visual-4.beta5/src/core/axial.cpp ... >> Compiling ../../visual-4.beta5/src/core/box.cpp ... >> Compiling ../../visual-4.beta5/src/core/cone.cpp ... >> Compiling ../../visual-4.beta5/src/core/cylinder.cpp ... >> Compiling ../../visual-4.beta5/src/core/display_kernel.cpp ... >> Compiling ../../visual-4.beta5/src/core/ellipsoid.cpp ... >> Compiling ../../visual-4.beta5/src/core/frame.cpp ... >> Compiling ../../visual-4.beta5/src/core/label.cpp ... >> Compiling ../../visual-4.beta5/src/core/mouseobject.cpp ... >> Compiling ../../visual-4.beta5/src/core/primitive.cpp ... >> Compiling ../../visual-4.beta5/src/core/pyramid.cpp ... >> Compiling ../../visual-4.beta5/src/core/rectangular.cpp ... >> Compiling ../../visual-4.beta5/src/core/renderable.cpp ... >> Compiling ../../visual-4.beta5/src/core/ring.cpp ... >> Compiling ../../visual-4.beta5/src/core/sphere.cpp ... >> Compiling ../../visual-4.beta5/src/python/convex.cpp ... >> Compiling ../../visual-4.beta5/src/python/curve.cpp ... >> Compiling ../../visual-4.beta5/src/python/cvisualmodule.cpp ... >> Compiling ../../visual-4.beta5/src/python/faces.cpp ... >> Compiling ../../visual-4.beta5/src/python/num_util.cpp ... >> Compiling ../../visual-4.beta5/src/python/num_util_impl_numarray.cpp ... >> make[1]: *** [num_util_impl_numarray.lo] Error 1 >> make[1]: Leaving directory `/home/jaap/work/downloads/buildbeta/src' >> make: *** [all-recursive] Error 1 >> [root@paix buildbeta]# >> >> >> >> >> But a 'make clean' and '../visual-4.beta5/configure' without arguments succeeded >> [root@paix buildbeta]# make >> Making all in site-packages/visual >> make[1]: Entering directory `/home/jaap/work/downloads/buildbeta/site-packages/visual' >> make[1]: Nothing to be done for `all'. >> make[1]: Leaving directory `/home/jaap/work/downloads/buildbeta/site-packages/visual' >> Making all in src >> make[1]: Entering directory `/home/jaap/work/downloads/buildbeta/src' >> Compiling ../../visual-4.beta5/src/core/arrow.cpp ... >> Compiling ../../visual-4.beta5/src/core/axial.cpp ... >> Compiling ../../visual-4.beta5/src/core/box.cpp ... >> Compiling ../../visual-4.beta5/src/core/cone.cpp ... >> Compiling ../../visual-4.beta5/src/core/cylinder.cpp ... >> Compiling ../../visual-4.beta5/src/core/display_kernel.cpp ... >> Compiling ../../visual-4.beta5/src/core/ellipsoid.cpp ... >> Compiling ../../visual-4.beta5/src/core/frame.cpp ... >> Compiling ../../visual-4.beta5/src/core/label.cpp ... >> Compiling ../../visual-4.beta5/src/core/mouseobject.cpp ... >> Compiling ../../visual-4.beta5/src/core/primitive.cpp ... >> Compiling ../../visual-4.beta5/src/core/pyramid.cpp ... >> Compiling ../../visual-4.beta5/src/core/rectangular.cpp ... >> Compiling ../../visual-4.beta5/src/core/renderable.cpp ... >> Compiling ../../visual-4.beta5/src/core/ring.cpp ... >> Compiling ../../visual-4.beta5/src/core/sphere.cpp ... >> Compiling ../../visual-4.beta5/src/python/convex.cpp ... >> Compiling ../../visual-4.beta5/src/python/curve.cpp ... >> Compiling ../../visual-4.beta5/src/python/cvisualmodule.cpp ... >> Compiling ../../visual-4.beta5/src/python/faces.cpp ... >> Compiling ../../visual-4.beta5/src/python/num_util.cpp ... >> Compiling ../../visual-4.beta5/src/python/num_util_impl_numarray.cpp ... >> Compiling ../../visual-4.beta5/src/python/num_util_impl_numeric.cpp ... >> Compiling ../../visual-4.beta5/src/python/scalar_array.cpp ... >> [...] >> Compiling ../../visual-4.beta5/src/python/wrap_ustring.cpp ... >> Linking cvisualmodule.la ... >> Installing cvisualmodule.la to /home/jaap/downloads/buildbeta/site-packages/cvisualmodule.la >> [...] > Why? I don't understand what is going on. Jaap |
|
From: Bruce S. <Bru...@nc...> - 2006-08-11 15:57:12
|
Jonathan has explained the general approach. But if you're just rotating about the y axis see stonehenge.py (one of the VPython sample programs) in which sideways mouse motions rotate scene.forward and vertical mouse motions move scene.center forward and back, with the effect that you can fly through the scene. For sliders, see colorsliders.py or controltest.py. For keyboard interactions, see that section of the VPpython help accessible from within IDLE. Bruce Sherwood Jonathan Brandmeyer wrote: >On Fri, 2006-08-11 at 09:37 +0300, Andrey Antonov wrote: > > >>Hi, >> >>Suppose that we have a scene with objects. >>I'd like to assign to a key or a slider possibility to rotate the scene >>uniformly like to move point of view on a parallel or meridian associated >>with >>scene.center. I need help (or more explanations, or samples or links) about >>the iteration formulas for changing the point of view, I mean in cartesian, >>spherical or cylindrical coordinates for example. >> >> > >The orientation of the camera is computed using forward, up, center, and >range. In most cases, in order to simply rotate the camera about it's >center, you will want to >-compute the appropriate 3x3 rotation matrix >-multiply scene.forward by it, and assign the result to scene.forward. > >Google for glRotate to get the definition of a rotation matrix that >VPython uses. Alternatively, look at the sources. In VPython 4.x, >src/core/display_kernel.cpp: display_kernel::report_mouse_motion() >handles the effects of dragging the mouse around the window. >src/core/util/tmatrix.cpp includes a routine for constructing a rotation >matrix as well. > >HTH, >-Jonathan > > >------------------------------------------------------------------------- >Using Tomcat but need to do more? Need to support web services, security? >Get stuff done quickly with pre-integrated technology to make your job easier >Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo >http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 >_______________________________________________ >Visualpython-users mailing list >Vis...@li... >https://lists.sourceforge.net/lists/listinfo/visualpython-users > > |
|
From: Jonathan B. <jbr...@ea...> - 2006-08-11 14:40:42
|
On Fri, 2006-08-11 at 09:37 +0300, Andrey Antonov wrote: > Hi, > > Suppose that we have a scene with objects. > I'd like to assign to a key or a slider possibility to rotate the scene > uniformly like to move point of view on a parallel or meridian associated > with > scene.center. I need help (or more explanations, or samples or links) about > the iteration formulas for changing the point of view, I mean in cartesian, > spherical or cylindrical coordinates for example. The orientation of the camera is computed using forward, up, center, and range. In most cases, in order to simply rotate the camera about it's center, you will want to -compute the appropriate 3x3 rotation matrix -multiply scene.forward by it, and assign the result to scene.forward. Google for glRotate to get the definition of a rotation matrix that VPython uses. Alternatively, look at the sources. In VPython 4.x, src/core/display_kernel.cpp: display_kernel::report_mouse_motion() handles the effects of dragging the mouse around the window. src/core/util/tmatrix.cpp includes a routine for constructing a rotation matrix as well. HTH, -Jonathan |
|
From: Andrey A. <an...@uc...> - 2006-08-11 06:39:14
|
Hi, Suppose that we have a scene with objects. I'd like to assign to a key or a slider possibility to rotate the scene uniformly like to move point of view on a parallel or meridian associated with scene.center. I need help (or more explanations, or samples or links) about the iteration formulas for changing the point of view, I mean in cartesian, spherical or cylindrical coordinates for example. Thanks Andrio |
|
From: Bruce S. <Bru...@nc...> - 2006-08-10 19:03:51
|
Thanks for the report. It may be some months before it can be addressed,=20 alas. Bruce Sherwood Flavio Coelho wrote: > Hi, > > I am getting a "Exception: degenerate primitive" error. Here is how=20 > to trigger the error: > > > In [1]: import visual > > In [2]: a=3Dvisual.box() > > In [3]: a.height=3Da.length=3Da.width=3D0 > > In [4]: a.height=3Da.length=3Da.width=3D1 > -----------------------------------------------------------------------= ---- > exceptions.Exception Traceback (most=20 > recent call last) > > /home/fccoelho/Documents/SVS/modelo3/<console> > > Exception: Degenerate primitive > > I am using visual 3.2.9 > > thanks, > > --=20 > Fl=E1vio Code=E7o Coelho > registered Linux user # 386432 > --------------------------- > "Laws are like sausages. It's better not to see them being made." > Otto von Bismark > >------------------------------------------------------------------------ > >------------------------------------------------------------------------= - >Using Tomcat but need to do more? Need to support web services, security= ? >Get stuff done quickly with pre-integrated technology to make your job e= asier >Download IBM WebSphere Application Server v.1.0.1 based on Apache Geroni= mo >http://sel.as-us.falkag.net/sel?cmd=3Dlnk&kid=3D120709&bid=3D263057&dat=3D= 121642 > >------------------------------------------------------------------------ > >_______________________________________________ >Visualpython-users mailing list >Vis...@li... >https://lists.sourceforge.net/lists/listinfo/visualpython-users > =20 > |
|
From: Bruce S. <Bru...@nc...> - 2006-08-10 18:20:20
|
4.beta5 is now downloadable from http://sourceforge.net/projects/visualpython Fixed many bugs. Documentation now included. The new example program texture_and_lighting.py displays many of the new features of version 4 created by Jonathan Brandmeyer (a swinging spotlight illuminates a translucent beach ball that rolls on a wood-texture table). In the "Recent developments" section of vpython.org you can read a summary of the new features, which is also included in the documentation contained in the release. This includes a description of remaining known bugs, some of which are serious, which means that you may enjoy playing with the exciting new features, but be aware that there are problems. I am not going to be able to do any more work on VPython for about three months, as the publisher of the physics textbook Ruth Chabay and I have written needs a second edition completed by November. Jonathan Brandmeyer has graduated from NCSU and is moving on to other things. So unless someone else steps forward, it is possible that this version 4 beta is frozen for several months. Bruce Sherwood |
|
From: Flavio C. <fcc...@gm...> - 2006-08-10 12:34:46
|
Hi, I am getting a "Exception: degenerate primitive" error. Here is how to trigger the error: In [1]: import visual In [2]: a=3Dvisual.box() In [3]: a.height=3Da.length=3Da.width=3D0 In [4]: a.height=3Da.length=3Da.width=3D1 --------------------------------------------------------------------------- exceptions.Exception Traceback (most recent call last) /home/fccoelho/Documents/SVS/modelo3/<console> Exception: Degenerate primitive I am using visual 3.2.9 thanks, --=20 Fl=E1vio Code=E7o Coelho registered Linux user # 386432 --------------------------- "Laws are like sausages. It's better not to see them being made." Otto von Bismark |
|
From: Jonathan B. <jbr...@ea...> - 2006-08-07 13:46:25
|
On Sun, 2006-08-06 at 14:24 -0300, Flavio Coelho wrote:
> Hi,
>=20
> apparently vpython 3.2.9 doesn't accept unicode strings in labels. It
> does, however accept the latin-1(iso-8859-1) encoding without
> problems:
>=20
> In [3]: a=3Dvisual.label(text=3D's=E3o')
>=20
> In [4]: a.text=3Dunicode ('s=E3o','latin-1')
> -------------------------------------------------------------------------=
--
> Boost.Python.ArgumentError Traceback (most
> recent call last)
>=20
> /home/fccoelho/<console>=20
>=20
> ArgumentError: Python argument types in
> None.None(label, unicode)
> did not match C++ signature:
> None(visual::Label {lvalue}, std::string)
>=20
> In [5]: unicode('s=E3o','latin-1')
> Out[5]: u's\xe3o'=20
>=20
> In [6]: print unicode('s=E3o','latin-1')
> s=E3o
> I need to put unicode strings into labels, is there any way of doing
> this? Will the next release of vpython handle Unicode?
The 4.x series should handle Unicode strings, but only on Linux+Gtk (or
one of the earlier Windows+GTK builds).
HTH,
-Jonathan
|
|
From: Bruce S. <Bru...@nc...> - 2006-08-07 03:21:48
|
Now available at http://sourceforge.net/projects/visualpython for Windows and Linux/Unix: Improvements to scene viewing and autoscaling, including hysteresis that prevents fibrillation, where the camera jitters in and out. Everywhere you can now use "opacity" instead of "alpha". Graph and stonehenge now work. Labels still problematic on Windows. Also still true that rings have fixed radius and setting axis other than in x direction makes mouse coordinates wrong. Arrows still get picked by mousing far from the arrow. The hysteresis feature can be seen by running the example program bounce.py. It used to be that the camera zoomed in and out as the ball bounced up and down, but now the camera stays rock steady. The scheme is basically this: If the scene grows, move the camera back to include the larger scene (unless the scene is merely growing back to a previous size). But if the scene shrinks somewhat, don't move the camera in, unless the scene shrinks drastically as can happen when you're first assembling a scene. The opacity vs. alpha issue is this: It has always been true that this property was called "opacity" in labels. In the computer graphics community it is often called "alpha", but not always. For example, in Photoshop the term "alpha" is used with many different kinds of graphics-associated channels, not just opacity. In 4.beta4, you can still use alpha as a synonym for opacity, but the documentation (when written) will emphasize opacity. Bruce Sherwood |
|
From: Flavio C. <fcc...@gm...> - 2006-08-06 17:24:42
|
Hi,
apparently vpython 3.2.9 doesn't accept unicode strings in labels. It does,
however accept the latin-1(iso-8859-1) encoding without problems:
In [3]: a=3Dvisual.label(text=3D's=E3o')
In [4]: a.text=3Dunicode('s=E3o','latin-1')
---------------------------------------------------------------------------
Boost.Python.ArgumentError Traceback (most
recent call last)
/home/fccoelho/<console>
ArgumentError: Python argument types in
None.None(label, unicode)
did not match C++ signature:
None(visual::Label {lvalue}, std::string)
In [5]: unicode('s=E3o','latin-1')
Out[5]: u's\xe3o'
In [6]: print unicode('s=E3o','latin-1')
s=E3o
I need to put unicode strings into labels, is there any way of doing this?
Will the next release of vpython handle Unicode?
thanks,
--=20
Fl=E1vio Code=E7o Coelho
registered Linux user # 386432
---------------------------
"Laws are like sausages. It's better not to see them being made."
Otto von Bismark
|
|
From: Ruth C. <rwc...@un...> - 2006-08-02 03:29:46
|
If you are using VPython in the teaching of physics or astronomy, at any level, *please* consider presenting a poster at the joint meeting of AAPT (American Association of Physics Teachers) and AAS (American Astronomical Society), in Seattle, WA, January 6-10, 2007. We are experimenting with a new format for a poster session, which will include live demos. Presentations on how you have modified, extended, or customized instructional applications of VPython at your institution, as well as on new approaches or applications, are very welcome. This will be an opportunity to exchange ideas with others who are using VPython in their teaching. Here is the call for papers for this session: *Physics Education with Vpython* Demonstrate your application of VPython in teaching physics or astronomy, with a poster and live demo. Bring a laptop; power outlets will be provided. Explain how you integrate 3D lecture demos, student programs, visualization tools, or other VPython applications into your instruction. This poster/demo session is intended to allow extended interaction and discussion. To submit an abstract, or to see more about the meeting, go to: http://www.aapt.org/Events/call4papers.cfm Abstracts are due by September 7, 2006. I'd be happy to try to answer any questions you may have about this session. Ruth Chabay -- ------------------------------- Ruth Chabay Professor of Physics North Carolina State University Raleigh NC 27695-8202 office: 506C Cox Hall email: Rut...@nc... |
|
From: Bruce S. <Bru...@nc...> - 2006-07-31 02:11:20
|
At http://sourceforge.net/projects/visualpython there is a new release 4.beta3 that fixes some (but not all) known bugs in the new beta version of VPython. See the "Recent developments" section of vpython.org for information about this new version. Notes: Significant restructuring: simplified scaling and viewing; various bugs fixed. Known remaining bugs: Rings have fixed radius, and setting axis other than in x direction has side effect of making mouse coordinates wrong. Arrows get picked by mousing far from the arrow. Labels not working at all well on Windows. Graphing not finished, though it works if x and y axes are comparable in scale. Mouse handling buggy (e.g. in stonehenge example rotation is way too fast; right drag and rotate are commingled). Some view stuff still not quite right (move in toward stonehenge and the front disappears too soon). Bruce Sherwood |
|
From: Jonathan B. <jbr...@ea...> - 2006-07-18 16:36:02
|
On Tue, 2006-07-18 at 14:12 +0200, Fr=E9d=E9ric Buelens wrote: > Hello, >=20 >=20 > I have a compilation problem with vpython. The configure script works > fine, but make fails at the linking time. Here is the make output: >=20 >=20 > g++ -fPIC -shared > -nostdlib /usr/lib/gcc/x86_64-redhat-linux/3.4.4/../../../../lib64/crti.o= /usr/lib/gcc/x86_64-redhat-linux/3.4.4/crtbeginS.o .libs/arrow.o .libs/ax= ial.o .libs/box.o .libs/color.o .libs/cone.o .libs/convex.o .libs/curve.o .= libs/cvisualmodule.o .libs/cylinder.o .libs/display.o .libs/displaylist.o .= libs/ellipsoid.o .libs/exceptions.o .libs/num_util.o .libs/scalar_array.o .= libs/vector_array.o .libs/slice.o .libs/sphmodel.o .libs/faceset.o .libs/fr= ame.o .libs/gldevice.o .libs/kbobject.o .libs/light.o .libs/label.o .libs/m= ouseobject.o .libs/prim.o .libs/vector.o .libs/pyramid.o .libs/rate.o .libs= /ring.o .libs/sphere.o .libs/tmatrix.o .libs/vcache.o .libs/cylmodel.o .lib= s/num_util_impl_numeric.o .libs/num_util_impl_numarray.o .libs/glcontext.o = .libs/platlinux.o .libs/xgl.o -Wl,--rpath -Wl,/usr/lib64 -Wl,--rpath -Wl,/= usr/lib64 -L/usr/lib64 -L/usr/X11R6/lib64 /usr/lib64/libgtk.so /usr/lib64/l= ibgdk.so /usr/lib64/libgmodule.so -ldl -lXi -lXext -lX11 -lgtkgl -lGL -lGLU= /usr/lib64/libgthread.so -lpthread /usr/lib64/libglib.so -lboost_python -L= /usr/lib/gcc/x86_64-redhat-linux/3.4.4 -L/usr/lib/gcc/x86_64-redhat-linux/3= .4.4/../../../../lib64 -L/usr/lib/gcc/x86_64-redhat-linux/3.4.4/../../.. -L= /lib/../lib64 -L/usr/lib/../lib64 -lstdc++ -lm -lc -lgcc_s /usr/lib/gcc/x86= _64-redhat-linux/3.4.4/crtendS.o /usr/lib/gcc/x86_64-redhat-linux/3.4.4/../= ../../../lib64/crtn.o -Wl,--version-script=3D../../visual-3.2.9/src/linux-= symbols.map -Wl,-soname -Wl,cvisualmodule.so.1 -o .libs/cvisualmodule.so.1.= 0.0 > /usr/bin/ld: /usr/lib64/libboost_python.a(numeric.o): relocation > R_X86_64_32 against `a local symbol' can not be used when making a > shared object; recompile with -fPIC > /usr/lib64/libboost_python.a: could not read symbols: Bad value > collect2: ld returned 1 exit status > [root@hydra999 build]#=20 Where did you get this build of /usr/lib64/libboost_python.a? Did it come with your distribution or did you build it yourself? If it is provided by the distribution, you will need to find a shared library build of this file (there should be one or more liboost_python*.so files). Otherwise, download Boost 1.33.1 from www.boost.org and install it manually, according to the directions on their website. Then perform step 5 of "Building the Boost libraries" from here: http://www.vpython.org/Building%20VPython%20on%20SuSE.html (modified for the latest boost version, of course). HTH, -Jonathan |
|
From: <fbu...@ul...> - 2006-07-18 12:13:10
|
Hello, I have a compilation problem with vpython. The configure script works =20= fine, but make fails at the linking time. Here is the make output: [root@hydra999 build]# make Making all in site-packages/visual make[1]: Entering directory `/bfucc/USRLOCAL/src/build/site-packages/=20 visual' make[1]: Nothing to be done for `all'. make[1]: Leaving directory `/bfucc/USRLOCAL/src/build/site-packages/=20 visual' Making all in src make[1]: Entering directory `/bfucc/USRLOCAL/src/build/src' Updating dependancy information for ../../visual-3.2.9/src/xgl.cpp ... Updating dependancy information for ../../visual-3.2.9/src/=20 platlinux.cpp ... Updating dependancy information for ../../visual-3.2.9/src/=20 glcontext.cpp ... Updating dependancy information for ../../visual-3.2.9/src/=20 num_util_impl_numarray.cpp ... Updating dependancy information for ../../visual-3.2.9/src/=20 num_util_impl_numeric.cpp ... Updating dependancy information for ../../visual-3.2.9/src/=20 cylmodel.cpp ... Updating dependancy information for ../../visual-3.2.9/src/=20 vcache.cpp ... Updating dependancy information for ../../visual-3.2.9/src/=20 tmatrix.cpp ... Updating dependancy information for ../../visual-3.2.9/src/=20 sphere.cpp ... Updating dependancy information for ../../visual-3.2.9/src/ring.cpp ... Updating dependancy information for ../../visual-3.2.9/src/rate.cpp ... Updating dependancy information for ../../visual-3.2.9/src/=20 pyramid.cpp ... Updating dependancy information for ../../visual-3.2.9/src/=20 vector.cpp ... Updating dependancy information for ../../visual-3.2.9/src/prim.cpp ... Updating dependancy information for ../../visual-3.2.9/src/=20 mouseobject.cpp ... Updating dependancy information for ../../visual-3.2.9/src/label.cpp ... Updating dependancy information for ../../visual-3.2.9/src/light.cpp ... Updating dependancy information for ../../visual-3.2.9/src/=20 kbobject.cpp ... Updating dependancy information for ../../visual-3.2.9/src/=20 gldevice.cpp ... Updating dependancy information for ../../visual-3.2.9/src/frame.cpp ... Updating dependancy information for ../../visual-3.2.9/src/=20 faceset.cpp ... Updating dependancy information for ../../visual-3.2.9/src/=20 sphmodel.cpp ... Updating dependancy information for ../../visual-3.2.9/src/slice.cpp ... Updating dependancy information for ../../visual-3.2.9/src/=20 vector_array.cpp ... Updating dependancy information for ../../visual-3.2.9/src/=20 scalar_array.cpp ... Updating dependancy information for ../../visual-3.2.9/src/=20 num_util.cpp ... Updating dependancy information for ../../visual-3.2.9/src/=20 exceptions.cpp ... Updating dependancy information for ../../visual-3.2.9/src/=20 ellipsoid.cpp ... Updating dependancy information for ../../visual-3.2.9/src/=20 displaylist.cpp ... Updating dependancy information for ../../visual-3.2.9/src/=20 display.cpp ... Updating dependancy information for ../../visual-3.2.9/src/=20 cylinder.cpp ... Updating dependancy information for ../../visual-3.2.9/src/=20 cvisualmodule.cpp ... Updating dependancy information for ../../visual-3.2.9/src/curve.cpp ... Updating dependancy information for ../../visual-3.2.9/src/=20 convex.cpp ... Updating dependancy information for ../../visual-3.2.9/src/cone.cpp ... Updating dependancy information for ../../visual-3.2.9/src/color.cpp ... Updating dependancy information for ../../visual-3.2.9/src/box.cpp ... Updating dependancy information for ../../visual-3.2.9/src/axial.cpp ... Updating dependancy information for ../../visual-3.2.9/src/arrow.cpp ... make[1]: Leaving directory `/bfucc/USRLOCAL/src/build/src' make[1]: Entering directory `/bfucc/USRLOCAL/src/build/src' This is a quiet Makefile. If make exits with an error, check src/=20 build.log to see the complete error message(s). In the event of an =20 error that you cannot debug, please send a message to visualpython-=20 us...@li..., including the files config.log and src/=20 build.log, requesting assistance. Compiling ../../visual-3.2.9/src/arrow.cpp ... Compiling ../../visual-3.2.9/src/axial.cpp ... Compiling ../../visual-3.2.9/src/box.cpp ... Compiling ../../visual-3.2.9/src/color.cpp ... Compiling ../../visual-3.2.9/src/cone.cpp ... Compiling ../../visual-3.2.9/src/convex.cpp ... Compiling ../../visual-3.2.9/src/curve.cpp ... Compiling ../../visual-3.2.9/src/cvisualmodule.cpp ... Compiling ../../visual-3.2.9/src/cylinder.cpp ... Compiling ../../visual-3.2.9/src/display.cpp ... Compiling ../../visual-3.2.9/src/displaylist.cpp ... Compiling ../../visual-3.2.9/src/ellipsoid.cpp ... Compiling ../../visual-3.2.9/src/exceptions.cpp ... Compiling ../../visual-3.2.9/src/num_util.cpp ... Compiling ../../visual-3.2.9/src/scalar_array.cpp ... Compiling ../../visual-3.2.9/src/vector_array.cpp ... Compiling ../../visual-3.2.9/src/slice.cpp ... Compiling ../../visual-3.2.9/src/sphmodel.cpp ... Compiling ../../visual-3.2.9/src/faceset.cpp ... Compiling ../../visual-3.2.9/src/frame.cpp ... Compiling ../../visual-3.2.9/src/gldevice.cpp ... Compiling ../../visual-3.2.9/src/kbobject.cpp ... Compiling ../../visual-3.2.9/src/light.cpp ... Compiling ../../visual-3.2.9/src/label.cpp ... Compiling ../../visual-3.2.9/src/mouseobject.cpp ... Compiling ../../visual-3.2.9/src/prim.cpp ... Compiling ../../visual-3.2.9/src/vector.cpp ... Compiling ../../visual-3.2.9/src/pyramid.cpp ... Compiling ../../visual-3.2.9/src/rate.cpp ... Compiling ../../visual-3.2.9/src/ring.cpp ... Compiling ../../visual-3.2.9/src/sphere.cpp ... Compiling ../../visual-3.2.9/src/tmatrix.cpp ... Compiling ../../visual-3.2.9/src/vcache.cpp ... Compiling ../../visual-3.2.9/src/cylmodel.cpp ... Compiling ../../visual-3.2.9/src/num_util_impl_numeric.cpp ... Compiling ../../visual-3.2.9/src/num_util_impl_numarray.cpp ... Compiling ../../visual-3.2.9/src/glcontext.cpp ... Compiling ../../visual-3.2.9/src/platlinux.cpp ... Compiling ../../visual-3.2.9/src/xgl.cpp ... Linking cvisualmodule.la ... make[1]: *** [cvisualmodule.la] Error 1 make[1]: Leaving directory `/bfucc/USRLOCAL/src/build/src' make: *** [all-recursive] Error 1 [root@hydra999 build]# Here are the last lines of the src/build.log file: g++ -fPIC -shared -nostdlib /usr/lib/gcc/x86_64-redhat-linux/=20 3.4.4/../../../../lib64/crti.o /usr/lib/gcc/x86_64-redhat-linux/3.4.4/=20= crtbeginS.o .libs/arrow.o .libs/axial.o .libs/box.o .libs/=20 color.o .libs/cone.o .libs/convex.o .libs/curve.o .libs/=20 cvisualmodule.o .libs/cylinder.o .libs/display.o .libs/=20 displaylist.o .libs/ellipsoid.o .libs/exceptions.o .libs/=20 num_util.o .libs/scalar_array.o .libs/vector_array.o .libs/=20 slice.o .libs/sphmodel.o .libs/faceset.o .libs/frame.o .libs/=20 gldevice.o .libs/kbobject.o .libs/light.o .libs/label.o .libs/=20 mouseobject.o .libs/prim.o .libs/vector.o .libs/pyramid.o .libs/=20 rate.o .libs/ring.o .libs/sphere.o .libs/tmatrix.o .libs/=20 vcache.o .libs/cylmodel.o .libs/num_util_impl_numeric.o .libs/=20 num_util_impl_numarray.o .libs/glcontext.o .libs/platlinux.o .libs/=20 xgl.o -Wl,--rpath -Wl,/usr/lib64 -Wl,--rpath -Wl,/usr/lib64 -L/usr/=20 lib64 -L/usr/X11R6/lib64 /usr/lib64/libgtk.so /usr/lib64/libgdk.so /=20 usr/lib64/libgmodule.so -ldl -lXi -lXext -lX11 -lgtkgl -lGL -lGLU /=20 usr/lib64/libgthread.so -lpthread /usr/lib64/libglib.so -=20 lboost_python -L/usr/lib/gcc/x86_64-redhat-linux/3.4.4 -L/usr/lib/gcc/=20= x86_64-redhat-linux/3.4.4/../../../../lib64 -L/usr/lib/gcc/x86_64-=20 redhat-linux/3.4.4/../../.. -L/lib/../lib64 -L/usr/lib/../lib64 -lstdc=20= ++ -lm -lc -lgcc_s /usr/lib/gcc/x86_64-redhat-linux/3.4.4/crtendS.o /=20 usr/lib/gcc/x86_64-redhat-linux/3.4.4/../../../../lib64/crtn.o -Wl,--=20= version-script=3D../../visual-3.2.9/src/linux-symbols.map -Wl,-soname -=20= Wl,cvisualmodule.so.1 -o .libs/cvisualmodule.so.1.0.0 /usr/bin/ld: /usr/lib64/libboost_python.a(numeric.o): relocation =20 R_X86_64_32 against `a local symbol' can not be used when making a =20 shared object; recompile with -fPIC /usr/lib64/libboost_python.a: could not read symbols: Bad value collect2: ld returned 1 exit status [root@hydra999 build]# As you can see in the build log, I have also tried with the -fPIC =20 option but that changes nothing. The OS is HP XC System Software 3.0, =20= which is a Linux system for HP XC clusters that should be 100% =20 compatible with Red Hat Linux Enterprise 4. It runs on AMD Opteron 64 =20= bits CPUs. Thank you very much, Fr=E9d=E9ric Buelens -- email: fbu...@ul... http://www.ulb.ac.be/BFUCC Universit=E9 Libre de Bruxelles Centre de Calcul - CP 197 Avenue F.D. Roosevelt 50 B-1050 Bruxelles Belgique |
|
From: Jonathan B. <jbr...@ea...> - 2006-07-15 22:07:18
|
On Sat, 2006-07-15 at 16:48 -0400, Ryan Hoban wrote: > Is Vpython capable of creating a display with an orthographic > projection, rather than the default perspective projection? Not right now, but you can fake it with a small field of view (say, .01 or .001) HTH, -Jonathan |
|
From: Ryan H. <rf...@ma...> - 2006-07-15 20:48:15
|
Is Vpython capable of creating a display with an orthographic = projection, rather than the default perspective projection? =20 Thanks, Ryan Hoban |
|
From: Bruce S. <Bru...@nc...> - 2006-07-15 16:23:32
|
I've updated the web site to make connections between that sample program and the summary of the new version (and vice versa). I also added a missing piece of information in the summary, namely that for the new lights the default is "local=True", and to make a light at infinity you say "local=False", in which case the light comes from infinity from the direction specified by the pos attribute. Bruce Sherwood Jonathan Brandmeyer wrote: > On Fri, 2006-07-14 at 21:45 -0700, Bumpy Stucko wrote: > >> Contributed application texturegenerator.py by Bruce Sherwood contains >> this line: >> >> lum = texture(data=u, type="luminance") >> >> texture() appears to be undefined. Does anyone know how it should be >> defined? >> > > It is only present in VPython 4.x > > -Jonathan > > > > ------------------------------------------------------------------------- > Using Tomcat but need to do more? Need to support web services, security? > Get stuff done quickly with pre-integrated technology to make your job easier > Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo > http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 > _______________________________________________ > Visualpython-users mailing list > Vis...@li... > https://lists.sourceforge.net/lists/listinfo/visualpython-users > |
|
From: Jonathan B. <jbr...@ea...> - 2006-07-15 14:45:27
|
On Fri, 2006-07-14 at 21:45 -0700, Bumpy Stucko wrote: > Contributed application texturegenerator.py by Bruce Sherwood contains > this line: > > lum = texture(data=u, type="luminance") > > texture() appears to be undefined. Does anyone know how it should be > defined? It is only present in VPython 4.x -Jonathan |
|
From: Bumpy S. <tho...@ya...> - 2006-07-15 04:45:20
|
Contributed application texturegenerator.py by Bruce Sherwood contains this line: lum = texture(data=u, type="luminance") texture() appears to be undefined. Does anyone know how it should be defined? Bumpy --------------------------------- Yahoo! Messenger with Voice. Make PC-to-Phone Calls to the US (and 30+ countries) for 2¢/min or less. |
|
From: Bruce S. <Bru...@nc...> - 2006-07-14 20:39:18
|
Do you ever set scene.uniform to False (0)? Do you ever set scene.range to have different values for x, y, and z? I very much need to hear how you use these little-used capabilities of VPython, as there are some cleanups that should be made to these facilities, and how corrections are made may be influenced by the ways in which people have found nonuniformity useful (or not). The only place I know of where this machinery is used in a major way is in the graph module. But it is purely two-dimensional, where nonuniformity isn't particularly problematic. In 3D, drawing something as simple as an arrow is highly problematic, because you might want to position the tail of the arrow based on nonuniform x,y,z scale factors, but you want an arrowhead that looks nice, not horribly distorted. Bruce Sherwood |
|
From: Jonathan B. <jbr...@ea...> - 2006-07-14 17:14:12
|
On Thu, 2006-07-13 at 13:59 +0100, Dr P H Borcherds wrote: > I have downloaded VPython-Win-Py2.4-4.beta2.exe (but visual.version = (4, > 'beta1')) > > My operating system is windows Me (update from windows 98) > > When I import visual as [from visual import *], dir() generates error > message : see below > but if I import it as "import visual" dir(visual) works ok There is a local variable named dir defined in site-packages/visual/__init__.py (on or about line 38). Rename it to _dir, and this won't be a problem. This has been fixed in CVS, and will be applied to the next release. This was my mistake - loops do not have their own scope (or something like that), and I had forgotten that property. -Jonathan |
|
From: Bruce S. <Bru...@nc...> - 2006-07-14 15:15:09
|
Thanks for the report. On Windows XP on a laptop I can reproduce the dir() behavior(str object not callable). When I try visual.sphere() I get a different problem: NameError: name 'visual' is not defined. There seem to be various screws loose in the Windows version, and it's useful to have a catalog of these loose screws. Bruce Sherwood Dr P H Borcherds wrote: > I have downloaded VPython-Win-Py2.4-4.beta2.exe (but visual.version = (4, > 'beta1')) > > My operating system is windows Me (update from windows 98) > > When I import visual as [from visual import *], dir() generates error > message : see below > but if I import it as "import visual" dir(visual) works ok > > When I type ball = visual.sphere() I get message from PythonW : > PythonW has caused an error in OPENGL32.DLL > > Help, please > > Peter Borcherds > > IDLE 1.1.3 > >>>> dir() >>>> > ['__builtins__', '__doc__', '__name__'] > >>>> from visual import * >>>> dir() >>>> > > Traceback (most recent call last): > File "<pyshell#2>", line 1, in -toplevel- > dir() > TypeError: 'str' object is not callable > >>>> ball = sphere() >>>> >>>> > > from Dr P H Borcherds > reply to: p.h...@bh... > telephone (+44) 121 475 3029 > > > ------------------------------------------------------------------------- > Using Tomcat but need to do more? Need to support web services, security? > Get stuff done quickly with pre-integrated technology to make your job easier > Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo > http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 > _______________________________________________ > Visualpython-users mailing list > Vis...@li... > https://lists.sourceforge.net/lists/listinfo/visualpython-users > |
|
From: Dr P H B. <P.H...@bh...> - 2006-07-13 13:07:10
|
I have downloaded VPython-Win-Py2.4-4.beta2.exe (but visual.version = (4,
'beta1'))
My operating system is windows Me (update from windows 98)
When I import visual as [from visual import *], dir() generates error
message : see below
but if I import it as "import visual" dir(visual) works ok
When I type ball = visual.sphere() I get message from PythonW :
PythonW has caused an error in OPENGL32.DLL
Help, please
Peter Borcherds
IDLE 1.1.3
>>> dir()
['__builtins__', '__doc__', '__name__']
>>> from visual import *
>>> dir()
Traceback (most recent call last):
File "<pyshell#2>", line 1, in -toplevel-
dir()
TypeError: 'str' object is not callable
>>> ball = sphere()
>>>
from Dr P H Borcherds
reply to: p.h...@bh...
telephone (+44) 121 475 3029
|
|
From: Jonathan B. <jbr...@ea...> - 2006-07-13 04:25:32
|
On Wed, 2006-07-12 at 16:07 +0200, Maxim Krikun wrote: > Hi > > I'm running visual python 3.2.1 with python 2.3.5 on Debian-unstable. > > After running from the python interpreter > >>> from visual import * > >>> c=curve(pos=[[0,0]]) > > the VPython window appears, and the CPU consumption by Xorg > goes to around 45%-50% (I don't have hardware openGL) You should get at least a cheap PCI graphics card. You won't be able to do anything interesting otherwise. > When using pyopengl directly, I don't see such behaviour. > > Does this mean that vpython constantly redraws the same model, > even when the model is not changed? Yes. It renders no faster than 50 fps, and always in a thread that is separate from your code. > If so, how can this be avoided? At present, it cannot. > > --Maxim HTH, -Jonathan |
33 messages has been excluded from this view by a project administrator.
