Comp-phys-alps-users

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

1 participants
1248 discussions

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

ALPS on Vistrails
by Noah Rahman 16 Jul '10

16 Jul '10

Hi all, I can't seem to execute the tutorials in Vistrails correctly, they execute for one cycle and then the central module in the workflow turns red and complains about execution failing. Vistrails recognizes the ALPS extensions, but I couldn't make it recognize the Ising simulation as an additional package in the first set of tutorials. It seemed that the tutorial script wants the 0.6.0 version of orgs.comp-phys.alps packages and ALPS 2.0 has version 0.7.0? I grepped and replaced it and the same issue remained This happened with the first monte-carlo autocorrelation simulation as well, it ran once upon hitting execute and then the parts of the workflow above the red center part turned yellow upon attempts to execute a second time. Best, Noah Rahman UCSB

2 8

ALPS 2.0.0b2 released
by Matthias Troyer 10 Jul '10

10 Jul '10

Dear ALPS users, ALPS version 2.0.0b2 is available on the web page. The main changes compared to 2.0.0b1 are bug fixes on Windows in the qwl and dmrg codes and more extensive documentation and tutorials. Matthias Troyer

1 0

[help] How to compute the expectation value of 4 operators( two creation and two destruction operators)
by Jun Wen 26 Jun '10

26 Jun '10

Hello all, I have been trying to compute the expectation value of cdag(1) c(2) cdag(3) c(4) where two creation and two destruction operators are involved and 1, 2 ,3 and 4 label the sites in a spinless Hubbard model. Could anyone kindly tell me how I should define this in the parameter file or in the models.xml? Thanks a lot! Best, Jun

2 2

Could you please remove me from this group?
by Huisky 24 Jun '10

24 Jun '10

Hi all, I don't know why I'm involved here, could you please do me the favor? Regards Hui

1 0

Jump to page:

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