Dear Wim,
Indeed. I did not know if the ChainCode was set to ' ' or to '', so I
wrote you an email to raise the point, just in case. I just put it badly
(sorry). Unlike an empty string. a single space is a perfectly valid
chainCode as far as I am concerned, so I have no objection to your using
that, if it is practical.
BTW, what is the etiquette for this kind of discussion group? Should all
discussions that start on the list continue on the list? Or should letters
that are probably of interest to only a couple of people be sent
privately, as I did with the email Wim is answering?
Yours,
Rasmus
> Hi Brian,
>
> > > The only advice I have until then is that you set the chain code to 'A'
> > > (or something) when creating a chain in the format converter.
> >
> > How? formatConverter just breezes through the import of an ANSIG sequence
> > file without offering the opportunity to set the chain code.
>
> Good point. I try to make the format conversion as 'non-clickable' as
> possible, so if there's only one chain it will automatically set code ' '
> for it. I can change this so you always have to enter a code yourself, but
> then other people might not be happy with this approach... it's tricky.
>
> And in response to Rasmus' email, a ' ' is not an empty string in my view
> (and None is not possible because Chain.code is obligatory). Anyway if you
> wonder why I'm using ' ' as default: I was originally using this so I
> could automatically write out files without chain codes (e.g. an XPLOR
> restraint list without segment code), but this has all changed in the
> meantime so if it is easier for everyone I will check if it is possible to
> start using 'A' as default.
>
> Bye,
>
> Wim.
>
|