February 2013 - Comp-phys-alps-users

alps-2.1.1-r6670-src-with-boost installation error on ubuntu 12.04
by dasari＠jncasr.ac.in 12 Feb '13

12 Feb '13

Hi, I am trying to install alps-2.1.1-r6670-src-with-boost on my Desktop(ubuntu 12.04, 64 bit machine). The following is the script I run at the terminal. After cmake it seems to me everything fine. After that I issued a command make -j 3. Then I got an error at 100% build. You can see that error at the end of this mail. Could any one help me to solve this problem? export Boost_ROOT_DIR=/opt/boost_1_49_0 export CXX=/usr/bin/g++ export CXXFLAGS="-W -march=native -O3" export CC=/usr/bin/gcc export BUILD_SHARED_LIBS=OFF export MPI_COMPILER=/usr/bin/mpicc export MPIEXEC=/usr/lib/openmpi/bin/mpiexec export CMAKE_BUILD_TYPE=RELEASE export ALPS_BUILD_TESTS=OFF export CMAKE_INSTALL_PREFIX=/home/dasari/DMFT_ALPS/alps export HDF5_LIB=/opt/hdf5/lib/libhdf5.so export HDF5_INC=/opt/hdf5/include export MPI_EXTRA_LIBRARY=/usr/lib/openmpi/lib/libmpi.so cmake ../alps-2.1.1-r6670-src-with-boost/alps -DBoost_ROOT_DIR=$Boost_ROOT_DIR \ -DBUILD_SHARED_LIBS=$BUILD_SHARED_LIBS \ -DALPS_BUILD_APPLICATIONS=ON \ -DALPS_BUILD_EXAMPLES=ON \ -DALPS_INSTALL_HEADERS=OFF \ --DALPS_INCLUDE_TUTORIALS=ON \ -DCMAKE_BUILD_TYPE=$CMAKE_BUILD_TYPE \ -DALPS_BUILD_TESTS=$ALPS_BUILD_TESTS \ -DCMAKE_INSTALL_PREFIX=$CMAKE_INSTALL_PREFIX \ -DALPS_BUILD_NGS="ON" \ -DHDF5_LIBRARIES=$HDF5_LIB \ -DHDF5_INCLUDE_DIR=$HDF5_INC\ -DALPS_BUILD_PYTHON="ON"\ -DMPIEXEC=$MPIEXEC \ -DMPI_COMPILER=$MPI_COMPILER \ -DMPI_EXTRA_LIBRARY=$MPI_EXTRA_LIBRARY This is the error I got. Linking CXX executable spinmc_evaluate [100%] Built target spinmc_evaluate Scanning dependencies of target worm [100%] Building CXX object applications/qmc/worms/CMakeFiles/worm.dir/main.C.o In file included from /opt/boost_1_49_0/boost/python/detail/wrap_python.hpp:50:0, from /opt/boost_1_49_0/boost/python/detail/prefix.hpp:13, from /opt/boost_1_49_0/boost/python/args.hpp:8, from /opt/boost_1_49_0/boost/python.hpp:11, from /home/dasari/DMFT_ALPS/alps-2.1.1-r6670-src-with-boost/alps/src/alps/alea/mcdata.hpp:76, from /home/dasari/DMFT_ALPS/alps-2.1.1-r6670-src-with-boost/alps/src/alps/alea.h:34, from /home/dasari/DMFT_ALPS/alps-2.1.1-r6670-src-with-boost/alps/src/alps/alea/observableset.h:49, from /home/dasari/DMFT_ALPS/alps-2.1.1-r6670-src-with-boost/alps/src/alps/scheduler/montecarlo.h:40, from /home/dasari/DMFT_ALPS/alps-2.1.1-r6670-src-with-boost/alps/src/alps/scheduler.h:31, from /home/dasari/DMFT_ALPS/alps-2.1.1-r6670-src-with-boost/alps/applications/qmc/worms/WRun.h:34, from /home/dasari/DMFT_ALPS/alps-2.1.1-r6670-src-with-boost/alps/applications/qmc/worms/main.C:29: /usr/include/python2.7/pyconfig.h:1161:0: warning: "_POSIX_C_SOURCE" redefined [enabled by default] /usr/include/features.h:164:0: note: this is the location of the previous definition /usr/include/python2.7/pyconfig.h:1183:0: warning: "_XOPEN_SOURCE" redefined [enabled by default] /usr/include/features.h:166:0: note: this is the location of the previous definition Scanning dependencies of target worm_evaluate [100%] Building CXX object applications/qmc/worms/CMakeFiles/worm_evaluate.dir/evaluate.C.o In file included from /opt/boost_1_49_0/boost/python/detail/wrap_python.hpp:50:0, from /opt/boost_1_49_0/boost/python/detail/prefix.hpp:13, from /opt/boost_1_49_0/boost/python/args.hpp:8, from /opt/boost_1_49_0/boost/python.hpp:11, from /home/dasari/DMFT_ALPS/alps-2.1.1-r6670-src-with-boost/alps/src/alps/alea/mcdata.hpp:76, from /home/dasari/DMFT_ALPS/alps-2.1.1-r6670-src-with-boost/alps/src/alps/alea.h:34, from /home/dasari/DMFT_ALPS/alps-2.1.1-r6670-src-with-boost/alps/src/alps/alea/observableset.h:49, from /home/dasari/DMFT_ALPS/alps-2.1.1-r6670-src-with-boost/alps/src/alps/scheduler/montecarlo.h:40, from /home/dasari/DMFT_ALPS/alps-2.1.1-r6670-src-with-boost/alps/src/alps/scheduler.h:31, from /home/dasari/DMFT_ALPS/alps-2.1.1-r6670-src-with-boost/alps/applications/qmc/worms/evaluate.C:29: /usr/include/python2.7/pyconfig.h:1161:0: warning: "_POSIX_C_SOURCE" redefined [enabled by default] /usr/include/features.h:164:0: note: this is the location of the previous definition /usr/include/python2.7/pyconfig.h:1183:0: warning: "_XOPEN_SOURCE" redefined [enabled by default] /usr/include/features.h:166:0: note: this is the location of the previous definition Linking CXX executable worm Linking CXX shared library cthyb.so /usr/bin/ld: ../../../src/alps/libalps.a(hdf5.cpp.o): relocation R_X86_64_32S against `vtable for alps::bad_cast' can not be used when making a shared object; recompile with -fPIC ../../../src/alps/libalps.a: could not read symbols: Bad value collect2: ld returned 1 exit status make[2]: *** [applications/dmft/qmc/cthyb.so] Error 1 make[1]: *** [applications/dmft/qmc/CMakeFiles/cthyb.so.dir/all] Error 2 make[1]: *** Waiting for unfinished jobs.... [100%] Built target worm Linking CXX executable worm_evaluate [100%] Built target worm_evaluate make: *** [all] Error 2 With regards, Dasari.

2 5

matrices as operators
by Mateusz Łącki 11 Feb '13

11 Feb '13

Dear All I would like to consult on the following manner: I would like to make it easy to use matrices stored in text files as operators in alps situations. My current solution is: 1. I have found a place where functions such as "sin" are defined in the code. 2. I have added "KroneckerDelta" function 3. I have written a script that produces apriopriate "model.xml" given text files with the operators I want to use in alps. It seems it works, but the solution is ugly: my custom operator are lengthy sums of the form KD(n,5)*0.321 for the diabonal operators, even worse for general, nondiagonal operator :) Is there a nicer way to do it ?:) Perhaps it is possible to write a nice function for alps that creates such an operatr. I would like to ask for a hit for best way to code it :) Regards, Mateusz Lacki

1 0

Winding numbers
by "Michał Maik" 08 Feb '13

08 Feb '13

Hello, I asked this question earilier but recieved no response so I'll try again. I am curious if is it possible to get the winding number histogram from the SSE and worms code. There seem to be references to it in the code but since I am not familiar with C++ I do not know how to extract it. In Wmeas.C I found "measurements["Winding number histogram"]" but adding, "MEASURE[Winding number histogram]=true" to the parameter file doesn't do anything. If anyone has any suggestions on how to get this to work I would really apprieciate it. Thanks! Best Regards Michal Maik

2 1

to capture the reduced dm eigenvalues in dmrg
by A. Giovanni Ramirez Garcia 04 Feb '13

04 Feb '13

Hi all, Emanuele, I use to save the eigenvalues of the reduced density matrix too. The way I do it is to pipe the standard output to a grep command, then to a file. I'm using a GNU/Linux and there the grep command can "include" or "exclude" patterns it reads from a file. You know, the standard output for VERBOSE=1 includes too much information then I select what patterns I want to keep: SWEEP, ITERATION, RHO and I save that patterns in a file "patterns_file" (one per line) in the same directory where I put the python file with the definitions then, I run alpspython defs.py | grep -f patterns > rdm.log Then, the file rdm.log keeps the information about what SWEEP and what ITERATION has that list of RHO EIGENVALUES. Maybe it is not the best way to do it, I would like to know if someone else find another way to do it. Ciao Giovanni

1 0

Running MaxEnt code
by Viveka Singh 03 Feb '13

03 Feb '13

Dear all, I need to do the analytic continuation of my imaginary frequency / imaginary time data to the real frequency. I want to use the ALPS MaxEnt code for that, but I am not able to find an elaborate documentation on how to use the maxent code. I have looked at the "hybdoc.pdf", but not enough is being mentioned there and it is pointed there that a tutorial for the ALPS maxent code will be provided elsewhere. Can someone send me that link? Or can someone describe the input parameters that are required for the maxent code like - what are ALPHA's and how do one decide upon FREQUENCY_GRID? Do you need to spacify the OMEGA_MAX/OMEGA_MIN, even if someone wants to do the analytic continuation of imaginary time data? With regards, Viveka Nand Singh

2 1

Getting edge or bond type in spinmc
by Kourosh Sartipi 01 Feb '13

01 Feb '13

Hi everyone! I'm trying to write a code to do different calculations for different bond types, so I changed my lattice file and set edge type to 8888 for test, a part of lattice file is as follows: <EDGE type="8888"><SOURCE vertex="1"/><TARGET vertex="2" offset=" 0 0 0"/></EDGE> <EDGE type="8888"><SOURCE vertex="3"/><TARGET vertex="4" offset=" 0 0 0"/></EDGE> <EDGE type="8888"><SOURCE vertex="2"/><TARGET vertex="1" offset=" 1 0 0"/></EDGE> and I added a test code in alps/applications/mc/spins/spinsim.h as following: typedef typename AbstractSpinSim<MIdMatrix<double, M::dim> >::bond_iterator bond_iterator; for(bond_iterator bi = this->bonds().first; bi != this->bonds().second; bi++) { int et = this->edge_type(*bi); std::cout << et << std::endl; } but all I get from bond types is zero. Do you know how can I get the correct bond type here? Yours, Kourosh

1 0