Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Messages - Julian Schneider

Pages: 1 2 [3] 4 5 ... 11
31
You can switch off the Si-Si interaction in  the Tersoff potential, but I would not recommend it, because, since the Tersoff potential is a manybody potential, it is not really made for disentangling the two and three body parts, meaning that removing the Si-Si interactions might have unpredictable consequences on the Si-O interactions.
Instead I would suggest to use the Tersoff Si-O potential for the entire system, as the Si-Si interaction in that potential are very similar to the original Tersoff potential for Silicon (Tersoff_Si_1988), with only slight modifications to few parameters (see the paper http://www.sciencedirect.com/science/article/pii/S0927025606002023).
You could test the potential for a silicon system alone to see if it reproduces the desired properties for silicon sufficiently well.

If you really want to use the SW potential for Si-Si, you have to follow the genral procedure to modify potentials, as outlined in the tutorial above, in your case you specifically have to remove the TersoffSingleTypePotential for Si and instead of the TersoffMixitPotential for Si-O you have to use the TersoffTriplePotential and specifiy all Si-O pair parameters manually using the combination rules given in the paper.
See also https://docs.quantumwise.com/manuals/Types/TersoffTriplePotential/TersoffTriplePotential.html#tersofftriplepotential-c  for more details.
Finally, the SW potential classes need to be added to the potential set.

32
General Questions and Answers / Re: Questions about potentials
« on: September 18, 2017, 14:54 »
Quote
i) If there are possible to obtain the phonon dispersion using reaxFF, please let me know.
In principle there should be no problem calculating the Phonon dispersion with ReaxFF, but phonons are probably not the primary type of property that ReaxFF potentials are fitted to.
Moreover, many ReaxFF potentials only give good results for the context they are parameterized for.  E.g. a potential that is parameterized primarily for SP3 Carbon atoms, might not give good results when applied to graphene. You should check the publication for that potential to find out if its the purpose it has been designed for, matches your application.

Quote
ii) Is it possible to use airebo potential? Actually, I know the parameter about the airebo potential.
Unfortunately Airebo potentials are currently not implemented in ATK. I'll check if there is a workaround, but I don't think so.

Quote
iii) If possible, I want you to recommend some potentials that can support C-O bonding.
I'll check if I can find a suitable potential.

