Comp-phys-alps-users July 2010

comp-phys-alps-users@lists.phys.ethz.ch

8 participants
12 discussions

Problems with worms??
by Jakub Zakrzewski 27 Oct '10

27 Oct '10

Hello, Sometimes QMC worm code (used on Bose-Hubbard) terminates with the following error: here come first earlier succesful simulations then ... Created run 85 remote on Host ID: 84 Created run 86 remote on Host ID: 85 Created run 87 remote on Host ID: 86 Created run 88 remote on Host ID: 87 All processes have been assigned Checking if Simulation 1 is finished: not yet, next check in 120 seconds ( 0% done). q = -0 state1 = 0 state2 = 0 bond_type = 0 zero matrix element in remove_jump application called MPI_Abort(MPI_COMM_WORLD, -2) - process 67 Could somebody advice what I can do? Best regards Kuba

2 2

[help] cannot compute local magnetization in ED
by jun wen 10 Aug '10

10 Aug '10

Hello All, I was trying to compute the local <S> in the Kitaev model defined on the honeycomb lattice with Exact Diagnolization Here is my parameter file: MODEL="kitaev"; LATTICE="honeycomb lattice"; LATTICE_LIBRARY="../../../definitions/kitaev/lattices.xml"; MODEL_LIBRARY="../../../definitions/kitaev/models.xml"; MEASURE_LOCAL[Local Sz]=Sz; MEASURE_LOCAL[Local Sx]=Sx; MEASURE_LOCAL[Local Sy]=Sy; local_S=1/2; L=2; W=2; J=1; However, in the output xml file, there are no such terms as the Local Sz or Local Splux or Local Sminus. I wonder if anyone could kindly point out what is the problem. The Kitaev model is defined in the following models.xml Thanks a lot! <MODELS> <SITEBASIS name="spin"> <PARAMETER name="local_spin" default="local_S"/> <PARAMETER name="local_S" default="1/2"/> <QUANTUMNUMBER name="S" min="local_spin" max="local_spin"/> <QUANTUMNUMBER name="Sz" min="-S" max="S"/> <OPERATOR name="Splus" matrixelement="sqrt(S*(S+1)-Sz*(Sz+1))"> <CHANGE quantumnumber="Sz" change="1"/> </OPERATOR> <OPERATOR name="Sminus" matrixelement="sqrt(S*(S+1)-Sz*(Sz-1))"> <CHANGE quantumnumber="Sz" change="-1"/> </OPERATOR> <OPERATOR name="Sz" matrixelement="Sz"/> </SITEBASIS> <SITEOPERATOR name="Sx" site="x"> 1/2*(Splus(x)+Sminus(x)) </SITEOPERATOR> <SITEOPERATOR name="Sy" site="x"> 1/2/I*(Splus(x)-Sminus(x)) </SITEOPERATOR> <BASIS name="spin"> <SITEBASIS ref="spin"/> </BASIS> <HAMILTONIAN name="kitaev"> <PARAMETER name="J1" default="1"/> <PARAMETER name="Jz" default="J1"/> <PARAMETER name="Jx" default="J1"/> <PARAMETER name="Jy" default="J1"/> <BASIS ref="spin"/> <BONDTERM type="0" source="i" target="j"> Jz*Sz(i)*Sz(j) </BONDTERM> <BONDTERM type="1" source="i" target="j"> Jx*Sx(i)*Sx(j) </BONDTERM> <BONDTERM type="2" source="i" target="j"> Jy*Sy(i)*Sy(j) </BONDTERM> </HAMILTONIAN> </MODELS> Jun

5 11

Re: [ALPS-users] dmrg errors
by sebastian.greschner＠itp.uni-hannover.de 01 Aug '10

01 Aug '10

