A fix has been comitted to the relax svn repository.
This impliments two internal select parameters. The first, userSelect,
is controlled by the user through select.res() and related commands. The
second, autoSelect, is automatically set to 0 if the number of
parameters exceeds the number of data points for that residue, and 1
otherwise. The overall selection,
self.relax.data.res[run][index].select, is given by (userSelect AND
autoSelect)
Because autoSelect varies in complex ways as the program state changes,
it is evaluated on-the-fly whenever the selection state of the residue
is queried.
Any attempt to bind self.relax.data.res[run][index].select or
self.relax.data.res[run][index].autoSelect will raise an AttributeError
Chris
On Thu, 2006-03-16 at 00:08 +1100, Edward d'Auvergne wrote:
The deselection bug described in #5501 was originally designed as a
feature specifically to prevent residues from having less relaxation
data points than parameters in the model-free models. If the
behaviour is changed, we will need to work out how to handle less data
than parameters. For example, what should relax do if a residue with
only one data point is encountered? If 6 data points are collected
but two are missing, what should happen with model m8? How can the
final behaviour be made so that it is obvious to the end user what
will actaully happen in any data vs. parameter combination?
Edward
On 3/15/06, Chris MacRaild <NO-REPLY.INVALID-ADDRESS@xxxxxxx> wrote:
URL:
<http://gna.org/bugs/?func=detailitem&item_id=5501>
Summary: residue deselection problem on relax_data.read()
Project: relax
Submitted by: macraild
Submitted on: Wednesday 03/15/2006 at 09:48
Category: None
Priority: 5 - Normal
Severity: 3 - Normal
Status: In Progress
Privacy: Public
Assigned to: macraild
Originator Email:
Open/Closed: Open
_______________________________________________________
Details:
Currently, relax_data.read() tests all residues for whether or not they
contain data after the data file hes been read. Those without data are
deselected.
This causes all residues which lack data in the first loaded file to be
deselected even after loading new data for that residue.
An immediate work-around is to explicitly select resdiues as neccesary.
_______________________________________________________
Reply to this item at:
<http://gna.org/bugs/?func=detailitem&item_id=5501>
_______________________________________________
Message sent via/by Gna!
http://gna.org/
_______________________________________________
Relax-devel mailing list
Relax-devel@xxxxxxx
To unsubscribe from this list, get a password reminder, or change your
subscription options, visit the list information page at
https://mail.gna.org/listinfo/relax-devel
Re: [bug #5501] residue deselection problem on relax_data.read()