***  For details on how to be removed from this list visit the  ***
***          CCP4 home page http://www.ccp4.ac.uk         ***



A workaround would be to switch off harvesting
with the NOHARVEST keyword or via GUI.

The fact that it is ccif_get_* rather than
ccif_put_* suggests it is a problem reading
the mmCIF dictionary which should be in
$CLIB/cif_mmdic.lib

Are you maybe using a dictionary generated
for another platform?

Can't say more without some context, e.g. a full
log file would have confirmed where it was failing.

Regards
Martyn

On Tue, 29 Nov 2005, Jie Li, PhD wrote:

> ***  For details on how to be removed from this list visit the  ***
> ***          CCP4 home page http://www.ccp4.ac.uk         ***
> 
> 
> Hi, ccp4 users,
> I failed to run MLPHARE. The information from the program 
> was:"
> <<<<CCIF signal CCIF_EXTRAMGE (severtity: severe 
> error/fatal>>>>
> (Raised in ccif_get_value)
> Context -1 out range (must be between 0 and 20 
> inclusive)."
> 
> Does someone know the reason?
> Thanks a lot.
> Lily
> 
>  
> This e-mail message may contain information that is
> confidential and/or privileged.  If you are not the intended
> recipient, any use, disclosure, copying, or communication
> of the contents of this message is prohibited.  If this
> message was received in error, please delete the message
> and any attachments from your computer.  Thank you.
>  
> 



**************************************************************************
*                                                                        *
*                  Dr. Martyn Winn                                       *
*                                                                        *
*      Daresbury Laboratory, Daresbury, Warrington, WA4 4AD, ENGLAND     *
*      Tel: +44 1925 603455    E-mail: [EMAIL PROTECTED] (personal)    *
*      Fax: +44 1925 603825    E-mail: [EMAIL PROTECTED]  (CCP4 problems)  * 
*          URL: http://www.ccp4.ac.uk/martyn/martyn.html                 *
**************************************************************************


Reply via email to