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

reduced density matrices eigenvalues
by Robertson Esperanza 03 Nov '16

03 Nov '16

Hello, Thank you for replying to my previous inquiries. For now, I'm looking at the von neumann entropy of some variation of the Hubbard Hamiltonian, and I'm using the mps_optim application. Since the von Neumann entropy can be calculated, will I be able to access the eigenvalues of the reduced density matrices? If yes, how can I do that? I would like to also do the same thing using the exact diagonalization, but there is no function, as far as I know, to calculate the non Neumann entropy. How can I access the eigenvalued of the reduced density matrices using the ALPS application for exact diagonalization? Regards, Robbie

3 7

DMRG code
by Julien 02 Nov '16

02 Nov '16

Hello ALPS community, First, sorry for my English and for the trivial question that I'm going to ask you. I already made the tutorial on the S=(1/2, 1) antiferromagnetic Heisenberg chain where I found the correlation function and the gap in the thermodynamic limit (for S = 1). Now, I'm trying to do the same thing for the S=1/2 ferromagnetic Heisenberg chain but I guess I made a mistake when we have to specify the different parameters. Here is what I wrote in my computer code : parms.append({ 'LATTICE' : 'open chain lattice', 'MODEL' : 'spin', 'CONSERVED_QUANTUMNUMBERS' : 'N,Sz', 'Sz_total' : 0, 'J' : -1, 'SWEEPS' : 4, 'NUMBER_EIGENVALUES' : 1, 'L' : 32, 'MAXSTATES' : 20, 'MEASURE_CORRELATIONS[Diagonal spin correlations]' : 'Sz', }) but the result is completely wrong. I only modify the sign of the coupling constant compared to the antiferromagnetic case. Thank you in advance for your help, Best regards, Julien

4 11

MPI problem
by Tadeusz Wasiutyński 02 Nov '16

02 Nov '16

2016-10-31 12:00 GMT+01:00 <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. MPI problem (Tadeusz Wasiuty?ski) > 2. Re: MPI problem (Michele Dolfi) > > > ---------- Wiadomość przekazana dalej ---------- > From: "Tadeusz Wasiutyński" <tadeusz.wasiutynski(a)gmail.com> > To: comp-phys-alps-users(a)lists.phys.ethz.ch > Cc: > Date: Sat, 29 Oct 2016 21:42:49 +0200 > Subject: [ALPS-users] MPI problem > Hello, > I met the problem on my CENTOS 7 installed on station with 24 threads. > After: > > ~/opt/bin/cmake -D Boost_ROOT_DIR:PATH=~/alps-2.2.b4-src-with-boost/boost/ > -D MPI_C_LIBRARIES=/usr/lib64/openmpi/libmpi.so -D > MPI_C_INCLUDE_PATH=/usr/lib64/openmpi/include/ -D > MPI_CXX_INCLUDE_PATH=/usr/lib64/openmpi/include -D > LPSolve_LIBRARY=/usr/lib64/liblpsolve55.so -D LPSolve_INCLUDE_DIR=/usr/include/lpsolve/ > -D HDF5_LIBRARIES=~/opt/lib/libhdf5.so -D HDF5_INCLUDE_DIR=~/opt/include/ > -D SZIP_LIBRARIES=/usr/lib64/lib/libsz.so -D SZIP_INCLUDE_DIRS=/usr/lib64/include/ > ~/alps-2.2.b4-src-with-boost/alps/ > > I receive: > > ---- Compiler version: c++ (GCC) 4.8.5 20150623 (Red Hat 4.8.5-4) > -- Build type: Release > -- Python interpreter /usr/bin/python > -- Python interpreter ok : version 2. PYTHON_INCLUDE_DIRS = > /usr/include/python2.7 > -- PYTHON_NUMPY_INCLUDE_DIR = /usr/lib64/python2.7/site- > packages/numpy/core/include > -- PYTHON_SITE_PKG = /usr/lib/python2.7/site-packages > -- PYTHON_LIBRARY = /usr/lib64/python2.7/config/libpython2.7.so > -- PYTHON_EXTRA_LIBS =-lpthread -ldl -lutil > -- PYTHON_LINK_FOR_SHARED = -Xlinker -export-dynamic > -- ALPS version: 2.2.b4 > -- Looking for Boost Source > -- Found Boost Source: /home/twasiutynsk/alps-2.2.b4-src-with-boost/boost > -- Boost Version: 1_58_0 > -- Adding Boost dir: /home/twasiutynsk/alps-2.2.b4-src-with-boost/boost > -- MPI compiler was /usr/lib64/openmpi/bin/mpicxx > -- Falling back to CMake provied LAPACK/BLAS detection. > -- A library with BLAS API found. > -- A library with BLAS API found. > -- A library with LAPACK API found. > -- SQLite Library: not found > -- Could NOT find SZIP (missing: SZIP_LIBRARIES SZIP_INCLUDE_DIRS) > -- HDF5 without THREADSAFE mode. ALPS will ensure thread safety by HDF5 > running sequentially. > -- Python interpreter /usr/bin/python > -- Python interpreter ok : version 2.7.5 > -- PYTHON_INCLUDE_DIRS = /usr/include/python2.7 > -- PYTHON_NUMPY_INCLUDE_DIR = /usr/lib64/python2.7/site- > packages/numpy/core/include > -- PYTHON_SITE_PKG = /usr/lib/python2.7/site-packages > -- PYTHON_LIBRARY = /usr/lib64/python2.7/config/libpython2.7.so > -- PYTHON_EXTRA_LIBS =-lpthread -ldl -lutil > -- PYTHON_LINK_FOR_SHARED = -Xlinker -export-dynamic > -- Numpy include in /usr/lib64/python2.7/site-packages/numpy/core/include > -- ALPS XML dir is /opt/alps/lib/xml > -- HDF5 without THREADSAFE mode. ALPS will ensure thread safety by HDF5 > running sequentially. > -- MPS: enabling NU1 symmetry. > -- HDF5 without THREADSAFE mode. ALPS will ensure thread safety by HDF5 > running sequentially. > -- tebd will not be built > -- HDF5 without THREADSAFE mode. ALPS will ensure thread safety by HDF5 > running sequentially. > -- Configuring done > -- Generating done > -- Build files have been written to: /home/twasiutynsk/build > > in ccmake I see MPI ON. make and make tests (all passed) go smoothly. In > tutorial runs I see however mess with MPI=24 while everything goes OK with > MPI=1. > Is something wrong in my HDF5? > > In docker hub I found dolfim/alps but could not run probably because of > some path problems. Anyone did it successfully? > Regards > > > -- > Tadeusz Wasiutyński > > > -- > Tadeusz Wasiutyński > > > ---------- Wiadomość przekazana dalej ---------- > From: Michele Dolfi <dolfim(a)phys.ethz.ch> > To: comp-phys-alps-users(a)lists.phys.ethz.ch > Cc: > Date: Mon, 31 Oct 2016 11:11:51 +0100 > Subject: Re: [ALPS-users] MPI problem > The configuration seems fine and the hdf5 message are not related to the > MPI execution. > > Can you clarify a bit what you mean by “see a mess”? How do you run the > mpi application? > > > Michele > > -- > ETH Zurich > Michele Dolfi > Institute for Theoretical Physics > HIT G 32.4 > Wolfgang-Pauli-Str. 27 > 8093 Zurich > Switzerland > > dolfim(a)phys.ethz.ch > www.itp.phys.ethz.ch > > +41 44 633 78 56 phone > +41 44 633 11 15 fax > > > > > > On Oct 29, 2016, at 9:42 PM, Tadeusz Wasiutyński < > tadeusz.wasiutynski(a)gmail.com> wrote: > > Hello, > I met the problem on my CENTOS 7 installed on station with 24 threads. > After: > > ~/opt/bin/cmake -D Boost_ROOT_DIR:PATH=~/alps-2.2.b4-src-with-boost/boost/ > -D MPI_C_LIBRARIES=/usr/lib64/openmpi/libmpi.so -D > MPI_C_INCLUDE_PATH=/usr/lib64/openmpi/include/ -D > MPI_CXX_INCLUDE_PATH=/usr/lib64/openmpi/include -D > LPSolve_LIBRARY=/usr/lib64/liblpsolve55.so -D LPSolve_INCLUDE_DIR=/usr/include/lpsolve/ > -D HDF5_LIBRARIES=~/opt/lib/libhdf5.so -D HDF5_INCLUDE_DIR=~/opt/include/ > -D SZIP_LIBRARIES=/usr/lib64/lib/libsz.so -D SZIP_INCLUDE_DIRS=/usr/lib64/include/ > ~/alps-2.2.b4-src-with-boost/alps/ > > I receive: > > ---- Compiler version: c++ (GCC) 4.8.5 20150623 (Red Hat 4.8.5-4) > -- Build type: Release > -- Python interpreter /usr/bin/python > -- Python interpreter ok : version 2. PYTHON_INCLUDE_DIRS = > /usr/include/python2.7 > -- PYTHON_NUMPY_INCLUDE_DIR = /usr/lib64/python2.7/site- > packages/numpy/core/include > -- PYTHON_SITE_PKG = /usr/lib/python2.7/site-packages > -- PYTHON_LIBRARY = /usr/lib64/python2.7/config/libpython2.7.so > -- PYTHON_EXTRA_LIBS =-lpthread -ldl -lutil > -- PYTHON_LINK_FOR_SHARED = -Xlinker -export-dynamic > -- ALPS version: 2.2.b4 > -- Looking for Boost Source > -- Found Boost Source: /home/twasiutynsk/alps-2.2.b4-src-with-boost/boost > -- Boost Version: 1_58_0 > -- Adding Boost dir: /home/twasiutynsk/alps-2.2.b4-src-with-boost/boost > -- MPI compiler was /usr/lib64/openmpi/bin/mpicxx > -- Falling back to CMake provied LAPACK/BLAS detection. > -- A library with BLAS API found. > -- A library with BLAS API found. > -- A library with LAPACK API found. > -- SQLite Library: not found > -- Could NOT find SZIP (missing: SZIP_LIBRARIES SZIP_INCLUDE_DIRS) > -- HDF5 without THREADSAFE mode. ALPS will ensure thread safety by HDF5 > running sequentially. > -- Python interpreter /usr/bin/python > -- Python interpreter ok : version 2.7.5 > -- PYTHON_INCLUDE_DIRS = /usr/include/python2.7 > -- PYTHON_NUMPY_INCLUDE_DIR = /usr/lib64/python2.7/site- > packages/numpy/core/include > -- PYTHON_SITE_PKG = /usr/lib/python2.7/site-packages > -- PYTHON_LIBRARY = /usr/lib64/python2.7/config/libpython2.7.so > -- PYTHON_EXTRA_LIBS =-lpthread -ldl -lutil > -- PYTHON_LINK_FOR_SHARED = -Xlinker -export-dynamic > -- Numpy include in /usr/lib64/python2.7/site-packages/numpy/core/include > -- ALPS XML dir is /opt/alps/lib/xml > -- HDF5 without THREADSAFE mode. ALPS will ensure thread safety by HDF5 > running sequentially. > -- MPS: enabling NU1 symmetry. > -- HDF5 without THREADSAFE mode. ALPS will ensure thread safety by HDF5 > running sequentially. > -- tebd will not be built > -- HDF5 without THREADSAFE mode. ALPS will ensure thread safety by HDF5 > running sequentially. > -- Configuring done > -- Generating done > -- Build files have been written to: /home/twasiutynsk/build > > in ccmake I see MPI ON. make and make tests (all passed) go smoothly. In > tutorial runs I see however mess with MPI=24 while everything goes OK with > MPI=1. > Is something wrong in my HDF5? > > In docker hub I found dolfim/alps but could not run probably because of > some path problems. Anyone did it successfully? > Regards > > > -- > Tadeusz Wasiutyński > > > -- > Tadeusz Wasiutyński > > > ---- > Comp-phys-alps-users Mailing List for the ALPS Project > http://alps.comp-phys.org/ > > List info: https://lists.phys.ethz.ch//listinfo/comp-phys-alps-users > Archive: https://lists.phys.ethz.ch//pipermail/comp-phys-alps-users > > Unsubscribe by writing a mail to comp-phys-alps-users-leave@ > lists.phys.ethz.ch. > > > > ---- > Comp-phys-alps-users Mailing List for the ALPS Project > http://alps.comp-phys.org/ > > List info: https://lists.phys.ethz.ch//listinfo/comp-phys-alps-users > Archive: https://lists.phys.ethz.ch//pipermail/comp-phys-alps-users > > Unsubscribe by writing a mail to comp-phys-alps-users-leave@ > lists.phys.ethz.ch. > When I run e.g. tutorial7a.py : .......................... #pyalps.runApplication('spinmc',input_file,Tmin=5) # use the following instead if you have MPI pyalps.runApplication('spinmc',input_file,Tmin=5,MPI=24) pyalps.evaluateSpinMC(pyalps.getResultFiles(prefix='parm7a')) ................................. result is different when MPI=1, 2, 8, 12, 24. I figured out that some temperatures are missed in result file. For temperatures well done all tasks have: ...out.run1 while the missed have more (run1, run2 and so on ). Finally while magnetization is collected from all temperatures, susceptibility and specific heat and Binder cumulants only from those which have only run1. Only MPI=1 gives full result. BTW it seems that for linear chain problem does not exist (Ising, Heisenberg, spinmc, loop). Tadeusz -- Tadeusz Wasiutyński

1 0

MPI problem
by Tadeusz Wasiutyński 31 Oct '16

31 Oct '16

Hello, I met the problem on my CENTOS 7 installed on station with 24 threads. After: ~/opt/bin/cmake -D Boost_ROOT_DIR:PATH=~/alps-2.2.b4-src-with-boost/boost/ -D MPI_C_LIBRARIES=/usr/lib64/openmpi/libmpi.so -D MPI_C_INCLUDE_PATH=/usr/lib64/openmpi/include/ -D MPI_CXX_INCLUDE_PATH=/usr/lib64/openmpi/include -D LPSolve_LIBRARY=/usr/lib64/liblpsolve55.so -D LPSolve_INCLUDE_DIR=/usr/include/lpsolve/ -D HDF5_LIBRARIES=~/opt/lib/libhdf5.so -D HDF5_INCLUDE_DIR=~/opt/include/ -D SZIP_LIBRARIES=/usr/lib64/lib/libsz.so -D SZIP_INCLUDE_DIRS=/usr/lib64/include/ ~/alps-2.2.b4-src-with-boost/alps/ I receive: ---- Compiler version: c++ (GCC) 4.8.5 20150623 (Red Hat 4.8.5-4) -- Build type: Release -- Python interpreter /usr/bin/python -- Python interpreter ok : version 2. PYTHON_INCLUDE_DIRS = /usr/include/python2.7 -- PYTHON_NUMPY_INCLUDE_DIR = /usr/lib64/python2.7/site-packages/numpy/core/include -- PYTHON_SITE_PKG = /usr/lib/python2.7/site-packages -- PYTHON_LIBRARY = /usr/lib64/python2.7/config/libpython2.7.so -- PYTHON_EXTRA_LIBS =-lpthread -ldl -lutil -- PYTHON_LINK_FOR_SHARED = -Xlinker -export-dynamic -- ALPS version: 2.2.b4 -- Looking for Boost Source -- Found Boost Source: /home/twasiutynsk/alps-2.2.b4-src-with-boost/boost -- Boost Version: 1_58_0 -- Adding Boost dir: /home/twasiutynsk/alps-2.2.b4-src-with-boost/boost -- MPI compiler was /usr/lib64/openmpi/bin/mpicxx -- Falling back to CMake provied LAPACK/BLAS detection. -- A library with BLAS API found. -- A library with BLAS API found. -- A library with LAPACK API found. -- SQLite Library: not found -- Could NOT find SZIP (missing: SZIP_LIBRARIES SZIP_INCLUDE_DIRS) -- HDF5 without THREADSAFE mode. ALPS will ensure thread safety by HDF5 running sequentially. -- Python interpreter /usr/bin/python -- Python interpreter ok : version 2.7.5 -- PYTHON_INCLUDE_DIRS = /usr/include/python2.7 -- PYTHON_NUMPY_INCLUDE_DIR = /usr/lib64/python2.7/site-packages/numpy/core/include -- PYTHON_SITE_PKG = /usr/lib/python2.7/site-packages -- PYTHON_LIBRARY = /usr/lib64/python2.7/config/libpython2.7.so -- PYTHON_EXTRA_LIBS =-lpthread -ldl -lutil -- PYTHON_LINK_FOR_SHARED = -Xlinker -export-dynamic -- Numpy include in /usr/lib64/python2.7/site-packages/numpy/core/include -- ALPS XML dir is /opt/alps/lib/xml -- HDF5 without THREADSAFE mode. ALPS will ensure thread safety by HDF5 running sequentially. -- MPS: enabling NU1 symmetry. -- HDF5 without THREADSAFE mode. ALPS will ensure thread safety by HDF5 running sequentially. -- tebd will not be built -- HDF5 without THREADSAFE mode. ALPS will ensure thread safety by HDF5 running sequentially. -- Configuring done -- Generating done -- Build files have been written to: /home/twasiutynsk/build in ccmake I see MPI ON. make and make tests (all passed) go smoothly. In tutorial runs I see however mess with MPI=24 while everything goes OK with MPI=1. Is something wrong in my HDF5? In docker hub I found dolfim/alps but could not run probably because of some path problems. Anyone did it successfully? Regards -- Tadeusz Wasiutyński -- Tadeusz Wasiutyński

2 1

ALPS install
by Safir 14 Oct '16

14 Oct '16

*Sir, I tried to install Alps from source code. But while running make install it giving errors. What are correct steps to install alps in ubuntu 16.04, whether VisTrails is necessary for alps?. If So how we can install Vistrails. How we can check Alps is installed or not. I am attaching screen shot of terminal* * I look forward to hearing from you.* -- *Many Thanks* *----------------------------------------------------------------------------------------------------------------------------------------------------*Safir TK Research Scholar Theoretical Physics Lab(TPL) Department Of physics National Institute of Technology Karnataka (NITK) Surathkal, P.O: Srinivasnagar, Mangalore, India - 575 025 Tel: +91 824 2473289 (Office) Mob: +91 - 7411797881, +91 -9946635799 Email : safirmon(a)gmail.com

3 9

EBH in DWA
by Mateusz Łącki 13 Oct '16

13 Oct '16

Dear All, could I ask if the DWA code actually supports the extended BH model (as defined in “boson Hubbard” hamiltonian in a standard issue of models.xml)? the results I obtain seem not to depend at all on the value of the V parameter. With sparsediag I observe no such behaviour. thebondterm contains “hopping” (proportional to t#) and interaction (proportional to V#). If I wanted to split (as the hopping is treated separately in worm-type algorithms I guess…) it into two bond-terms it seems that only the last bondterm is taken into account: this results in t=0 result <SITETERM site="i"> <PARAMETER name="mu#" default="mu"/> <PARAMETER name="U#" default="U"/> -mu#*n(i)+U#*n(i)*(n(i)-1)/2 </SITETERM> <BONDTERM source="i" target="j"> <PARAMETER name="t#" default="0"/> -t#*(bdag(i)*b(j)+bdag(j)*b(i)) </BONDTERM> <BONDTERM source="i" target="j"> <PARAMETER name="V#" default="0"/> -V#*(n(j)*n(i)) </BONDTERM> this in V=0 result: <SITETERM site="i"> <PARAMETER name="mu#" default="mu"/> <PARAMETER name="U#" default="U"/> -mu#*n(i)+U#*n(i)*(n(i)-1)/2 </SITETERM> <BONDTERM source="i" target="j"> <PARAMETER name="V#" default="0"/> -V#*(n(j)*n(i)) </BONDTERM> <BONDTERM source="i" target="j"> <PARAMETER name="t#" default="0"/> -t#*(bdag(i)*b(j)+bdag(j)*b(i)) </BONDTERM> Best, Mateusz Łącki

3 6

Re: [ALPS-users] Comp-phys-alps-users Digest, Vol 124, Issue 6
by Tadeusz Wasiutyński 28 Sep '16

28 Sep '16

Thank you Xiao Liang. Indeed compilation with gcc-5.4 goes smoothly while with 6.1 not. Now I have problems with openmpi: MPI_EXTRA_LIBRARY NOT FOUND Was this issue discussed earlier? Best regards Tadeusz 2016-07-25 12:00 GMT+02:00 <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. problem compiling alps-2.2.b4 (Tadeusz Wasiuty?ski) > 2. Re: problem compiling alps-2.2.b4 (??) > 3. question (Hocine Ahmed) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Sun, 24 Jul 2016 21:05:51 +0200 > From: Tadeusz Wasiuty?ski <tadeusz.wasiutynski(a)ifj.edu.pl> > To: comp-phys-alps-users(a)lists.phys.ethz.ch > Subject: [ALPS-users] problem compiling alps-2.2.b4 > Message-ID: > <CAKNmYXi5nOpvN=8QbBczCMe3q=smBH4cqYqby_Ww=XOp7EkwrQ@mail. > gmail.com> > Content-Type: text/plain; charset="utf-8" > > In the past I had no problems with compiling alps from source. Recently I > tried to compile it on Fedora 24 and failed. I noticed that the source does > not like boost 1.6 from Fedora, used native 1.58 from alps. Cmake result > looks good but make fails: > > cmake -D Boost_ROOT_DIR:PATH=~/alps-2.2.b4-src-with-boost/boost/ > -DCMAKE_INSTALL_PREFIX=$HOME/ALPS/ > LPSolve_LIBRARY=/usr/lib64/liblpsolve55.so -D > LPSolve_INCLUDE_DIR=/usr/include/lpsolve/ -D > HDF5_LIBRARIES=/usr/lib64/libhdf5.so -D HDF5_INCLUDE_DIR=/usr/include/ > ~/alps-2.2.b4-src-with-boost/alps/ > > -- Compiler version: c++ (GCC) 6.1.1 20160621 (Red Hat 6.1.1-3) > -- Build type: Release > -- Python interpreter /usr/bin/python > -- Python interpreter ok : version 2.7.12 > -- PYTHON_INCLUDE_DIRS = /usr/include/python2.7 > -- PYTHON_NUMPY_INCLUDE_DIR = > /usr/lib64/python2.7/site-packages/numpy/core/include > -- PYTHON_SITE_PKG = /usr/lib/python2.7/site-packages > -- PYTHON_LIBRARY = /usr/lib64/python2.7/config/libpython2.7.so > -- PYTHON_EXTRA_LIBS =-lpthread -ldl -lutil > -- PYTHON_LINK_FOR_SHARED = -Xlinker -export-dynamic > -- ALPS version: 2.2.b4 > -- Looking for Boost Source > -- Found Boost Source: /home/tadeusz/alps-2.2.b4-src-with-boost/boost > -- Boost Version: 1_58_0 > -- Adding Boost dir: /home/tadeusz/alps-2.2.b4-src-with-boost/boost > -- Could NOT find MPI_C (missing: MPI_C_LIBRARIES MPI_C_INCLUDE_PATH) > -- Could NOT find MPI_CXX (missing: MPI_CXX_LIBRARIES > MPI_CXX_INCLUDE_PATH) > -- MPI compiler was > -- Falling back to CMake provied LAPACK/BLAS detection. > -- A library with BLAS API found. > -- A library with BLAS API found. > -- A library with LAPACK API found. > -- Could NOT find SZIP (missing: SZIP_LIBRARIES SZIP_INCLUDE_DIRS) > -- Python interpreter /usr/bin/python > -- Python interpreter ok : version 2.7.12 > -- PYTHON_INCLUDE_DIRS = /usr/include/python2.7 > -- PYTHON_NUMPY_INCLUDE_DIR = > /usr/lib64/python2.7/site-packages/numpy/core/include > -- PYTHON_SITE_PKG = /usr/lib/python2.7/site-packages > -- PYTHON_LIBRARY = /usr/lib64/python2.7/config/libpython2.7.so > -- PYTHON_EXTRA_LIBS =-lpthread -ldl -lutil > -- PYTHON_LINK_FOR_SHARED = -Xlinker -export-dynamic > -- Numpy include in /usr/lib64/python2.7/site-packages/numpy/core/include > -- ALPS XML dir is /home/tadeusz/ALPS/lib/xml > -- MPS: enabling NU1 symmetry. > -- tebd will not be built > -- Configuring done > -- Generating done > -- Build files have been written to: /home/tadeusz/build > > > ?make result: > ?[ 65%] Building CXX object > applications/dmrg/dmrg/CMakeFiles/dmrg.dir/dmrg.C.o > In file included from /usr/include/python2.7/pyconfig.h:6:0, > from > /home/tadeusz/alps-2.2.b4-src-with-boost/boost/boost/python/ > detail/wrap_python.hpp:50, > from > /home/tadeusz/alps-2.2.b4-src-with-boost/boost/boost/python/ > detail/prefix.hpp:13, > from > /home/tadeusz/alps-2.2.b4-src-with-boost/boost/boost/python/args.hpp:8, > from > /home/tadeusz/alps-2.2.b4-src-with-boost/boost/boost/python.hpp:11, > from > /home/tadeusz/alps-2.2.b4-src-with-boost/alps/src/alps/alea/mcdata.hpp:79, > from > /home/tadeusz/alps-2.2.b4-src-with-boost/alps/src/alps/alea.h:34, > from > /home/tadeusz/alps-2.2.b4-src-with-boost/alps/src/alps/alea/ > observableset.h:49, > from > /home/tadeusz/alps-2.2.b4-src-with-boost/alps/src/alps/ > scheduler/montecarlo.h:40, > from > /home/tadeusz/alps-2.2.b4-src-with-boost/alps/src/alps/scheduler.h:31, > from > /home/tadeusz/alps-2.2.b4-src-with-boost/alps/applications/ > dmrg/dmrg/dmrg.C:31: > /usr/include/python2.7/pyconfig-64.h:1202:0: warning: "_POSIX_C_SOURCE" > redefined > #define _POSIX_C_SOURCE 200112L > --------------------------------------------- > In file included from /usr/include/c++/6.1.1/memory:81:0, > from > /home/tadeusz/alps-2.2.b4-src-with-boost/boost/boost/smart_ > ptr/scoped_ptr.hpp:21, > from > /home/tadeusz/alps-2.2.b4-src-with-boost/boost/boost/scoped_ptr.hpp:14, > from > /home/tadeusz/alps-2.2.b4-src-with-boost/boost/boost/smart_ptr.hpp:19, > from > /home/tadeusz/alps-2.2.b4-src-with-boost/alps/src/alps/osiris/dump.h:38, > from > /home/tadeusz/alps-2.2.b4-src-with-boost/alps/src/alps/ > scheduler/info.h:38, > from > /home/tadeusz/alps-2.2.b4-src-with-boost/alps/src/alps/ > scheduler/worker.h:35, > from > /home/tadeusz/alps-2.2.b4-src-with-boost/alps/src/alps/ > scheduler/task.h:41, > from > /home/tadeusz/alps-2.2.b4-src-with-boost/alps/src/alps/ > scheduler/factory.h:34, > from > /home/tadeusz/alps-2.2.b4-src-with-boost/alps/applications/ > dmrg/dmrg/factory.h:31, > from > /home/tadeusz/alps-2.2.b4-src-with-boost/alps/applications/ > dmrg/dmrg/factory.C:30: > /usr/include/c++/6.1.1/bits/unique_ptr.h:49:28: note: declared here > template<typename> class auto_ptr; > ^~~~~~~~ > applications/dmrg/dmrg/CMakeFiles/dmrg.dir/build.make:86: for > 'applications/dmrg/dmrg/CMakeFiles/dmrg.dir/factory.C.o' failed > make[2]: *** [applications/dmrg/dmrg/CMakeFiles/dmrg.dir/factory.C.o] > error > 1 > CMakeFiles/Makefile2:6096: polecenia dla obiektu > 'applications/dmrg/dmrg/CMakeFiles/dmrg.dir/all' failed > make[1]: *** [applications/dmrg/dmrg/CMakeFiles/dmrg.dir/all] error 2 > Makefile:160: polecenia dla obiektu 'all' failed > make: *** [all] error 2 > > ?Any suggestions? > Regards? > > -- > Tadeusz Wasiuty?ski >

1 0

SxSx Correlation function in DMRG - MPS
by Natanael de Carvalho Costa 05 Sep '16

05 Sep '16

Dear All, I'm using ALPS DMRG (MPS) to study the magnetism of XY model in a frustrated chain. In order to obtain the Sx correlation functions, I add the following command line: MEASURE_CORRELATIONS[Sx_correlation]= Sx I expected that the output file presented me all <Sx(i) Sx(j)> correlation functions. However, there were only this line in the output file. <SCALAR_AVERAGE name="Sx_correlation"><MEAN>6.7066684180584175e-317</MEAN></SCALAR_AVERAGE> Even when I chose to program make only specifics calculations, such as MEASURE_LOCAL_AT[SxSx_corr] = "Sx:Sx|(0,1),(0,2),(0,3),(0,4)" the answer I obtained was zero, no matter of the choice of the external parameters, as showed below. <VECTOR_AVERAGE name="SxSx_corr"> <SCALAR_AVERAGE indexvalue="( 0 ) -- ( 0 )"><MEAN>0</MEAN></SCALAR_AVERAGE> <SCALAR_AVERAGE indexvalue="( 0 ) -- ( 0 )"><MEAN>0</MEAN></SCALAR_AVERAGE> <SCALAR_AVERAGE indexvalue="( 0 ) -- ( 1 )"><MEAN>0</MEAN></SCALAR_AVERAGE> <SCALAR_AVERAGE indexvalue="( 0 ) -- ( 1 )"><MEAN>0</MEAN></SCALAR_AVERAGE> </VECTOR_AVERAGE> *(the index are not the same in the input and output file because I'm working with a unit cell with 3 sites.) Owing to these not good results, I did a test, and then I measured the correlation functions <Splus(i) Splus(j)>, <Splus(i) Sminus(j)> and <Sminus(i) Sminus(j)>, as showed below MEASURE_LOCAL_AT[SxSx_corr1] = "Splus:Splus|(3,18)" MEASURE_LOCAL_AT[SxSx_corr2] = "Splus:Sminus|(3,18)" MEASURE_LOCAL_AT[SxSx_corr3] = "Sminus:Splus|(3,18)" MEASURE_LOCAL_AT[SxSx_corr4] = "Sminus:Sminus|(3,18)" and I obtained <VECTOR_AVERAGE name="SxSx_corr1"> <SCALAR_AVERAGE indexvalue="( 1 ) -- ( 6 )"><MEAN>-0.1565028679350004</MEAN></SCALAR_AVERAGE> </VECTOR_AVERAGE> <VECTOR_AVERAGE name="SxSx_corr2"> <SCALAR_AVERAGE indexvalue="( 1 ) -- ( 6 )"><MEAN>-0.15912792472820933</MEAN></SCALAR_AVERAGE> </VECTOR_AVERAGE> <VECTOR_AVERAGE name="SxSx_corr3"> <SCALAR_AVERAGE indexvalue="( 1 ) -- ( 6 )"><MEAN>-0.15912792472820814</MEAN></SCALAR_AVERAGE> </VECTOR_AVERAGE> <VECTOR_AVERAGE name="SxSx_corr4"> <SCALAR_AVERAGE indexvalue="( 1 ) -- ( 6 )"><MEAN>-0.15650286793499901</MEAN></SCALAR_AVERAGE> </VECTOR_AVERAGE> which means that <SxSx>'s are really nonzero. Actually, these last results are in good agreement with exact diagonalization for a small chain. (Before you asked me, I correctly defined the onsite operator Sx in the model library.) Then, probably it could be a bug when the program is summing the terms of SxSx correlations. I really thank you for this great program. Regards, Natanael C. Costa

