-
Notifications
You must be signed in to change notification settings - Fork 13
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
Doubt regarding callable integer in Hamiltonian functions #202
Comments
Hi Mario, |
@Marioherreroglez agreed with Miles that if something is more of a question rather than an issue or feature request it should be posted on the support forum rather than on Github. As a short answer, this allows for users to pass either numbers as parameters, in which case they are treated as uniform couplings and fields, or as a function of the edges and vertices in the case of non-uniform couplings and fields. In the simplest case, if the couplings and fields are constants (the same on every site/vertex in the case of the fields or bond/edge in the case of the couplings), you can just pass numbers, and the conversion to a callable is just an internal detail that you don't have to worry about. |
This question was reposted and answered here: https://itensor.discourse.group/t/itensornetworks-callable-hamiltonian-parameters/2031. |
I am trying to understand why we need to make parameters for the Hamiltonians callable and hence depend on the graph. I want to define three-body terms (actual node, nearest neighbor node, and next nearest neighbor), should I make the parameters depend also on these (below)?
What would be the implications of skipping the callable part as shown below?
The text was updated successfully, but these errors were encountered: