-
Notifications
You must be signed in to change notification settings - Fork 3
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
Ising cluster update code #22
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Несколько комментариев. Прдправляйте и в ту же ветку коммит.
Tried to run a simulation of a 4x4 lattice, and I cannot make sense of the results:
Could you please explain / update the PR @MoskalenkoRomanBorisovich ? |
W.r.t. reading the structure, what you have here is nice but what's really needed is an example of building a lattice out of it. Maybe a simpler, shorter conformation where you can follow the site numbering and neighbors. THis is best left for a separate PR though. |
L is the number of spins, for a 4 * 4 grid this is 16, not 4. This is a rudiment left from cy_ising.pyx, I will remove it in the next commit |
Please add a usage example. Ideally, add a comparison to exact enumeration for a 4x4 lattice. Enumeration might live in a Jupyter notebook or a python script or a cython code, whichever is simpler for you. |
Check out this pull request on See visual diffs & provide feedback on Jupyter Notebooks. Powered by ReviewNB |
Несколько комментариев по коду, исправляйте и push пжлст @MoskalenkoRomanBorisovich Дальше, точный пересчет произвольных решеток это зачетная попытка, но нужно убрать. Это плохой пример (экспоненциально малые значения в сумме; экспоненциально много членов в сумму). Нужно сделать проще пример, двумерную решетку 4-на-4, на питоне точный пересчет, прямо в ноутбуке. Как сделано для одномерия в https://github.com/ev-br/mc_lib/blob/master/examples/1DIsing.ipynb Как сделаете, @-отметьте меня пожалуйста. |
Также посмотрел в ноутбук. Хорошо, но доделываем:
|
Co-authored-by: Evgeni Burovski <evgeny.burovskiy@gmail.com>
Co-authored-by: Evgeni Burovski <evgeny.burovskiy@gmail.com>
@ev-br |
Okay, let's merge it. Thanks @MoskalenkoRomanBorisovich Follow-ups in gh-53. |
No description provided.