Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Explain how the (useful!) _estimate_min_cpus was defined? #887

Closed
superstar54 opened this issue Oct 23, 2024 · 1 comment · Fixed by #972
Closed

Explain how the (useful!) _estimate_min_cpus was defined? #887

superstar54 opened this issue Oct 23, 2024 · 1 comment · Fixed by #972
Assignees

Comments

@superstar54
Copy link
Member

The warning message related to calculator too big suggests “>= 100 cpus) this suggestion originates from max(100,estimate_min_cpus). Can you explain how the (useful!) _estimate_min_cpus was defined? Can we have a notebook or python script with the data, to be able to further discuss and refine over time?
Image

@mikibonacci
Copy link
Member

mikibonacci commented Dec 15, 2024

I added more details in the _estimate_min_cpus method, but basically I used parameters on number of atoms, volume, cpus, scf_cycles and time for a moderate relax run of SiO2, and then I found the power laws of the following formula

num_cpus = num_cpus0 * (n/n0)^3 * (v/v0)^(3/2) * (scf_cycles * t0)/tmax

using other simulations on SiO2, Silicon and Gold to find the power laws. This is very rough, and actually I plan to find a new more accurate model for this. So, I will produce soon a repository with more data and useful analysis.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants