-
Notifications
You must be signed in to change notification settings - Fork 15
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
Spin susceptibility in Sr2RuO4 and RPA tutorial broken #42
Comments
Actually the calc_sc_DMFT code works well for me with the unstable branch. |
Dear Andrew and Olivier, Thank you both for reporting the issues. To help me backtrace the issues could you please help me reproduce them? What versions of triqs+tprf+cthyb+w2dynamics_interface are you using and what version of the tutorial? Please note that the default documentation points to the latest release (not unstable). If you want to get the tutorial files from a given version, I'd recommend to pick up the files from the repo rather than downloading from the web, see e.g. https://github.com/TRIQS/tprf/tree/3.2.x/doc/user_guide/dmft_susceptibility_dbse Cheers, Hugo |
Hugo, Thanks for the quick response. I am using v3.2.0 for TRIQS, TPRF, CTHYB, and Version 1.1.3, July 2022 for w2dynamics. I indeed pulled from the website. With Olivier's suggestion, the unstable branch does seem to work. By the way, on the topic of the path, the X,M points are also flipped in the RPA tutorial |
@HugoStrand Is there a plan to update the tutorials at some point? In the unstable branch, the
|
I am not sure the last time the tutorials have been updated. Currently trying to run
calc_sc_dmft
and theParameterCollection()
is missingt
,n_iter
, andB
as attributes.I can add them, but the CTHYB solver also needs the Green's function structure to be defined. The density of bugs makes me wonder if there is a newer version that is just missing from the website or the tutorial has just not been touched in a while. I can make a pull request with everything fixed, but wanted to check if there was a correct version first.
The text was updated successfully, but these errors were encountered: