Comp-phys-alps-users

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

1248 discussions

Re: [ALPS-users] Some questions on ALPS
by Synge Todo 31 May '07

31 May '07

Dear Dr. Chern, Cc: comp-phys-alps-users From: "CHERN, Chyh-Hong" <chern(a)issp.u-tokyo.ac.jp> Date: Wed, 30 May 2007 13:58:20 +0900 > Dear Professor Todo, > > Sorry for occupying your valuable time. We encounter some problems when > using your ALPS. We will appreciate highly if you can kindly help. > > I am a postdoctoral researcher in Oshikawa's group in ISSP. Recently, we > are interested in the transverse Ising model in the kagome system. We are > doing the Monte Carlo simulation and would like use your exact > diagonalization in ALPS to calibrate. I attached the lattice.xml and parm1 > that I used. We doubt on the results and would like to listen to your > comments. Let me list what happened to us. > > 1. We obtained the exactly the same results for L=1 and L=2 on energy, > entropy, specific heat, and the free energy. When running L=3, we failed to > get any results even though the memory is only used ~ 25%. Your kagome lattice with L=3 has 27 vertices, which obviously requires too much amount of memory (8*(2^27)^2 bytes = 10^8 GB!) to store the full Hamiltonian matrix... Instead of the fulldiag code, you can use my qmc code (qmc/looper), as long as the diagonal (Sz) interaction is ferromagnetic (i.e. no frustration). > 2. If we do not add CONSERVED_QUANTNUMBERS="Sz" in the parm1, we do not have > the result on the susceptibility but do have others. If we do include that > line, we have susceptibility, but lose the results on other thermodynamics > quantities. As we know, Sz is not the conserved quantum number for the > Ising model in the transverse magnetic field. Calculating canonical correlations of the operators which do not commute with the Hamiltonian requires substantial CPU time (N^3?). This is the reason why the fulldiag skips measuring the susceptibility unless total Sz is a conserved quantity. Again you can use qmc/loop, which calculates the susceptibility even in this case, instead for calibrating your simulation code. Best regards, Synge

1 0

how to modify spin model in models.xml file
by aniket＠jncasr.ac.in 10 May '07

10 May '07

Hi, I am in the very early stages of experimenting around with ALPS. I have special interest in quantum Monte Carlo. I want to modify spin model(models.xml file) in such manner that I can give different spin values to different lattice points. I have attached unit cell of Kagome lattice(kagome1.pdf). In that point C, are having same spin value (i.e 1) whereas, points D and E are having spin value 2. Please tell me the procedure which incorporates this change. with Regards, Aniket

2 1

ALPS release 1.3b5
by Matthias Troyer 02 May '07

02 May '07

Release 1.3b5 of ALPS is ready for download. It contains a bugfix for fermionic simulations with the new DMRG application, as well a a fix to the momentum iterations for structure factor measurements on non- square or non-cubic lattices. Matthias

1 0

MPI Issues
by Niall Moran 27 Apr '07

27 Apr '07

