July 2013 - Comp-phys-alps-users

Inconsistent comment in generate_spline_matrix in the DMFT folder
by Kuangshing Chen 22 Jul '15

22 Jul '15

Hi, The function generate_spline_matrix in fouriertransform.C in the dmft folder shows the comments as follows: // A is the matrix whose inverse defines spline_matrix // // 6 6 // 1 4 1 // 1 4 1 // A = ... // // 1 4 1 // -2 0 0 2 However, the following codes, dense_matrix A = 4*dt/6.*boost::numeric::ublas::identity_matrix<double>(Np1); for (int i=1; i<Np1-1; i++) { A(i,i-1) = dt/6.; A(i,i+1) = dt/6.; } A(0,0) = 1.; A(0, Np1-1) = 1.; A(Np1-1, 0) = -2.*dt/6.; A(Np1-1, 1) = -1.*dt/6.; A(Np1-1, Np1-2) = 1*dt/6.; A(Np1-1, Np1-1) = 2*dt/6.; the red lines will make the matrix looks like // 6 6 // 1 4 1 // 1 4 1 // A = ... // // 1 4 1 // -2 *-1* *1* 2 Is the comment correct or the code correct? Any reference for this algorithm? Thank you, Kuang-Shing Chen

5 25

Entropy calculations for classical model using Quantum-Wang-Landau
by Vipin Varma 02 Aug '13

02 Aug '13

Dear all, I am trying to use the Quantum-Wang-Landau (QWL) algorithm to calculate the entropy of a linear chain spin-1/2 model with Jxy=0 in a field h=1, which is classical but QWL seems to be suggested for entropy calculations. However with forty sites and down to low temperatures, I don't seem to be getting near the correct entropy density result of S ~ 0.4812 ... The parameter file is <<<<<<<<<<<<<<<<<<<<<<<<<< LATTICE="chain lattice" MODEL="spin" local_S=1/2 h=1 J = 1 Jxy = 0 CUTOFF = 500 {L=40} <<<<<<<<<<<<<<<<<<<<<<<<< and a partial output of entropy density versus temperature is <SNIP> </PARAMETERS> <legend show="true"/> <xaxis label="Temperature"/> <yaxis label="Entropy Density"/> <set label=""> <point><x>0.10000000000000001</x><y>0.065628773413218822</y></point> <point><x>0.20000000000000001</x><y>0.13394955300729872</y></point> <point><x>0.30000000000000004</x><y>0.24229259030929573</y></point> <point><x>0.40000000000000002</x><y>0.31481859757794478</y></point> <point><x>0.5</x><y>0.39826073000393336</y></point> <point><x>0.59999999999999998</x><y>0.46128739087861204</y></point> <point><x>0.69999999999999996</x><y>0.50938492873462538</y></point> <point><x>0.79999999999999993</x><y>0.5481023575910553</y></point> <point><x>0.89999999999999991</x><y>0.57776445729654646</y></point> <point><x>0.99999999999999989</x><y>0.59988758184662683</y></point> <point><x>1.0999999999999999</x><y>0.61635447545226674</y></point> <SNIP> I have tried changing the lattice length and cut-off but not much changes. Any advice on what I might be doing wrong will be greatly appreciated. With regards, Vipin

2 7

Re: [ALPS-users] Problem with having Sz conserved in TEBD quench
by Michael Wall 31 Jul '13

31 Jul '13

