Dear Synge Todo Thanks for your kind answer!
After I ran the simulation the param.task*.out.xml files have different sizes: Is it normal to have these diversity of output? Can I choose any option to just have the first kind of files?
This depends on the number of 'runs' of each parameter set. You can specify '--Nmin=2' options to force multiple runs. It reduces the size of XML as a side-effect (but it approximately doubles the total amount of CPU time).
I'm not sure if I understood your answer... For example I noticed that the difference between the param.task88.out.xml and param.task89.out.xml files generated are related with the method to calculate the error bars: - param.task88.out.xml (2.3M) uses <MEAN method="jackknife"> - param.task.89.out.xml (20M) uses <MEAN method="simple">
I don't understand why this difference... the only difference between two different param.task*.in.xml files is the temperature value... Could it be related to running with mpi? With the way that the parallelization is implemented? Can I choose the method to be used to calculate the error bars?
Is there any way to select that I just want the correlation between two given spins?
Currently No. But it is rather easy to modify looper/correlation.h to measure correlation between two specific spins. I could help you if you inform me the detail of your lattice and spin pairs on which you want to measure the correlation.
It's a very simple thing, I have a open lattice with with 50 1/2- spins that interact with the isotropic Heisenberg Hamiltonean. The only special issue is that the interaction constant is not uniform in the lattice. I am measuring the correlation between the spins in the boundaries ("Spin Correlations" type="VECTOR_AVERAGE" index="( 0 ) -- ( 49 )") .
Thanks for your time and help
The best João Lopes