QuantumATK Forum

QuantumATK => General Questions and Answers => Topic started by: Jin You Lu on September 6, 2016, 21:57

Title: lattice_const_looping struck ....
Post by: Jin You Lu on September 6, 2016, 21:57
Dear Sir
I want to scan the lattice to find minimum total energy of structure.
So i use the file in the tutorial to practice it , but it always struck in the calculating Kinetic matrix.
 Please check the attached files,thanks
Title: Re: lattice_const_looping struck ....
Post by: zh on September 7, 2016, 03:11
The error isn't reproduced by the  Atomistix ToolKit 2016.a1 [Build 3750602].
Title: Re: lattice_const_looping struck ....
Post by: Jin You Lu on September 7, 2016, 07:08
I am using the Latest official release: Version 2016.0 (June 21, 2016) (64bit Wins).
So where i can find 2016a1 version.
Thanks
Title: Re: lattice_const_looping struck ....
Post by: Ulrik G. Vej-Hansen on September 7, 2016, 09:20
2016.a1 is a pre-release version, so you should keep using 2016.0 until 2016.1 comes out.

I could not reproduce on Ubuntu 64-bit, so I will have to check if it appears on Windows for me. Could you try running it again? It is a very quick script.
Title: Re: lattice_const_looping struck ....
Post by: Jess Wellendorff on September 7, 2016, 10:06
This is a bug in ATK 2016.0 in Windows. Should be fixed in an upcoming version 2016.1. In the meantime, you can execute the script from terminal instead of using the Job Manager:
- in the Windows 2Start" manu, navigate to the "QuantumWise" folder, and click the "Command line terminal" icon. A terminal will open.
- in terminal, navigate to the folder with the script you want to execute (use "cd dirname" to change directory, and use "dir" to display the contents of a folder).
- execute the script by the command "atkpython.exe lattice_const_looping.py".

The calculations will run and the plot should show up.
Title: Re: lattice_const_looping struck ....
Post by: Anders Blom on September 7, 2016, 10:52
I don't think this is fixed in 2016.1, which now is available for download, so you need to use the command-line approach for a while still. Alternatively, and perhaps better, is to modify the plot statements in the script, so instead of popping up the plot, just save it to a file. To do this, change

pylab.show()

to

pylab.savefig("plot.png")