Hi Matthias, it seems to me that the segfaults occur for lattices with different types of vertices. For example, if I add fields at the beginning and the end of a Heisenberg-chain, I get segmentation faults for the following parameter file LATTICE_LIBRARY="mychain.xml" LATTICE="my open chain lattice N=16" MODEL="spin" NUMBER_EIGENVALUES=1 SWEEPS=4 COMPLEX=1 L=16 h0=1.5 h1=0.0 h2=1.5 MEASURE_LOCAL[Sz]=Sz {MAXSTATES=20} Strangely, if I change some parameters, for example set h0 and h2=1.0 or VERBOSE=1 everything works fine... Here mychain.xml just defines an open chain with edge-fields: <LATTICES> <GRAPH name = "my open chain lattice N=16" dimension="1" vertices="16" edges="15"> <VERTEX id="1" type="0"><COORDINATE>0</COORDINATE></VERTEX> <VERTEX id="2" type="1"><COORDINATE>1</COORDINATE></VERTEX> <VERTEX id="3" type="1"><COORDINATE>2</COORDINATE></VERTEX> <VERTEX id="4" type="1"><COORDINATE>3</COORDINATE></VERTEX> <VERTEX id="5" type="1"><COORDINATE>4</COORDINATE></VERTEX> <VERTEX id="6" type="1"><COORDINATE>5</COORDINATE></VERTEX> <VERTEX id="7" type="1"><COORDINATE>6</COORDINATE></VERTEX> <VERTEX id="8" type="1"><COORDINATE>7</COORDINATE></VERTEX> <VERTEX id="9" type="1"><COORDINATE>8</COORDINATE></VERTEX> <VERTEX id="10" type="1"><COORDINATE>9</COORDINATE></VERTEX> <VERTEX id="11" type="1"><COORDINATE>10</COORDINATE></VERTEX> <VERTEX id="12" type="1"><COORDINATE>11</COORDINATE></VERTEX> <VERTEX id="13" type="1"><COORDINATE>12</COORDINATE></VERTEX> <VERTEX id="14" type="1"><COORDINATE>13</COORDINATE></VERTEX> <VERTEX id="15" type="1"><COORDINATE>14</COORDINATE></VERTEX> <VERTEX id="16" type="2"><COORDINATE>15</COORDINATE></VERTEX> <EDGE source="1" target="2" id="1" type="0" vector="1"/> <EDGE source="2" target="3" id="2" type="0" vector="1"/> <EDGE source="3" target="4" id="3" type="0" vector="1"/> <EDGE source="4" target="5" id="4" type="0" vector="1"/> <EDGE source="5" target="6" id="5" type="0" vector="1"/> <EDGE source="6" target="7" id="6" type="0" vector="1"/> <EDGE source="7" target="8" id="7" type="0" vector="1"/> <EDGE source="8" target="9" id="8" type="0" vector="1"/> <EDGE source="9" target="10" id="9" type="0" vector="1"/> <EDGE source="10" target="11" id="10" type="0" vector="1"/> <EDGE source="11" target="12" id="11" type="0" vector="1"/> <EDGE source="12" target="13" id="12" type="0" vector="1"/> <EDGE source="13" target="14" id="13" type="0" vector="1"/> <EDGE source="14" target="15" id="14" type="0" vector="1"/> <EDGE source="15" target="16" id="15" type="0" vector="1"/> </GRAPH> </LATTICES> Can you reproduce this error?! Sebastian On 23/07/10 15:23, Matthias Troyer wrote: > Hi Sebastian, > > can you please post an example parameter file that segfaults at the > beginning? > > Matthias > > On 23 Jul 2010, at 03:53, Sebastian Greschner wrote: > >> Hi Matthias, >> >> Thank you - now dmrg gives the correct results! >> >> Unfortunately there is still one (but probably unrelated) problem with >> dmrg (I am working on a Debian Lenny system - Intel Xeon): Depending on >> the parameters I choose (some special model parameters, Number of >> MAXSTATES, etc.) in the parameter file, I sometimes get segmentation >> faults at the beginning or at the end. Sorry - I haven't figured out >> yet, when this happens exactly, but maybe somebody has observed similar >> errors... >> >> Best, >> Sebastian >> >> On 22/07/10 17:25, Matthias Troyer wrote: >>> >>> On 22 Jul 2010, at 05:33, Sebastian Greschner wrote: >>> >>>> Hi, >>>> >>>> I am having some trouble with the dmrg-program (e.g. of current ALPS >>>> 2.0b3) and "complex-valued" models. >>>> It seems to me that dmrg ignores the imaginary part of model-parameters >>>> (even with COMPLEX set to true). "sparsediag" gives the correct results. >>>> >>>> Is this a bug or a general restriction of the dmrg-program? Or is it >>>> just a problem of my model or my local installation? >>>> >>>> Thanks in advance and greetings, >>>> Sebastian >>>> >>> >>> >>> Hi Sebastian, >>> >>> I fixed one bug and the fix will show up in the MacOS and source >>> versions of thennext nightly snapshot (Friday morning). Can you >>> please try that? >>> >>> Matthias >>> >>> >> > >