Hi Joseph, When you conserve Sz, you should include both 'CONSERVED_QUANTUMNUMBERS' : 'Sz' and the actual value of the magnetization desired, e.g. 'Sz' : 0.0 in the parms data. If you do not put any value for Sz then tebd will work in the sector with all spins up, as you described. -Michael Hello all again, > > I have been having a problem with my results for quenching a spin-1/2 XXZ > model in the TEBD code and both my colleagues and I are stumped. I am > attempting to study a quench from Delta = 4 to 2 in the XXZ model, starting > from the ground state of the original Hamiltonian, and looking at the local > magnetisation and correlation functions that result. I tried this out in > small systems (around L=32), following the tutorials very closely and > adapting them to my situation, and looking at the local magnetisation. When > I included S_z (the total S_z) as a conserved quantum number in my > parameters, I got no time dependence in my results, with each S_z being 1/2 > everywhere along the chain for every time, which seems to be nonsensical. > However, when I removed this constraint, I got (after a much longer > simulation) more sensible results, with a time-dependence and the results > being closer to 0. I am fairly certain that S_z should be conserved here, > so my question is why does this not seem to work? I followed the tutorials > very closely, and those scripts seem to work well enough. The parameter > section of my script is as follows: > > import pyalps > import matplotlib.pyplot as plt > import pyalps.plot > import numpy as np > import copy > > parms = [ { > 'L' : 32, > 'MODEL' : 'spin', > 'local_S' : 0.5, > 'Jxy' : 1, > 'Jz' : 4.0, > 'ITP_CHIS' : [40, 40, 40], > 'ITP_DTS' : [0.05, 0.05, 0.025], > 'ITP_CONVS' : [1E-9, 1E-9, 1E-10], > 'INITIAL_STATE' : 'ground', > 'CHI_LIMIT' : 40, > 'TRUNC_LIMIT' : 1E-12, > 'NUM_THREADS' : 1, > 'TAUS' : [0.0, 50.0], > 'POWS' : [0.0, 1.0], > 'GS' : ['Jz', 'Jz'], > 'GIS' : [4.0, 2.0], > 'GFS' : [2.0, 2.0], > 'NUMSTEPS' : [100, 2500], > 'STEPSFORSTORE' : [5, 5] > } ] > > baseName = 'Jz4to2Quench1L32' > nmlname = pyalps.writeTEBDfiles(parms, baseName) > res = pyalps.runTEBD(nmlname) > > Data = pyalps.load.loadTimeEvolution(pyalps.getResultFiles(prefix = > 'Jz4to2Quench1L32'), measurements = ['Local Magnetization']) > > Any help would be greatly appreciated, as my simulations would be much > faster if I could include this! > > Thanks, > > Joseph Prentice > >

1 0

Problem with having Sz conserved in TEBD quench
by Joseph Prentice 31 Jul '13

31 Jul '13

Hello all again, I have been having a problem with my results for quenching a spin-1/2 XXZ model in the TEBD code and both my colleagues and I are stumped. I am attempting to study a quench from Delta = 4 to 2 in the XXZ model, starting from the ground state of the original Hamiltonian, and looking at the local magnetisation and correlation functions that result. I tried this out in small systems (around L=32), following the tutorials very closely and adapting them to my situation, and looking at the local magnetisation. When I included S_z (the total S_z) as a conserved quantum number in my parameters, I got no time dependence in my results, with each S_z being 1/2 everywhere along the chain for every time, which seems to be nonsensical. However, when I removed this constraint, I got (after a much longer simulation) more sensible results, with a time-dependence and the results being closer to 0. I am fairly certain that S_z should be conserved here, so my question is why does this not seem to work? I followed the tutorials very closely, and those scripts seem to work well enough. The parameter section of my script is as follows: import pyalps import matplotlib.pyplot as plt import pyalps.plot import numpy as np import copy parms = [ { 'L' : 32, 'MODEL' : 'spin', 'local_S' : 0.5, 'Jxy' : 1, 'Jz' : 4.0, 'ITP_CHIS' : [40, 40, 40], 'ITP_DTS' : [0.05, 0.05, 0.025], 'ITP_CONVS' : [1E-9, 1E-9, 1E-10], 'INITIAL_STATE' : 'ground', 'CHI_LIMIT' : 40, 'TRUNC_LIMIT' : 1E-12, 'NUM_THREADS' : 1, 'TAUS' : [0.0, 50.0], 'POWS' : [0.0, 1.0], 'GS' : ['Jz', 'Jz'], 'GIS' : [4.0, 2.0], 'GFS' : [2.0, 2.0], 'NUMSTEPS' : [100, 2500], 'STEPSFORSTORE' : [5, 5] } ] baseName = 'Jz4to2Quench1L32' nmlname = pyalps.writeTEBDfiles(parms, baseName) res = pyalps.runTEBD(nmlname) Data = pyalps.load.loadTimeEvolution(pyalps.getResultFiles(prefix = 'Jz4to2Quench1L32'), measurements = ['Local Magnetization']) Any help would be greatly appreciated, as my simulations would be much faster if I could include this! Thanks, Joseph Prentice

1 0

Re: [ALPS-users] Possible Measurements in TEBD code
by Joseph Prentice 30 Jul '13

30 Jul '13

Hi Michael, Brilliant, that's just what I needed! Thank you very much. Joseph On 30 Jul 2013, at 11:00, <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. Possible Measurements in TEBD code (Joseph Prentice) > 2. Re: Possible Measurements in TEBD code (Michael Wall) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Mon, 29 Jul 2013 10:02:01 +0000 > From: Joseph Prentice <Joseph.Prentice(a)physics.ox.ac.uk> > To: "comp-phys-alps-users(a)lists.phys.ethz.ch" > <comp-phys-alps-users(a)lists.phys.ethz.ch> > Subject: [ALPS-users] Possible Measurements in TEBD code > Message-ID: > <747861816F6A5C47BE50FCA07F5B2B4A0DD609(a)EXCHNG16.physics.ox.ac.uk> > Content-Type: text/plain; charset="us-ascii" > > Hi all, > > I'm attempting to look at spin correlation functions, both nearest neighbour and next nearest neighbour, near the centre of an XXZ chain that is undergoing a quench using the TEBD code. As far as I can tell from the documentation, these measurements are hardcoded in to the TEBD code, but the documentation gives no clue on how to access them. In effect, what I would like to know is what can I write into the following line of Python (taken from the second TEBD tutorial): > Data = pyalps.load.loadTimeEvolution(pyalps.getResultFiles(prefix='tutorial_2a'), measurements=['Local Magnetization']) > instead of 'Local Magnetization', in order to obtain the correlation functions, and also how I could then define which sites the correlation function will be calculated using. I think a question similar to this was asked in January, but there was no answer. > > Thank you very much in advance! > Joseph Prentice > > ------------------------------ > > Message: 2 > Date: Mon, 29 Jul 2013 20:23:15 -0600 > From: Michael Wall <mwall.physics(a)gmail.com> > To: comp-phys-alps-users(a)lists.phys.ethz.ch, Lincoln Carr > <lcarr(a)mines.edu>, "ebekarog(a)mines.edu" <ebekarog(a)mines.edu> > Subject: Re: [ALPS-users] Possible Measurements in TEBD code > Message-ID: > <CA+DwVMoxud1UCTkCHgGLXYfDDW8V0mZR_ky=B2jA7zR2Ny6S1A(a)mail.gmail.com> > Content-Type: text/plain; charset="iso-8859-1" > > Hi Joseph, > > Indeed, the measurements are hardcoded in the present version of the code. > You can determine the syntax of the outputs by looking at one of the > output *.h5 files. There's too many to list here, so I've attached a > screenshot. For the correlation functions which are computed, they are > computed for all pairs of sites i and j and returned as a matrix. Hope > this helps. > > -Michael > [image: Inline image 1] > > Hi all, >> I'm attempting to look at spin correlation functions, both nearest >> neighbour and next nearest neighbour, near the centre of an XXZ chain that >> is undergoing a quench using the TEBD code. As far as I can tell from the >> documentation, these measurements are hardcoded in to the TEBD code, but >> the documentation gives no clue on how to access them. In effect, what I >> would like to know is what can I write into the following line of Python >> (taken from the second TEBD tutorial): >> Data = >> pyalps.load.loadTimeEvolution(pyalps.getResultFiles(prefix='tutorial_2a'), >> measurements=['Local Magnetization']) >> instead of 'Local Magnetization', in order to obtain the correlation >> functions, and also how I could then define which sites the correlation >> function will be calculated using. I think a question similar to this was >> asked in January, but there was no answer. >> Thank you very much in advance! >> Joseph Prentice >

1 0

Re: [ALPS-users] Possible Measurements in TEBD code
by Michael Wall 30 Jul '13

30 Jul '13

Hi Joseph, Indeed, the measurements are hardcoded in the present version of the code. You can determine the syntax of the outputs by looking at one of the output *.h5 files. There's too many to list here, so I've attached a screenshot. For the correlation functions which are computed, they are computed for all pairs of sites i and j and returned as a matrix. Hope this helps. -Michael [image: Inline image 1] Hi all, > I'm attempting to look at spin correlation functions, both nearest > neighbour and next nearest neighbour, near the centre of an XXZ chain that > is undergoing a quench using the TEBD code. As far as I can tell from the > documentation, these measurements are hardcoded in to the TEBD code, but > the documentation gives no clue on how to access them. In effect, what I > would like to know is what can I write into the following line of Python > (taken from the second TEBD tutorial): > Data = > pyalps.load.loadTimeEvolution(pyalps.getResultFiles(prefix='tutorial_2a'), > measurements=['Local Magnetization']) > instead of 'Local Magnetization', in order to obtain the correlation > functions, and also how I could then define which sites the correlation > function will be calculated using. I think a question similar to this was > asked in January, but there was no answer. > Thank you very much in advance! > Joseph Prentice