Hi, I have built and installed ALPS 1.3b3 and am trying to get the MPI version working. I am using a simple input file (shown below) and using the dirloop_sse_mpi tool. When running this on a single processor with dirloop_sse it takes around 62 seconds for each task and does each sequentially on a single cpu. I then tried running this in parallel on 8 processors. System has PBS for batch processing. Submitted job interactively and requested a walltime of 20 minutes and 8 cpus (4 x 2 processors per node). qsub -l walltime=00:20:00 -l nodes=4:ppn=2 -I Then started simulation with mpiexec -n 8 dirloop_sse_mpi job.in.xml All the tasks seem to finish correctly however the processes remain until the walltime is up. Output is listed below. Have tried building ALPS with both gcc 3.3.3 and also pathscale 2.5 compiler along with mpich-1.2.7. The same thing happens with each. Does anyone have any ideas what is going on? Many Thanks, Niall. Parameter version of input file. --------------------------------------------------------------------------- MODEL_LIBRARY="/alps/lib/xml/models.xml" MODEL="spin"; LATICE_LIBRARY="/alps/lib/xml/lattices.xml" LATTICE="chain lattice" SWEEPS=1000; THERMALIZATION=100; WORK_FACTOR=L*SWEEPS; { L=10; T=0.1; } { L=15; T=0.15; } { L=20; T=0.2; } { L=25; T=0.05; } { L=30; T=0.05; } { L=35; T=0.3; } { L=40; T=0.05; } { L=45; T=0.05; } Output of simulation in parallel. -------------------------------------------------------------------------- Quantum Monte simulations using the generalized directed loop algorithm v. 1.1 available from http://alps.comp-phys.org/ copyright (c) 2001-2005 by Fabien Alet <alet(a)comp-phys.org>, Synge Todo <wistaria(a)comp-phys.org>, and Matthias Troyer <troyer(a)comp-phys.org> see F. Alet, S. Wessel and M. Troyer, Phys. Rev. E 71, 036706 (2005) for details. using the ALPS parallelizing scheduler copyright (c) 1994-2006 by Matthias Troyer <troyer(a)comp-phys.org>. see Lecture Notes in Computer Science, Vol. 1505, p. 191 (1998). based on the ALPS libraries version 1.3b3 available from http://alps.comp-phys.org/ copyright (c) 1994-2006 by the ALPS collaboration. Consult the web page for license details. For details see the publication: F. Alet et al., J. Phys. Soc. Jpn. Suppl., Vol. 74, 30 (2005). parsing task files ... Created a new simulation: 2 on 1 processes Created a new simulation: 3 on 1 processes Created a new simulation: 4 on 1 processes Created a new simulation: 5 on 1 processes Created a new simulation: 6 on 1 processes Created a new simulation: 7 on 1 processes Created a new simulation: 8 on 1 processes Creating a new simulation: 1 on 1 processes Created run 1 locally All processes have been assigned Checking if Simulation 1 is finished: not yet, next check in 60 seconds ( 0% done). Created run 1 locally Checking if Simulation 2 is finished: not yet, next check in 60 seconds ( 0% done). Created run 1 locally Created run 1 locally Created run 1 locally Created run 1 locally Created run 1 locally Created run 1 locally Checking if Simulation 3 is finished: not yet, next check in 60 seconds ( 0% done). Checking if Simulation 4 is finished: not yet, next check in 60 seconds ( 0% done). Checking if Simulation 5 is finished: not yet, next check in 60 seconds ( 0% done). Checking if Simulation 6 is finished: not yet, next check in 60 seconds ( 0% done). Checking if Simulation 7 is finished: not yet, next check in 60 seconds ( 0% done). Checking if Simulation 8 is finished: not yet, next check in 60 seconds ( 0% done). Checking if Simulation 2 is finished: Finished Halted Simulation 2 Checking if Simulation 1 is finished: Finished Halted Simulation 1 Assigning 2 processes No work for master process No work for 1. All processes have been assigned Checking if Simulation 3 is finished: Finished Halted Simulation 3 Checking if Simulation 4 is finished: Finished Halted Simulation 4 Checking if Simulation 5 is finished: Finished Halted Simulation 5 Checking if Simulation 6 is finished: Finished Halted Simulation 6 Assigning 5 processes No work for 5. All processes have been assigned Checking if Simulation 7 is finished: Finished Halted Simulation 7 Checking if Simulation 8 is finished: Finished Halted Simulation 8 Assigning 7 processes All processes have been assigned Checkpointing Simulation 1 Checkpointing Simulation 2 Checkpointing Simulation 3 Checkpointing Simulation 4 Checkpointing Simulation 5 Checkpointing Simulation 6 Checkpointing Simulation 7 Checkpointing Simulation 8 Finished with all tasks. WARNING : Hamiltonian has a sign problem... p7_10096: p4_error: Timeout in establishing connection to remote process: 0 rm_l_7_10098: (365.230469) net_send: could not write to fd=5, errno = 32 p7_10096: (365.234375) net_send: could not write to fd=5, errno = 32 WARNING : Hamiltonian has a sign problem... p5_12240: p4_error: Timeout in establishing connection to remote process: 0 rm_l_5_12242: (365.238281) net_send: could not write to fd=5, errno = 32 p0_29156: p4_error: net_recv read: probable EOF on socket: 1 WARNING : Hamiltonian has a sign problem... p3_12614: p4_error: Timeout in establishing connection to remote process: 0 rm_l_3_12616: (365.238281) net_send: could not write to fd=5, errno = 32 p5_12240: (373.246094) net_send: could not write to fd=5, errno = 32 p0_29156: (374.425781) net_send: could not write to fd=4, errno = 32 p3_12614: (373.250000) net_send: could not write to fd=5, errno = 32 WARNING : Hamiltonian has a sign problem... p1_29158: p4_error: net_recv read: probable EOF on socket: 1 p1_29158: (381.265625) net_send: could not write to fd=5, errno = 32

