- Comp-phys-alps-users - lists.phys.ethz.ch

extract mean values from DMRG
by João Manuel Viana Parente Lopes 25 Nov '08

25 Nov '08

Hi, The problem is that the standard scripts like extracttext or extractxmgr doesn't recognize the format of the dmrg output (at least in the version that I'm running). For example if I run a small dmrg simulation and I pretend to extract the energy value from the param.ask1.out.xml... This file looks like: <EIGENSTATES number="2"> <EIGENSTATE number="0"> <SCALAR_AVERAGE name="Energy"><MEAN>-8.90438652987646</MEAN></ SCALAR_AVERAGE> <SCALAR_AVERAGE name="Truncation error"><MEAN>1.127923664741207e-13</MEAN></SCALAR_AVERAGE> </EIGENSTATE> <EIGENSTATE number="1"> <SCALAR_AVERAGE name="Energy"><MEAN>-8.686440986186689</MEAN></ SCALAR_AVERAGE> </EIGENSTATE> </EIGENSTATES> As Mathias says there are the different averages associated with each eigenstate... If I use the standard plot.xml file I could not extract the energy from the <EIGENSTATES> block ... The question is: Should I modify the standard plot.xml file or it's needed changes in the alps scripts? Thanks for your support! João Lopes

2 1

extract mean values from DMRG
by João Manuel Viana Parente Lopes 21 Nov '08

21 Nov '08

Dear All, I'm trying to produce a plot.xml file to extract the mean values from param.task1.out.xml file generated by dmrg program. The different SCALAR_AVERAGE tags are inside the xml structure: <EIGENSTATES number=""> <EIGENSTATE number="0"> .... </EIGENSTATE> </EIGENSTATES> And until know I wasn't able the extract any quantity from this structure... Can You give any clue? Thanks in advance João Lopes

3 2

Compiler error taken care of
by Charles Mathy 21 Nov '08

21 Nov '08

Pardon my previous posting, it was covered in a previous thread. Just installed version 1.3.3 and it installed fine.

1 0

Compiler error
by Charles Mathy 21 Nov '08

21 Nov '08

Hello, Configure ran without errors, but when trying to make alps I ran into a conflict error. I installed boost and tested it, it seems to work fine. In the configuration I disabled hfd5 because that was giving errors. make[1]: Entering directory `/group/cmtheory/cmathy/ALPS/alps-1.2.2/lib' Making all in alps make[2]: Entering directory `/group/cmtheory/cmathy/ALPS/alps-1.2.2/lib/alps' if /bin/sh ../../libtool --mode=compile g++ -DHAVE_CONFIG_H -I../../src -I../../src -DNDEBUG -I/group/cmtheory/cmathy/BOOST/boost_1_37_0 -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 g++ -DHAVE_CONFIG_H -I../../src -I../../src -DNDEBUG -I/group/cmtheory/cmathy/BOOST/boost_1_37_0 -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 ../../src/alps/lattice/latticegraph.h: 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 /group/cmtheory/cmathy/BOOST/boost_1_37_0/boost/type_traits/extent.hpp:132: error: `template<class T, 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 `/group/cmtheory/cmathy/ALPS/alps-1.2.2/lib/alps' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/group/cmtheory/cmathy/ALPS/alps-1.2.2/lib' make: *** [all-recursive] Error 1 Sincerely, Charles

1 0

DMRG for ferrimagnets
by zhian asadzadeh 17 Oct '08

17 Oct '08

