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

miniqmc input that's representative of QMCPack #169

Open
jeacook opened this issue Jul 31, 2018 · 4 comments
Open

miniqmc input that's representative of QMCPack #169

jeacook opened this issue Jul 31, 2018 · 4 comments

Comments

@jeacook
Copy link

jeacook commented Jul 31, 2018

I'm trying to quantitatively show (hardware level) that miniqmc is actually representative of QMCPack. We're using the CORAL2 NiO input, but not sure how to configure miniqmc to match that. Is this possible, and if so, which -g size really matches the CORAL2 NiO input?

@ye-luo
Copy link
Collaborator

ye-luo commented Jul 31, 2018

Based on the size chart
-g "2 2 2" corresponds to the CORAL2 size.

@ye-luo
Copy link
Collaborator

ye-luo commented Jul 31, 2018

miniQMC captures the most computationally intensive pieces of QMCPACK but per piece percentage may differ significantly.

@markdewing
Copy link
Collaborator

There has been some information about miniQMC-QMCPACK performance added on the wiki page https://github.com/QMCPACK/miniqmc/wiki/Comparing-performance-with-QMCPACK

@prckent
Copy link
Contributor

prckent commented Sep 27, 2018

Besides the system size, setting the acceptance ratio is critical: to emulate DMC a ratio around 0.999 is needed. DMC nearly always accepts a move. Miniqmc's default currently emulates a typical VMC run.

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

No branches or pull requests

4 participants