[Robotics] Feedback on MORSE installation instructions...

koen buys koen.buys at mech.kuleuven.be
Thu Jan 6 14:50:35 CET 2011


I'm currently looking in how to adapt the current GUI for Robotics
that we have so that it would fit inside MORSE.

On 6 January 2011 13:10, Redouane Boumghar <redouane.boumghar at laas.fr> wrote:
> Hello all !
>
> I have tried using Morse in the early development with my intel chipset.
> I have an intel GM45 video chipset with DRI2 Enabled...
>
>
> With xorg-drivers and xorg-server < 1.7 and blender 2.4* :
> I could only use the GLSL Materials and all I was getting was the
> the default mixing color of materials (pink :) )
>
> Now I have a stable version of the xorg-server 1.7.7
> and xorg-drivers 1.7 (I know I do not live on the edge). In the game
> engine, the texture are perfect but on special features like normal maps
> where I still get a strange render.
> Anyway My intel video card is still too slow to play with it.
> I only get a maximum of 5 frames per seconds on any-kind of scene.
>
> So I use another computer with a NVidia graphic card.
>
> By the way I am kind of pionneer using Morse for outdoor scenes
> simulation and my role in development has been essentially to
> unveil bugs to the core development team (I live face to face with
> Gilberto during the daylight :D )
>
> And yesterday as I was reading the hackaton wiki page again :
> http://www.openrobots.org/wiki/morse/events/hackaton_jan_2011
>
> I was thinking the same. We need a "hello world robot!" example;
> simple & fast & fun in order to increase the new-users input.
> So Herman, I'll join you on this topic.. at least on ideas.
>
> A good thing would be to share ideas before we start the hack-a-ton
> by using the (previously cited) wiki.
>
> (each hackaton page can be suffixed with "?action=edit" in order
> to edit it, as this link does not appear on all of them yet).
>
> For now I have added comments on these pages :
> http://www.openrobots.org/wiki/morse/events/hackaton_jan_2011/gui
> http://www.openrobots.org/wiki/morse/events/hackaton_jan_2011
> and will soon add this page when allowed to :
> http://www.openrobots.org/wiki/morse/events/hackaton_jan_2011/helloworldrobots
>
> Best Regards,
> --
> Redouane Boumghar
> PhD Student: Decision theory and multi-robot cooperation
> RIA LAAS / CNRS - MAGELLIUM
> tel: +33 561337895
>
> On Thu, Jan 06, 2011 at 11:39:10AM +0100, Séverin Lemaignan wrote:
>> Hello!
>>
>> Thanks a lot, Herman, for your valuable feedback! (and very happy to
>> know that it worked out for you :-) )
>>
>> The Intel i915 is definitely not powerful enough to run Blender with
>> acceptable performances: you really need a graphic card with support for
>> shaders.
>>
>> I've updated the installation documentation with your comments and to
>> match the latest version (morse-0.2b1). By the way, you should not need
>> anymore to change the PYTHONPATH variable. It's now automatically detected.
>>
>> See you next week,
>> Séverin
>>
>> Le 01/06/2011 11:15 AM, Herman Bruyninckx a écrit :
>> > Dear all,
>> >
>> > as a preparation of the "hack-a-ton" of next week,
>> >    <http://www.openrobots.org/wiki/morse/events/hackaton_jan_2011>,
>> > I tried to install Morse on a "completely fresh" system, and not a fancy
>> > modern one: a MacBook of four years old, with an Intel i915 graphics card,
>> > and Ubuntu 10.10.
>> >
>> > So, maybe you can use this feedback to update the current installation tutorial on
>> >    <http://homepages.laas.fr/slemaign/openrobots/doku.php?id=morse:user:installation>
>> > At the end of this message, I attach my "installation log", including
>> > some remarks and feedback.
>> >
>> > In summary:
>> >
>> > - I succeeded in getting a working morse, in the simplest configuration,
>> >     that is without the middleware or pocolibs, in about an hour or so.
>> >     Which means the current installation guide is not bad at all :-)
>> >
>> > - the current examples are rather "high end" already, both with respect to
>> >     GPU requirements and complexity of the scene
>> >
>> > Overall, I liked what I saw, but the experience also made me aware of the
>> > fact that we will have to come up with a simple "hello robot world!"
>> > example, in order to make the entry threshold a bit lower. This might be a
>> > task that I like to set myself, if nobody else volunteers :-) Maybe we can
>> > have a short discussion on the "hack-a-ton" about what would be an
>> > appropriate as-simple-but-still-relevant-as-possible .blend to give new
>> > users a good feeling about what morse is capable of...
>> >
>> > Best regards,
>> >
>> > Herman Bruyninckx
>> > =================================
>> >
>> > I followed the instructions on
>> > <http://homepages.laas.fr/slemaign/openrobots/doku.php?id=morse:user:installation>
>> >
>> > The git stuff went without errors or problems. I updated ("git pull") an
>> > older version of morse that I checked out a month or two ago.
>> >
>> > My Ubuntu 10.10 does not have Python 3.1 installed by default. All I had to
>> > do was to install the "python3.1" and "python3.1-dev" packages from the
>> > standard repository.
>> >
>> > The Blender executable I use is blender-2.56-beta-linux-glibc27-i686, that
>> > is, the last one available from blender.org. I installed it quick and
>> > simply from the provided tar-ball.
>> >
>> > I spent some time in finding the right set of environment variables for my
>> > system, which resulted in the following bash script:
>> > "
>> > export MORSE_ROOT=/usr/local
>> > export MORSE_BLENDER=$HOME//blender-2.56-beta-linux-glibc27-i686/blender
>> > export PYTHONPATH=$MORSE_ROOT/lib/python3/dist-packages
>> > "
>> >
>> > Note that the website says
>> >     "export PYTHONPATH=$MORSE_ROOT/lib/python3.1/dist-packages"
>> > but the cmake code installs in
>> >     "/lib/python3/dist-packages".
>> > (That is, "3" instead of "3.1"!)
>> >
>> > The "$ make install" command had to be replaced by "$sudo make install".
>> >
>> > Now, "morse check" returns without errors.
>> > And I continued with the Testing:
>> > " To test the external control clients:
>> >       * On a text terminal, run the morse command
>> > "
>> > The result is that Blender starts, with the following text on the console:
>> > "morse 0.2b1
>> > Copyright LAAS-CNRS 2010
>> > found bundled python:
>> > /home/herman/blender-2.56-beta-linux-glibc27-i686/2.56/python
>> > read blend: /home/herman/code/morse/./scene.01.blend
>> > WARNING: No module named yarp
>> > YARP middleware will not work
>> > "
>> >
>> > That's fine, since I did not compile in the middleware.
>> >
>> > The tutorial goes on as follows:
>> >     "Open the Blender file:
>> >     $MORSE_ROOT/share/examples/morse/scenarii/tutorial-1-solved.blend
>> >     "
>> > but that file "tutorial-1-solved.blend" does not exist. I do see the
>> > following files:
>> >     action-4-2.54.blend         grande_salle-1.blend
>> >     stereo_test.blend
>> >     action-4.blend              grande_salle-2.5-kuka-poster.blend
>> >     camera_calibration-1.blend  stereo_test-2.54-1.blend
>> > All these files are rather huge Blender scenes (and they rely on a modern
>> > graphics card, I guess). A simpler "hello robot world" example would be
>> > nice to have, that is, without having to use middleware or cameras.
>> >
>> > "Start the simulation P" ->  not a nice result for my old laptop with Intel
>> > i915 graphics card :-) But hey, morse works!
>> >
>> >
>> > _______________________________________________
>> > Robotics mailing list
>> > Robotics at blender.org
>> > http://lists.blender.org/mailman/listinfo/robotics
>>
>> --
>>            Séverin Lemaignan - severin.lemaignan at laas.fr
>>    [00]    PhD student on Cognitive Robotics
>>   /|__|\   LAAS-CNRS - RIS group / Technische Uni München - IAS group
>>     ''     +33561337844 / +498928917780
>>            http://www.laas.fr/~slemaign
>> _______________________________________________
>> Robotics mailing list
>> Robotics at blender.org
>> http://lists.blender.org/mailman/listinfo/robotics
>
> _______________________________________________
> Robotics mailing list
> Robotics at blender.org
> http://lists.blender.org/mailman/listinfo/robotics
>


More information about the Robotics mailing list