---------- Forwarded message ---------- From: <comp-phys-alps-users-request(a)phys.ethz.ch> Date: Fri, Oct 17, 2008 at 1:30 PM Subject: Comp-phys-alps-users Digest, Vol 31, Issue 5 To: comp-phys-alps-users(a)phys.ethz.ch Send Comp-phys-alps-users mailing list submissions to comp-phys-alps-users(a)phys.ethz.ch To subscribe or unsubscribe via the World Wide Web, visit https://webmail.phys.ethz.ch/mailman/listinfo/comp-phys-alps-users or, via email, send a message with subject or body 'help' to comp-phys-alps-users-request(a)phys.ethz.ch You can reach the person managing the list at comp-phys-alps-users-owner(a)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. Re: Comp-phys-alps-users Digest, Vol 31, Issue 4 (zhian asadzadeh) ---------------------------------------------------------------------- Message: 1 Date: Thu, 16 Oct 2008 04:17:31 -0700 From: "zhian asadzadeh" <zhian.asadzadeh(a)gmail.com> Subject: Re: [ALPS-users] Comp-phys-alps-users Digest, Vol 31, Issue 4 To: comp-phys-alps-users(a)phys.ethz.ch Message-ID: <89e5d6760810160417u754c084ap20b050269ac89b13(a)mail.gmail.com> Content-Type: text/plain; charset="iso-8859-1" Dear All I used Sz_total=N(S1-S2),as an input parameter but this thing just speed up the calculation and it doesn't any effect on the output,means that with this input parameter i have result that it doesn't differ with the result that earlier i have got.i want to achieve the results that earlier are achieved in the following paper, *(SK Pati, S Ramasesha, D Sen - Physical Review B, 1997 - APS)* they study the ferrimagnetic chain and present the ground state energy and some correlations. they consider N cell that each cell consist of two spin(s1,s2). Hamiltonian is H=sum_i (S2_i . S1_i+1)+(S1_i.S2_i -1) i counts the cells and it is form 0 to N. the results that i achieve,two digite concur with theirs results. I don't know what must i do that i have a better results. Thanks On Wed, Oct 15, 2008 at 3:00 AM, <comp-phys-alps-users-request(a)phys.ethz.ch>wrote: > Send Comp-phys-alps-users mailing list submissions to > comp-phys-alps-users(a)phys.ethz.ch > > To subscribe or unsubscribe via the World Wide Web, visit > https://webmail.phys.ethz.ch/mailman/listinfo/comp-phys-alps-users > or, via email, send a message with subject or body 'help' to > comp-phys-alps-users-request(a)phys.ethz.ch > > You can reach the person managing the list at > comp-phys-alps-users-owner(a)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. Ferrimagnet (zhian asadzadeh) > 2. Re: Ferrimagnet (Adrian E. Feiguin) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Tue, 14 Oct 2008 19:02:01 +0330 > From: "zhian asadzadeh" <zhian.asadzadeh(a)gmail.com> > Subject: [ALPS-users] Ferrimagnet > To: Comp-phys-alps-users(a)phys.ethz.ch > Message-ID: > <89e5d6760810140832p1dec90d9h3dfb0cab0d2367ee(a)mail.gmail.com> > Content-Type: text/plain; charset="iso-8859-1" > > Dear All > > I'm making my first experiments with Alps... > I want to use DMRG for ferrimagnetic chain,but i have some problems. > First,in the dmrg steps because the chain don't have the symmetry between > left and right halves,the density matrices for these two halves should be > constructed at every iteration of the calculation. > Second,I think that it isn't exist spin parity symmetry. > How i can do these? > > Thanks in advance > > zhian >

2 1

Re: [ALPS-users] Comp-phys-alps-users Digest, Vol 31, Issue 4
by zhian asadzadeh 16 Oct '08

16 Oct '08