1 0

Possible Measurements in TEBD code
by Joseph Prentice 29 Jul '13

29 Jul '13

Hi all, I'm attempting to look at spin correlation functions, both nearest neighbour and next nearest neighbour, near the centre of an XXZ chain that is undergoing a quench using the TEBD code. As far as I can tell from the documentation, these measurements are hardcoded in to the TEBD code, but the documentation gives no clue on how to access them. In effect, what I would like to know is what can I write into the following line of Python (taken from the second TEBD tutorial): Data = pyalps.load.loadTimeEvolution(pyalps.getResultFiles(prefix='tutorial_2a'), measurements=['Local Magnetization']) instead of 'Local Magnetization', in order to obtain the correlation functions, and also how I could then define which sites the correlation function will be calculated using. I think a question similar to this was asked in January, but there was no answer. Thank you very much in advance! Joseph Prentice

1 0

"forming reference to void" error building ALPS
by Jonathan Patterson 25 Jul '13

25 Jul '13

I tried to build both: alps-2.1.1-r6176-src-with-boost alps-2.1.2-r6963-src-with-boost If that isn't what you mean by "What version of ALPS did you try to build?" then can you clarify? On 24/07/13 11:00, 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. "forming reference to void" error building ALPS > (Jonathan Patterson) > 2. Re: "forming reference to void" error building ALPS > (Matthias Troyer) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Tue, 23 Jul 2013 20:53:26 +0100 > From: Jonathan Patterson <jop(a)astro.ox.ac.uk> > To: <comp-phys-alps-users(a)lists.phys.ethz.ch> > Subject: [ALPS-users] "forming reference to void" error building ALPS > Message-ID: <51EEDF36.5070705(a)astro.ox.ac.uk> > Content-Type: text/plain; charset="ISO-8859-1" > > > Hi! > Firstly, sorry - I must be doing something wrong, but I can't see what. I've tried > alps-2.1.1-r6176-src-with-boost > alps-2.1.2-r6963-src-with-boost > with gcc 4.1.2, gcc 4.7.2, Intel compilers 11.1 > Each time I get a variation of the following error when compiling: > alps-2.1.1-r6176-src-with-boost/alps/src/alps/lattice/latticelibrary.C:147:59: required from here > alps-2.1.1-r6176-src-with-boost/alps/src/alps/lattice/propertymap.h:212:13: error: forming reference to void > I'm using the following to setup the build. Anyone got any ideas what's going wrong please? Thank you. > > ~jop/installed/cmake/cmake-2.8.8/bin/cmake -D FFTW_INCLUDE_DIR=/usr/local/shared/fftw3.3.3/include -D FFTW_LIBRARIES=/usr/local/shared/fftw3.3.3/lib/libfftw3.so.3 -D ALPS_BUILD_FORTRAN=ON -D ALPS_ENABLE_OPENMP=ON -D CMAKE_INSTALL_PREFIX=/usr/local/shared/alps-2.1.1 -D BLAS_LIBRARY=/usr/local/shared/lapack-3.4.1-gfortran/libblas.a -D LAPACK_LIBRARY=/usr/local/shared/lapack-3.4.1/liblapack.a -D PYTHON_INTERPRETER=/usr/local/shared/bin/python27fpic -D CMAKE_C_COMPILER=gcc472 -D CMAKE_Fortran_COMPILER=gfortran472 -D CMAKE_CXX_COMPILER=g++472 -D HDF5_INCLUDE_DIR=/usr/local/shared/hdf5-1.8.10/include -D HDF5_STATIC_LIBRARIES=/usr/local/shared/hdf5-1.8.10/lib/libhdf5.a -D HDF5_LIBRARIES=/usr/local/shared/hdf5-1.8.10/lib/libhdf5.so.7 -D Boost_ROOT_DIR:PATH=/usersVol2/jop/installed/alps/alps-2.1.2-r6963-src-with-boost/boost/ /usersVol2/jop/installed/alps/alps-2.1.1-r6176-src-with-boost/alps/ > > > > ------------------------------ > > Message: 2 > Date: Tue, 23 Jul 2013 13:54:52 -0600 > From: Matthias Troyer <troyer(a)phys.ethz.ch> > To: comp-phys-alps-users(a)lists.phys.ethz.ch > Subject: Re: [ALPS-users] "forming reference to void" error building > ALPS > Message-ID: <94EA1D75-1070-47AB-813E-3EF8443E5F21(a)phys.ethz.ch> > Content-Type: text/plain; charset=iso-8859-1 > > What version of ALPS do you try to build? > > On Jul 23, 2013, at 1:53 PM, Jonathan Patterson <jop(a)astro.ox.ac.uk> wrote: > >> >> Hi! >> Firstly, sorry - I must be doing something wrong, but I can't see what. I've tried >> alps-2.1.1-r6176-src-with-boost >> alps-2.1.2-r6963-src-with-boost >> with gcc 4.1.2, gcc 4.7.2, Intel compilers 11.1 >> Each time I get a variation of the following error when compiling: >> alps-2.1.1-r6176-src-with-boost/alps/src/alps/lattice/latticelibrary.C:147:59: required from here >> alps-2.1.1-r6176-src-with-boost/alps/src/alps/lattice/propertymap.h:212:13: error: forming reference to void >> I'm using the following to setup the build. Anyone got any ideas what's going wrong please? Thank you. >> >> ~jop/installed/cmake/cmake-2.8.8/bin/cmake -D FFTW_INCLUDE_DIR=/usr/local/shared/fftw3.3.3/include -D FFTW_LIBRARIES=/usr/local/shared/fftw3.3.3/lib/libfftw3.so.3 -D ALPS_BUILD_FORTRAN=ON -D ALPS_ENABLE_OPENMP=ON -D CMAKE_INSTALL_PREFIX=/usr/local/shared/alps-2.1.1 -D BLAS_LIBRARY=/usr/local/shared/lapack-3.4.1-gfortran/libblas.a -D LAPACK_LIBRARY=/usr/local/shared/lapack-3.4.1/liblapack.a -D PYTHON_INTERPRETER=/usr/local/shared/bin/python27fpic -D CMAKE_C_COMPILER=gcc472 -D CMAKE_Fortran_COMPILER=gfortran472 -D CMAKE_CXX_COMPILER=g++472 -D HDF5_INCLUDE_DIR=/usr/local/shared/hdf5-1.8.10/include -D HDF5_STATIC_LIBRARIES=/usr/local/shared/hdf5-1.8.10/lib/libhdf5.a -D HDF5_LIBRARIES=/usr/local/shared/hdf5-1.8.10/lib/libhdf5.so.7 -D Boost_ROOT_DIR:PATH=/usersVol2/jop/installed/alps/alps-2.1.2-r6963-src-with-boost/boost/ /usersVol2/jop/installed/alps/alps-2.1.1-r6176-src-with-boost/alps/ >> > > > > End of Comp-phys-alps-users Digest, Vol 88, Issue 8 > *************************************************** >

