Recent Posts

Pages: 1 2 [3] 4 5 ... 10
21
The concern I have with that is that whichever MD image you pick, it will have a lot of randomness to it. That is, picking 2 or 3 different images (spaced out decently in time, but in the steady-state phase) you might get quite different results. So it is probably necessary to sample several images, which not only gives you an average but also a variation, i.e. error bars.

The idea with the thermal displacement method is that it provides a single structure which is a statistical ensemble for a given temperature and thus eliminates the need for the averaging (that is, you can do just a single DFT calculation for the elastic constants). The "price" you pay is a more expensive calculation of the dynamical matrix, but with a forcefield it's not an issue anyway.

Whether or not these two methods give the same result would of course be interesting to compare! Formally they are supposed to...

Finally, keep in mind that the accuracy of the forcefield should perhaps be checked for the specific material. I doubt ZrC was specifically included when they derived the ReaxFF potenial... (In fact, the original paper is for SiC, and I think all those metal elements are just included as possible impurities.) This might be an example where no forcefield exists and you have to resort to DFT. Or, why not try the MACE or M3GNet neural network potential (included in W-2024.09) - that might actually work really well here! You can also fit a machine-learned forcefield (MTP) using QuantumATK - it should actually be relatively easy for ZrC if you "only" need phonons and not melted or amorphous structures.

Also, when using the displacement method you need to use a larger unit cell (and you also need that for the MD method). For anything involving finite temperature, you cannot operate on small unit cells; a simple way to understand that is that the phonon wavelengths are typically much larger than lattice constants (at least a few nanometers, typically).
22
General Questions and Answers / Re: Elastic Constants at higher Temperature
« Last post by Habib on November 21, 2024, 22:23 »
Hi Anders,

Thanks for the corrections, but still the results are not convincing, i am trying my best let see.

I have another idea regarding the simulation of elastic constants at different temperatures using a combination of DFT and MD simulations (maybe i am completely wrong). 
How about this approach: 
1. First, optimize the model using DFT. 
2. Then, use the DFT-optimized model for MD simulations at the desired temperature (e.g., heat up to 1500 K or any Temperature) with the NPT ensemble. 
3. Finally, take the last snapshot of the MD-simulated model (at the desired temperature) and calculate the elastic constants using DFT again, without further optimization. 
23
In your scripts, the elastic constants are computed using "bulk_configuration", but the thermally excited geometry is "new_configuration".
24
General Questions and Answers / Re: Elastic Constants at higher Temperature
« Last post by Habib on November 21, 2024, 12:44 »
Hi Anders,

I followed your method and calculated the Elastic Constants of ZrC at three different temperatures (0 K, 300 K, and 1500 K) using the provided forcefield in QuantumATK (ReaxFF_CHONSiPtZrYBaTi_2013). Since these are very fast calculations, I also computed the Dynamical Matrix for all of them. However, I got similar results for all of these three temperatures.


+------------------------------------------------------------------------------+
| Elastic Constants in GPa                                                     |
+------------------------------------------------------------------------------+
|   402.38     101.43     101.43       0.00       0.00       0.00              |
|              402.38     101.43       0.00       0.00       0.00              |
|                         402.38       0.00       0.00       0.00              |
|                                    192.39       0.00       0.00              |
|                                               192.39       0.00              |
|                                                          192.39              |
+------------------------------------------------------------------------------+

The scripts of these three cases are attached. Could you please review them and let me know where I am making mistakes?

Kind regards,
Habib
25
[16547.681714] quantumatk[113938]: segfault at 100000009 ip 000079a194d08280 sp 00007fff5bf16218 error 4 in libQt5Gui.so.5.15.12[79a1948e5000+466000] likely on CPU 91 (core 43, socket 1)
Hello!
I found the crash report of coredump
Is there any solution to this?
The QATK version I use is 2024.09 and the OS version is ubuntu24.04.
The coredump occurs when SCF has completed its convergence when calculating IVCharacteristics. When entering Calculating Transmission, it suddenly crashes. My MPI setting is 24 and the threads setting is 8. What causes the coredump?
My CPU is amd epyc7k62 x2 total is 96cores and
Ram is 512g
Thanks
26
General Questions and Answers / How to Initialize from a converged state
« Last post by dmicje12 on November 20, 2024, 13:43 »
Hi everyone!
Because coredump happens frequently on my server.
I confirm that my memory usage is sufficient (but I'm not sure if my ram is damaged)
I am calculating the IV of a 2-lead device. My plan is that I want my job to first converge to dE and dH 1e-2, then use this as the Initial state to calculate 1e-3, and finally converge to 1e- 4 or less, can this be done? If it can be done, how should it be done? If not, is there a similar method?
thank you
27
General Questions and Answers / Re: TorchX_MACE_MP_0_L0_2023
« Last post by Anders Blom on November 18, 2024, 23:11 »
Yes, it was added to W-2024.09
28
General Questions and Answers / Re: Band Structure
« Last post by Anders Blom on November 18, 2024, 23:11 »
Spin-polarized? If so, make sure to only extract one spin component at the time using bs.evaluate(spin=Spin.Up)
29
General Questions and Answers / Re: TorchX_MACE_MP_0_L0_2023
« Last post by AsifShah on November 17, 2024, 14:48 »
Hi,

I think its available in latest 2024 package
30
General Questions and Answers / TorchX_MACE_MP_0_L0_2023
« Last post by nimamat on November 16, 2024, 10:44 »
Hello,

How can we use mace potentials (TorchX_MACE_MP_0_L0_2023)?
Everything can be loaded on this page (https://docs.quantumatk.com/manual/ForceField.html#pretrained-moment-tensor-potential-mtp-parameter-sets) except TorchX_MACE_MP* and it shows the error "NameError: name 'TorchX_MACE_MP_0_L0_2023' is not defined" in QuantumATk 2023.

Thanks in advance.
Pages: 1 2 [3] 4 5 ... 10