Dear ADRIAN I used Sz_total=N(S1-S2),as an input parameter but this thing just speed up the calculation and it doesn't any effect on the output,means that with this input parameter i have result that it doesn't differ with the result that earlier i have got.i want to achieve the results that earlier are achieved in the following paper, *(SK Pati, S Ramasesha, D Sen - Physical Review B, 1997 - APS)* they study the ferrimagnetic chain and present the ground state energy and some correlations. they consider N cell that each cell consist of two spin(s1,s2). Hamiltonian is H=sum_i (S2_i . S1_i+1)+(S1_i.S2_i -1) i counts the cells and it is form 0 to N. the results that i achieve,two digite concur with theirs results. I don't what must i do that i have a better results. Thanks On Wed, Oct 15, 2008 at 3:00 AM, <comp-phys-alps-users-request(a)phys.ethz.ch>wrote: > Send Comp-phys-alps-users mailing list submissions to > comp-phys-alps-users(a)phys.ethz.ch > > To subscribe or unsubscribe via the World Wide Web, visit > https://webmail.phys.ethz.ch/mailman/listinfo/comp-phys-alps-users > or, via email, send a message with subject or body 'help' to > comp-phys-alps-users-request(a)phys.ethz.ch > > You can reach the person managing the list at > comp-phys-alps-users-owner(a)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. Ferrimagnet (zhian asadzadeh) > 2. Re: Ferrimagnet (Adrian E. Feiguin) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Tue, 14 Oct 2008 19:02:01 +0330 > From: "zhian asadzadeh" <zhian.asadzadeh(a)gmail.com> > Subject: [ALPS-users] Ferrimagnet > To: Comp-phys-alps-users(a)phys.ethz.ch > Message-ID: > <89e5d6760810140832p1dec90d9h3dfb0cab0d2367ee(a)mail.gmail.com> > Content-Type: text/plain; charset="iso-8859-1" > > Dear All > > I'm making my first experiments with Alps... > I want to use DMRG for ferrimagnetic chain,but i have some problems. > First,in the dmrg steps because the chain don't have the symmetry between > left and right halves,the density matrices for these two halves should be > constructed at every iteration of the calculation. > Second,I think that it isn't exist spin parity symmetry. > How i can do these? > > Thanks in advance > > zhian >

1 0

Ferrimagnet
by zhian asadzadeh 15 Oct '08

15 Oct '08

Dear All I'm making my first experiments with Alps... I want to use DMRG for ferrimagnetic chain,but i have some problems. First,in the dmrg steps because the chain don't have the symmetry between left and right halves,the density matrices for these two halves should be constructed at every iteration of the calculation. Second,I think that it isn't exist spin parity symmetry. How i can do these? Thanks in advance zhian

2 1

Re: [ALPS-users] internal compiler error
by Tadeusz Wasiutynski 05 Oct '08

05 Oct '08

On Sun, 05 Oct 2008 12:00:02 +0200, comp-phys-alps-users-request wrote > Send Comp-phys-alps-users mailing list submissions to > comp-phys-alps-users(a)phys.ethz.ch > > To subscribe or unsubscribe via the World Wide Web, visit > https://webmail.phys.ethz.ch/mailman/listinfo/comp-phys-alps-users > or, via email, send a message with subject or body 'help' to > comp-phys-alps-users-request(a)phys.ethz.ch > > You can reach the person managing the list at > comp-phys-alps-users-owner(a)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. internal compiler error (Tadeusz Wasiutynski) > 2. Re: internal compiler error (Matthias Troyer) > > ---------------------------------------------------------------------- > > Message: 1 > Date: Sat, 4 Oct 2008 12:50:32 +0200 > From: "Tadeusz Wasiutynski" <Tadeusz.Wasiutynski(a)ifj.edu.pl> > Subject: [ALPS-users] internal compiler error > To: comp-phys-alps-users(a)phys.ethz.ch > Message-ID: <20081004103922.M32785(a)ifj.edu.pl> > Content-Type: text/plain; charset=iso-8859-2 > > I try to install alps-applications but there is a problem. > Installation of alps library seems to be smooth: > make OK > make examples OK > make tests OK > make install OK > then in the alps-application directory: > ./configure --with-lp_solve=/home/tadek/alps/lp_solve_4.0 > configure: loading site script /home/tadek/ALPS/share/config.site > configure: loading cache /home/tadek/ALPS/share/alps/config.cache > checking for a BSD-compatible install... (cached) /usr/bin/install -c > checking whether build environment is sane... yes > checking for a thread-safe mkdir -p... (cached) /bin/mkdir -p > checking for gawk... (cached) gawk > checking whether make sets $(MAKE)... (cached) yes > checking whether to enable maintainer-specific portions of > Makefiles... no checking for ALPS Libraries... OK checking for ALPS > version... 1.3.3 checking for gcc... (cached) gcc checking for C > compiler default output file name... a.out checking whether the C > compiler works... yes checking whether we are cross compiling... no > checking for suffix of executables... checking for suffix of object > files... (cached) o checking whether we are using the GNU C > compiler... (cached) yes checking whether gcc accepts -g... (cached) > yes checking for gcc option to accept ISO C89... (cached) none > needed checking for style of include used by make... GNU checking > dependency style of gcc... (cached) gcc3 checking for g++... (cached) > g++ checking whether we are using the GNU C++ compiler... (cached) yes > checking whether g++ accepts -g... (cached) yes > checking dependency style of g++... (cached) gcc3 > checking build system type... (cached) i686-pc-linux-gnu > checking host system type... (cached) i686-pc-linux-gnu > checking for a sed that does not truncate output... (cached) /bin/sed > checking for grep that handles long lines and -e... (cached) > /bin/grep checking for egrep... (cached) /bin/grep -E checking for > ld used by gcc... (cached) /usr/bin/ld checking if the linker > (/usr/bin/ld) is GNU ld... (cached) yes checking for /usr/bin/ld > option to reload object files... (cached) -r checking for BSD- > compatible nm... (cached) /usr/bin/nm -B checking whether ln -s > works... yes checking how to recognize dependent libraries... > (cached) pass_all checking how to run the C preprocessor... (cached) > gcc -E checking for ANSI C header files... (cached) yes checking for > sys/types.h... (cached) yes checking for sys/stat.h... (cached) yes > checking for stdlib.h... (cached) yes checking for string.h... > (cached) yes checking for memory.h... (cached) yes checking for > strings.h... (cached) yes checking for inttypes.h... (cached) yes > checking for stdint.h... (cached) yes checking for unistd.h... > (cached) yes checking for dlfcn.h... (cached) yes checking how to > run the C++ preprocessor... (cached) g++ -E checking whether we are > using the GNU Fortran 77 compiler... (cached) no checking whether no > accepts -g... (cached) no checking the maximum length of command > line arguments... (cached) 1966080 checking command to parse > /usr/bin/nm -B output from gcc object... (cached) ok checking for > objdir... (cached) .libs checking for ar... (cached) ar checking for > ranlib... (cached) ranlib checking for strip... (cached) strip > checking if gcc supports -fno-rtti -fno-exceptions... (cached) yes > checking for gcc option to produce PIC... -fPIC checking if gcc PIC > flag -fPIC works... (cached) yes checking if gcc static flag -static > works... (cached) yes checking if gcc supports -c -o file.o... > (cached) yes checking whether the gcc linker (/usr/bin/ld) supports > shared libraries... yes checking whether -lc should be explicitly > linked in... no checking dynamic linker characteristics... GNU/Linux > ld.so > (cached) (cached) checking how to hardcode library paths into programs... > immediate > checking whether stripping libraries is possible... yes > checking if libtool supports shared libraries... yes > checking whether to build shared libraries... yes > checking whether to build static libraries... yes > configure: creating libtool > appending configuration tag "CXX" to libtool > checking for ld used by g++... (cached) /usr/bin/ld > checking if the linker (/usr/bin/ld) is GNU ld... (cached) yes > checking whether the g++ linker (/usr/bin/ld) supports shared > libraries... yes checking for g++ option to produce PIC... -fPIC > checking if g++ PIC flag -fPIC works... (cached) yes checking if g++ > static flag -static works... (cached) yes checking if g++ supports > -c -o file.o... (cached) yes checking whether the g++ linker > (/usr/bin/ld) supports shared libraries... yes checking dynamic > linker characteristics... GNU/Linux ld.so > (cached) (cached) checking how to hardcode library paths into programs... > immediate > appending configuration tag "F77" to libtool > checking for MPI library... no > checking for LAPACK library... yes > checking for IETL library... /home/tadek/ALPS/include > checking ietl/lanczos.h usability... yes > checking ietl/lanczos.h presence... yes > checking for ietl/lanczos.h... yes > checking lpkit.h usability... yes > checking lpkit.h presence... yes > checking for lpkit.h... yes > checking for make_lp in -llpk... yes > configure: creating ./config.status > config.status: creating Makefile > config.status: creating diag/Makefile > config.status: creating diag/fulldiag/Makefile > config.status: creating diag/sparsediag/Makefile > config.status: creating dmrg/Makefile > config.status: creating dmrg/dmrg/Makefile > config.status: creating dmrg/particle_in_box/Makefile > config.status: creating mc/Makefile > config.status: creating mc/spins/Makefile > config.status: creating qmc/Makefile > config.status: creating qmc/checksign/Makefile > config.status: creating qmc/looper/Makefile > config.status: creating qmc/sse/Makefile > config.status: creating qmc/worms/Makefile > config.status: creating qmc/qwl/Makefile > config.status: creating test/Makefile > config.status: creating test/parm > config.status: creating test/parm_fermion > config.status: creating test/parm_fermion2 > config.status: creating test/parm_boson > config.status: creating test/energy.xsl > config.status: creating test/fulldiag/Makefile > config.status: creating test/sparsediag/Makefile > config.status: creating test/sparsediag/groundstate.xsl > config.status: creating test/checksign/Makefile > config.status: creating test/looper/Makefile > config.status: creating test/sse/Makefile > config.status: creating test/worms/Makefile > config.status: creating test/qwl/Makefile > config.status: creating test/qwl/parm > config.status: creating test/mc/Makefile > config.status: creating test/mc/spins/Makefile > config.status: creating test/mc/spins/check.sh > config.status: creating test/mc/spins/ising_local.parm > config.status: creating test/mc/spins/ising_cluster.parm > config.status: creating test/mc/spins/heisenberg_chain.parm > config.status: creating test/mc/spins/heisenberg_ladder.parm > config.status: creating config/config.h > config.status: config/config.h is unchanged > config.status: executing depfiles commands > > Summary of configuration: > Diagonalization > Full yes > Sparse yes > DMRG > DMRG yes > Particle in box yes > Classical Monte Carlo > Spin yes > Quantum Monte Carlo > Checksign yes > Looper yes > SSE-dirloop yes > Worms yes > Quantum Wang-Landau yes > > In the make step however I encountered: > .............. > mv -f .deps/fitting_scheduler.Tpo .deps/fitting_scheduler.Po > g++ -DHAVE_CONFIG_H -I. -I. -I../.. -DNDEBUG -I/home/tadek/ALPS/include > -I/home/tadek/ALPS/include -I/home/tadek/alps/lp_solve_4.0 - > pthread -ftemplate-depth-150 -O3 -DBOOST_DISABLE_ASSERTS > -fexceptions -w -MT spinmc_factory.o -MD -MP -MF > .deps/spinmc_factory.Tpo -c -o spinmc_factory.o spinmc_factory.C > spinmc_factory.C: In constructor ‘AbstractSpinSim<MAT>::AbstractSpinSim(const > alps::ProcessList&, const alps::Parameters&, int) [with MAT = > DiagMatrix<double, 3>]’: > spinmc_factory.C:194: internal compiler error: Memory violation > Please submit a full bug report, > with preprocessed source if appropriate. > See <http://bugzilla.redhat.com/bugzilla> for instructions. > Preprocessed source stored into /tmp/ccWCP9wP.out file, please > attach this to your bugreport. make[2]: *** [spinmc_factory.o] Error > 1 make[2]: Opuszczenie katalogu `/home/tadek/alps/alps-applications-1.3.3/mc/spins' > make[1]: *** [all-recursive] Error 1 > make[1]: Opuszczenie katalogu `/home/tadek/alps/alps-applications-1.3.3/mc' > make: *** [all-recursive] B??d 1 > > My system is Fedora 9 > Where should I go to look for? > > Prof. dr hab. Tadeusz Wasiutynski > H. Niewodniczanski Institute of Nuclear Physics PAN > tel. +48(12)6628251 fax: +48(12)6628251 > e-mail: tadeusz.wasiutynski(a)ifj.edu.pl > > ------------------------------ > > Message: 2 > Date: Sat, 4 Oct 2008 19:53:28 +0200 > From: Matthias Troyer <troyer(a)phys.ethz.ch> > Subject: Re: [ALPS-users] internal compiler error > To: comp-phys-alps-users(a)phys.ethz.ch > Message-ID: <D0B6E357-5094-4EAF-83E3-58FD49448150(a)phys.ethz.ch> > Content-Type: text/plain; charset=ISO-8859-2; format=flowed; delsp=yes > > On 4 Oct 2008, at 12:50, Tadeusz Wasiutynski wrote: > > > I try to install alps-applications but there is a problem. > > Installation of alps library seems to be smooth: > > \ > > spinmc_factory.C:194: internal compiler error: Memory violation > > Please submit a full bug report, > > with preprocessed source if appropriate. > > See <http://bugzilla.redhat.com/bugzilla> for instructions. > > Preprocessed source stored into /tmp/ccWCP9wP.out file, please > > attach this to > > your bugreport. > > make[2]: *** [spinmc_factory.o] Error 1 > > make[2]: Opuszczenie katalogu `/home/tadek/alps/alps- > > applications-1.3.3/mc/spins' > > make[1]: *** [all-recursive] Error 1 > > make[1]: Opuszczenie katalogu `/home/tadek/alps/alps- > > applications-1.3.3/mc' > > make: *** [all-recursive] B??d 1 > > > > My system is Fedora 9 > > Where should I go to look for? > > > > Prof. dr hab. Tadeusz Wasiutynski > > H. Niewodniczanski Institute of Nuclear Physics PAN > > tel. +48(12)6628251 fax: +48(12)6628251 > > e-mail: tadeusz.wasiutynski(a)ifj.edu.pl > > Which compiler version do you use? Type g++ --version to find out. > Often updating to a more recent compiler version can help. > > Matthias > > End of Comp-phys-alps-users Digest, Vol 31, Issue 2 > *************************************************** g++ --version g++ (GCC) 4.3.0 20080428 (Red Hat 4.3.0-8) Copyright (C) 2008 Free Software Foundation, Inc. This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. I am afraid it is kind of hardware problem: spinmc_factory.C:194: internal compiler error: Segmentation fault I shall try to install the package on the other machine. It is now for tutorial, the real job will be run elsewhere. Thank you for your reply. Tadeusz Prof. dr hab. Tadeusz Wasiutynski H. Niewodniczanski Institute of Nuclear Physics PAN tel. +48(12)6628251 fax: +48(12)6628251 e-mail: tadeusz.wasiutynski(a)ifj.edu.pl