3 2

question about using alps on mac
by 刘东皓 22 Aug '16

22 Aug '16

I have two questions about using ALPS with python I have two macs with both installed alps from binary packages. When I use the *.py files in tutorials. (1) One shows "Fatal Python error PyThreadState_Get : no current thread" Abort trap :6 (2) The other mac has an error : "ImportError: No module named pymcdata_c" Can anyone help me Thanks -- 刘东皓（Donghao Liu） International Center for Quantum Materials(ICQM) Physics WestBuilding 618 Peking University No. 209 Chengfu Road, Haidian District Beijing, 100871, China

3 2

use MPS to calculate the correlation
by 北尘心 10 Aug '16

10 Aug '16

Dear all, I would like to use MPS to calculate the correlation of four operators .The correlation of four operators like this cdag_up(i):cdag_down(i+1):c_up(i+1):c_down(i+2) I use the following two ways to calculate,but the results of the two methods are opposite. The first method: In model file <SITEOPERATOR name="cdag_down__c_up" site="x"> cdag_down(x)*c_up(x) </SITEOPERATOR> In command file MEASURE_LOCAL_AT[cdag_up:cdag_down:c_up:c_down] = "cdag_up:cdag_down__c_up:c_down|(0,1,2)" another method: In model file <OPERATOR name="ca" matrixelement="1"> <CHANGE quantumnumber="Ndown" change="1"/> <CHANGE quantumnumber="Nup" change="-1"/> </OPERATOR> In command file MEASURE_LOCAL_AT[cdag_up:cdag_down:c_up:c_down] = "cdag_up:ca:c_down|(0,1,2)" I would like to know which method is correct and why the answers are opposite? It is highly grateful for your any suggestions. Yours sincerely, Xingbo Wei Zhejiang Normal Universtiy, Jinhua, 230014, China

1 0