Hi Bob (and the others),
thanks for your answer - this helps enormously. I have a bunch of legacy files
created by a legacy utility - I modified the code to no longer put stuff after
the integer.
As a side note: the xyz::broken.xyz trick also works on the command line (which
is how I start
No changes ever.
On Mon, Sep 26, 2016 at 9:08 AM, Angel Herráez wrote:
>
> OK, I will ammend the wiki to clarify the issue.
>
> But, important: Peter, has this behaviour changed across Jmol versions?
> It is one thing that Jmol identifies or not the format, as Bob has
>
OK, I will ammend the wiki to clarify the issue.
But, important: Peter, has this behaviour changed across Jmol versions?
It is one thing that Jmol identifies or not the format, as Bob has explained;
it
is another if there has been a change in behaviour.
Thanks
Peter,
On my editor, your “broken” file has an additional text (the letter “a’) on the
first line.
Could that be the problem?
Matt Kubasik
On Sep 26, 2016, at 6:46 AM, Peter Brommer
> wrote:
Hi,
This concerns Jmol Version:
The *xyz reader *ignores everything else on the first line after the
integer.
The *reader format resolver *is what requires just an integer (the number
of atoms) and white space on the first line in order to send the data to
the xyz reader, because there are several other formats that start with
Hi,
This concerns Jmol Version: 14.6.1_2016.08.11 2016-08-11 22:11.
There is an issue with reading/recognising xyz files. On the wiki page
http://wiki.jmol.org/index.php/File_formats/Formats/XYZ those are described as
having two header lines per step in a multi-step format, the first of which
6 matches
Mail list logo