1 0

internal compiler error
by Tadeusz Wasiutynski 05 Oct '08

05 Oct '08

I try to install alps-applications but there is a problem. Installation of alps library seems to be smooth: make OK make examples OK make tests OK make install OK then in the alps-application directory: ./configure --with-lp_solve=/home/tadek/alps/lp_solve_4.0 configure: loading site script /home/tadek/ALPS/share/config.site configure: loading cache /home/tadek/ALPS/share/alps/config.cache checking for a BSD-compatible install... (cached) /usr/bin/install -c checking whether build environment is sane... yes checking for a thread-safe mkdir -p... (cached) /bin/mkdir -p checking for gawk... (cached) gawk checking whether make sets $(MAKE)... (cached) yes checking whether to enable maintainer-specific portions of Makefiles... no checking for ALPS Libraries... OK checking for ALPS version... 1.3.3 checking for gcc... (cached) gcc checking for C compiler default output file name... a.out checking whether the C compiler works... yes checking whether we are cross compiling... no checking for suffix of executables... checking for suffix of object files... (cached) o checking whether we are using the GNU C compiler... (cached) yes checking whether gcc accepts -g... (cached) yes checking for gcc option to accept ISO C89... (cached) none needed checking for style of include used by make... GNU checking dependency style of gcc... (cached) gcc3 checking for g++... (cached) g++ checking whether we are using the GNU C++ compiler... (cached) yes checking whether g++ accepts -g... (cached) yes checking dependency style of g++... (cached) gcc3 checking build system type... (cached) i686-pc-linux-gnu checking host system type... (cached) i686-pc-linux-gnu checking for a sed that does not truncate output... (cached) /bin/sed checking for grep that handles long lines and -e... (cached) /bin/grep checking for egrep... (cached) /bin/grep -E checking for ld used by gcc... (cached) /usr/bin/ld checking if the linker (/usr/bin/ld) is GNU ld... (cached) yes checking for /usr/bin/ld option to reload object files... (cached) -r checking for BSD-compatible nm... (cached) /usr/bin/nm -B checking whether ln -s works... yes checking how to recognize dependent libraries... (cached) pass_all checking how to run the C preprocessor... (cached) gcc -E checking for ANSI C header files... (cached) yes checking for sys/types.h... (cached) yes checking for sys/stat.h... (cached) yes checking for stdlib.h... (cached) yes checking for string.h... (cached) yes checking for memory.h... (cached) yes checking for strings.h... (cached) yes checking for inttypes.h... (cached) yes checking for stdint.h... (cached) yes checking for unistd.h... (cached) yes checking for dlfcn.h... (cached) yes checking how to run the C++ preprocessor... (cached) g++ -E checking whether we are using the GNU Fortran 77 compiler... (cached) no checking whether no accepts -g... (cached) no checking the maximum length of command line arguments... (cached) 1966080 checking command to parse /usr/bin/nm -B output from gcc object... (cached) ok checking for objdir... (cached) .libs checking for ar... (cached) ar checking for ranlib... (cached) ranlib checking for strip... (cached) strip checking if gcc supports -fno-rtti -fno-exceptions... (cached) yes checking for gcc option to produce PIC... -fPIC checking if gcc PIC flag -fPIC works... (cached) yes checking if gcc static flag -static works... (cached) yes checking if gcc supports -c -o file.o... (cached) yes checking whether the gcc linker (/usr/bin/ld) supports shared libraries... yes checking whether -lc should be explicitly linked in... no checking dynamic linker characteristics... GNU/Linux ld.so (cached) (cached) checking how to hardcode library paths into programs... immediate checking whether stripping libraries is possible... yes checking if libtool supports shared libraries... yes checking whether to build shared libraries... yes checking whether to build static libraries... yes configure: creating libtool appending configuration tag "CXX" to libtool checking for ld used by g++... (cached) /usr/bin/ld checking if the linker (/usr/bin/ld) is GNU ld... (cached) yes checking whether the g++ linker (/usr/bin/ld) supports shared libraries... yes checking for g++ option to produce PIC... -fPIC checking if g++ PIC flag -fPIC works... (cached) yes checking if g++ static flag -static works... (cached) yes checking if g++ supports -c -o file.o... (cached) yes checking whether the g++ linker (/usr/bin/ld) supports shared libraries... yes checking dynamic linker characteristics... GNU/Linux ld.so (cached) (cached) checking how to hardcode library paths into programs... immediate appending configuration tag "F77" to libtool checking for MPI library... no checking for LAPACK library... yes checking for IETL library... /home/tadek/ALPS/include checking ietl/lanczos.h usability... yes checking ietl/lanczos.h presence... yes checking for ietl/lanczos.h... yes checking lpkit.h usability... yes checking lpkit.h presence... yes checking for lpkit.h... yes checking for make_lp in -llpk... yes configure: creating ./config.status config.status: creating Makefile config.status: creating diag/Makefile config.status: creating diag/fulldiag/Makefile config.status: creating diag/sparsediag/Makefile config.status: creating dmrg/Makefile config.status: creating dmrg/dmrg/Makefile config.status: creating dmrg/particle_in_box/Makefile config.status: creating mc/Makefile config.status: creating mc/spins/Makefile config.status: creating qmc/Makefile config.status: creating qmc/checksign/Makefile config.status: creating qmc/looper/Makefile config.status: creating qmc/sse/Makefile config.status: creating qmc/worms/Makefile config.status: creating qmc/qwl/Makefile config.status: creating test/Makefile config.status: creating test/parm config.status: creating test/parm_fermion config.status: creating test/parm_fermion2 config.status: creating test/parm_boson config.status: creating test/energy.xsl config.status: creating test/fulldiag/Makefile config.status: creating test/sparsediag/Makefile config.status: creating test/sparsediag/groundstate.xsl config.status: creating test/checksign/Makefile config.status: creating test/looper/Makefile config.status: creating test/sse/Makefile config.status: creating test/worms/Makefile config.status: creating test/qwl/Makefile config.status: creating test/qwl/parm config.status: creating test/mc/Makefile config.status: creating test/mc/spins/Makefile config.status: creating test/mc/spins/check.sh config.status: creating test/mc/spins/ising_local.parm config.status: creating test/mc/spins/ising_cluster.parm config.status: creating test/mc/spins/heisenberg_chain.parm config.status: creating test/mc/spins/heisenberg_ladder.parm config.status: creating config/config.h config.status: config/config.h is unchanged config.status: executing depfiles commands Summary of configuration: Diagonalization Full yes Sparse yes DMRG DMRG yes Particle in box yes Classical Monte Carlo Spin yes Quantum Monte Carlo Checksign yes Looper yes SSE-dirloop yes Worms yes Quantum Wang-Landau yes In the make step however I encountered: .............. mv -f .deps/fitting_scheduler.Tpo .deps/fitting_scheduler.Po g++ -DHAVE_CONFIG_H -I. -I. -I../.. -DNDEBUG -I/home/tadek/ALPS/include -I/home/tadek/ALPS/include -I/home/tadek/alps/lp_solve_4.0 -pthread -ftemplate-depth-150 -O3 -DBOOST_DISABLE_ASSERTS -fexceptions -w -MT spinmc_factory.o -MD -MP -MF .deps/spinmc_factory.Tpo -c -o spinmc_factory.o spinmc_factory.C spinmc_factory.C: In constructor ‘AbstractSpinSim<MAT>::AbstractSpinSim(const alps::ProcessList&, const alps::Parameters&, int) [with MAT = DiagMatrix<double, 3>]’: spinmc_factory.C:194: internal compiler error: Memory violation Please submit a full bug report, with preprocessed source if appropriate. See <http://bugzilla.redhat.com/bugzilla> for instructions. Preprocessed source stored into /tmp/ccWCP9wP.out file, please attach this to your bugreport. make[2]: *** [spinmc_factory.o] Error 1 make[2]: Opuszczenie katalogu `/home/tadek/alps/alps-applications-1.3.3/mc/spins' make[1]: *** [all-recursive] Error 1 make[1]: Opuszczenie katalogu `/home/tadek/alps/alps-applications-1.3.3/mc' make: *** [all-recursive] Błąd 1 My system is Fedora 9 Where should I go to look for? Prof. dr hab. Tadeusz Wasiutynski H. Niewodniczanski Institute of Nuclear Physics PAN tel. +48(12)6628251 fax: +48(12)6628251 e-mail: tadeusz.wasiutynski(a)ifj.edu.pl