2 4

Re: [ALPS-users] Comp-phys-alps-users Digest, Vol 88, Issue 8
by Jonathan Patterson 24 Jul '13

24 Jul '13

I tried to build both: alps-2.1.1-r6176-src-with-boost alps-2.1.2-r6963-src-with-boost If that isn't what you mean by "What version of ALPS did you try to build?" then can you clarify? > Date: Tue, 23 Jul 2013 13:54:52 -0600 > From: Matthias Troyer <troyer(a)phys.ethz.ch> > To: comp-phys-alps-users(a)lists.phys.ethz.ch > Subject: Re: [ALPS-users] "forming reference to void" error building > ALPS > Message-ID: <94EA1D75-1070-47AB-813E-3EF8443E5F21(a)phys.ethz.ch> > Content-Type: text/plain; charset=iso-8859-1 > > What version of ALPS do you try to build? > > On Jul 23, 2013, at 1:53 PM, Jonathan Patterson <jop(a)astro.ox.ac.uk> wrote: > >> >> Hi! >> Firstly, sorry - I must be doing something wrong, but I can't see what. I've tried >> alps-2.1.1-r6176-src-with-boost >> alps-2.1.2-r6963-src-with-boost >> with gcc 4.1.2, gcc 4.7.2, Intel compilers 11.1 >> Each time I get a variation of the following error when compiling: >> alps-2.1.1-r6176-src-with-boost/alps/src/alps/lattice/latticelibrary.C:147:59: required from here >> alps-2.1.1-r6176-src-with-boost/alps/src/alps/lattice/propertymap.h:212:13: error: forming reference to void >> I'm using the following to setup the build. Anyone got any ideas what's going wrong please? Thank you. >> >> ~jop/installed/cmake/cmake-2.8.8/bin/cmake -D FFTW_INCLUDE_DIR=/usr/local/shared/fftw3.3.3/include -D FFTW_LIBRARIES=/usr/local/shared/fftw3.3.3/lib/libfftw3.so.3 -D ALPS_BUILD_FORTRAN=ON -D ALPS_ENABLE_OPENMP=ON -D CMAKE_INSTALL_PREFIX=/usr/local/shared/alps-2.1.1 -D BLAS_LIBRARY=/usr/local/shared/lapack-3.4.1-gfortran/libblas.a -D LAPACK_LIBRARY=/usr/local/shared/lapack-3.4.1/liblapack.a -D PYTHON_INTERPRETER=/usr/local/shared/bin/python27fpic -D CMAKE_C_COMPILER=gcc472 -D CMAKE_Fortran_COMPILER=gfortran472 -D CMAKE_CXX_COMPILER=g++472 -D HDF5_INCLUDE_DIR=/usr/local/shared/hdf5-1.8.10/include -D HDF5_STATIC_LIBRARIES=/usr/local/shared/hdf5-1.8.10/lib/libhdf5.a -D HDF5_LIBRARIES=/usr/local/shared/hdf5-1.8.10/lib/libhdf5.so.7 -D Boost_ROOT_DIR:PATH=/usersVol2/jop/installed/alps/alps-2.1.2-r6963-src-with-boost/boost/ /usersVol2/jop/installed/alps/alps-2.1.1-r6176-src-with-boost/alps/ >> > > > > End of Comp-phys-alps-users Digest, Vol 88, Issue 8 > *************************************************** >

