The current interface to CrysFML is file-based. The content of a temporary CIF file is regenerated after any change and then that file is read by CrysFML using CFML_api.CIFFile(cif_fname). This approach is not stable and reduces overall performance. It seems that the phase object in CrysFML could also be created programmatically (with minor issues related to multiplicity and site occupancy). This would allow the development of a fileless interface to CrysFML. A jupyter notepad with an example is attached (as PDF) - CFML_fileless.pdf
The current interface to
CrysFML
is file-based. The content of a temporary CIF file is regenerated after any change and then that file is read byCrysFML
usingCFML_api.CIFFile(cif_fname)
. This approach is not stable and reduces overall performance. It seems that the phase object inCrysFML
could also be created programmatically (with minor issues related to multiplicity and site occupancy). This would allow the development of a fileless interface to CrysFML. A jupyter notepad with an example is attached (as PDF) - CFML_fileless.pdf