[Biopython-dev] Notification: incoming/50

biopython-bugs at bioperl.org biopython-bugs at bioperl.org
Wed Oct 24 20:49:43 EDT 2001

JitterBug notification

new message incoming/50

Message summary for PR#50
	From: "Gavin E. Crooks" <gec at compbio.berkeley.edu>
	Subject: Re: [Biopython-dev] Notification: incoming/49
	Date: Wed, 24 Oct 2001 17:40:52 -0700
	0 replies 	0 followups


>From gec at sienna.berkeley.edu Wed Oct 24 20:49:43 2001
Received: from sienna.berkeley.edu (IDENT:root at sienna.Berkeley.EDU [])
	by pw600a.bioperl.org (8.11.2/8.11.2) with ESMTP id f9P0ngB25247
	for <biopython-bugs at bioperl.org>; Wed, 24 Oct 2001 20:49:42 -0400
Received: from localhost (localhost [[UNIX: localhost]])
	by sienna.berkeley.edu (8.9.3/8.9.3) id RAA03432
	for biopython-bugs at bioperl.org; Wed, 24 Oct 2001 17:49:42 -0700
From: "Gavin E. Crooks" <gec at compbio.berkeley.edu>
Reply-To: gec at compbio.berkeley.edu
Organization: Very Little
To: biopython-bugs at bioperl.org
Subject: Re: [Biopython-dev] Notification: incoming/49
Date: Wed, 24 Oct 2001 17:40:52 -0700
X-Mailer: KMail [version 1.0.29]
Content-Type: text/plain
References: <200110242357.f9ONvGB24883 at pw600a.bioperl.org>
In-Reply-To: <200110242357.f9ONvGB24883 at pw600a.bioperl.org>
MIME-Version: 1.0
Message-Id: <01102417494205.14420 at sienna.berkeley.edu>
Content-Transfer-Encoding: 8bit

How about  "A:-1-126", direct from SCOP...
16118	px	a.4.5.8	d1b9ma1	1b9m A:-1-126

I am in the middle of updating the SCOP module, and I have already
refactored that code, and fixed this bug. And I've written a nice shiny
unit test.  But I was concerned that this same bug could crop up elsewhere.
Its the kind of obscure boundary case that could trip up any code working 
with PDB sequence numbers.


gec at compbio.berkeley.edu

> Hi Gavin,
> Could you send me a sample of this?  It'll be helpful to have a test 
> case to test fixes.
> Thanks,
> Jeff
> >Full_Name: Gavin Crooks
> >Module: SCOP/Location.py
> >Version:
> >OS:
> >Submission from: sienna.berkeley.edu (
> >
> >PDB residue sequence numbers can, on occasion, be
> >negative. e.g. 1B9N. SCOP domains sometimes start
> >on negative sequence numbers. This breaks the
> >location parser in Bio.SCOP.Location.py

More information about the Biopython-dev mailing list