Re: [ccp4bb] CCP4 GUI

- Protein crystallography

Main steps:

- Protein purification
- Crystallisation

Special:

- Programs for crystallography
- X-ray detectors

Basic tutorials:

   - Chemistry
   - Protein
   - Peptide
   - Amino Acids

Xtal community:

- CCP4BB

CCP4bb navigation

CCP4bb <-- 1999 <-- November 1999 <-- 30 November 1999

Previous message:
Subject: xsect.dat=cossec.lib?
From: Bernhard Rupp bernhardrupp {- at -} SBCGLOBAL {- dot -} NET
Date: 2007-05-11

Next message:
Subject: Re: CCP4 GUI
From: Kevin Cowtan cowtan {- at -} YSBL {- dot -} YORK {- dot -} AC {- dot -} UK
Date: 2007-05-11

Subject: Re: CCP4 GUI
From: Harry Powell harry {- at -} MRC-LMB {- dot -} CAM {- dot -} AC {- dot -} UK
Date: 2007-05-11

Hi

> Maybe any parameter setting unchanged from the values in the
> $CCP4/ccp4i/tasks/*.def file should be internally flagged as being at
> the 'default value' - resulting in them _not_ being written to the
> com-file? This way any potential change in defaults inside the actual
> program would have immediate effect, even if the CCP4i hasn't been
> updated yet.

This is a _really_ good idea for another reason. There are programs which
determine processing parameter values dyamically, based on what they have
actually been presented with - UNLESS those values have been input by the
user, who is assumed to "know better". If an interface (e.g. ccp4i) sets
the value to a default, the program really has no way of knowing that it
was the interface and not a user who knows their data which has input the
value.

Just my two ha'porth...

Harry
--
Dr Harry Powell, MRC Laboratory of Molecular Biology, MRC Centre, Hills
Road, Cambridge, CB2 2QH

CCP4bb navigation

CCP4bb <-- 1999 <-- November 1999 <-- 30 November 1999

Previous message:
Subject: xsect.dat=cossec.lib?
From: Bernhard Rupp bernhardrupp {- at -} SBCGLOBAL {- dot -} NET
Date: 2007-05-11

Next message:
Subject: Re: CCP4 GUI
From: Kevin Cowtan cowtan {- at -} YSBL {- dot -} YORK {- dot -} AC {- dot -} UK
Date: 2007-05-11