2 1

generalized susceptibility in loop algorithm
by Kubila 28 Jul '10

28 Jul '10

Hi all Currently I am studying spin-1/2 XY model using the loop algorithm in ALPS. The staggered susceptibility measured using the loop algorithm does not grow with space-time volume. On the other hand, the generalized susceptibility measured using the loop algorithm seems to scale with space-time volume. I was wondering is the generalized susceptibility exactly the correlator of the X-component of the staggered magnetization M_s = \sum_{x} (-1)^{x_1+x_2}\vec{S}_x?, here \vec{S}_x is the spin-1/2 operator at site x. Also is the z-direction the quantized direction in the loop algorithm? Thanks in advance. kubila

2 1

Poor results with QWL
by Miles Stoudenmire 28 Jul '10

28 Jul '10

Hi, I would like to use the Quantum Wang-Landau app to obtain some benchmark results for the free energy of a spin chain. To make sure I understood the parameters I decided to do the two-qubit Heisenberg model first (with open BC's). Unfortunately, no matter how I adjust the parameters the resulting energies seem quite poor compared to my exact calcuation in Mathematica. To be more specific, I've been adjusting the CUTOFF parameter to between 100-1000 and the number of WL steps from 16-25. The results I've been seeing are energies around -0.3 at the lowest T's (where E~-0.75 in fact) and a wide variance in energies at the highest T's, often more than 30% off the actual value. Thanks for any help! -- -=Miles Stoudenmire=- miles.stoudenmire(a)gmail.com

2 2

Complex numbers
by Sebastian Greschner 23 Jul '10

23 Jul '10

Hi, when I try to define a complex Hamiltonian (e.g. some extended Heisenberg-model with Sx _and_ Sy=-I/2(Splus-Sminus) couplings to external fields) fulldiag or other ALPS-programs end with the error "can not convert complex number into real one" Is this a general restriction for ALPS, or did I miss some configuration or compile option? If not - do you know any patch or work-around to enable complex-numbers? Thanks in advance and greetings, Sebastian

2 5

Trouble getting lp_solve to work with ALPS 2.0.0b3
by Brian Koopman 20 Jul '10

20 Jul '10

Hello everyone, I am having trouble getting lp_solve working with ALPS 2.0.0b3. I have downloaded the alps-2.0.0b3-r4750-src-with-boost.tar.gz as well as the lp_solve_5.1_source.tar.gz files from the ALPS wiki. Digging through lp_solve_5.1/ I found lpsolve51/ which contains instructions to build the library using $ sh ccc. I get the following output: $ sh ccc ../commonlib.c: In function blockWriteINT: ../commonlib.c:459: warning: format not a string literal and no format arguments ../commonlib.c: In function blockWriteBOOL: ../commonlib.c:478: warning: format not a string literal and no format arguments ../commonlib.c: In function blockWriteREAL: ../commonlib.c:500: warning: format not a string literal and no format arguments ../lp_report.c: In function blockWriteLREAL: ../lp_report.c:161: warning: format not a string literal and no format arguments ../lp_report.c: In function blockWriteAMAT: ../lp_report.c:190: warning: format not a string literal and no format arguments ../lp_report.c: In function blockWriteBMAT: ../lp_report.c:242: warning: format not a string literal and no format arguments ar: creating liblpsolve51.a a - lp_MDO.o a - commonlib.o a - myblas.o a - fortify.o a - colamd.o a - lp_rlp.o a - lp_crash.o a - lp_etaPFI.o a - lp_Hash.o a - lp_lib.o a - lp_wlp.o a - lp_matrix.o a - lp_mipbb.o a - lp_MPS.o a - lp_presolve.o a - lp_price.o a - lp_pricePSE.o a - lp_report.o a - lp_scale.o a - lp_simplex.o a - lp_SOS.o a - lp_utils.o a - yacc_read.o ../commonlib.c: In function blockWriteINT: ../commonlib.c:459: warning: format not a string literal and no format arguments ../commonlib.c: In function blockWriteBOOL: ../commonlib.c:478: warning: format not a string literal and no format arguments ../commonlib.c: In function blockWriteREAL: ../commonlib.c:500: warning: format not a string literal and no format arguments ../lp_report.c: In function blockWriteLREAL: ../lp_report.c:161: warning: format not a string literal and no format arguments ../lp_report.c: In function blockWriteAMAT: ../lp_report.c:190: warning: format not a string literal and no format arguments ../lp_report.c: In function blockWriteBMAT: ../lp_report.c:242: warning: format not a string literal and no format arguments I included that output because I don't have a lot of compiling experience and I don't know what those warnings really mean. But it appears the library has compiled to me. ~/lp_solve_5.1/lpsolve51$ ls ccc ccc.osx dll.sln liblpsolve51.so lpsolve.rc ccc.hp-ux cgcc.bat dll.vcproj lib.sln readme.txt cccLUSOL.osx cvc6.bat liblpsolve51.a lib.vcproj resource.h Now where should this library be put? I've tried many variations of /usr/lib/ and /lib/ but everytime I run cmake I get this output: $ cmake /home/magnet/alps-2.0.0b3-r4750-src-with-boost/alps/ -- Build type: Release -- Python interpreter /usr/bin/python -- Python interpreter ok : version 2.6.5 -- PYTHON_INCLUDE_DIRS = /usr/include/python2.6 -- PYTHON_NUMPY_INCLUDE_DIR = /usr/lib/python2.6/dist-packages/numpy/core/include -- PYTHON_SITE_PKG = /usr/lib/python2.6/dist-packages -- PYTHON_LIBRARY = /usr/lib/python2.6/config/libpython2.6.so -- PYTHON_EXTRA_LIBS =-lssl -lcrypto -lssl -lcrypto -L/usr/lib -lz -lpthread -ldl -lutil -- PYTHON_LINK_FOR_SHARED = -Xlinker -export-dynamic -Wl,-O1 -Wl,-Bsymbolic-functions -- ALPS version: 2.0.0b3 -- Looking for Boost Source -- Found Boost Source: /home/magnet/alps-2.0.0b3-r4750-src-with-boost/boost -- Boost Version: 1_43_0 -- Could NOT find MPI (missing: MPI_LIBRARY MPI_INCLUDE_PATH) 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 -- LPSolve Library: not found -- Could NOT find SZIP (missing: SZIP_LIBRARIES SZIP_INCLUDE_DIRS) -- HDF5 version found is 1.8.4 in /usr/include -- Python interpreter /usr/bin/python -- Python interpreter ok : version 2.6.5 -- PYTHON_INCLUDE_DIRS = /usr/include/python2.6 -- PYTHON_NUMPY_INCLUDE_DIR = /usr/lib/python2.6/dist-packages/numpy/core/include -- PYTHON_SITE_PKG = /usr/lib/python2.6/dist-packages -- PYTHON_LIBRARY = /usr/lib/python2.6/config/libpython2.6.so -- PYTHON_EXTRA_LIBS =-lssl -lcrypto -lssl -lcrypto -L/usr/lib -lz -lpthread -ldl -lutil -- PYTHON_LINK_FOR_SHARED = -Xlinker -export-dynamic -Wl,-O1 -Wl,-Bsymbolic-functions -- Numpy include in /usr/lib/python2.6/dist-packages/numpy/core/include -- Adding Boost dir: /home/magnet/alps-2.0.0b3-r4750-src-with-boost/boost -- HDF5 version found is 1.8.4 in /usr/include -- dirloop_sse will not be built since the lp_solve library has not found -- Configuring done -- Generating done -- Build files have been written to: /home/magnet/alps-2.0.0b3-r4750-src-with-boost/alps The line that got my attention at first was "-- dirloop_sse will not be built since the lp_solve library has not found," since I need dirloop_sse built. I then noticed, "-- LPSolve Library: not found". Am I putting the library in the right place? I know if I use sudo-apt get install lp-solve it installs liblpsolve55.so to /usr/lib/lp_solve/liblpsolve55.so, and I've tried putting liblpsolve51.so there after removing 5.5 of course, but it doesn't work. Any thoughts on where I am going wrong would help, I have to be missing something here. Thanks in advance, -Brian Koopman PS - I forgot to mention, this is on an old Dell OptiPlex with a Pentium III running Ubuntu 10.04.

2 1

Re: [ALPS-users] Question on running tutorial in ALPS_2.0b3
by bolun_chen＠mail.bnu.edu.cn 20 Jul '10

20 Jul '10

Dear Prof. Troyer, As you pointed out, I found I mistakenly ran the tutorial using another Python 2.6 (not the one contained in Vistrails directory). Sorry for that! As another try, I ran the vispython.bat in C:\Program Files\ALPS\bin, and I got an error "The specified procedure could not be found." Opening vispython.bat by notepad, I found the followings: "IF EXIST %HOMEDRIVE%\"Program Files"\VisTrails\vistrails %HOMEDRIVE%\"Program Files"\VisTrails\vistrails\Python25\python.exe IF EXIST %HOMEDRIVE%\"Program Files (x86)"\VisTrails\vistrails %HOMEDRIVE%\"Program Files (x86)"\VisTrails\vistrails\Python25\python.exe" I thought maybe "Python25" should be replaced by "Python26", so I made the change, and the vispython was loaded properly. But when I entered "import pyalps" again, the error remains: "Traceback (most recent call last): File "<stdin>", line 1, in <module> File "C:\Program Files\Vistrails\vistrails\Python26\lib\site-packages\pyalps\__init__.py", line 29, in <module> from tools import * File "C:\Program Files\Vistrails\vistrails\Python26\lib\site-packages\pyalps\tools.py", line 39, in <module> from pyalps.pytools import convert2xml, hdf5_name_encode, hdf5_name_decode, rng File "C:\Program Files\Vistrails\vistrails\Python26\lib\site-packages\pyalps\pytools.py", line 28, in <module> from pytools_c import * ImportError: DLL load failed: The specified module could not be found." When I ran the tutorial in ALPS by python.exe contained in C:\Program Files\Vistrails\vistrals\Python26, this error still occurs. I don't know what is missing, I'm eager to hear your advices. Thanks a lot! Best, Bolun ------------------ 原始邮件 ------------------ >From: Matthias Troyer <troyer(a)phys.ethz.ch> >Reply-To: comp-phys-alps-users(a)lists.phys.ethz.ch >To: "comp-phys-alps-users(a)lists.phys.ethz.ch"<comp-phys-alps-users(a)lists.phys.ethz.ch> >Subject: Re: [ALPS-users] Question on running tutorial in ALPS_2.0b3 >Date: Mon, 19 Jul 2010 14:30:55 -0600 > >Hi Bolun Chen > >I am confused by your reference to C:\Python26\lib\site-packages\pyalps\tools.py below. ALPS does not install anything into that location. > >Matthias Troyer > >Sent from my iPad > >On Jul 19, 2010, at 8:57 AM, Matthias Troyer wrote: > >> Did that problem occur when running the tutorial from Vistrails or from the shell using vispython? >> >> Matthioas >> >> On 19 Jul 2010, at 08:09, bolun_chen(a)mail.bnu.edu.cn wrote: >> >>> Hi All, >>> >>> I am a beginner to ALPS and I want to use it to perform QMC. I have downloaded and installed the Vistrails 1.5, the ALPS 2.0b3 and ALPS Vistrails extensions on Windows. But when I ran the tutorial using Python 2.65 contained in the Vistrails, I got an error, which read, >>> >

2 1

ALPS 2.0b3 release
by Matthias Troyer 19 Jul '10

19 Jul '10

Dear ALPS developers and users, The next beta release of ALPS is available. Updates compared to b2 include: - updated the ALPS VisTrails package to VisTrails version 1.5 - updated the DMRG application and added tutorials for DMRG - fixed compatibility issue with Windows in the MC-07 tutorial - fixed compatibility issues with some Linux shells On Windows please make sure to uninstall VisTrails and the ALPS VisTrails extension before installing VisTrails 1.5 and ALPS 2.0b3 Matthias Troyer

2 2

Question on running tutorial in ALPS_2.0b3
by bolun_chen＠mail.bnu.edu.cn 19 Jul '10

19 Jul '10

Hi All, I am a beginner to ALPS and I want to use it to perform QMC. I have downloaded and installed the Vistrails 1.5, the ALPS 2.0b3 and ALPS Vistrails extensions on Windows. But when I ran the tutorial using Python 2.65 contained in the Vistrails, I got an error, which read, "Traceback (most recent call last): File "<stdin>", line 1, in <module> File "C:\Python26\lib\site-packages\pyalps\__init__.py", line 29, in <module> from tools import * File "C:\Python26\lib\site-packages\pyalps\tools.py", line 39, in <module> from pyalps.pytools import convert2xml, hdf5_name_encode, hdf5_name_decode, rng File "C:\Python26\lib\site-packages\pyalps\pytools.py", line 28, in <module> from pytools_c import * ImportError: DLL load failed: The specified module could not be found." Can someone help me to tackle this problem? Thanks very much! Best, Bolun Chen

2 2

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

Comp-phys-alps-users July 2010