-
Notifications
You must be signed in to change notification settings - Fork 25
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
How should I use the standard mode to generate the following file for the expert mode?Just like the files you displayed #170
Comments
In standard mode, if the specified interactions are represented by standard interactions such as
In this case, the Kitaev interactions are represented by
You are right. The Hermitian conjugate pair is necessary in
You can specify both diagonal terms and off-diagonal terms in
You can represent all interaction in |
Please refer to the HPhi manual. The figure below is taken from Figure 4.2 in the manual. If my understanding of your requirements is correct, the specifications for the interactions with the input file provided by tmisawa-san will change as follows according to the figure above:
|
@shuailiu199966
This 24-site cluster consists of two 12-site loops and |
How can I generate the following file for expert mode using standard mode? I want to obtain the InterAll file for the model using standard mode. How should I proceed? I executed
HPhi -sdry stan.in
, but it did not produce an InterAll file.In your InterAll file, it is mentioned that to ensure the generated Hamiltonian is a Hermitian matrix, the input needs to include both
and its Hermitian conjugate
.
How should I implement this in the InterAll file? For example, if I first input "2 0 2 1 3 0 3 1 -0.25 -0.25 ", do I need to continue inputting "3 1 3 0 2 1 2 0 -0.25 0.25"
Does this operation need to be performed for all interaction terms, or only for off-diagonal terms? For example, should this be done for the x-bond and y-bond directions in the Kitaev model, but not for the interaction terms in the z-bond direction?
The text was updated successfully, but these errors were encountered: