From dblank at brynmawr.edu  Tue Jul 11 10:28:03 2006
From: dblank at brynmawr.edu (Douglas S. Blank)
Date: Tue Jul 11 10:28:03 2006
Subject: [Pyro-developers] Re: Update for pyrobot.gui.console.py
In-Reply-To: <44B2F4BB.6030500@hrl.com>
References: <44B2F4BB.6030500@hrl.com>
Message-ID: <1152628083.9515.119.camel@mightymouse.brynmawr.edu>

Cool. Thanks, Jerry! Very handy. Will add to CVS.

-Doug

On Mon, 2006-07-10 at 17:45 -0700, Jerry Isdale wrote:
> The attached version of pyrobot/gui/console.py supports python logging 
> as well as the original print-to-tk-window
> It also has convenience functions logDebug() logInfo() logWarn() 
> logError() logCritical() to make it easier to use the log.
> I often find it helpful to use the python logging since it can log to 
> file as well as console, etc.
> Also attached is startLogging.py.  If you call it at the begining of 
> pyrobot.py:
> ...
> from startLogging import *
> startLogging("pyrobot")
> ...
> it will create a log file whose name includes the date/time in a form 
> such that the .logs will sort alphanumerically.
> Downside is you occasionally have to go into pyrobot/bin and clear out 
> the old .log files.

-- 
Douglas S. Blank       Computer Science
Assistant Professor    Bryn Mawr College
(610)526-6501          http://cs.brynmawr.edu/~dblank


From danbmil99 at yahoo.com  Mon Jul 17 15:00:04 2006
From: danbmil99 at yahoo.com (dan miller)
Date: Thu Mar  8 17:03:41 2007
Subject: [Pyro-developers] gazebo issues
Message-ID: <20060717190005.24367.qmail@web34011.mail.mud.yahoo.com>

hi --

I worked with Pyro a while ago (early '05), and I'm now re-installing &
getting up to date for a new project.  We need to use Gazebo.

After much wrestling with hardware & drivers, I have an FC4 machine with
proper  rendering (ie fast glxgears, direct screen etc).  However I found
that all versions of Gazebo 5.x I tried -- whether from your site,
playerstage directly, rpm, source etc -- have some sort of bug in the
wxgazebo python scripts, where I get an error along the lines of "cannot
allocate buffer -- size wrong" (sorry I didn't write it down verbatim).  I
recall it was in a file called _core_.py, or something similar.

So I upgraded to Gazebo 6.0, which solved this problem (I can run simple
example Gazebo worlds).  Now I'm trying to
get a reasonable version of Player, Stage, and Pyro working with this
version of Gazebo.  The problem I'm running into is in trying to figure out
which versions will work together.  I assumed the p/s 2.02 release would be
in sync, but I'm getting errors on tutorial.cfg.  Perusing the p/s lists, it
appears some parameter names have been changed, presumably to protect the
innocent until proven guilty.

So my question, finally, is what is the recommended way to get completely
up-to-date on the Pyro project, with working versions of player, stage, and
Gazebo, in sync with the tutorials and example files?  I'm concerned that
perhaps Gazebo has not had much attention of late, as it seems broken on the
liveCD release (tried it on 3 machines).  As you must know, it's a bit of a
bear to keep running, with a slew of dependencies, hardware reqs, and config
options.

Any help will be greatly appreciated.

-dan miller

__________________________________________________
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around 
http://mail.yahoo.com