You can subscribe to this list here.
2004 |
Jan
|
Feb
|
Mar
(13) |
Apr
|
May
(1) |
Jun
(34) |
Jul
(23) |
Aug
(16) |
Sep
|
Oct
(11) |
Nov
(13) |
Dec
(1) |
---|---|---|---|---|---|---|---|---|---|---|---|---|
2005 |
Jan
(2) |
Feb
(3) |
Mar
(13) |
Apr
(1) |
May
(5) |
Jun
(11) |
Jul
(5) |
Aug
(10) |
Sep
(16) |
Oct
(8) |
Nov
(4) |
Dec
(5) |
2006 |
Jan
(18) |
Feb
(5) |
Mar
(6) |
Apr
(12) |
May
(3) |
Jun
(1) |
Jul
(4) |
Aug
(16) |
Sep
(1) |
Oct
(5) |
Nov
(35) |
Dec
(7) |
2007 |
Jan
(17) |
Feb
(14) |
Mar
(7) |
Apr
(9) |
May
(16) |
Jun
(31) |
Jul
(13) |
Aug
(23) |
Sep
|
Oct
(2) |
Nov
(3) |
Dec
(1) |
2008 |
Jan
(8) |
Feb
(1) |
Mar
(3) |
Apr
(2) |
May
|
Jun
(4) |
Jul
|
Aug
|
Sep
|
Oct
(1) |
Nov
|
Dec
|
2009 |
Jan
|
Feb
(5) |
Mar
|
Apr
(2) |
May
|
Jun
(1) |
Jul
|
Aug
(5) |
Sep
(1) |
Oct
|
Nov
(3) |
Dec
|
2010 |
Jan
(6) |
Feb
(6) |
Mar
(10) |
Apr
(5) |
May
(11) |
Jun
|
Jul
|
Aug
(2) |
Sep
(8) |
Oct
(2) |
Nov
(3) |
Dec
(5) |
2011 |
Jan
(7) |
Feb
|
Mar
(1) |
Apr
(3) |
May
(10) |
Jun
(1) |
Jul
(1) |
Aug
(1) |
Sep
(1) |
Oct
(1) |
Nov
|
Dec
|
2012 |
Jan
|
Feb
|
Mar
|
Apr
|
May
(6) |
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
2013 |
Jan
(1) |
Feb
|
Mar
|
Apr
(4) |
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
2014 |
Jan
|
Feb
|
Mar
(1) |
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
2023 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
(1) |
From: Joseph H. <jha...@gm...> - 2023-12-28 17:11:31
|
I'm trying to install PyODE and getting an error on the execution of: python setup.py build or install C:\Users\jhand\Downloads\PyODE-snapshot-2010-03-22\PyODE-snapshot-2010-03-22>python setup.py install File "C:\Users\jhand\Downloads\PyODE-snapshot-2010-03-22\PyODE-snapshot-2010-03-22\setup.py", line 62 print "INFO:",msg ^^^^^^^^^^^^^^^^^ SyntaxError: Missing parentheses in call to 'print'. Did you mean print(...)? I'll appreciate any suggestions, I find it completely odd all the print instructions are missing the parenthesis. ______________________________________________ Joseph M Handschu Phone: (919) 601-3612 |
From: Llewellyn P. <ll...@ou...> - 2014-03-08 18:55:23
|
Dear All, I am trying to use pyode to do some simple simulations but when I try to run the first tutorial script (http://pyode.sourceforge.net/tutorials/tutorial1.html) I get the following error """ ODE Message 2: mass must be > 0 in dMassCheck() File ../../../../../ode/src/mass.cpp Line 49 0.00sec: pos=( 0.000, 0.000, 2.000) vel=( 0.000, 0.000, 0.000) ODE INTERNAL ERROR 1: assertion "bNormalizationResult" failed in _dNormalize4() [../../../../../include/ode/odemath.h] Aborted (core dumped) """ It appears that the error come from: M.setSphere(2500.0, 0.05) Can anyone advise? I am running Ubuntu 13.10 and using the versions of python, libode and pyode from the repositories. Thank you! Llew |
From: John M. <jo...@zu...> - 2013-04-28 03:28:34
|
Hi Ethan, Thanks for committing our patches. Good news here, too: the Fedora review is all done, and now it's just a matter of getting the sources checked in and running it through the Fedora build servers and the unstable and finally stable package repositories. Probably about two weeks. Here's the bugzilla package review ticket: https://bugzilla.redhat.com/show_bug.cgi?id=927611 We're using the following tarball. The first patch wasn't applied there, but it's included in the package, and that fixes the segfaults. https://downloads.sourceforge.net/project/pyode/pyode/snapshot-2010-03-22/PyODE-snapshot-2010-03-22.tar.gz Anyway, I do see both patches in the git tree, thanks! If you want to make a release, we'll definitely pick it up in our packaging. No urgency though, since the two packages that depend on pyode seem to work well with 2010-03-22 and those patches added. When you get around to it, let me know and I'll make the update. Believe me, I understand about busy! John On 04/25/2013 10:37 PM, Ethan wrote: > Thanks for the patches, John! I meant to address this when you emailed > the first patch, but I've been pretty busy this week. > > The good news is the first patch was applied in 2010-10-13. From the > patch you sent, it looks like you're working off of version 2012-03-22. > It looks like I might have tried to cut a release for version 1.2.1 in > 2012, but I might have messed up somewhere. Let me know if you can't > find it anywhere. > > The other good news ;) is that I applied your other patch and pushed it. > If you need me to make a new release, let me know. > > Ethan > > > > On Thu, Apr 25, 2013 at 11:13 PM, John Morris <jo...@zu... > <mailto:jo...@zu...>> wrote: > > One more fix to those tests. They fail on Fedora but not el6 (el6 is > quite a bit older), and on 64-bit but not 32-bit. > > The failure is because of a rounding error; the results differ by 6e-8. > > The attached patch adds a check to the unittests that compares the > floats to within five decimals. It's tested to pass on el6 and f17-f20, > and 64- and 32-bit. > > John > > > > On 04/24/2013 12:42 AM, John Morris wrote: > > Hi Ethan, > > > > Thanks for the quick reply! > > > > I must have been keyword challenged last time around, but this time I > > easily googled up a ready-made solution: > > > > http://comments.gmane.org/gmane.comp.python.pyode.user/174 > > > > If it matters, I'm building against ODE version 0.11.1. > > > > Attached is the patch to fix the segfault. This will be included > in the > > Fedora package. If this patch makes it into git and you release a > > snapshot, I'll package up the new version & drop the patch. > > > > Thanks- > > > > John > > > > > > On 04/23/2013 11:12 PM, Ethan wrote: > >> Hi John, > >> > >> To be honest, I never used or understood the xode code. Sorry, I > can't help. > >> > >> Ethan > >> > >> > >> On Tue, Apr 23, 2013 at 12:14 PM, John Morris <jo...@zu... > <mailto:jo...@zu...> > >> <mailto:jo...@zu... <mailto:jo...@zu...>>> wrote: > >> > >> Hi list, > >> > >> I'm working on packaging pyode for Fedora. Everything has > gone smoothly > >> except the tests, which segfault after successful completion > of all 110 > >> tests. Has this been seen before? Below is the output of > the test run > >> and a gdb stack trace on the resulting core file. > >> > >> John > >> > >> > >> $ python PyODE-snapshot-2010-03-22/tests/test_xode.py > >> > .............................................................................................................. > >> > ---------------------------------------------------------------------- > >> Ran 110 tests in 1.014s > >> > >> OK > >> Segmentation fault > >> > >> > >> > >> > >> > >> #0 0x00007f48659dc253 in dBodyDestroy () from > /usr/lib64/libode.so.1 > >> #1 0x00007f4865cb6434 in __pyx_f_3ode_4Body___dealloc__ ( > >> o=<value optimized out>) at ode_trimesh.c:3355 > >> #2 __pyx_tp_dealloc_3ode_Body (o=<value optimized out>) > >> at ode_trimesh.c:14829 > >> #3 0x00007f4865cb3eeb in __pyx_tp_dealloc_3ode_GeomObject > >> (o=0x7f4866144650) > >> at ode_trimesh.c:16892 > >> #4 0x00007f486ccfe49b in PyDict_Clear () from > >> /usr/lib64/libpython2.6.so.1.0 > >> #5 0x00007f486ccfe529 in ?? () from > /usr/lib64/libpython2.6.so.1.0 > >> #6 0x00007f486cd87f6a in ?? () from > /usr/lib64/libpython2.6.so.1.0 > >> #7 0x00007f486cd88564 in PyGC_Collect () from > >> /usr/lib64/libpython2.6.so.1.0 > >> #8 0x00007f486cd798b6 in Py_Finalize () from > >> /usr/lib64/libpython2.6.so.1.0 > >> #9 0x00007f486cd79a08 in Py_Exit () from > /usr/lib64/libpython2.6.so.1.0 > >> #10 0x00007f486cd79b51 in ?? () from > /usr/lib64/libpython2.6.so.1.0 > >> #11 0x00007f486cd79dcd in PyErr_PrintEx () from > >> /usr/lib64/libpython2.6.so.1.0 > >> #12 0x00007f486cd7a297 in PyRun_SimpleFileExFlags () > >> from /usr/lib64/libpython2.6.so.1.0 > >> #13 0x00007f486cd86c32 in Py_Main () from > /usr/lib64/libpython2.6.so.1.0 > >> #14 0x00007f486c060cdd in __libc_start_main (main=0x400710, > argc=2, > >> ubp_av=0x7fff7c22c758, init=<value optimized out>, > >> fini=<value optimized out>, rtld_fini=<value optimized out>, > >> stack_end=0x7fff7c22c748) at libc-start.c:226 > >> #15 0x0000000000400649 in ?? () > >> #16 0x00007fff7c22c748 in ?? () > >> #17 0x000000000000001c in ?? () > >> #18 0x0000000000000002 in ?? () > >> #19 0x00007fff7c22dc19 in ?? () > >> #20 0x00007fff7c22dc20 in ?? () > >> #21 0x0000000000000000 in ?? () > >> > >> > ------------------------------------------------------------------------------ > >> Try New Relic Now & We'll Send You this Cool Shirt > >> New Relic is the only SaaS-based application performance > monitoring > >> service > >> that delivers powerful full stack analytics. Optimize and > monitor your > >> browser, app, & servers with just a few lines of code. Try > New Relic > >> and get this awesome Nerd Life shirt! > >> http://p.sf.net/sfu/newrelic_d2d_apr > >> _______________________________________________ > >> Pyode-user mailing list > >> Pyo...@li... > <mailto:Pyo...@li...> > >> <mailto:Pyo...@li... > <mailto:Pyo...@li...>> > >> https://lists.sourceforge.net/lists/listinfo/pyode-user > >> > >> > > > > |
From: John M. <jo...@zu...> - 2013-04-26 03:13:49
|
One more fix to those tests. They fail on Fedora but not el6 (el6 is quite a bit older), and on 64-bit but not 32-bit. The failure is because of a rounding error; the results differ by 6e-8. The attached patch adds a check to the unittests that compares the floats to within five decimals. It's tested to pass on el6 and f17-f20, and 64- and 32-bit. John On 04/24/2013 12:42 AM, John Morris wrote: > Hi Ethan, > > Thanks for the quick reply! > > I must have been keyword challenged last time around, but this time I > easily googled up a ready-made solution: > > http://comments.gmane.org/gmane.comp.python.pyode.user/174 > > If it matters, I'm building against ODE version 0.11.1. > > Attached is the patch to fix the segfault. This will be included in the > Fedora package. If this patch makes it into git and you release a > snapshot, I'll package up the new version & drop the patch. > > Thanks- > > John > > > On 04/23/2013 11:12 PM, Ethan wrote: >> Hi John, >> >> To be honest, I never used or understood the xode code. Sorry, I can't help. >> >> Ethan >> >> >> On Tue, Apr 23, 2013 at 12:14 PM, John Morris <jo...@zu... >> <mailto:jo...@zu...>> wrote: >> >> Hi list, >> >> I'm working on packaging pyode for Fedora. Everything has gone smoothly >> except the tests, which segfault after successful completion of all 110 >> tests. Has this been seen before? Below is the output of the test run >> and a gdb stack trace on the resulting core file. >> >> John >> >> >> $ python PyODE-snapshot-2010-03-22/tests/test_xode.py >> .............................................................................................................. >> ---------------------------------------------------------------------- >> Ran 110 tests in 1.014s >> >> OK >> Segmentation fault >> >> >> >> >> >> #0 0x00007f48659dc253 in dBodyDestroy () from /usr/lib64/libode.so.1 >> #1 0x00007f4865cb6434 in __pyx_f_3ode_4Body___dealloc__ ( >> o=<value optimized out>) at ode_trimesh.c:3355 >> #2 __pyx_tp_dealloc_3ode_Body (o=<value optimized out>) >> at ode_trimesh.c:14829 >> #3 0x00007f4865cb3eeb in __pyx_tp_dealloc_3ode_GeomObject >> (o=0x7f4866144650) >> at ode_trimesh.c:16892 >> #4 0x00007f486ccfe49b in PyDict_Clear () from >> /usr/lib64/libpython2.6.so.1.0 >> #5 0x00007f486ccfe529 in ?? () from /usr/lib64/libpython2.6.so.1.0 >> #6 0x00007f486cd87f6a in ?? () from /usr/lib64/libpython2.6.so.1.0 >> #7 0x00007f486cd88564 in PyGC_Collect () from >> /usr/lib64/libpython2.6.so.1.0 >> #8 0x00007f486cd798b6 in Py_Finalize () from >> /usr/lib64/libpython2.6.so.1.0 >> #9 0x00007f486cd79a08 in Py_Exit () from /usr/lib64/libpython2.6.so.1.0 >> #10 0x00007f486cd79b51 in ?? () from /usr/lib64/libpython2.6.so.1.0 >> #11 0x00007f486cd79dcd in PyErr_PrintEx () from >> /usr/lib64/libpython2.6.so.1.0 >> #12 0x00007f486cd7a297 in PyRun_SimpleFileExFlags () >> from /usr/lib64/libpython2.6.so.1.0 >> #13 0x00007f486cd86c32 in Py_Main () from /usr/lib64/libpython2.6.so.1.0 >> #14 0x00007f486c060cdd in __libc_start_main (main=0x400710, argc=2, >> ubp_av=0x7fff7c22c758, init=<value optimized out>, >> fini=<value optimized out>, rtld_fini=<value optimized out>, >> stack_end=0x7fff7c22c748) at libc-start.c:226 >> #15 0x0000000000400649 in ?? () >> #16 0x00007fff7c22c748 in ?? () >> #17 0x000000000000001c in ?? () >> #18 0x0000000000000002 in ?? () >> #19 0x00007fff7c22dc19 in ?? () >> #20 0x00007fff7c22dc20 in ?? () >> #21 0x0000000000000000 in ?? () >> >> ------------------------------------------------------------------------------ >> Try New Relic Now & We'll Send You this Cool Shirt >> New Relic is the only SaaS-based application performance monitoring >> service >> that delivers powerful full stack analytics. Optimize and monitor your >> browser, app, & servers with just a few lines of code. Try New Relic >> and get this awesome Nerd Life shirt! >> http://p.sf.net/sfu/newrelic_d2d_apr >> _______________________________________________ >> Pyode-user mailing list >> Pyo...@li... >> <mailto:Pyo...@li...> >> https://lists.sourceforge.net/lists/listinfo/pyode-user >> >> > |
From: John M. <jo...@zu...> - 2013-04-24 05:43:03
|
Hi Ethan, Thanks for the quick reply! I must have been keyword challenged last time around, but this time I easily googled up a ready-made solution: http://comments.gmane.org/gmane.comp.python.pyode.user/174 If it matters, I'm building against ODE version 0.11.1. Attached is the patch to fix the segfault. This will be included in the Fedora package. If this patch makes it into git and you release a snapshot, I'll package up the new version & drop the patch. Thanks- John On 04/23/2013 11:12 PM, Ethan wrote: > Hi John, > > To be honest, I never used or understood the xode code. Sorry, I can't help. > > Ethan > > > On Tue, Apr 23, 2013 at 12:14 PM, John Morris <jo...@zu... > <mailto:jo...@zu...>> wrote: > > Hi list, > > I'm working on packaging pyode for Fedora. Everything has gone smoothly > except the tests, which segfault after successful completion of all 110 > tests. Has this been seen before? Below is the output of the test run > and a gdb stack trace on the resulting core file. > > John > > > $ python PyODE-snapshot-2010-03-22/tests/test_xode.py > .............................................................................................................. > ---------------------------------------------------------------------- > Ran 110 tests in 1.014s > > OK > Segmentation fault > > > > > > #0 0x00007f48659dc253 in dBodyDestroy () from /usr/lib64/libode.so.1 > #1 0x00007f4865cb6434 in __pyx_f_3ode_4Body___dealloc__ ( > o=<value optimized out>) at ode_trimesh.c:3355 > #2 __pyx_tp_dealloc_3ode_Body (o=<value optimized out>) > at ode_trimesh.c:14829 > #3 0x00007f4865cb3eeb in __pyx_tp_dealloc_3ode_GeomObject > (o=0x7f4866144650) > at ode_trimesh.c:16892 > #4 0x00007f486ccfe49b in PyDict_Clear () from > /usr/lib64/libpython2.6.so.1.0 > #5 0x00007f486ccfe529 in ?? () from /usr/lib64/libpython2.6.so.1.0 > #6 0x00007f486cd87f6a in ?? () from /usr/lib64/libpython2.6.so.1.0 > #7 0x00007f486cd88564 in PyGC_Collect () from > /usr/lib64/libpython2.6.so.1.0 > #8 0x00007f486cd798b6 in Py_Finalize () from > /usr/lib64/libpython2.6.so.1.0 > #9 0x00007f486cd79a08 in Py_Exit () from /usr/lib64/libpython2.6.so.1.0 > #10 0x00007f486cd79b51 in ?? () from /usr/lib64/libpython2.6.so.1.0 > #11 0x00007f486cd79dcd in PyErr_PrintEx () from > /usr/lib64/libpython2.6.so.1.0 > #12 0x00007f486cd7a297 in PyRun_SimpleFileExFlags () > from /usr/lib64/libpython2.6.so.1.0 > #13 0x00007f486cd86c32 in Py_Main () from /usr/lib64/libpython2.6.so.1.0 > #14 0x00007f486c060cdd in __libc_start_main (main=0x400710, argc=2, > ubp_av=0x7fff7c22c758, init=<value optimized out>, > fini=<value optimized out>, rtld_fini=<value optimized out>, > stack_end=0x7fff7c22c748) at libc-start.c:226 > #15 0x0000000000400649 in ?? () > #16 0x00007fff7c22c748 in ?? () > #17 0x000000000000001c in ?? () > #18 0x0000000000000002 in ?? () > #19 0x00007fff7c22dc19 in ?? () > #20 0x00007fff7c22dc20 in ?? () > #21 0x0000000000000000 in ?? () > > ------------------------------------------------------------------------------ > Try New Relic Now & We'll Send You this Cool Shirt > New Relic is the only SaaS-based application performance monitoring > service > that delivers powerful full stack analytics. Optimize and monitor your > browser, app, & servers with just a few lines of code. Try New Relic > and get this awesome Nerd Life shirt! > http://p.sf.net/sfu/newrelic_d2d_apr > _______________________________________________ > Pyode-user mailing list > Pyo...@li... > <mailto:Pyo...@li...> > https://lists.sourceforge.net/lists/listinfo/pyode-user > > |
From: John M. <jo...@zu...> - 2013-04-23 16:14:37
|
Hi list, I'm working on packaging pyode for Fedora. Everything has gone smoothly except the tests, which segfault after successful completion of all 110 tests. Has this been seen before? Below is the output of the test run and a gdb stack trace on the resulting core file. John $ python PyODE-snapshot-2010-03-22/tests/test_xode.py .............................................................................................................. ---------------------------------------------------------------------- Ran 110 tests in 1.014s OK Segmentation fault #0 0x00007f48659dc253 in dBodyDestroy () from /usr/lib64/libode.so.1 #1 0x00007f4865cb6434 in __pyx_f_3ode_4Body___dealloc__ ( o=<value optimized out>) at ode_trimesh.c:3355 #2 __pyx_tp_dealloc_3ode_Body (o=<value optimized out>) at ode_trimesh.c:14829 #3 0x00007f4865cb3eeb in __pyx_tp_dealloc_3ode_GeomObject (o=0x7f4866144650) at ode_trimesh.c:16892 #4 0x00007f486ccfe49b in PyDict_Clear () from /usr/lib64/libpython2.6.so.1.0 #5 0x00007f486ccfe529 in ?? () from /usr/lib64/libpython2.6.so.1.0 #6 0x00007f486cd87f6a in ?? () from /usr/lib64/libpython2.6.so.1.0 #7 0x00007f486cd88564 in PyGC_Collect () from /usr/lib64/libpython2.6.so.1.0 #8 0x00007f486cd798b6 in Py_Finalize () from /usr/lib64/libpython2.6.so.1.0 #9 0x00007f486cd79a08 in Py_Exit () from /usr/lib64/libpython2.6.so.1.0 #10 0x00007f486cd79b51 in ?? () from /usr/lib64/libpython2.6.so.1.0 #11 0x00007f486cd79dcd in PyErr_PrintEx () from /usr/lib64/libpython2.6.so.1.0 #12 0x00007f486cd7a297 in PyRun_SimpleFileExFlags () from /usr/lib64/libpython2.6.so.1.0 #13 0x00007f486cd86c32 in Py_Main () from /usr/lib64/libpython2.6.so.1.0 #14 0x00007f486c060cdd in __libc_start_main (main=0x400710, argc=2, ubp_av=0x7fff7c22c758, init=<value optimized out>, fini=<value optimized out>, rtld_fini=<value optimized out>, stack_end=0x7fff7c22c748) at libc-start.c:226 #15 0x0000000000400649 in ?? () #16 0x00007fff7c22c748 in ?? () #17 0x000000000000001c in ?? () #18 0x0000000000000002 in ?? () #19 0x00007fff7c22dc19 in ?? () #20 0x00007fff7c22dc20 in ?? () #21 0x0000000000000000 in ?? () |
From: tim r. <bla...@ya...> - 2013-01-27 23:05:40
|
http://oddsinyourfavour.com/wp-content/themes/celine/images/muchmoneynow.html ......................................... tim rau |
From: James T. <jt...@mi...> - 2012-05-25 20:24:44
|
Turns out Panda3d does implement mass.rotate. I think the reason why I did not use it is because it needs a 3x3 rotation matrix and my code uses quaternions everywhere. So I need to add some glue-code to make it work. What I have noticed is that Panda3d seems to be based on a newer version of ODE than PyODE (or they have altered the API) and the differences are significant when it comes to composite bodies (for example they don't have transform geoms). Unfortunately I think the solution for you is to calculate the inertia tensor yourself for the composite of the mass objects. Then just make a single mass for your body and assign it the inertia tensor you calculated. Maybe that is deeper than you were hoping to dig but it should something that is pretty well covered on the Internet. JT |
From: Bill C. <we...@pr...> - 2012-05-22 05:05:01
|
On 5/21/2012 1:32 PM, Will Bosworth wrote: > Hi Bill, > > I do not understand your initial assumption not to use joints. Fixed > joints are very straightforward to implement, and I believe are stiff > to the extent that the global ERP and CFM integrator parameters are > stiff. What documentation suggests not to use joints? I'd like to see > it. > > Based on what I know about your problem and ODE, if in your shoes i > would stick to a one-to-one mass and body implementation and use fixed > joints to sew the complex body together. I am pretty sure that bodies > can be rotated with body.setRotation(r), for instance as in > http://monsterden.net/software/ragdoll-pyode-tutorial (string search > setRotation there). > > best, > Will > > > > On Sat, May 19, 2012 at 8:23 PM, Bill Call<we...@pr...> wrote: >> Hi : >> >> I'm trying to build a rigid-body simulation using PyODE/PyOpenGL. Since >> I'm just doing rigid-body, it is my understanding that I have no need >> for joints; I just need to add masses to my body at the appropriate >> translations/rotations. >> >> I have a number of cylindrical masses in my body. These cylinders have >> fixed positions and rotations within the body, but are not necessarily >> aligned with the X, Y or Z axis. PyODE does not bind the rotateMass() >> function from ODE; it only allows me to specify an X, Y or Z orientation >> for cylindrical mass (at creation time). This means that I am unable to >> rotate my cylindrical masses to the correct orientation. >> >> My guess is that this would not be a problem if each of these masses had >> their own Body; I could just rotate the body after the mass was bound. >> Doing doing it that way might work, but it would mean connecting the >> cylinders to the main body via joints, and what little documentation >> there is seems to contraindicate the use of joints for rigid-body >> simulations. >> >> My questions are as follows: >> >> 1) Am I correct in my assumption that I must rotate/translate the mass >> tensor to reflect the true location/orientation of my cylindrical masses >> within the containing body? It seems (to me) to be intuitively obvious >> that I do, but I don't put much stock in my intuition regarding this >> subject. >> >> 2) If the answer to (1) is "yes", then can anybody point me a rotation >> implementation? If "no", then would someone be willing to explain why not? >> >> I have already spent a lot of time Googling about for this information, >> but I am not sufficiently grounded in the subject to really understand >> the answers I have been able to find on my own; not well enough to write >> a function to rotate inertial tensors, anyway. >> >> Thanks in Advance, >> >> >> Bill Call >> >> >> >> >> >> ------------------------------------------------------------------------------ >> Live Security Virtual Conference >> Exclusive live event will cover all the ways today's security and >> threat landscape has changed and how IT managers can respond. Discussions >> will include endpoint security, mobile security and the latest in malware >> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ >> _______________________________________________ >> Pyode-user mailing list >> Pyo...@li... >> https://lists.sourceforge.net/lists/listinfo/pyode-user Will: Following up on the whole "why not use fixed joints?" question, I was able to find the original data. The most telling comment comes from the ODE Wiki itself: http://ode-wiki.org/wiki/index.php?title=Manual:_Joint_Types_and_Functions#Fixed and reads as follows: "The fixed joint maintains a fixed relative position and orientation between two bodies, or between a body and the static environment. Using this joint is almost never a good idea in practice, except when debugging. If you need two bodies to be glued together it is better to represent that as a single body." I can understand the point: the ERP and CFM parameters are always going to leave some wiggle room. If you want it rigid, make it a single body. I can testify that this works quite well. In my case, though I am trying to simulate a quad-copter, and I just want to apply torque to the motor bodies and let ODE compute the net effect. I don't see how I can do that with a single body unless I want to do the math myself. Regards, Bill C. |
From: Will B. <bos...@mi...> - 2012-05-21 18:32:59
|
Hi Bill, I do not understand your initial assumption not to use joints. Fixed joints are very straightforward to implement, and I believe are stiff to the extent that the global ERP and CFM integrator parameters are stiff. What documentation suggests not to use joints? I'd like to see it. Based on what I know about your problem and ODE, if in your shoes i would stick to a one-to-one mass and body implementation and use fixed joints to sew the complex body together. I am pretty sure that bodies can be rotated with body.setRotation(r), for instance as in http://monsterden.net/software/ragdoll-pyode-tutorial (string search setRotation there). best, Will On Sat, May 19, 2012 at 8:23 PM, Bill Call <we...@pr...> wrote: > Hi : > > I'm trying to build a rigid-body simulation using PyODE/PyOpenGL. Since > I'm just doing rigid-body, it is my understanding that I have no need > for joints; I just need to add masses to my body at the appropriate > translations/rotations. > > I have a number of cylindrical masses in my body. These cylinders have > fixed positions and rotations within the body, but are not necessarily > aligned with the X, Y or Z axis. PyODE does not bind the rotateMass() > function from ODE; it only allows me to specify an X, Y or Z orientation > for cylindrical mass (at creation time). This means that I am unable to > rotate my cylindrical masses to the correct orientation. > > My guess is that this would not be a problem if each of these masses had > their own Body; I could just rotate the body after the mass was bound. > Doing doing it that way might work, but it would mean connecting the > cylinders to the main body via joints, and what little documentation > there is seems to contraindicate the use of joints for rigid-body > simulations. > > My questions are as follows: > > 1) Am I correct in my assumption that I must rotate/translate the mass > tensor to reflect the true location/orientation of my cylindrical masses > within the containing body? It seems (to me) to be intuitively obvious > that I do, but I don't put much stock in my intuition regarding this > subject. > > 2) If the answer to (1) is "yes", then can anybody point me a rotation > implementation? If "no", then would someone be willing to explain why not? > > I have already spent a lot of time Googling about for this information, > but I am not sufficiently grounded in the subject to really understand > the answers I have been able to find on my own; not well enough to write > a function to rotate inertial tensors, anyway. > > Thanks in Advance, > > > Bill Call > > > > > > ------------------------------------------------------------------------------ > Live Security Virtual Conference > Exclusive live event will cover all the ways today's security and > threat landscape has changed and how IT managers can respond. Discussions > will include endpoint security, mobile security and the latest in malware > threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ > _______________________________________________ > Pyode-user mailing list > Pyo...@li... > https://lists.sourceforge.net/lists/listinfo/pyode-user |
From: Bill C. <we...@pr...> - 2012-05-21 18:16:19
|
On 5/21/2012 9:50 AM, James Thomas wrote: > In my experience there is a limitation which prevents summing masses > except at their cg. In general, in order to make a single body with a > complex mass you need to use transform geoms. Unfortunately I'm not > sure whether applying the rotation to the transform geom solves your > problem. Looking at my code I have a comment that I need to use > mass.rotate() but then I don't. I may have just punted and left it as > a loose end. My code is using the Ode implementation in Panda3d which > is based on a different version of ODE and does not use transform > geoms so I can't really help you with code specifics. > > JT > > On Sat, May 19, 2012 at 5:23 PM, Bill Call <we...@pr... > <mailto:we...@pr...>> wrote: > > Hi : > > I'm trying to build a rigid-body simulation using PyODE/PyOpenGL. > Since > I'm just doing rigid-body, it is my understanding that I have no > need > for joints; I just need to add masses to my body at the appropriate > translations/rotations. > > I have a number of cylindrical masses in my body. These cylinders > have > fixed positions and rotations within the body, but are not necessarily > aligned with the X, Y or Z axis. PyODE does not bind the rotateMass() > function from ODE; it only allows me to specify an X, Y or Z > orientation > for cylindrical mass (at creation time). This means that I am > unable to > rotate my cylindrical masses to the correct orientation. > > My guess is that this would not be a problem if each of these > masses had > their own Body; I could just rotate the body after the mass was bound. > Doing doing it that way might work, but it would mean connecting the > cylinders to the main body via joints, and what little documentation > there is seems to contraindicate the use of joints for rigid-body > simulations. > > My questions are as follows: > > 1) Am I correct in my assumption that I must rotate/translate the mass > tensor to reflect the true location/orientation of my cylindrical > masses > within the containing body? It seems (to me) to be intuitively > obvious > that I do, but I don't put much stock in my intuition regarding this > subject. > > 2) If the answer to (1) is "yes", then can anybody point me a rotation > implementation? If "no", then would someone be willing to explain > why not? > > I have already spent a lot of time Googling about for this > information, > but I am not sufficiently grounded in the subject to really understand > the answers I have been able to find on my own; not well enough to > write > a function to rotate inertial tensors, anyway. > > Thanks in Advance, > > > Bill Call > > > > > > ------------------------------------------------------------------------------ > Live Security Virtual Conference > Exclusive live event will cover all the ways today's security and > threat landscape has changed and how IT managers can respond. > Discussions > will include endpoint security, mobile security and the latest in > malware > threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ > _______________________________________________ > Pyode-user mailing list > Pyo...@li... > <mailto:Pyo...@li...> > https://lists.sourceforge.net/lists/listinfo/pyode-user > > > > > ------------------------------------------------------------------------------ > Live Security Virtual Conference > Exclusive live event will cover all the ways today's security and > threat landscape has changed and how IT managers can respond. Discussions > will include endpoint security, mobile security and the latest in malware > threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ > > > _______________________________________________ > Pyode-user mailing list > Pyo...@li... > https://lists.sourceforge.net/lists/listinfo/pyode-user James: Thanks for your reply. I am using transform geoms. As you note I have no choice in this matter as PyODE does not support offsets. The transform geoms seem to be working correctly; all my geoms render in the correct location, even when rotation/translation is applied to the parent body. It is also true the ODE requires that a single body with multiple masses have its CoG at (0, 0, 0); this I have also done. In any event, the transform geoms don't help, because mass is bound to bodies, not geoms. I assume that if each of my geoms had its own body, mass rotation wouldn't be an issue. Interestingly, I did try an experiment in which I created a body with a single cylinder geom and cylinder mass, then rotated the body. Examining the inertia tensor before and after the rotation shows that the tensor did not change. This doesn't really surprise me; I assume it means that the tensor is is terms of the bodies coordinate system, which is presumably constant. I don't know about Panda3d, but the PyODE bindings don't support mass.rotate(); perhaps this is also a problem for Panda3d, and this is why you did not implement? In any event, I cannot imagine how this could not be important. If the tensors for the off-axis masses are not rotated/translated correctly, then the summed inertial tensor for the body will be off, which is not a good thing for my application. I am currently attempting to work around the problem by reverse-engineering the orignal ODE roatate mass code from C++ to python. Since I only have to rotate each affected mass once, at the time I construct my body, the fact that performance will be poor is not a factor. This seems to be working, but I am currently setting up a test to compare the output of my Python dMassRotate() function with that of ODE. Regards, Bill C. |
From: James T. <jt...@mi...> - 2012-05-21 15:14:33
|
In my experience there is a limitation which prevents summing masses except at their cg. In general, in order to make a single body with a complex mass you need to use transform geoms. Unfortunately I'm not sure whether applying the rotation to the transform geom solves your problem. Looking at my code I have a comment that I need to use mass.rotate() but then I don't. I may have just punted and left it as a loose end. My code is using the Ode implementation in Panda3d which is based on a different version of ODE and does not use transform geoms so I can't really help you with code specifics. JT On Sat, May 19, 2012 at 5:23 PM, Bill Call <we...@pr...> wrote: > Hi : > > I'm trying to build a rigid-body simulation using PyODE/PyOpenGL. Since > I'm just doing rigid-body, it is my understanding that I have no need > for joints; I just need to add masses to my body at the appropriate > translations/rotations. > > I have a number of cylindrical masses in my body. These cylinders have > fixed positions and rotations within the body, but are not necessarily > aligned with the X, Y or Z axis. PyODE does not bind the rotateMass() > function from ODE; it only allows me to specify an X, Y or Z orientation > for cylindrical mass (at creation time). This means that I am unable to > rotate my cylindrical masses to the correct orientation. > > My guess is that this would not be a problem if each of these masses had > their own Body; I could just rotate the body after the mass was bound. > Doing doing it that way might work, but it would mean connecting the > cylinders to the main body via joints, and what little documentation > there is seems to contraindicate the use of joints for rigid-body > simulations. > > My questions are as follows: > > 1) Am I correct in my assumption that I must rotate/translate the mass > tensor to reflect the true location/orientation of my cylindrical masses > within the containing body? It seems (to me) to be intuitively obvious > that I do, but I don't put much stock in my intuition regarding this > subject. > > 2) If the answer to (1) is "yes", then can anybody point me a rotation > implementation? If "no", then would someone be willing to explain why not? > > I have already spent a lot of time Googling about for this information, > but I am not sufficiently grounded in the subject to really understand > the answers I have been able to find on my own; not well enough to write > a function to rotate inertial tensors, anyway. > > Thanks in Advance, > > > Bill Call > > > > > > > ------------------------------------------------------------------------------ > Live Security Virtual Conference > Exclusive live event will cover all the ways today's security and > threat landscape has changed and how IT managers can respond. Discussions > will include endpoint security, mobile security and the latest in malware > threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ > _______________________________________________ > Pyode-user mailing list > Pyo...@li... > https://lists.sourceforge.net/lists/listinfo/pyode-user > |
From: Bill C. <we...@pr...> - 2012-05-20 00:23:28
|
Hi : I'm trying to build a rigid-body simulation using PyODE/PyOpenGL. Since I'm just doing rigid-body, it is my understanding that I have no need for joints; I just need to add masses to my body at the appropriate translations/rotations. I have a number of cylindrical masses in my body. These cylinders have fixed positions and rotations within the body, but are not necessarily aligned with the X, Y or Z axis. PyODE does not bind the rotateMass() function from ODE; it only allows me to specify an X, Y or Z orientation for cylindrical mass (at creation time). This means that I am unable to rotate my cylindrical masses to the correct orientation. My guess is that this would not be a problem if each of these masses had their own Body; I could just rotate the body after the mass was bound. Doing doing it that way might work, but it would mean connecting the cylinders to the main body via joints, and what little documentation there is seems to contraindicate the use of joints for rigid-body simulations. My questions are as follows: 1) Am I correct in my assumption that I must rotate/translate the mass tensor to reflect the true location/orientation of my cylindrical masses within the containing body? It seems (to me) to be intuitively obvious that I do, but I don't put much stock in my intuition regarding this subject. 2) If the answer to (1) is "yes", then can anybody point me a rotation implementation? If "no", then would someone be willing to explain why not? I have already spent a lot of time Googling about for this information, but I am not sufficiently grounded in the subject to really understand the answers I have been able to find on my own; not well enough to write a function to rotate inertial tensors, anyway. Thanks in Advance, Bill Call |
From: Terry D. <td...@ii...> - 2011-10-25 22:11:49
|
Hullo All, I'm just starting out with PyODE. I have been trying to work with the examples provided in 'PyODE-snapshot-2010-03-22', and have come up against a few issues. I have tried experimenting with some code mods in vehicle.py which cause errors. As an example, I tried altering the spheres to cylinders, and get a 'not implemented' message. This leads me to ask if there is a later, more complete, version of PyODE available somewhere? Cheers, -- Regards, Terry Duell |
From: German L. M. <ger...@gm...> - 2011-09-01 20:32:20
|
> > I thought that's a warning, not an error? No, it is an error. Maybe in previous python versions (I'm running 2.7.1 on linux) it was just a warning. I think many of them are now errors, to take care of possible bugs. Germán Larrain |
From: German L. M. <ger...@gm...> - 2011-08-30 20:57:09
|
Tutorial 2 has a bug. The output is: > Traceback (most recent call last): > File "tutorial2.py", line 155, in <module> > simulate(world, body1, body2) > File "tutorial2.py", line 141, in simulate > pygame.draw.circle(srf, (55,0,200), coord(x1,y1), 20, 0) > TypeError: integer argument expected, got float An easy fix is to replace the "coord" function content with this: return int(320+170*x), int(400-170*y) that is, convert to int the values to be returned. I used the 2010.10.13 snapshot, and I'm running Ubuntu 11.04 32 bits. -- Germán Larrain |
From: Will B. <bos...@mi...> - 2011-07-09 22:56:46
|
Hello, I am trying to install the 2010-03-22 pyode snapshot onto python2.7 / osx, and seem to be having trouble at the gcc step. I have pyrex installed and have installed xcode recently. 'python setup.py build' results in the folowing errors: building 'ode' extension creating build/temp.macosx-10.3-fat-2.7 gcc-4.0 -fno-strict-aliasing -fno-common -dynamic -arch ppc -arch i386 -g -O2 -DNDEBUG -g -O3 -I/usr/include -I/usr/local/include -I/opt/local/include -I/Library/Frameworks/Python.framework/Versions/2.7/include/python2.7 -c ode_trimesh.c -o build/temp.macosx-10.3-fat-2.7/ode_trimesh.o -I/usr/local/Cellar/ode/r1760/include -DdSINGLE unable to execute gcc-4.0: No such file or directory error: command 'gcc-4.0' failed with exit status 1 My machine has gcc-4.2 installed (verified with 'which gcc-4.2'), and not gcc-4.0 . Any thoughts on how to tell the build process how to find my functioning gcc ? (or: any other ideas?) thanks, will |
From: john j. <jja...@al...> - 2011-06-09 00:55:22
|
I just installed ode 0.11.1 and py26-ode 1.2.0 via macports and on my macbook running OS X10.6.7 and when I try the first tutorial it crashes. The first data point comes out OK, but the rest are blown up (until it crashes) - it looks like a divide by zero. Anyone have any thoughts? Now I get these messages: after line: M.setSphere(2500.0, 0.05): ODE Message 2: mass must be > 0 in dMassCheck() File mass.cpp Line 49 0.00sec: pos=( 0.000, 0.000, 2.000) vel=( 0.000, 0.000, 0.000) and then when in the loop, right when it crashes, I get the message: ODE INTERNAL ERROR 1: assertion "bNormalizationResult" failed in _dNormalize4() [../../include/ode/odemath.h] |
From: Hart's A. <bha...@ya...> - 2011-05-19 13:12:54
|
Hi,I am having good progress with the ctypes bindings to ODE, i haven't tested everything yet, but so far everything is working. For the most part its just like PyODE, but there are still some points where you have to directly deal with ctypes. http://pyppet.blogspot.com/2011/05/ode-ctypes-in-blender.html http://rpythonic.googlecode.com/files/Active-Physics-Blender-release1.zip Quick Example: ode.InitODE()print( 'ode init ok' ) world = ode.WorldCreate()print( dir(world) )print( 'angular damping default', world.GetAngularDamping() )print( 'quickstep default', world.GetQuickStepNumIterations() )world.SetQuickStepNumIterations(24)world.SetGravity( 0, 0, -.9 ) space = ode.SimpleSpaceCreate()print( 'space', space ) bodies = []for i in range(200): body = ode.BodyCreate( world ) bodies.append( body ) body.SetPosition( random(), random(), random() ) mass = ode.Mass() # no function to create a mass? mass.SetSphere( 0.1+random(), 0.5) # density, radius body.SetMass( mass ) start = time.time()for i in range(500): world.QuickStep( 1.1 ) print( 'frame', i ) for b in bodies: b.AddForce(0.1, .0, .0) x,y,z = b.GetPosition() print(x,y,z)print('time', time.time()-start) ode.CloseODE() |
From: Robert R. <tif...@ho...> - 2011-05-18 06:05:32
|
Its a brill site where you can buy everything you want!. http://csr-cam.com/friends_links.php?atID=63h5 |
From: German L. M. <ger...@gm...> - 2011-05-17 12:28:52
|
Paul: Maybe Codeblocks could help you. http://www.codeblocks.org/ It is crossplatform. Ah, Netbeans too. http://netbeans.org/ Good luck -- Germán Larrain |
From: Paul K. <pki...@in...> - 2011-05-17 11:42:03
|
Hi I have been a very long time user of PyODE, using an ODE.PYD version compiled against Win32 Python 2.2 and 2.4. Unfortunately I now need to recompile (some 7 years later) for Python 2.4 64 bit and Python 2.7 32 and 64 bit. I am having trouble compiling for both version of python. For python 2.4 64 bit, it seems I need an old version of Visual Studio - long longer available. Does anyone know a workaround for this? I'm also struggling to compile PyODE for Python 2.7 using Vis Studio 2008. I compile ODE in Vis Studio ok, but then the pyode build gives link errors such as: (dReal) LIBCMT.lib(crtheap.obj) : error LNK2005: __malloc_crt already defined in MSVCRT. lib(MSVCR90.dll) LIBCMT.lib(crt0dat.obj) : error LNK2005: __amsg_exit already defined in MSVCRT.l ib(MSVCR90.dll) LIBCMT.lib(crt0dat.obj) : error LNK2005: __initterm_e already defined in MSVCRT. lib(MSVCR90.dll) LIBCMT.lib(crt0dat.obj) : error LNK2005: _exit already defined in MSVCRT.lib(MSV CR90.dll) LIBCMT.lib(fflush.obj) : error LNK2005: _fflush already defined in MSVCRT.lib(MS VCR90.dll) LIBCMT.lib(crt0init.obj) : error LNK2005: ___xi_a already defined in MSVCRT.lib( cinitexe.obj) LIBCMT.lib(crt0init.obj) : error LNK2005: ___xi_z already defined in MSVCRT.lib( cinitexe.obj) LIBCMT.lib(crt0init.obj) : error LNK2005: ___xc_a already defined in MSVCRT.lib( cinitexe.obj) LIBCMT.lib(crt0init.obj) : error LNK2005: ___xc_z already defined in MSVCRT.lib( cinitexe.obj) LIBCMT.lib(winxfltr.obj) : error LNK2005: ___CppXcptFilter already defined in MS VCRT.lib(MSVCR90.dll) LIBCMT.lib(tidtable.obj) : error LNK2005: __encode_pointer already defined in MS VCRT.lib(MSVCR90.dll) LIBCMT.lib(tidtable.obj) : error LNK2005: __encoded_null already defined in MSVC RT.lib(MSVCR90.dll) LIBCMT.lib(tidtable.obj) : error LNK2005: __decode_pointer already defined in MS VCRT.lib(MSVCR90.dll) LIBCMT.lib(mlock.obj) : error LNK2005: __unlock already defined in MSVCRT.lib(MS VCR90.dll) LIBCMT.lib(mlock.obj) : error LNK2005: __lock already defined in MSVCRT.lib(MSVC R90.dll) Creating library build\temp.win32-2.7\Release\ode.lib and object build\temp.w in32-2.7\Release\ode.exp LINK : warning LNK4098: defaultlib 'MSVCRT' conflicts with use of other libs; us e /NODEFAULTLIB:library LINK : warning LNK4098: defaultlib 'LIBCMT' conflicts with use of other libs; us e /NODEFAULTLIB:library LIBCMT.lib(crt0.obj) : error LNK2019: unresolved external symbol _main reference d in function ___tmainCRTStartup build\lib.win32-2.7\ode.pyd : fatal error LNK1120: 1 unresolved externals error: command '"C:\Program Files\Microsoft Visual Studio 9.0\VC\BIN\link.exe"' failed with exit status 1120 Does anyone have any advice pls? Thanks in advance. Paul |
From: German L. M. <ger...@gm...> - 2011-05-13 21:53:43
|
Hi Brett, Thanks for the answer. Are you working on that project on your own? Also, is it compatible with the last release of ODE, or the current svn version? Thanks, Germán On Fri, May 13, 2011 at 1:33 AM, Hart's Antler <bha...@ya...> wrote: > Hi German, > > I am still working with ODE, you can try my ctypes bindings, they are py3k > compatible. > http://pastebin.com/hLwCexG8 > > you can load it directly, but you get a nicer wrapper if you install load > through Rpythonic. > http://code.google.com/p/rpythonic/ > > -brett > > --- On *Thu, 5/12/11, German Larrain M. <ger...@gm...>* wrote: > > > From: German Larrain M. <ger...@gm...> > Subject: [Pyode-user] Development status? > To: pyo...@li... > Date: Thursday, 12 May, 2011, 5:11 PM > > > Hi. I'm thinking about using pyode for a project, but I'm concerned about > whether development will continue or not. For example, moving on to Python 3 > may be necessary in the future, as well as keeping up with new ODE releases. > > Anybody wants to share thoughts on this? > > It would be a really nice thing if this project got incorporated in ODE, as > happened with the python interface of OpenCV. > > Best regards, > Germán > > -- > Germán Larrain > > -----Inline Attachment Follows----- > > > ------------------------------------------------------------------------------ > Achieve unprecedented app performance and reliability > What every C/C++ and Fortran developer should know. > Learn how Intel has extended the reach of its next-generation tools > to help boost performance applications - inlcuding clusters. > http://p.sf.net/sfu/intel-dev2devmay > > -----Inline Attachment Follows----- > > _______________________________________________ > Pyode-user mailing list > Pyo...@li...<http://mc/compose?to=Pyo...@li...> > https://lists.sourceforge.net/lists/listinfo/pyode-user > > -- Germán Larrain |
From: Hart's A. <bha...@ya...> - 2011-05-13 05:33:41
|
Hi German, I am still working with ODE, you can try my ctypes bindings, they are py3k compatible. http://pastebin.com/hLwCexG8 you can load it directly, but you get a nicer wrapper if you install load through Rpythonic. http://code.google.com/p/rpythonic/ -brett --- On Thu, 5/12/11, German Larrain M. <ger...@gm...> wrote: From: German Larrain M. <ger...@gm...> Subject: [Pyode-user] Development status? To: pyo...@li... Date: Thursday, 12 May, 2011, 5:11 PM Hi. I'm thinking about using pyode for a project, but I'm concerned about whether development will continue or not. For example, moving on to Python 3 may be necessary in the future, as well as keeping up with new ODE releases. Anybody wants to share thoughts on this? It would be a really nice thing if this project got incorporated in ODE, as happened with the python interface of OpenCV. Best regards, Germán -- Germán Larrain -----Inline Attachment Follows----- ------------------------------------------------------------------------------ Achieve unprecedented app performance and reliability What every C/C++ and Fortran developer should know. Learn how Intel has extended the reach of its next-generation tools to help boost performance applications - inlcuding clusters. http://p.sf.net/sfu/intel-dev2devmay -----Inline Attachment Follows----- _______________________________________________ Pyode-user mailing list Pyo...@li... https://lists.sourceforge.net/lists/listinfo/pyode-user |
From: German L. M. <ger...@gm...> - 2011-05-13 00:12:04
|
Hi. I'm thinking about using pyode for a project, but I'm concerned about whether development will continue or not. For example, moving on to Python 3 may be necessary in the future, as well as keeping up with new ODE releases. Anybody wants to share thoughts on this? It would be a really nice thing if this project got incorporated in ODE, as happened with the python interface of OpenCV. Best regards, Germán -- Germán Larrain |