3 4

Customizing the Hamiltonian in the Spinmc Application
by Miles Stoudenmire 02 Oct '08

02 Oct '08

Hi, I'm trying to add a biquadratic term of the form K*(S_i . S_j)^2 to the Hamiltonian of a classical spin system consisting of Heisenberg spins. Also, I'm working on a frustrated lattice, so I'm only using local updates. My thinking at the moment is that I need to primarly make changes to the functions "bond_energy" and "bond_energy_change" in the on.h file. However, that leaves me with two questions. 1) What would be the best (i.e. least obtrusive) way to pass the parameter K into those functions? At the moment they only seem to be able to handle two-spin interactions. Could I perhaps make the code in the on.h file aware of the simulation parameters directly (i.e. such that the code double K = parms["K"] works)? Or, should I make K a field/property of the ONMoment class? Or some other approach (function overloading, then passing K in through a call in localupdate.h)? 2) Could someone please explain what in fact the function bond_energy_change is doing? Here is the function definition: template <class M> inline double bond_energy_change(const ONMoment<M::dim>& m1, const ONMoment<M::dim>& m2, M J, typename ONMoment<M::dim>::update_type dir) { TinyVector<double,M::dim> tmp = dir*dot(dir,m1.state_); return 2.*J.vec_mat_vec(tmp, m2.state_); } I am confused about the above definition in two ways. One is that ONMoment is initialzed as ONMoment<3> for the Heisenberg model, yet here the template calls for a class "M" and refers to "M::dim", though surely an int (i.e. 3) doesn't have a property "dim". Also, my understanding is that the argument "dir" in the above code is a random unit vector and independent of m1.state_. If so, how exactly does the above function give the energy change? Wouldn't the energy change be equal to J.vec_mat_vec((dir - m1.state_),m2.state_) ? That is, whence the factor of 2 and the definition of tmp? Thanks! -- -=Miles Stoudenmire=- miles(a)physics.ucsb.edu miles.stoudenmire(a)gmail.com http://www.crazytheory.com/

1 0