Comments (9)
I have a couple of thoughts having looked more closely at the lobster workflow:
- I wonder if the need for many more steps is because NBANDS is only set after the preconvergence job? If you could do the pre-convergence with the same higher NBANDS that might make things faster since it would have converged all necessary bands?
- Can you use a non-scf uniform input set for the
LobsterStaticMaker
? Obviously this won't work for hybrid calculations but that should allow you to go to very dense k-point meshes without much slowdown. If we did this, we should make the preconvergence step compulsory. In fact, an even better approach would be to replace both thepreconverge_static_maker
andlobster_static_maker
with a single makerlobster_uniform_maker
that is actually a flow maker. E.g., some variation ofUniformBandStructureMaker
but with symmetry disabled for the second job. - Can we switch to using
reciprocal_density
instead ofgrid_density
for theLobsterStaticMaker
?
from atomate2.
Strategy 2 seems to work now:
51 s with smaller number of reciprocal points (reciprocal_density: 100) and without symmetry (50s), uniform band structure computation with wavecar writing (reciprocal_density: 400, 150 s)
400 s with only one static computation (400 s, reciproal_density: 400)
I will now try to confirm that the Lobster outputs also still look fine based on this.
from atomate2.
- Yes, this is also my current assumption. I have to test it in detail for some cases once our cluster is back up. I hope it will lead to additional speed-up.
- I haven't performed Lobster computations in this way. This would also be something we need to check.
- Sure. I think it is much better
from atomate2.
I now changed NBANDS in the preconverge step:
For my test case Silicon on 144 cores:
- Without preconverge step, the static run takes 112.338 s
- Preconverge step: 9.674 s, 94.304 s. Copying the WAVECAR also takes a bit *of time so that the speed-up is still not large but exists at least. (btw, maybe linking could be an option as well)
- Preconvergence step (same number of kpoints as in static run): 17.306, static run: 85 s. This is again slightly faster.
I will now make a test for a larger but very symmetric structure.
SrTiO3:
preconv (same number of kpoints): 81.158 s, static: 220 s
static alone: 274 s
This is now slower. I would probably need to test more systematically...
Maybe, we should really go for the lobster_uniform_maker but this would take a longer time to implement. I naively thought that the number of iterations should be much lower when starting from a pre-converged wavefunction. I still get more than 10 in each of the cases.
from atomate2.
It looks very similar. Just VASP sets the band gap differently in VASP 6 and in this new maker ISPIN is set to 1 (i.e., plot 1 shows both spin channels but they are on top of each other, plot 2 shows the non-spinpolarized computation).
I also compared ICOHPLIST.lobster and again the agreement is very good.
from atomate2.
Nice! That looks promising.
By the way, I think if you upgrade to the latest VASP, they fixed the issue with setting the Fermi level so it goes back to how it used to be.
from atomate2.
That's great. I guess we will then compile a new version soon!
from atomate2.
I will now create new test data and fix the tests and also check if all folders in the output schema have been included.
from atomate2.
I will close it as the mentioned pull request has been merged.
from atomate2.
Related Issues (20)
- BUG: ElasticMaker deepcopy error HOT 4
- BUG: not able to read potcars correctly HOT 5
- Adding git tags HOT 3
- Path to next atomate2 release HOT 9
- Ensuring MP workflow compatibility when switching to Pymatgen for input sets
- `BadInputSetWarning` should not be raised for ISMEAR = 0 relaxations with metals if SIGMA is small
- How to cite? HOT 2
- New pymatgen breaks lobster and phonopy workflows HOT 5
- Design of a universal base DFT task document
- Advertising the atomate2 paper writing HOT 66
- Convergence check for relaxation with forcefields
- Dealing with large structures in the phonon workflow for forcefields HOT 5
- BUG: WAVECAR deletion HOT 8
- Discussion: sigma value in NSCF calculation
- BUG: custom CHGNET model in PhononFlow throws `jsanitize` error HOT 27
- BUG:ValueError: dictionary update sequence element #0 has length 1; 2 is required HOT 1
- FEATURE: GW workflow with VASP HOT 4
- BUG: pip install atomate2 does not automatically install phonopy and seekpath HOT 2
- Feature: add an additional step to the LOBSTER workflow to reduce run times
- Improve failed perturbations handling in elastic workflow HOT 1
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from atomate2.