Re: [ALPS-users] Time propagation in TEBD stops prematurely
Hi Michael, Unfortunately, the fix you suggested, deleting one of my quenches, only worked for a little bit (although I had to change it a little, by making POW 1 instead of 0 - otherwise the quench did not occur at all). As I've increased Chi up to around 800, I've encountered the same issue as before - namely that the program just stops at around t=5 in the real time propagation when it should continue to t=15, with no error message at all. The parameters of my new Python script, incorporating the suggestion from before is below. Is there anything else I can do? I'm running on a Linux cluster. Any help would be brilliant. Thank you very much, Joseph Python script parameters: parms = [ { 'L' : 128, 'MODEL' : 'spin', 'local_S' : 0.5, 'CONSERVED_QUANTUMNUMBERS' : 'Sz', 'Sz' : 0, 'Jxy' : 1, 'Jz' : 3.0, 'ITP_CHIS' : [80, 80], 'ITP_DTS' : [0.05, 0.025], 'ITP_CONVS' : [1E-10, 1E-11], 'INITIAL_STATE' : 'ground', 'CHI_LIMIT' : 800, 'TRUNC_LIMIT' : 1E-12, 'NUM_THREADS' : 1, 'TAUS' : [15.0], 'POWS' : [1.0], 'GS' : ['Jz'], 'GIS' : [6.0], 'GFS' : [6.0], 'NUMSTEPS' : [625], 'STEPSFORSTORE' : [10], 'VERBOSE' : 'true' } ] On 22 Aug 2013, at 11:00, <comp-phys-alps-users-request@lists.phys.ethz.ch> <comp-phys-alps-users-request@lists.phys.ethz.ch> wrote:
Send Comp-phys-alps-users mailing list submissions to comp-phys-alps-users@lists.phys.ethz.ch
To subscribe or unsubscribe via the World Wide Web, visit https://lists.phys.ethz.ch/listinfo/comp-phys-alps-users or, via email, send a message with subject or body 'help' to comp-phys-alps-users-request@lists.phys.ethz.ch
You can reach the person managing the list at comp-phys-alps-users-owner@lists.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. Alps 2.1.2 r6963 hybridization expansion: No parameter available (backes@th.physik.uni-frankfurt.de) 2. Time propagation in TEBD stops prematurely (Joseph Prentice) 3. Re: Alps 2.1.2 r6963 hybridization expansion: No parameter available (Emanuel Gull) 4. Re: Alps 2.1.2 r6963 hybridization expansion: No parameter available (Hartmut Hafermann) 5. Re: Time propagation in TEBD stops prematurely (Michael Wall) 6. Re: Alps 2.1.2 r6963 hybridization expansion: No parameter available (backes@th.physik.uni-frankfurt.de)
----------------------------------------------------------------------
Message: 1 Date: Wed, 21 Aug 2013 13:51:25 +0200 From: backes@th.physik.uni-frankfurt.de To: comp-phys-alps-users@lists.phys.ethz.ch Subject: [ALPS-users] Alps 2.1.2 r6963 hybridization expansion: No parameter available Message-ID: <70b90575915bdffa61ec46f7481c0ecb.squirrel@th.physik.uni-frankfurt.de> Content-Type: text/plain;charset=utf-8
Dear all,
I want to use the newest version of the ALPS Hybridization Expansion Impurity Solver from the nightly build 2.1.2-r6963. Compilation is successful, but when running the solver with a simple test case I get the following Error (I shortened the paths for readability):
hybridization parm.h5
terminate called after throwing an instance of 'std::runtime_error' what(): No parameter available In [..]/alps/src/alps/ngs/detail/paramproxy.hpp on 78 in cast [..]applications/dmft/qmc/hybridization(_ZNK4alps6detail10paramproxy4castIiEET_v+0x13d) [0x42dbad] [..]applications/dmft/qmc/hybridization(_ZN13hybridizationC1ERKN4alps6paramsEi+0x10b8) [0x43f968] [..]applications/dmft/qmc/hybridization(main+0x103) [0x41dfe3] /lib64/libc.so.6(__libc_start_main+0xfd) [0x7ffff415fcdd] [..]applications/dmft/qmc/hybridization() [0x41d409]
I tested a previous version 2.1.1-r6670 with identical compilation process on the same input files and it works flawlessly.
There seem to be some significant changes in this version: There is a new hybridization2 folder in applications/dmft/qmc/ and also the Documentation inside this directory vanished. Do I have to change something in my parm.h5 input file for this new version?
Thanks for your help. Best wishes, Steffen
------------------------------
Message: 2 Date: Wed, 21 Aug 2013 12:05:05 +0000 From: Joseph Prentice <Joseph.Prentice@physics.ox.ac.uk> To: "comp-phys-alps-users@lists.phys.ethz.ch" <comp-phys-alps-users@lists.phys.ethz.ch> Subject: [ALPS-users] Time propagation in TEBD stops prematurely Message-ID: <747861816F6A5C47BE50FCA07F5B2B4A0E25BB@EXCHNG16.physics.ox.ac.uk> Content-Type: text/plain; charset="us-ascii"
Hi all,
I'm having a bit of trouble with getting a quench using the XXZ model to run in TEBD. I'm running the job on a Linux cluster, quenching Delta instantaneously from 3 to 6, and the program stops earlier than it should. I turned on the Verbose option, and it seems as though the imaginary time propagation works fine, but the real time propagation stops prematurely, with no error message. Does anyone have any idea why this has happened? It seems very odd. I will attach my Python script in case there is something wrong with it, and the output I obtained.
Thanks very much,
Joseph Prentice
Hi Joseph, Your code runs without stopping for me well past 5 time units. Is there a time limit for jobs on your cluster? You may also check any memory restrictions and make sure you are not going over them. Otherwise, I am not able to reproduce this problem. -Michael On Mon, Sep 16, 2013 at 4:10 AM, Joseph Prentice < Joseph.Prentice@physics.ox.ac.uk> wrote:
Hi Michael,
Unfortunately, the fix you suggested, deleting one of my quenches, only worked for a little bit (although I had to change it a little, by making POW 1 instead of 0 - otherwise the quench did not occur at all). As I've increased Chi up to around 800, I've encountered the same issue as before - namely that the program just stops at around t=5 in the real time propagation when it should continue to t=15, with no error message at all. The parameters of my new Python script, incorporating the suggestion from before is below. Is there anything else I can do? I'm running on a Linux cluster. Any help would be brilliant.
Thank you very much, Joseph
Python script parameters: parms = [ { 'L' : 128, 'MODEL' : 'spin', 'local_S' : 0.5, 'CONSERVED_QUANTUMNUMBERS' : 'Sz', 'Sz' : 0, 'Jxy' : 1, 'Jz' : 3.0, 'ITP_CHIS' : [80, 80], 'ITP_DTS' : [0.05, 0.025], 'ITP_CONVS' : [1E-10, 1E-11], 'INITIAL_STATE' : 'ground', 'CHI_LIMIT' : 800, 'TRUNC_LIMIT' : 1E-12, 'NUM_THREADS' : 1, 'TAUS' : [15.0], 'POWS' : [1.0], 'GS' : ['Jz'], 'GIS' : [6.0], 'GFS' : [6.0], 'NUMSTEPS' : [625], 'STEPSFORSTORE' : [10], 'VERBOSE' : 'true' } ]
On 22 Aug 2013, at 11:00, <comp-phys-alps-users-request@lists.phys.ethz.ch
<comp-phys-alps-users-request@lists.phys.ethz.ch> wrote:
Send Comp-phys-alps-users mailing list submissions to comp-phys-alps-users@lists.phys.ethz.ch
To subscribe or unsubscribe via the World Wide Web, visit https://lists.phys.ethz.ch/listinfo/comp-phys-alps-users or, via email, send a message with subject or body 'help' to comp-phys-alps-users-request@lists.phys.ethz.ch
You can reach the person managing the list at comp-phys-alps-users-owner@lists.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. Alps 2.1.2 r6963 hybridization expansion: No parameter available (backes@th.physik.uni-frankfurt.de) 2. Time propagation in TEBD stops prematurely (Joseph Prentice) 3. Re: Alps 2.1.2 r6963 hybridization expansion: No parameter available (Emanuel Gull) 4. Re: Alps 2.1.2 r6963 hybridization expansion: No parameter available (Hartmut Hafermann) 5. Re: Time propagation in TEBD stops prematurely (Michael Wall) 6. Re: Alps 2.1.2 r6963 hybridization expansion: No parameter available (backes@th.physik.uni-frankfurt.de)
----------------------------------------------------------------------
Message: 1 Date: Wed, 21 Aug 2013 13:51:25 +0200 From: backes@th.physik.uni-frankfurt.de To: comp-phys-alps-users@lists.phys.ethz.ch Subject: [ALPS-users] Alps 2.1.2 r6963 hybridization expansion: No parameter available Message-ID: < 70b90575915bdffa61ec46f7481c0ecb.squirrel@th.physik.uni-frankfurt.de> Content-Type: text/plain;charset=utf-8
Dear all,
I want to use the newest version of the ALPS Hybridization Expansion Impurity Solver from the nightly build 2.1.2-r6963. Compilation is successful, but when running the solver with a simple test case I get the following Error (I shortened the paths for readability):
hybridization parm.h5
terminate called after throwing an instance of 'std::runtime_error' what(): No parameter available In [..]/alps/src/alps/ngs/detail/paramproxy.hpp on 78 in cast
[..]applications/dmft/qmc/hybridization(_ZNK4alps6detail10paramproxy4castIiEET_v+0x13d)
[0x42dbad]
[..]applications/dmft/qmc/hybridization(_ZN13hybridizationC1ERKN4alps6paramsEi+0x10b8)
[0x43f968] [..]applications/dmft/qmc/hybridization(main+0x103) [0x41dfe3] /lib64/libc.so.6(__libc_start_main+0xfd) [0x7ffff415fcdd] [..]applications/dmft/qmc/hybridization() [0x41d409]
I tested a previous version 2.1.1-r6670 with identical compilation process on the same input files and it works flawlessly.
There seem to be some significant changes in this version: There is a new hybridization2 folder in applications/dmft/qmc/ and also the Documentation inside this directory vanished. Do I have to change something in my parm.h5 input file for this new version?
Thanks for your help. Best wishes, Steffen
------------------------------
Message: 2 Date: Wed, 21 Aug 2013 12:05:05 +0000 From: Joseph Prentice <Joseph.Prentice@physics.ox.ac.uk> To: "comp-phys-alps-users@lists.phys.ethz.ch" <comp-phys-alps-users@lists.phys.ethz.ch> Subject: [ALPS-users] Time propagation in TEBD stops prematurely Message-ID: <747861816F6A5C47BE50FCA07F5B2B4A0E25BB@EXCHNG16.physics.ox.ac.uk> Content-Type: text/plain; charset="us-ascii"
Hi all,
I'm having a bit of trouble with getting a quench using the XXZ model to run in TEBD. I'm running the job on a Linux cluster, quenching Delta instantaneously from 3 to 6, and the program stops earlier than it should. I turned on the Verbose option, and it seems as though the imaginary time propagation works fine, but the real time propagation stops prematurely, with no error message. Does anyone have any idea why this has happened? It seems very odd. I will attach my Python script in case there is something wrong with it, and the output I obtained.
Thanks very much,
Joseph Prentice
participants (2)
-
Joseph Prentice
-
Michael Wall