2 8

Re: [ALPS-users] Help on Ising spin monte carlo simulation
by Matthias Troyer 26 Apr '07

26 Apr '07

Dear Zhimin Xiong, A simple local update MC code for an Ising model is in the example/ scheduler directory of the ALPS libraries. Matthias Troyer On 26 Apr 2007, at 12:05, Zhimin Xiong wrote: > Dear Troyer, > > I am a graduate student at Graduate University of Chinese Academy > of Sciences, and now I just started to study the topic of spin > glasses. At the beginning, I want to have a simple code to do some > exercise and simulation, so I found your project "ALPS" and > downloaded the library and application. After my first look at it, > there are some spin models in the packages. Now my question is, > whether your codes contain the algorithm for Ising spin glass > model, if so, I will need to a careful study of these related > codes, and if not, could you please give me some suggestion on how > to get a piece of simple code for Ising spin model? Thank you in > advance! >

1 0

kagome lattice, I want to introduce
by aniket＠jncasr.ac.in 26 Apr '07

26 Apr '07

hi, I want to introduce kagome lattice. How can I do that? Please tell me in briefly. I have attached kagome lattice also. How can I check the generated lattice is kagome or not? That means I want to extract the coordinates of the lattice. I am waiting for reply. Regards, aniket

2 1

how to define own unit cell
by aniket＠jncasr.ac.in 26 Apr '07

26 Apr '07

hi , I know the procedure for writing own unit cell i.e., you have to write lattice, latticegraph, unit cell, finite lattice, and graph. But I was trying for Kagome lattice but it wasn't working. So please help me out. I am giving you unit cell for kagome. Please find attached. Description: There are 5 vertices per unit cell. There is one triangle and a line included in that. The coordinates for 5 vertices are (0,0), (a,0) ,(a/2, sqrt(3)*a/2), (a/2, 0) and (a/4, sqrt(3)*a/4). One more thing, how to extract the coordinates of any generated lattice? I am waiting for your reply. Regards, Aniket

3 7

main executable
by Niall Moran 24 Apr '07

24 Apr '07

Hi, I have just managed to get the alps 1.3b3 library and applications installed. I am new to this area so have started going through the tutorials at http://alps.comp-phys.org:16080/mediawiki-1.9.3/index.php/Tutorials:Overview. The first tutorial uses an executable called "main" in the alps bin directory to run the simulation. I do not have any executable in the bin directory by that name. I am guessing that it might be that the name has changed from version 1.2.2. Can anyone tell me the name of the equivalent executable if this is the case? Thanks, Niall.

2 2

Compiling Alps 1.2.2
by Niall Moran 23 Apr '07

23 Apr '07

