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 - Anders Blom

Pages: 1 2 3 [4] 5 6 ... 363
46
General Questions and Answers / Re: M3GNet energies
« on: March 19, 2024, 20:51 »
You are not telling it to print anything...
Add nlprint(total_energy) and you will see the energy printed

47
General Questions and Answers / Re: Zero bias transmission
« on: March 11, 2024, 19:57 »
No, all transport we compute is elastic by default. Otherwise you would have to introduce extra effects that take/give the energy the electron loses/gains in the process. This could be phonons, and QuantumATK can handle inelastic phonon scattering, see corresponding tutorials on that, like https://docs.quantumatk.com/tutorials/inelastic_current_in_si_pn_junction/inelastic_current_in_si_pn_junction.html.

48
Good question, happy that we get a chance to answer it here for the benefit of all users.

  • Start we a fresh empty workflow in the Workflow Builder
  • Insert a "Load from file" block from the Algorithms group and double-click the inserted block to open it
  • Click the button "Load from file" and select the file and object in the file that you want to read in
  • Close the "Load from file" widget
  • Now you can add any analysis you want to the script. Usually it's automatically connected to the loaded object, if not (some analysis takes multiple input configurations) you can connect them manually by clicking the little colorful icons on the right (next to the red warning badge that appears in these situations).

I didn't make screenshots as I hope it's clear already but let me know if you need more guidance.


49
The term "ballistic" is somewhat ambiguous. In our NEGF mode it's taken to mean the opposite of diffusive (as in "ballistic transport", below the mean free path, i.e. no energy relaxation from phonon scattering), since we include scattering of interfaces, defects, surface roughness, etc as created by any atom not in a perfectly periodic arrangement. In some other models i's defined it as "no scattering at all", which would only be possible in a perfect crystal, and thus is rather uninteresting in an atomistic picture, but makes sense in higher-level models when you only use the mobility or set transmission to 1 to model a ballistic conductor.

No matter the bias, the transmission spectrum is computed including the effects of all atoms present in the system.

50
This is confusing, as this error has nothing to do running a script (no matter what task, like TransmissionSpectrum), but rather is related to the GUI itself and how it stores the status of running jobs. Do you see the error in the script log file or does the GUI crash?

51
The easiest way to set up an electric field across a molecule would be add the metallic plates on either side of the molecule, sort of like how we did in this tutorial: https://docs.quantumatk.com/tutorials/opening_a_band_gap/opening_a_band_gap.html

Then molecular polarizability is the derivative of the dipole moment (see https://docs.quantumatk.com/manual/Types/ElectronDensity/ElectronDensity.html#usage-examples) as  function of the field strength.

52
A pristine material, i.e. a perfectly periodic crystal, has an infinite mean free path by definition. The only reason we speak of a MFP is because there is some kind of scattering source that breaks this periodicity, such as edge roughness, dopants, or indeed temperature. The closest to what you might be looking for (undoped, perfect 2D material) is probably then to introduce some randomness due to thermal vibrations, using the SpecialThermalDisplacement method (https://docs.quantumatk.com/manual/Types/SpecialThermalDisplacement/SpecialThermalDisplacement.html), and then proceed just like the tutorial (updated link: https://docs.quantumatk.com/tutorials/elastic_scattering_impurity_in_si_nanowire/elastic_scattering_impurity_in_si_nanowire.html)

53
PAW-GGA-LCAO should work fine, although there are some other details in PAW that might not work. You could also use the planewave calculator with PAW.

Yes, there is no predefined +1/2 parameters for Pr (or in fact a lot of exotic elements). I would probably recommend GGA+U for Pr, but either way you will need to fit the parameter.


54
Yes, this is expected for most semiempirical models, as they only contain parameters for the electronic structure, not forces and stress, and hence cannot be used for geometry optimization, MD, or phonons. The exception is DFTB, which typically works for all that.

55
Should work in newer versions, but not in older like 2021.

56
General Questions and Answers / Re: Query regarding GPU
« on: February 15, 2024, 21:28 »
So far we only support ForceField calculations on GPU, and only some of them.

We haven't formulated any specific requirements, but it only works with CUDA, so obviously it should be a Nvidia GPU.

Otherwise I think the usual considerations apply, balance performance vs. price and get a modern GPU, but probably no need for the absolutely newest model or highest spec.

57
Although the tutorial was actually inspired by this paper, the width of the ribbon is quite different. I think that is a major factor. We do use a fast Huckel model in the tutorial vs DFT in the paper, but if the band structure is similar, this should not play a significant role (not orders of magnitude).

58
Yes, but NPT will still work fine in the device configuration, since the constraints work to keep the device correct. The problem with NPT is just if you run the central region alone; I think one can still get it work right with the correct constraints but might require rigid body regions rather than fixed atoms, since fixed atoms (as I recall) means fractional coordinates are fixed, and if the volume changes, the interatomic distances do too. This is described a bit more in https://docs.quantumatk.com/tutorials/device_relaxation/device_relaxation.html#central-region-relaxation (look for the Rigid body constraint).

59
I'll be rather brief, maybe you have follow-up questions after that.

Yes, we always use periodic boundary conditions in MD, although you can of course have vacuum around a structure like a CNT etc; since the range of interatomic forces in classical potentials is usually quite short (electrostatic forces may have longer range) this effectively makes the system 1D.

For devices, however, since the electrodes and their repetitions (more correctly, the electrode extension) are indeed always fixed, it's sort of not periodic in Z, since the atoms cannot move there. Not sure what you observe about atoms leaving the cell, you'd have to show an example.

Cell size will change if you are using NPT, but I would use the device structure, because a small change in atoms doesn't make a difference, at least for forcefields. For DFT, you would have to think carefully about doing an MD simulation for such a large structure as a device. Keeping it as a device structure makes it much easier to do a DFT-NEGF calculation afterwards, without worrying about the cell size change or atoms in the electrode extensions moving.

Do not repeat in Z if it's a device, but otherwise yes, you usually need a relatively large supercell, else you are limiting the degrees of freedom the systems can explore.

60
General Questions and Answers / Re: Adaptive grid
« on: February 9, 2024, 21:32 »
Sounds like a good idea.

function_values cannot be used if you specify kA_range. As the manual states, this is to be used if restarting from an older created adaptive grid (same with kpoints, triangles, and intervals).

So for your first attempt, just stick to kA_range, tolerance and experiment with the refinement. Indeed, to much refinement might be slower than a (coarse) MP sampling, but will generally be more accurate. The manual is quite explicit on how the triangles are constructed, see https://docs.quantumatk.com/manual/Types/AdaptiveGrid/AdaptiveGrid.html

Pages: 1 2 3 [4] 5 6 ... 363