33
If you are talking about an interface system that looks like copper-substrate / graphene layer / copper substrate (i.e. something like in https://journals.aps.org/prb/abstract/10.1103/PhysRevB.88.045444) or copper substrate / bulk-like graphene layers then yes we can simulate it.
Just one copper substrate and a single layer of graphene on top, bounded by vacuum, would probably be difficult, it depends how one would define thermal conductance in a meaningful way for that case.

To calculate the intrefacial thermal conductance via MD (as in the tutorial) one would probably have to use a classical potential (e.g. EAM for copper and Tersoff for graphene) and couple the interactions between copper and graphene via Lennard Jones-potentials (as in the paper mentioned above).

Phonon transmission via NEMD would also be possible, here one could even try using DFT.

We don't have a tutorial on that particular case interface but the main challenge here is primarily setting up the classical potentials, the rest should be more or less analogue to the tutorial and the paper mentioned above.

34
The elastic constants analysis object is primarily suited for bulk materials, not for 2D- or 1D-systems, so the script should be more correct.

35
The Lennard-Jones potential is probably not a suitable potential to model bonding between atoms, as it is a non-bonded potential which only accounts for dispersion interactions (plus a repulsive part).
The best potential and parameters depends on what you want to simulate.
If you already know that the atoms will bond and how they will bond and you want to maintain the bonding in an MD simulation, a Morse-potential (http://docs.quantumwise.com/manuals/Types/MorsePotential/MorsePotential.html#morsepotential-) might be a better choice than LJ to keep the bonds stable.
If you don't know if and how the atoms are bonding then it is more difficult to select a  suitable potential. In this case it might make more sense to run a DFT calculation (at least on a small part of the system that contains your C-Pt-O2 group) to understand how that part behaves.

36
Future Releases / Re: Combining potentials of classical
« on: July 24, 2017, 16:34 »
You cannot select particle types when you set up a ReaxFF potential (see http://docs.quantumwise.com/manuals/Types/ReaxFFPotential/ReaxFFPotential.html#reaxffpotential-c). It automatically acts on all particles in the system, meaning that the reax parameter file must contain parameters for at least all elements in the configuration.
If you wanted the potential not to act on some of the elements, you would have to add these as dummy elements with zero interaction to the reax parameter file.

Once you have set up a ReaxFF potential for your entire system, you can add (almost) any other potential on top of the ReaxFF potential to extend the potential if necessary.

37
Future Releases / Re: Combining potentials of classical
« on: July 22, 2017, 12:09 »
In principle you can combine all potentials, not only Lennard Jones and Tersoff.
There are some limitations for EAM and ReaxFF, which means that a ReaxFF or EAM potential cannot be used for only a part of the configuration, but they must be defined for all atoms in the system (for EAM one can make a workaround, if necessary).
Still, other potentials, such as Lennard Jones, can be added to a ReaxFF or EAM potential, as well.

38
With these settings you should in principle be able to import your trajectory in the labfloor in VNL.
VNL looks for the log file that has been generated by lammps,  make sure that this file ends with ".lammps", otherwise VNL will not detect it as lammps file. Rename the file if it has a different extension.
From this log file, VNL will read the name of the lammps trajectory file and import the trajectory.
The trajectory should show up under the name "xxx" if "xxx.lammps" is the name of the lammps log file.
You can treat it as a normal VNL MD-Trajectory. i.e. open it in the Viewer / MovieTool / MD-Analyzer, etc.
 If you want to send a snapshot of the trajectory to the Script Generator, open the lammps trajectory with the MovieTool, play the movie until you have reached the desired snapshot, and then use the blue "Send To" arrow in the lower right-hand corner to send the configuration to the ScriptGenerator.
If you haven't done so already, you should read the tutorial http://docs.quantumwise.com/tutorials/lammps_trajectories/lammps_trajectories.html, everything should be explained there.

39
General Questions and Answers / Re: Stress Error
« on: July 12, 2017, 13:58 »
If you use the ScriptGenerator:
You will only do a stress optimization if you uncheck the "Constrain Lattice Vectors" box, no matter what stress error tolerance value you give.

If you set up the calculation in a script:
Whether you do a stress optimization or not, depends on if you set the parameter
Code
disable_stress
to True (no stress optimization) or False (so a stress optimization).
If you don't set this keyword, the default is False, that means by default you do a stress optimization (see http://docs.quantumwise.com/manuals/Types/OptimizeGeometry/OptimizeGeometry.html#optimizegeometry-f).
That also means you will perform a stress optimization, even if you don't explicitly give the stress error tolerance (i.e. via the
Code
max_stress
keyword). In that case the default stress tolerance of 0.1*GPa will be used.
Same with the
Code
target_stress
, here the default is 0.0*GPa, unless you specify something else.

40
General Questions and Answers / Re: Stress Error
« on: July 10, 2017, 12:49 »
The stress error tells you by how much the current stress deviates from the given target stress. The stress error must be below the given stress tolerance to consider the stress optimization converged.

41
I would guess the problem comes from the fact that the Tersoff-potential only describes the local bonded interactions within the graphene-layers, but does not account for the longer-ranged dispersion interactions between adjacent layers. This is  a known short-coming of Tersoff- and similar potentials. If there is no interactions between adjacent layers, then phonons cannot be transmitted across different layers.
This is typically corrected by adding a Lennard-Jones potential between Carbon-atoms, that accounts for the dispersion interactions, as e.g. in http://dx.doi.org/10.1103/PhysRevB.88.045444 .

42
General Questions and Answers / Re: About trajectory files
« on: May 17, 2017, 09:29 »
Hi,

This is a known shortcoming for nc trajectories with a small interval.
Most of these issues will be solved in the upcoming ATK-2017 version, where we use the HDF5 format to save MD trajectories. There will also be an option to disable storing velocities, forces, and stress to make the file size smaller.
For ATK-2016 the workaround to make it at least somewhat faster for such cases is that you switch off  "Save trajectory" (or set
Code
trajectory_filename=None
in the script in the MolecularDynamics function), and instead make sure that you check "Save" in the Molecular Dynamics widget (or add a line 
Code
nlsave('trajectory.nc', md_trajectory)
after the MolecularDynamics block in the script).
Then the trajectory is not saved on-the-fly during the simulation, but as a whole after the simulation has completed, which should be faster.

43
If you select only M, then the voidsize calculation is performed only on the M atoms in the system, i.e. all other atoms are ignored.

44
The voidsizes are a measure for how evenly the atoms in a material are distributed. This is primarily of interest for amorphous materials, as the atoms are arranged in an irregular manner.
What you measure is essentially the volume of the void space between the atoms.
This volume is calculated by first creating a Delauney traingulation (https://en.wikipedia.org/wiki/Delaunay_triangulation) of the atoms in the system, and then calculating the tetrahedral volume for each simplex. The size of a void is then calculated as the diameter (in Angstrom) of a sphere with equivalent volume.
The Voidsize Distribution analysis gives the distribution of these sizes in the system.
The Element selection lets you select only a subset of elements for whcih the voidsaize should be calculated, but the most common case would be that would calculate the voidsize for all elements in the system.
The Resolution selection lets you choose the bin size that is used when calculating the histogram of the void sizes.

45
Anharmonic effects are not included in phonon transmission calculated via non-equilibrium Green's functions. Everything is purely harmonic. Therefore NEGF is primarily suited for interfacial thermal conductance (where scattering at the interface is the main contribution to thermal resistance) and not so much for bulk conductivity (where inelastic phonon-phonon-scattering is the main contribution to resistance).

Non-equilibrium MD, on the other hand fully includes anharmonic effects and can therefore be used to calculate both interface conductance and bulk conductivity.
So what you observe makes perfect sense.

Have a look at our recent webinar on thermal transport simulations http://docs.quantumwise.com/webinars/webinars.html

Pages: 1 2 [3] 4 5 ... 11