[RMCProfile-users] [EXTERNAL] xyz to cif

[Zhang, Yuanpeng]

Hi,

I am not sure what you were trying to achieve. Given an xyz file, we don’t have a box defined and therefore any defined lattice would be sort of arbitrary. Then having those bounding issues seem natural to me. If you want to create disordered system, I cannot see the reason why we have to start with an xyz file.

Cheers,
Yuanpeng

—

Dr. Yuanpeng Zhang
SNS-HFIR, ORNL

1 Bethel Valley Rd, TN 37830, US
Mobile: +1(865)335-4818
Email: zhangy3 at ornl.gov
Web: https://www.iris2020.net


________________________________
From: rmcprofile-users <rmcprofile-users-bounces at shadow.nd.rl.ac.uk> on behalf of Sumit Khadka via rmcprofile-users <rmcprofile-users at shadow.nd.rl.ac.uk>
Sent: Friday, October 14, 2022 5:36:23 PM
To: rmcprofile-users at rmcprofile.org <rmcprofile-users at rmcprofile.org>
Cc: Sumit Khadka <sumitkhadka08 at gmail.com>
Subject: [EXTERNAL] [RMCProfile-users] xyz to cif

Hi,

This question has been asked several times but none of the solutions worked
best for me. When converting xyz to cif there are always issues on boundary
and unphysical bounding box. RMCProfile seems to have an effective way of
creating cif files for disordered systems. Please see the attachment.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <hxxps://lists.rmcprofile.org/pipermail/rmcprofile-users/attachments/20221014/09430dc8/attachment.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: xyz2cif.jpg
Type: image/jpeg
Size: 203967 bytes
Desc: not available
URL: <hxxps://lists.rmcprofile.org/pipermail/rmcprofile-users/attachments/20221014/09430dc8/attachment.jpg>
_______________________________________________
rmcprofile-users mailing list
rmcprofile-users at rmcprofile.org
hxxp://lists.rmcprofile.org/mailman/listinfo/rmcprofile-users

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.rmcprofile.org/pipermail/rmcprofile-users/attachments/20221017/59b212ff/attachment-0001.htm>