Open samuelcajahuaringa opened 7 months ago
Hi Samuel,
A change was pushed that inadvertently broke attribute propagation from a QM result (e.g. NWChem) to its geometry instance. In other words, after calling isicle.qm.dft
, the resulting geometry should have attributes for energy
, charge
, etc., as requested in the configuration step.
This is currently running through continuous integration as a pull request (#31). Alternatively, you can checkout an earlier branch (before we began adding ORCA functionality) to revert to previous, pre-bug behavior (i.e. commit a69208e7c89359d5649914882992eab82e3ea6ec).
Note that we are working on refactoring how some of this functions, to decouple simulations from parsing. Reason being that a simulation may run successfully to completion, but any issues with the parser could cause a workflow management system (e.g. Snakemake, NextFlow) to purge simulation outputs. With these steps separated, the simulation can run to completion independent of the parsing operation. Stay tuned!
Best,
Sean
Hello isicle developers,
I try to calculate the CCS but I have the following errors:
when I try to calculate the CCS using the tutorial example:
I inspect the dft2 dictionary and according to the dictionary dft2['geom'] is equivalent to dft2.geom?
after that, I try run again the CCS
how can I correct this problem, there are how convert the dictionary dft2 to a object?
Any suggestions thanks Samuel