1 0

"forming reference to void" error building ALPS
by Jonathan Patterson 23 Jul '13

23 Jul '13

Hi! Firstly, sorry - I must be doing something wrong, but I can't see what. I've tried alps-2.1.1-r6176-src-with-boost alps-2.1.2-r6963-src-with-boost with gcc 4.1.2, gcc 4.7.2, Intel compilers 11.1 Each time I get a variation of the following error when compiling: alps-2.1.1-r6176-src-with-boost/alps/src/alps/lattice/latticelibrary.C:147:59: required from here alps-2.1.1-r6176-src-with-boost/alps/src/alps/lattice/propertymap.h:212:13: error: forming reference to void I'm using the following to setup the build. Anyone got any ideas what's going wrong please? Thank you. ~jop/installed/cmake/cmake-2.8.8/bin/cmake -D FFTW_INCLUDE_DIR=/usr/local/shared/fftw3.3.3/include -D FFTW_LIBRARIES=/usr/local/shared/fftw3.3.3/lib/libfftw3.so.3 -D ALPS_BUILD_FORTRAN=ON -D ALPS_ENABLE_OPENMP=ON -D CMAKE_INSTALL_PREFIX=/usr/local/shared/alps-2.1.1 -D BLAS_LIBRARY=/usr/local/shared/lapack-3.4.1-gfortran/libblas.a -D LAPACK_LIBRARY=/usr/local/shared/lapack-3.4.1/liblapack.a -D PYTHON_INTERPRETER=/usr/local/shared/bin/python27fpic -D CMAKE_C_COMPILER=gcc472 -D CMAKE_Fortran_COMPILER=gfortran472 -D CMAKE_CXX_COMPILER=g++472 -D HDF5_INCLUDE_DIR=/usr/local/shared/hdf5-1.8.10/include -D HDF5_STATIC_LIBRARIES=/usr/local/shared/hdf5-1.8.10/lib/libhdf5.a -D HDF5_LIBRARIES=/usr/local/shared/hdf5-1.8.10/lib/libhdf5.so.7 -D Boost_ROOT_DIR:PATH=/usersVol2/jop/installed/alps/alps-2.1.2-r6963-src-with-boost/boost/ /usersVol2/jop/installed/alps/alps-2.1.1-r6176-src-with-boost/alps/

2 1