Account Options

  1. Sign in
The old Google Groups will be going away soon, but your browser is incompatible with the new version.
Google Groups Home
« Groups Home
Message from discussion Printed output on clusters
The group you are posting to is a Usenet group. Messages posted to this group will make your email address visible to anyone on the Internet.
Your reply message has not been sent.
Your post was successful
 
From:
To:
Cc:
Followup To:
Add Cc | Add Followup-to | Edit Subject
Subject:
Validation:
For verification purposes please type the characters you see in the picture below or the numbers you hear by clicking the accessibility icon. Listen and type the numbers you hear
 
David Warde-Farley  
View profile  
 More options Oct 20 2012, 11:49 pm
From: David Warde-Farley <d.warde.far...@gmail.com>
Date: Sat, 20 Oct 2012 23:49:02 -0400
Local: Sat, Oct 20 2012 11:49 pm
Subject: Re: [pylearn-dev] Printed output on clusters
On Sat, Oct 20, 2012 at 6:00 PM, Ian Goodfellow

<goodfellow....@gmail.com> wrote:
> Does anyone have a good solution to the problem of logs on the cluster not
> appearing / not being in sync, etc?
> It seems like most of the time I have a problem on the cluster, it is hard
> to debug, because a good portion of
> the output from the program doesn't get copied into the log file, or the log
> file just never appears.
> Usually this seems to be the fault of the job management software, since
> usually the filesystem is working just
> fine, and if I change my code to write out files at a pre-specified
> location, the writes show up.
> I'm thinking maybe we should make a logging module for pylearn2, so that the
> stuff pylearn2 currently prints to
> stdout could be easily redirected to a file when running on the cluster.
> Before I do that, I thought I should check if there is any existing logging
> system we should aim to be compatible with,
> or just use. For example, is this something that jobman solves?

http://docs.python.org/library/logging.html

I've been meaning to move all print statements over to appropriate log
levels on a logger from the stdlib logging module, anyway. Multiple
destinations can be set up using the addHandler mechanism. I'll try to
find a tutorial-style introduction, I've read/watched a few in the
past.

IIRC there are other more specialized modules that implement this API
as well so we can always move to one of those.

David


 
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.