Hi, I am trying to build and install alps on a distributed memory cluster. I am using the mpich with gcc-3.3.3. Boost 1.33_1 has been installed in /usr/local/. The configure command I am using is. ./configure --with-mpi-incdir=/usr/local/mpich/gcc/include/ --with-mpi-libdir=/usr/local/mpich/gcc/lib64 --prefix=${HOME}/local/alps CC=mpicc CXX=mpicxx When I run make I get the following error. if /bin/sh ../../libtool --mode=compile mpicxx -DHAVE_CONFIG_H -I../../src -I../../src -DNDEBUG -DNDEBUG -pthread -w -ftemplate-depth-150 -O3 -fexceptions -MT latticelibrary.lo -MD -MP -MF ".deps/latticelibrary.Tpo" -c -o latticelibrary.lo `test -f '../../src/alps/lattice/latticelibrary.C' || echo './'`../../src/alps/lattice/latticelibrary.C; \ then mv -f ".deps/latticelibrary.Tpo" ".deps/latticelibrary.Plo"; else rm -f ".deps/latticelibrary.Tpo"; exit 1; fi mpicxx -DHAVE_CONFIG_H -I../../src -I../../src -DNDEBUG -DNDEBUG -pthread -w -ftemplate-depth-150 -O3 -fexceptions -MT latticelibrary.lo -MD -MP -MF .deps/latticelibrary.Tpo -c ../../src/alps/lattice/latticelibrary.C -fPIC -DPIC -o .libs/latticelibrary.o /usr/include/boost/type_traits/extent.hpp: In function `void alps::make_graph_from_lattice(GRAPH&, const LATTICE&) [with LATTICE = alps::lattice_graph<alps::hypercubic_lattice<alps::coordinate_lattice<alps::simple_lattice<alps::GraphUnitCell, alps::simple_cell<alps::GraphUnitCell, std::vector<int, std::allocator<int> > > >, std::vector<double, std::allocator<double> > >, std::vector<int, std::allocator<int> > >, alps::coordinate_graph_type>, GRAPH = alps::coordinate_graph_type]': ../../src/alps/lattice/latticegraph.h:207: instantiated from `alps::lattice_graph<L, G>::lattice_graph(const L2&) [with L2 = alps::LatticeGraphDescriptor, LATTICE = alps::hypercubic_lattice<alps::coordinate_lattice<alps::simple_lattice<alps::GraphUnitCell, alps::simple_cell<alps::GraphUnitCell, std::vector<int, std::allocator<int> > > >, std::vector<double, std::allocator<double> > >, std::vector<int, std::allocator<int> > >, GRAPH = alps::coordinate_graph_type]' ../../src/alps/lattice/latticelibrary.C:135: instantiated from here /usr/include/boost/type_traits/extent.hpp:121: error: `template<class T, long unsigned int N> struct boost::extent' is not a function, ../../src/alps/lattice/lattice.h:198: error: conflict with `template<class Lattice> typename alps::VectorTraits<typename alps::lattice_traits<L>::extent_type>::value_type alps::extent(const Lattice&, unsigned int)' ../../src/alps/lattice/latticegraph.h:166: error: in call to `extent' make[2]: *** [latticelibrary.lo] Error 1 make[2]: Leaving directory `/....../packages/alps/alps-1.2.2/lib/alps' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/......./packages/alps/alps-1.2.2/lib' make: *** [all-recursive] Error 1 It seems the struct extent from the boost header extent.hpp is conflicting with the function called extent from alps. From what I can see alps should work with this version of boost and compiler. Has anyone else encountered this issue or know of a way to get around it? Thanks, Niall.

2 2

new lattice
by aniket＠jncasr.ac.in 19 Apr '07

19 Apr '07

Respected sir, I want to use new lattice other than whatever specified in lattice.xml. Suppose new lattice name is kagome lattice. What will be procedure for defining this lattice? I am waiting for reply. with regards, Aniket

2 1

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