- Comp-phys-alps-users - lists.phys.ethz.ch

TIME in looper headers causes ALPS compile to crash
by Wolfram Brenig 20 Apr '11

20 Apr '11

Hi, compiling ALPS on SuSE 11.4 crashes with errors as listed at the end of this mail. [gcc version 4.5.1 20101208 [gcc-4_5-branch revision 167585] (SUSE Linux), kernel 2.6.37.1-1.2-desktop] The err msgs seem to point to the 'TIME' typename in a bunch of header files in alps_whatever/applications/qmc/looper/looper, namely in correlation.h susceptibility.h measurement.h custom.h operator.h stiffness.h Indeed, simply changing 'TIME' in these headers into something else, say 'MyTIME', does away with the compile error. However if this fix will induce other errors at run-time, I don't know? Does anybody have a clue on this? Wolfram Brenig PS.: Actually, there seems to be a somehow similar issue with VTK, over which I stumbled while compiling it prior to vistrails, and which seems to have bugged also others: http://comments.gmane.org/gmane.comp.lib.vtk.user/55300 compile errs:-------------------------------------------- [ 49%] Building CXX object applications/qmc/looper/CMakeFiles/loop.dir/loop_custom.C.o cd /home/userxx/temporary/alpsbuilt/applications/qmc/looper && /usr/bin/c++ -O3 -march=core2 -DNDEBUG -I/usr/local/include -I/usr/lib64/python2.7/site-packages/numpy/core/include -I/usr/include/python2.7 -I/home/userxx/temporary/alpsbuilt/src -I/home/userxx/temporary/alps/src -I/home/userxx/temporary/alps/applications/qmc/looper -o CMakeFiles/loop.dir/loop_custom.C.o -c /home/userxx/temporary/alps/applications/qmc/looper/loop_custom.C In file included from /home/userxx/temporary/alps/applications/qmc/looper/looper/correlation.h:29:0, from /home/userxx/temporary/alps/applications/qmc/looper/loop_config.h:38, from /home/userxx/temporary/alps/applications/qmc/looper/loop_custom.C:26: /home/userxx/temporary/alps/applications/qmc/looper/looper/measurement.h:182:72: error: expected nested-name-specifier before string constant /home/userxx/temporary/alps/applications/qmc/looper/looper/measurement.h:182:72: error: expected ‘>’ before string constant /home/userxx/temporary/alps/applications/qmc/looper/looper/measurement.h:418:48: error: expected nested-name-specifier before string constant /home/userxx/temporary/alps/applications/qmc/looper/looper/measurement.h:418:48: error: expected ‘>’ before string constant /home/userxx/temporary/alps/applications/qmc/looper/looper/measurement.h:422:13: error: expected unqualified-id before string constant /home/userxx/temporary/alps/applications/qmc/looper/looper/measurement.h:483:48: error: expected nested-name-specifier before string constant /home/userxx/temporary/alps/applications/qmc/looper/looper/measurement.h:483:48: error: expected ‘>’ before string constant /home/userxx/temporary/alps/applications/qmc/looper/looper/measurement.h:490:13: error: expected unqualified-id before string constant /home/userxx/temporary/alps/applications/qmc/looper/looper/measurement.h:491:49: error: type/value mismatch at argument 3 in template parameter list for ‘template<class MEASUREMENT1, class MEASUREMENT2> template<class MC, class LAT, int <anonymous> > struct looper::composite_measurement<M1, M2>::estimator’ /home/userxx/temporary/alps/applications/qmc/looper/looper/measurement.h:491:49: error: expected a constant of type ‘int’, got ‘time_t’ In file included from /home/userxx/temporary/alps/applications/qmc/looper/loop_config.h:38:0, from /home/userxx/temporary/alps/applications/qmc/looper/loop_custom.C:26: /home/userxx/temporary/alps/applications/qmc/looper/looper/correlation.h:37:48: error: expected nested-name-specifier before string constant /home/userxx/temporary/alps/applications/qmc/looper/looper/correlation.h:37:48: error: expected ‘>’ before string constant /home/userxx/temporary/alps/applications/qmc/looper/looper/correlation.h:41:13: error: expected unqualified-id before string constant /home/userxx/temporary/alps/applications/qmc/looper/looper/correlation.h:136:60: error: ‘"16:54:59"’ is not a valid template argument for type ‘int’ because string literals can never be used in this context /home/userxx/temporary/alps/applications/qmc/looper/looper/correlation.h:136:61: error: ‘<declaration error>’ is not a template /home/userxx/temporary/alps/applications/qmc/looper/looper/correlation.h:139:60: error: ‘"16:54:59"’ is not a valid template argument for type ‘int’ because string literals can never be used in this context /home/userxx/temporary/alps/applications/qmc/looper/looper/correlation.h:139:61: error: ‘<declaration error>’ is not a template In file included from /home/userxx/temporary/alps/applications/qmc/looper/loop_config.h:39:0, from /home/userxx/temporary/alps/applications/qmc/looper/loop_custom.C:26: /home/userxx/temporary/alps/applications/qmc/looper/looper/custom.h:63:48: error: expected nested-name-specifier before string constant /home/userxx/temporary/alps/applications/qmc/looper/looper/custom.h:63:48: error: expected ‘>’ before string constant /home/userxx/temporary/alps/applications/qmc/looper/looper/custom.h:127:60: error: ‘"16:54:59"’ is not a valid template argument for type ‘int’ because string literals can never be used in this context /home/userxx/temporary/alps/applications/qmc/looper/looper/custom.h:127:61: error: ‘<declaration error>’ is not a template /home/userxx/temporary/alps/applications/qmc/looper/looper/custom.h:130:60: error: ‘"16:54:59"’ is not a valid template argument for type ‘int’ because string literals can never be used in this context /home/userxx/temporary/alps/applications/qmc/looper/looper/custom.h:130:61: error: ‘<declaration error>’ is not a template In file included from /home/userxx/temporary/alps/applications/qmc/looper/loop_config.h:40:0, from /home/userxx/temporary/alps/applications/qmc/looper/loop_custom.C:26: /home/userxx/temporary/alps/applications/qmc/looper/looper/stiffness.h:40:48: error: expected nested-name-specifier before string constant /home/userxx/temporary/alps/applications/qmc/looper/looper/stiffness.h:40:48: error: expected ‘>’ before string constant /home/userxx/temporary/alps/applications/qmc/looper/looper/stiffness.h:45:13: error: expected unqualified-id before string constant /home/userxx/temporary/alps/applications/qmc/looper/looper/stiffness.h:46:49: error: type/value mismatch at argument 3 in template parameter list for ‘template<unsigned int MAX_DIM> template<class MC, class LAT, int <anonymous> > struct looper::stiffness<MAX_DIM>::estimator’ /home/userxx/temporary/alps/applications/qmc/looper/looper/stiffness.h:46:49: error: expected a constant of type ‘int’, got ‘time_t’ /home/userxx/temporary/alps/applications/qmc/looper/looper/stiffness.h: In member function ‘void looper::stiffness<MAX_DIM>::estimator<MC, LAT, <anonymous> >::estimate::begin_bs(const looper::stiffness::estimator::estimator_t&, const lattice_t&, double, int, int, int)’: /home/userxx/temporary/alps/applications/qmc/looper/looper/stiffness.h:98:15: error: request for member ‘bond_vector_relative’ in ‘emt’, which is of non-class type ‘const looper::stiffness::estimator::estimator_t’ /home/userxx/temporary/alps/applications/qmc/looper/looper/stiffness.h:98:40: error: request for member ‘real_bond’ in ‘emt’, which is of non-class type ‘const looper::stiffness::estimator::estimator_t’ /home/userxx/temporary/alps/applications/qmc/looper/looper/stiffness.h:99:33: error: request for member ‘dim’ in ‘emt’, which is of non-class type ‘const looper::stiffness::estimator::estimator_t’ /home/userxx/temporary/alps/applications/qmc/looper/looper/stiffness.h: In member function ‘void looper::stiffness<MAX_DIM>::estimator<MC, LAT, <anonymous> >::estimate::end_bs(const looper::stiffness::estimator::estimator_t&, const lattice_t&, double, int, int, int)’: /home/userxx/temporary/alps/applications/qmc/looper/looper/stiffness.h:105:15: error: request for member ‘bond_vector_relative’ in ‘emt’, which is of non-class type ‘const looper::stiffness::estimator::estimator_t’ /home/userxx/temporary/alps/applications/qmc/looper/looper/stiffness.h:105:40: error: request for member ‘real_bond’ in ‘emt’, which is of non-class type ‘const looper::stiffness::estimator::estimator_t’ /home/userxx/temporary/alps/applications/qmc/looper/looper/stiffness.h:106:33: error: request for member ‘dim’ in ‘emt’, which is of non-class type ‘const looper::stiffness::estimator::estimator_t’ In file included from /home/userxx/temporary/alps/applications/qmc/looper/loop_config.h:41:0, from /home/userxx/temporary/alps/applications/qmc/looper/loop_custom.C:26: /home/userxx/temporary/alps/applications/qmc/looper/looper/susceptibility.h: At global scope: /home/userxx/temporary/alps/applications/qmc/looper/looper/susceptibility.h:37:48: error: expected nested-name-specifier before string constant /home/userxx/temporary/alps/applications/qmc/looper/looper/susceptibility.h:37:48: error: expected ‘>’ before string constant /home/userxx/temporary/alps/applications/qmc/looper/looper/susceptibility.h:41:13: error: expected unqualified-id before string constant /home/userxx/temporary/alps/applications/qmc/looper/looper/susceptibility.h:42:49: error: type/value mismatch at argument 3 in template parameter list for ‘template<class MC, class LAT, int <anonymous> > struct looper::susceptibility::estimator’ /home/userxx/temporary/alps/applications/qmc/looper/looper/susceptibility.h:42:49: error: expected a constant of type ‘int’, got ‘time_t’ /home/userxx/temporary/alps/applications/qmc/looper/looper/susceptibility.h: In member function ‘void looper::susceptibility::estimator<MC, LAT, <anonymous> >::estimate::end_s(const looper::susceptibility::estimator::estimator_t&, const lattice_t&, double, int, int)’: /home/userxx/temporary/alps/applications/qmc/looper/looper/susceptibility.h:128:25: error: request for member ‘gauge’ in ‘emt’, which is of non-class type ‘const looper::susceptibility::estimator::estimator_t’ /home/userxx/temporary/alps/applications/qmc/looper/looper/susceptibility.h: In member function ‘void looper::susceptibility::estimator<MC, LAT, <anonymous> >::estimate::start_bottom(const looper::susceptibility::estimator::estimator_t&, const lattice_t&, double, int, int)’: /home/userxx/temporary/alps/applications/qmc/looper/looper/susceptibility.h:140:25: error: request for member ‘gauge’ in ‘emt’, which is of non-class type ‘const looper::susceptibility::estimator::estimator_t’ make[2]: *** [applications/qmc/looper/CMakeFiles/loop.dir/loop_custom.C.o] Error 1 make[2]: Leaving directory `/home/userxx/temporary/alpsbuilt' make[1]: *** [applications/qmc/looper/CMakeFiles/loop.dir/all] Error 2 make[1]: Leaving directory `/home/userxx/temporary/alpsbuilt' make: *** [all] Error 2

3 5

Dzyaloshinsky-Moriya interaction
by kaveh edalat 19 Apr '11

19 Apr '11

Dear All It is possible to add Dzyaloshinsky- Moriya (DM) interaction to Heisenberg model to do classical Monte Carlo (in 3D lattice)? Best regards Kaveh

1 0

Re: [ALPS-users] about printgraph
by 孙照宇 16 Apr '11

16 Apr '11

Dear Rui: As I know, a .xml file would be the output file, rather than the input file, of the command "printgraph". Suppose you have the following parameter file (such as "parm1a" in ED-01): ---------------------------------------------- MODEL="spin" LATTICE="chain lattice" CONSERVED_QUANTUMNUMBERS="Sz" MEASURE_STRUCTURE_FACTOR[Structure Factor Sz]=Sz MEASURE_CORRELATIONS[Diagonal spin correlations]=Sz MEASURE_CORRELATIONS[Offdiagonal spin correlations]="Splus:Sminus" local_S=1 J=1 {L=4;} ---------------------------------------------- If you want to check its grapha, you first need to edit the above file into the following form： ---------------------TOBECHECKED------------------------- MODEL="spin" LATTICE="chain lattice" L=4 ---------------------------------------------------------------------- which is saved as a file "_tobechecked_". Then you can run the following command: printgraph _tobechecked_ And you would get a .xml file describing the grapha of the model. At present my computer is not at hand, thus I answer the question just with the help of my memory. And I hope I have not missed any important points. Good Luck sunzhaoyu2000(a)gmail.com 2011/4/15 <comp-phys-alps-users-request(a)lists.phys.ethz.ch>: > Send Comp-phys-alps-users mailing list submissions to > comp-phys-alps-users(a)lists.phys.ethz.ch > > To subscribe or unsubscribe via the World Wide Web, visit > https://lists.phys.ethz.ch/listinfo/comp-phys-alps-users > or, via email, send a message with subject or body 'help' to > comp-phys-alps-users-request(a)lists.phys.ethz.ch > > You can reach the person managing the list at > comp-phys-alps-users-owner(a)lists.phys.ethz.ch > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of Comp-phys-alps-users digest..." > > > Today's Topics: > > 1. problems with "printgraph" or "lattice viewer" or "lattice > previewer" (zheng rui) > 2. boost_filesystem causes exception (Andreas Herrmann) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Thu, 14 Apr 2011 12:56:10 +0800 > From: zheng rui <rzhengphy(a)gmail.com> > Subject: [ALPS-users] problems with "printgraph" or "lattice viewer" > or "lattice previewer" > To: comp-phys-alps-users(a)lists.phys.ethz.ch > Message-ID: <BANLkTi=FTE4RZKNq0KL1wpL_uPh4SBtUKQ(a)mail.gmail.com> > Content-Type: text/plain; charset="iso-8859-1" > > Dear professors: > > Yesterday i tried many ways to print out the lattice graph from the xml > file, but still i cant make it. I install alps from synaptic of Ubuntu > Marverick 10.10. In the tutorials, it says "printgraph parameter_file" will > generate the graphy, so i made a xml file "temp.xml" like this: > > <LATTICES> > > <LATTICE name="square" dimension="2"> > <BASIS> > <VECTOR> 1 0 </VECTOR> > <VECTOR> 0 1 </VECTOR> > </BASIS> > </LATTICE> > > <FINITELATTICE name="rectangular periodic" dimension="2"> > <LATTICE ref="square"/> > <EXTENT dimension="1" size="5"/> > <EXTENT dimension="2" size="6"/> > <BOUNDARY type="periodic"/> > </FINITELATTICE> > > <UNITCELL name="complex example" dimension="2" vertices="2"> > <VERTEX id="1" type="0"><COORDINATE> 0.3 0.7 </COORDINATE></VERTEX> > <VERTEX id="2" type="1"><COORDINATE> 0.6 0.3 </COORDINATE></VERTEX> > <EDGE><SOURCE vertex="1"/><TARGET vertex="1" offset="1 0"/></EDGE> > <EDGE><SOURCE vertex="1"/><TARGET vertex="1" offset="0 1"/></EDGE> > <EDGE><SOURCE vertex="1"/><TARGET vertex="2"/></EDGE> > </UNITCELL> > > <LATTICEGRAPH> > <FINITELATTICE ref="rectangular periodic"/> > <UNITCELL ref="complex example"/> > </LATTICEGRAPH> > > </LATTICES> > > then i type "printgraph temp.xml", and it returns error: Caught exception: > parameter parse error at "<LATTICES> <LATTICE name="squa" > i also tried the parm1.in.xml and parm1.task.in.xml but got the same error > msg, i dont know how to make printgraph work normally, can anyone show me an > example? > > In this posting: > > https://lists.phys.ethz.ch/pipermail/comp-phys-alps-users/2009/000676.html > > someone had already asked exactly the same question, and i have installed > all the stuff as Synge Todo said, and it did show a 3 dimensional cone after > i type "wxVTKRenderWindowInteractorConeExample()" but after this i still > dont know how to move on. In the pdf > > http://alps.comp-phys.org/mediawiki/images/c/cb/Alps-gui.pdf > > Synge Todo had showed a simple gui of making lattice and parameters, i dont > know how to get the gui like that, i found the "preview.py. > lattice-preview.in, printgraph.c" files in the > "alps-2.0.0-r5363-src-with-boost/alps/tool/" documentary after i unzip the > alps-2.0.0-r5363-src-with-boost.tar.gz<http://alps.comp-phys.org/static/software/releases/alps-2.0.0-r5363-src-wit…>, > so i think there must be ways to print the lattice graph, i tried to > compile the "preview.py", but it says "no module named config", so i > download a config softpackage from this website: > > http://www.red-dove.com/config-doc/ > > and install the package so i could import config module in python, then i > try to compile preview.py again, it says config module has no attribute > version, i guess the config module in alps should be connected with the file > "config.py.in" in the tool documentary, but not the config softpackage i > download, but i dont know how to use the "config.py.in" file, so i get > stucked again. > > In another posting: > > https://lists.phys.ethz.ch/pipermail/comp-phys-alps-users/2007/000106.html > > someone also asked a similar question, and Matthias suggested " To visualize > it please use the lattice viewer that i send in a separate mail and > copy&paste above text into it ", so i wonder whether the lattice previewer > tool is only for private use, but those postings were years ago, i m > confused. > > Hope someone could tell me how to print out the lattice graph when i want to > make my own lattice. > > > Thanks and Best Wishes! > > Rui >

1 0

problems with "printgraph" or "lattice viewer" or "lattice previewer"
by zheng rui 14 Apr '11

14 Apr '11

Dear professors: Yesterday i tried many ways to print out the lattice graph from the xml file, but still i cant make it. I install alps from synaptic of Ubuntu Marverick 10.10. In the tutorials, it says "printgraph parameter_file" will generate the graphy, so i made a xml file "temp.xml" like this: <LATTICES> <LATTICE name="square" dimension="2"> <BASIS> <VECTOR> 1 0 </VECTOR> <VECTOR> 0 1 </VECTOR> </BASIS> </LATTICE> <FINITELATTICE name="rectangular periodic" dimension="2"> <LATTICE ref="square"/> <EXTENT dimension="1" size="5"/> <EXTENT dimension="2" size="6"/> <BOUNDARY type="periodic"/> </FINITELATTICE> <UNITCELL name="complex example" dimension="2" vertices="2"> <VERTEX id="1" type="0"><COORDINATE> 0.3 0.7 </COORDINATE></VERTEX> <VERTEX id="2" type="1"><COORDINATE> 0.6 0.3 </COORDINATE></VERTEX> <EDGE><SOURCE vertex="1"/><TARGET vertex="1" offset="1 0"/></EDGE> <EDGE><SOURCE vertex="1"/><TARGET vertex="1" offset="0 1"/></EDGE> <EDGE><SOURCE vertex="1"/><TARGET vertex="2"/></EDGE> </UNITCELL> <LATTICEGRAPH> <FINITELATTICE ref="rectangular periodic"/> <UNITCELL ref="complex example"/> </LATTICEGRAPH> </LATTICES> then i type "printgraph temp.xml", and it returns error: Caught exception: parameter parse error at "<LATTICES> <LATTICE name="squa" i also tried the parm1.in.xml and parm1.task.in.xml but got the same error msg, i dont know how to make printgraph work normally, can anyone show me an example? In this posting: https://lists.phys.ethz.ch/pipermail/comp-phys-alps-users/2009/000676.html someone had already asked exactly the same question, and i have installed all the stuff as Synge Todo said, and it did show a 3 dimensional cone after i type "wxVTKRenderWindowInteractorConeExample()" but after this i still dont know how to move on. In the pdf http://alps.comp-phys.org/mediawiki/images/c/cb/Alps-gui.pdf Synge Todo had showed a simple gui of making lattice and parameters, i dont know how to get the gui like that, i found the "preview.py. lattice-preview.in, printgraph.c" files in the "alps-2.0.0-r5363-src-with-boost/alps/tool/" documentary after i unzip the alps-2.0.0-r5363-src-with-boost.tar.gz<http://alps.comp-phys.org/static/software/releases/alps-2.0.0-r5363-src-wit…>, so i think there must be ways to print the lattice graph, i tried to compile the "preview.py", but it says "no module named config", so i download a config softpackage from this website: http://www.red-dove.com/config-doc/ and install the package so i could import config module in python, then i try to compile preview.py again, it says config module has no attribute version, i guess the config module in alps should be connected with the file "config.py.in" in the tool documentary, but not the config softpackage i download, but i dont know how to use the "config.py.in" file, so i get stucked again. In another posting: https://lists.phys.ethz.ch/pipermail/comp-phys-alps-users/2007/000106.html someone also asked a similar question, and Matthias suggested " To visualize it please use the lattice viewer that i send in a separate mail and copy&paste above text into it ", so i wonder whether the lattice previewer tool is only for private use, but those postings were years ago, i m confused. Hope someone could tell me how to print out the lattice graph when i want to make my own lattice. Thanks and Best Wishes! Rui

1 0

energy fluctuation
by muzi352 14 Apr '11

14 Apr '11

Dear ALPS developers： thank you for your reply, my question is that sweeps=20 and 30,the ground energy is unequal .I try it sever times . I think that the energy is converged in case.strangly ,for example : Jxy1-0.5,Jz1=-1.0,Jz2and Jxy2 vary ,the ground energy is:(sweeps=30,a=J2/Jz1) ,when a<0.4,the energy fluctuation. thank you At 2011-04-13，comp-phys-alps-users-request(a)lists.phys.ethz.ch wrote: >Send Comp-phys-alps-users mailing list submissions to > comp-phys-alps-users(a)lists.phys.ethz.ch > >To subscribe or unsubscribe via the World Wide Web, visit > https://lists.phys.ethz.ch/listinfo/comp-phys-alps-users >or, via email, send a message with subject or body 'help' to > comp-phys-alps-users-request(a)lists.phys.ethz.ch > >You can reach the person managing the list at > comp-phys-alps-users-owner(a)lists.phys.ethz.ch > >When replying, please edit your Subject line so it is more specific >than "Re: Contents of Comp-phys-alps-users digest..." > > >Today's Topics: > > 1. Re: Comp-phys-alps-users Digest, Vol 61, Issue 2 ( sunzhaoyu2000 ) > 2. Re: Comp-phys-alps-users Digest, Vol 61, Issue 2 (???) > 3. Re: Comp-phys-alps-users Digest, Vol 61, Issue 2 (Matthias Troyer) > > >---------------------------------------------------------------------- > >Message: 1 >Date: Tue, 12 Apr 2011 21:12:01 +0800 >From: " sunzhaoyu2000 " <sunzhaoyu2000(a)qq.com> >Subject: Re: [ALPS-users] Comp-phys-alps-users Digest, Vol 61, Issue 2 >To: " comp-phys-alps-users " <comp-phys-alps-users(a)lists.phys.ethz.ch> >Message-ID: <tencent_08AFFA496BBAE9F666EFF7C4(a)qq.com> >Content-Type: text/plain; charset="iso-8859-1" > >Dear Matthias: > >Thank you very much for your reply. > >This random result is obtained by my DMRG code rather than ALPS. > >Do you mean that as parts of the Hamiltonian (H), all terms should be converged ? >In fact, the term included in H is S1S2, thus S1S2=(SxSx+SySy+SzSz) acts as a whole in H. >What I find is that: SxSx, SySy and SzSz are random, >however, I think S1S2(=SxSx+SySy+SzSz) as a whole should have already be converged. >I will check whether or not S1S2 is converged and present the result as soon as possible. > >Thank you again ! > > > > >------------------ Original ------------------ >From: "comp-phys-alps-users-request"<comp-phys-alps-users-request(a)lists.phys.ethz.ch>; >Date: Tue, Apr 12, 2011 06:00 PM >To: "comp-phys-alps-users"<comp-phys-alps-users(a)lists.phys.ethz.ch>; > >Subject: Comp-phys-alps-users Digest, Vol 61, Issue 2 > > > Send Comp-phys-alps-users mailing list submissions to > comp-phys-alps-users(a)lists.phys.ethz.ch > >To subscribe or unsubscribe via the World Wide Web, visit > https://lists.phys.ethz.ch/listinfo/comp-phys-alps-users >or, via email, send a message with subject or body 'help' to > comp-phys-alps-users-request(a)lists.phys.ethz.ch > >You can reach the person managing the list at > comp-phys-alps-users-owner(a)lists.phys.ethz.ch > >When replying, please edit your Subject line so it is more specific >than "Re: Contents of Comp-phys-alps-users digest..." > > >Today's Topics: > > 1. Would all the pairwise correlations be converged after the > gound-state energy converges ? (???) > 2. Re: Would all the pairwise correlations be converged after > the gound-state energy converges ? (Matthias Troyer) > > >---------------------------------------------------------------------- > >Message: 1 >Date: Tue, 12 Apr 2011 09:40:50 +0800 >From: ??? <sunzhaoyu2000(a)gmail.com> >Subject: [ALPS-users] Would all the pairwise correlations be converged > after the gound-state energy converges ? >To: comp-phys-alps-users(a)lists.phys.ethz.ch >Message-ID: <BANLkTi=5kxfMAFzVhTNYK5i67CT=znarrQ(a)mail.gmail.com> >Content-Type: text/plain; charset=ISO-8859-1 > >Dear ALPS users and developers: > >I want to study a spin ladder with four-site interaction. >[ ? ?Phys. Rev. B 67, 100409(R) (2003), >http://prb.aps.org/abstract/PRB/v67/i10/e100409 ? ? ] > >As ALPS 2.0 do not support 4-site terms, I code DMRG myself. >For small size system(L=2,4,6,8,10) and the four-site interaction is zero, >I have checked my DMRG code by comparing the obtained ground-state >energy with that obtained by ED in ALPS. >The two are fairly consistent. > >Then I move on to larger systems and four-body term are included. >However, I am confused by the DMRG results: >in the staggered dimer state of the system(see Phys. Rev. B 67, >100409(R) (2003), Fig. 2), >when the ground-state of the ladder has converged, >I check the two-site correlations, and find that >the correlation function [ G_leg ] between nearest-neighboring two >sites on the leg converges very well, >meanwhile the correlation function [ G_rung ] between the two sites on >the same rung does not converge at all >( G_rung seems to be random with the increase of size L, L = 100 ). > >I wonder is this a reasonable result ( is it possible that G_rung >becomes undefined or because of some other physical reason, >leading to a random average value for G_rung ) ? >Or all the pairwise correlations in the system should always be >converged after the gound-state energy converges ? >Any suggestion would be appreciated. > >sunzhaoyu2000(a)gmail.com > > >------------------------------ > >Message: 2 >Date: Tue, 12 Apr 2011 06:58:27 +0200 >From: Matthias Troyer <troyer(a)phys.ethz.ch> >Subject: Re: [ALPS-users] Would all the pairwise correlations be > converged after the gound-state energy converges ? >To: comp-phys-alps-users(a)lists.phys.ethz.ch >Message-ID: <639622C3-988E-44CB-9E33-7329CC65A19F(a)phys.ethz.ch> >Content-Type: text/plain; charset=utf-8 > >Hi, > >was this random result obtained by ALPS or by your code? Could you please send us the input files if it was with ALPS? Since the rung correlation function is actually part of the Hamiltonian I don't think that the energy is converged in your case. > >Matthias > >On 12 Apr 2011, at 03:40, ??? wrote: > >> Dear ALPS users and developers: >> >> I want to study a spin ladder with four-site interaction. >> [ Phys. Rev. B 67, 100409(R) (2003), >> http://prb.aps.org/abstract/PRB/v67/i10/e100409 ] >> >> As ALPS 2.0 do not support 4-site terms, I code DMRG myself. >> For small size system(L=2,4,6,8,10) and the four-site interaction is zero, >> I have checked my DMRG code by comparing the obtained ground-state >> energy with that obtained by ED in ALPS. >> The two are fairly consistent. >> >> Then I move on to larger systems and four-body term are included. >> However, I am confused by the DMRG results: >> in the staggered dimer state of the system(see Phys. Rev. B 67, >> 100409(R) (2003), Fig. 2), >> when the ground-state of the ladder has converged, >> I check the two-site correlations, and find that >> the correlation function [ G_leg ] between nearest-neighboring two >> sites on the leg converges very well, >> meanwhile the correlation function [ G_rung ] between the two sites on >> the same rung does not converge at all >> ( G_rung seems to be random with the increase of size L, L = 100 ). >> >> I wonder is this a reasonable result ( is it possible that G_rung >> becomes undefined or because of some other physical reason, >> leading to a random average value for G_rung ) ? >> Or all the pairwise correlations in the system should always be >> converged after the gound-state energy converges ? >> Any suggestion would be appreciated. >> >> sunzhaoyu2000(a)gmail.com >> > > > >End of Comp-phys-alps-users Digest, Vol 61, Issue 2 >*************************************************** >

1 0

Re: [ALPS-users] Comp-phys-alps-users Digest, Vol 61, Issue 2
by sunzhaoyu2000 12 Apr '11

12 Apr '11

Dear Matthias: Thank you very much for your reply. This random result is obtained by my DMRG code rather than ALPS. Do you mean that as parts of the Hamiltonian (H), all terms should be converged ? In fact, the term included in H is S1S2, thus S1S2=(SxSx+SySy+SzSz) acts as a whole in H. What I find is that: SxSx, SySy and SzSz are random, however, I think S1S2(=SxSx+SySy+SzSz) as a whole should have already be converged. I will check whether or not S1S2 is converged and present the result as soon as possible. Thank you again ! ------------------ Original ------------------ From: "comp-phys-alps-users-request"<comp-phys-alps-users-request(a)lists.phys.ethz.ch>; Date: Tue, Apr 12, 2011 06:00 PM To: "comp-phys-alps-users"<comp-phys-alps-users(a)lists.phys.ethz.ch>; Subject: Comp-phys-alps-users Digest, Vol 61, Issue 2 Send Comp-phys-alps-users mailing list submissions to comp-phys-alps-users(a)lists.phys.ethz.ch To subscribe or unsubscribe via the World Wide Web, visit https://lists.phys.ethz.ch/listinfo/comp-phys-alps-users or, via email, send a message with subject or body 'help' to comp-phys-alps-users-request(a)lists.phys.ethz.ch You can reach the person managing the list at comp-phys-alps-users-owner(a)lists.phys.ethz.ch When replying, please edit your Subject line so it is more specific than "Re: Contents of Comp-phys-alps-users digest..." Today's Topics: 1. Would all the pairwise correlations be converged after the gound-state energy converges ? (???) 2. Re: Would all the pairwise correlations be converged after the gound-state energy converges ? (Matthias Troyer) ---------------------------------------------------------------------- Message: 1 Date: Tue, 12 Apr 2011 09:40:50 +0800 From: ??? <sunzhaoyu2000(a)gmail.com> Subject: [ALPS-users] Would all the pairwise correlations be converged after the gound-state energy converges ? To: comp-phys-alps-users(a)lists.phys.ethz.ch Message-ID: <BANLkTi=5kxfMAFzVhTNYK5i67CT=znarrQ(a)mail.gmail.com> Content-Type: text/plain; charset=ISO-8859-1 Dear ALPS users and developers: I want to study a spin ladder with four-site interaction. [ ? ?Phys. Rev. B 67, 100409(R) (2003), http://prb.aps.org/abstract/PRB/v67/i10/e100409 ? ? ] As ALPS 2.0 do not support 4-site terms, I code DMRG myself. For small size system(L=2,4,6,8,10) and the four-site interaction is zero, I have checked my DMRG code by comparing the obtained ground-state energy with that obtained by ED in ALPS. The two are fairly consistent. Then I move on to larger systems and four-body term are included. However, I am confused by the DMRG results: in the staggered dimer state of the system(see Phys. Rev. B 67, 100409(R) (2003), Fig. 2), when the ground-state of the ladder has converged, I check the two-site correlations, and find that the correlation function [ G_leg ] between nearest-neighboring two sites on the leg converges very well, meanwhile the correlation function [ G_rung ] between the two sites on the same rung does not converge at all ( G_rung seems to be random with the increase of size L, L = 100 ). I wonder is this a reasonable result ( is it possible that G_rung becomes undefined or because of some other physical reason, leading to a random average value for G_rung ) ? Or all the pairwise correlations in the system should always be converged after the gound-state energy converges ? Any suggestion would be appreciated. sunzhaoyu2000(a)gmail.com ------------------------------ Message: 2 Date: Tue, 12 Apr 2011 06:58:27 +0200 From: Matthias Troyer <troyer(a)phys.ethz.ch> Subject: Re: [ALPS-users] Would all the pairwise correlations be converged after the gound-state energy converges ? To: comp-phys-alps-users(a)lists.phys.ethz.ch Message-ID: <639622C3-988E-44CB-9E33-7329CC65A19F(a)phys.ethz.ch> Content-Type: text/plain; charset=utf-8 Hi, was this random result obtained by ALPS or by your code? Could you please send us the input files if it was with ALPS? Since the rung correlation function is actually part of the Hamiltonian I don't think that the energy is converged in your case. Matthias On 12 Apr 2011, at 03:40, ??? wrote: > Dear ALPS users and developers: > > I want to study a spin ladder with four-site interaction. > [ Phys. Rev. B 67, 100409(R) (2003), > http://prb.aps.org/abstract/PRB/v67/i10/e100409 ] > > As ALPS 2.0 do not support 4-site terms, I code DMRG myself. > For small size system(L=2,4,6,8,10) and the four-site interaction is zero, > I have checked my DMRG code by comparing the obtained ground-state > energy with that obtained by ED in ALPS. > The two are fairly consistent. > > Then I move on to larger systems and four-body term are included. > However, I am confused by the DMRG results: > in the staggered dimer state of the system(see Phys. Rev. B 67, > 100409(R) (2003), Fig. 2), > when the ground-state of the ladder has converged, > I check the two-site correlations, and find that > the correlation function [ G_leg ] between nearest-neighboring two > sites on the leg converges very well, > meanwhile the correlation function [ G_rung ] between the two sites on > the same rung does not converge at all > ( G_rung seems to be random with the increase of size L, L = 100 ). > > I wonder is this a reasonable result ( is it possible that G_rung > becomes undefined or because of some other physical reason, > leading to a random average value for G_rung ) ? > Or all the pairwise correlations in the system should always be > converged after the gound-state energy converges ? > Any suggestion would be appreciated. > > sunzhaoyu2000(a)gmail.com > End of Comp-phys-alps-users Digest, Vol 61, Issue 2 ***************************************************

2 1

Re: [ALPS-users] Comp-phys-alps-users Digest, Vol 61, Issue 2
by 孙照宇 12 Apr '11

12 Apr '11

Dear Matthias: Thank you very much for your reply. This random result is obtained by my DMRG code rather than ALPS. Do you mean that all terms in the Hamiltonian (H) should be converged ? In fact, the term included in H is S1S2, thus S1S2=(SxSx+SySy+SzSz) acts as a whole in H. What I find is that: SxSx, SySy and SzSz are random, however, I think S1S2(=SxSx+SySy+SzSz) as a whole should have already be converged. I will check whether or not S1S2 is converged and present the result as soon as possible. Thank you again ! 2011/4/12 <comp-phys-alps-users-request(a)lists.phys.ethz.ch>: > Send Comp-phys-alps-users mailing list submissions to > comp-phys-alps-users(a)lists.phys.ethz.ch > > To subscribe or unsubscribe via the World Wide Web, visit > https://lists.phys.ethz.ch/listinfo/comp-phys-alps-users > or, via email, send a message with subject or body 'help' to > comp-phys-alps-users-request(a)lists.phys.ethz.ch > > You can reach the person managing the list at > comp-phys-alps-users-owner(a)lists.phys.ethz.ch > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of Comp-phys-alps-users digest..." > > > Today's Topics: > > 1. Would all the pairwise correlations be converged after the > gound-state energy converges ? (???) > 2. Re: Would all the pairwise correlations be converged after > the gound-state energy converges ? (Matthias Troyer) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Tue, 12 Apr 2011 09:40:50 +0800 > From: ??? <sunzhaoyu2000(a)gmail.com> > Subject: [ALPS-users] Would all the pairwise correlations be converged > after the gound-state energy converges ? > To: comp-phys-alps-users(a)lists.phys.ethz.ch > Message-ID: <BANLkTi=5kxfMAFzVhTNYK5i67CT=znarrQ(a)mail.gmail.com> > Content-Type: text/plain; charset=ISO-8859-1 > > Dear ALPS users and developers: > > I want to study a spin ladder with four-site interaction. > [ ? ?Phys. Rev. B 67, 100409(R) (2003), > http://prb.aps.org/abstract/PRB/v67/i10/e100409 ? ? ] > > As ALPS 2.0 do not support 4-site terms, I code DMRG myself. > For small size system(L=2,4,6,8,10) and the four-site interaction is zero, > I have checked my DMRG code by comparing the obtained ground-state > energy with that obtained by ED in ALPS. > The two are fairly consistent. > > Then I move on to larger systems and four-body term are included. > However, I am confused by the DMRG results: > in the staggered dimer state of the system(see Phys. Rev. B 67, > 100409(R) (2003), Fig. 2), > when the ground-state of the ladder has converged, > I check the two-site correlations, and find that > the correlation function [ G_leg ] between nearest-neighboring two > sites on the leg converges very well, > meanwhile the correlation function [ G_rung ] between the two sites on > the same rung does not converge at all > ( G_rung seems to be random with the increase of size L, L = 100 ). > > I wonder is this a reasonable result ( is it possible that G_rung > becomes undefined or because of some other physical reason, > leading to a random average value for G_rung ) ? > Or all the pairwise correlations in the system should always be > converged after the gound-state energy converges ? > Any suggestion would be appreciated. > > sunzhaoyu2000(a)gmail.com > > > ------------------------------ > > Message: 2 > Date: Tue, 12 Apr 2011 06:58:27 +0200 > From: Matthias Troyer <troyer(a)phys.ethz.ch> > Subject: Re: [ALPS-users] Would all the pairwise correlations be > converged after the gound-state energy converges ? > To: comp-phys-alps-users(a)lists.phys.ethz.ch > Message-ID: <639622C3-988E-44CB-9E33-7329CC65A19F(a)phys.ethz.ch> > Content-Type: text/plain; charset=utf-8 > > Hi, > > was this random result obtained by ALPS or by your code? Could you please send us the input files if it was with ALPS? Since the rung correlation function is actually part of the Hamiltonian I don't think that the energy is converged in your case. > > Matthias > > On 12 Apr 2011, at 03:40, ??? wrote: > >> Dear ALPS users and developers: >> >> I want to study a spin ladder with four-site interaction. >> [ Phys. Rev. B 67, 100409(R) (2003), >> http://prb.aps.org/abstract/PRB/v67/i10/e100409 ] >> >> As ALPS 2.0 do not support 4-site terms, I code DMRG myself. >> For small size system(L=2,4,6,8,10) and the four-site interaction is zero, >> I have checked my DMRG code by comparing the obtained ground-state >> energy with that obtained by ED in ALPS. >> The two are fairly consistent. >> >> Then I move on to larger systems and four-body term are included. >> However, I am confused by the DMRG results: >> in the staggered dimer state of the system(see Phys. Rev. B 67, >> 100409(R) (2003), Fig. 2), >> when the ground-state of the ladder has converged, >> I check the two-site correlations, and find that >> the correlation function [ G_leg ] between nearest-neighboring two >> sites on the leg converges very well, >> meanwhile the correlation function [ G_rung ] between the two sites on >> the same rung does not converge at all >> ( G_rung seems to be random with the increase of size L, L = 100 ). >> >> I wonder is this a reasonable result ( is it possible that G_rung >> becomes undefined or because of some other physical reason, >> leading to a random average value for G_rung ) ? >> Or all the pairwise correlations in the system should always be >> converged after the gound-state energy converges ? >> Any suggestion would be appreciated. >> >> sunzhaoyu2000(a)gmail.com >> > > > > End of Comp-phys-alps-users Digest, Vol 61, Issue 2 > *************************************************** >

1 0

Would all the pairwise correlations be converged after the gound-state energy converges ?
by 孙照宇 12 Apr '11

12 Apr '11

Dear ALPS users and developers: I want to study a spin ladder with four-site interaction. [ Phys. Rev. B 67, 100409(R) (2003), http://prb.aps.org/abstract/PRB/v67/i10/e100409 ] As ALPS 2.0 do not support 4-site terms, I code DMRG myself. For small size system(L=2,4,6,8,10) and the four-site interaction is zero, I have checked my DMRG code by comparing the obtained ground-state energy with that obtained by ED in ALPS. The two are fairly consistent. Then I move on to larger systems and four-body term are included. However, I am confused by the DMRG results: in the staggered dimer state of the system(see Phys. Rev. B 67, 100409(R) (2003), Fig. 2), when the ground-state of the ladder has converged, I check the two-site correlations, and find that the correlation function [ G_leg ] between nearest-neighboring two sites on the leg converges very well, meanwhile the correlation function [ G_rung ] between the two sites on the same rung does not converge at all ( G_rung seems to be random with the increase of size L, L = 100 ). I wonder is this a reasonable result ( is it possible that G_rung becomes undefined or because of some other physical reason, leading to a random average value for G_rung ) ? Or all the pairwise correlations in the system should always be converged after the gound-state energy converges ? Any suggestion would be appreciated. sunzhaoyu2000(a)gmail.com

2 1

Re: [ALPS-users] [Alps-users] error in instaling alps
by Algis Garliauskas 07 Apr '11

07 Apr '11

> > All users, > I have installed Alps.1.3.5 and got to my mind the good results of > configuration bellow. But after make command it shows very many error. > What is wrong? I tried different boost options with prefix. Nothing changes > after 'make' the same errors > are repeating. Something is connected with private note: class version_type { private: typedef uint_least32_t base_type; base_type t; public: // should be private - but MPI fails if it's not!!! version_type(): t(0) {}; explicit version_type(const unsigned int & t_) : t(t_){ assert(t_ <= boost::integer_traits<base_type>::const_max); } or class class_id_type { private: typedef int_least16_t base_type; base_type t; public: // should be private - but then can't use BOOST_STRONG_TYPE below class_id_type() : t(0) {}; explicit class_id_type(const int t_) : t(t_){ assert(t_ <= boost::integer_traits<base_type>::const_max); } I can not edit: It is not possible! The boost prefix options doesn't influence to content of an archive file 'basic_archive.h', where almost all errors are appeared. See, about all in attached make results > Thanks for your advises in advance > Algis Garliauskas > > Summary of configuration: > ALPS version 1.3.5 > prefix /home/ag/ALPS > compiler type gnu [g++] > optimization yes > exceptions yes > warnings no > Boost version svn > MPI support no > OpenMP support no > HDF5 support no > LAPACK support no > SQLite support yes > XML parser native > Documentation no > ..---... > [ag@localhost ALPS]$ make > Making all in lib > make[1]: Entering directory `/ALPS/lib' > Making all in comm-sgl > make[2]: Entering directory `/ALPS/lib/comm-sgl' > /bin/sh ../../libtool --tag=CXX --mode=compile g++ -DHAVE_CONFIG_H > -I../../src -I../../src -DNDEBUG -g -O2 -MT buffer.lo -MD -MP > -MF .deps/buffer.Tpo -c -o buffer.lo `test -f > '../../src/alps/osiris/buffer.C' || echo > './'`../../src/alps/osiris/buffer.C > libtool: compile: g++ -DHAVE_CONFIG_H -I../../src -I../../src -DNDEBUG > -g -O2 -MT buffer.lo -MD -MP -MF .deps/buffer.Tpo > -c ../../src/alps/osiris/buffer.C -fPIC -DPIC -o .libs/buffer.o > In file included from ../../src/alps/osiris/dump.h:221:0, > from ../../src/alps/osiris/buffer.C:32: > /usr/include/boost/archive/basic_archive.hpp: In member function ‘void > alps::odump_archive::save_override(const boost::archive::version_type&, > int)’: > /usr/include/boost/archive/basic_archive.hpp:78:15: error: > ‘boost::archive::version_type::base_type > boost::archive::version_type::t’ is private > ../../src/alps/osiris/dumparchive.h:111:24: error: within this context > /usr/include/boost/archive/basic_archive.hpp: In member function ‘void > alps::odump_archive::save_override(const boost::archive::class_id_type&, > int)’: > /usr/include/boost/archive/basic_archive.hpp:111:15: error: > ‘boost::archive::class_id_type::base_type > boost::archive::class_id_type::t’ is private > ../../src/alps/osiris/dumparchive.h:117:29: error: within this context > /usr/include/boost/archive/basic_archive.hpp: In member function ‘void > alps::odump_archive::save_override(const > boost::archive::class_id_reference_type&, int)’: > /usr/include/boost/archive/basic_archive.hpp:111:15: error: > ‘boost::archive::class_id_type::base_type > boost::archive::class_id_type::t’ is private > ../../src/alps/osiris/dumparchive.h:123:29: error: within this context > /usr/include/boost/archive/basic_archive.hpp: In member function ‘void > alps::odump_archive::save_override(const > boost::archive::object_id_type&, int)’: > /usr/include/boost/archive/basic_archive.hpp:150:15: error: > ‘boost::archive::object_id_type::base_type > boost::archive::object_id_type::t’ is private > ../../src/alps/osiris/dumparchive.h:129:30: error: within this context > /usr/include/boost/archive/basic_archive.hpp: In member function ‘void > alps::odump_archive::save_override(const > boost::archive::object_reference_type&, int)’: > /usr/include/boost/archive/basic_archive.hpp:150:15: error: > ‘boost::archive::object_id_type::base_type > boost::archive::object_id_type::t’ is private > ../../src/alps/osiris/dumparchive.h:135:30: error: within this context > ../../src/alps/osiris/dumparchive.h: In member function ‘void > alps::idump_archive::load_override(boost::archive::class_id_reference_type&, > int)’: > ../../src/alps/osiris/dumparchive.h:238:54: error: no matching function > for call to > > ‘boost::archive::class_id_reference_type::class_id_reference_type(int_least16_t&)’ > /usr/include/boost/archive/basic_archive.hpp:261:73: note: candidates > are: > > boost::archive::class_id_reference_type::class_id_reference_type(boost::archive::class_id_type) > /usr/include/boost/archive/basic_archive.hpp:261:54: note: > boost::archive::class_id_reference_type::class_id_reference_type(const > boost::archive::class_id_reference_type&) > ../../src/alps/osiris/dumparchive.h: In member function ‘void > alps::idump_archive::load_override(boost::archive::object_reference_type&, > int)’: > ../../src/alps/osiris/dumparchive.h:252:52: error: no matching function > for call to > > ‘boost::archive::object_reference_type::object_reference_type(uint_least32_t&)’ > /usr/include/boost/archive/basic_archive.hpp:263:72: note: candidates > are: > > boost::archive::object_reference_type::object_reference_type(boost::archive::object_id_type) > /usr/include/boost/archive/basic_archive.hpp:263:53: note: > boost::archive::object_reference_type::object_reference_type(const > boost::archive::object_reference_type&) > make[2]: *** [buffer.lo] Error 1 > make[2]: Leaving directory `/ALPS/lib/comm-sgl' > make[1]: *** [all-recursive] Error 1 > make[1]: Leaving directory `/ALPS/lib' > make: *** [all-recursive] Error 1 > > > > -- Algis Garliauskas Prof., Hab. dr. Vilnius University Institute of Mathematics & Informatics Akademijos 4, LT-6883, Vilnius, Lithuania Tel.:370 5 2109333

2 1

alps scheduler, histogram observable
by Sebastian Huber 29 Mar '11

29 Mar '11

Dear all, I am using the alea libraries for an implementation of a monte carlo simulation. If I try to use the HistogramObservable as follows: measurements << alps::HistogramObservable<double>("MyObservable"); It compiles, it runs, but when it tries to write the hdf5 file either while checkpointing or when finished I get the following error: HDF5 Error writing path '/' on type 'N4alps9scheduler12MCSimulationE': HDF5 Error writing path '/simulation/results' on type 'N4alps13ObservableSetE': HDF5 Error writing path 'MyObservable' on type 'N4alps19HistogramObservableIdEE': HDF5 Error writing path '@size' on type 'j': Error in /Users/sebi/ALPS/include/alps/hdf5.hpp on 842 in set_attribute: unknown path: /simulation/results/MyObservable Regards, Sebastian -- Sebastian Huber Department of Condensed Matter Physics The Weizmann Institute of Science 76100 Rehovot Web: http://www.weizmann.ac.il/~huber Tel: +972 8 934 4258

2 2