On Dec 27, 2012, at 4:31 PM, Deepak Iyer deepak.g.iyer@gmail.com wrote:

Hi

Thanks for the reply! I've seen this page. I was hoping there'd be a more detailed doc on this.

Each function has built-in help.

In particular, I can't get the functions loadObservableList and loadMeasurements to work (i.e. the return empty lists) with custom observables in sparsediag. Does it work only for internal hardcoded measurements, or am I doing something wrong?

No, it loads everything that has been measured.

Also MEASURE_LOCAL is ignored, and MEASURE_AVERAGE gives me an average for each site. I'm confused by this.

MEASURE_LOCAL is not used when the lattice is translation invariant, as it is the same as MEASURE_AVERAGE in that case. MEASURE_AVERAGE, as the name says, averages over all sites.

Look at the built-in documentation of these functions. This can. e,g, be done by:

from pydoc import help help(pyalps.flatten)

Best regards

Matthias Troyer

Also other functions like flatten etc that are used in the tutorials are not described on this page. Where can I find docs for them?

Thanks and sorry for the trouble! Deepak

On Thu, Dec 27, 2012 at 6:29 AM, Matthias Troyer troyer@phys.ethz.ch wrote: Hi Deepak,

The pyalps functions are listed at http://alps.comp-phys.org/mediawiki/index.php/Documentation:The_palps_Python... . The hard coded measurements depend on the code that you run, and are documented with the codes.

Matthias Troyer

On Dec 27, 2012, at 4:04 AM, Deepak Iyer deepak.g.iyer@gmail.com wrote:

...

Hi

New user here.

I've been looking for some docs where there is a complete list of all the pyalps functions with descriptions. Also, is there some place I can find a list of all the hardcoded measurements, etc.?

Thanks! Deepak

On Dec 27, 2012, at 16:57, Deepak Iyer deepak.g.iyer@gmail.com wrote:

On Thu, Dec 27, 2012 at 10:37 AM, Matthias Troyer troyer@phys.ethz.ch wrote:

...

Each function has built-in help.

Thanks! That makes life much easier :)

...

...

In particular, I can't get the functions loadObservableList and loadMeasurements to work (i.e. the return empty lists) with custom observables in sparsediag. Does it work only for internal hardcoded measurements, or am I doing something wrong?

No, it loads everything that has been measured.

Will have to play with this - still coming up with empty lists.

...

...

Also MEASURE_LOCAL is ignored, and MEASURE_AVERAGE gives me an average for each site. I'm confused by this.

MEASURE_LOCAL is not used when the lattice is translation invariant, as it is the same as MEASURE_AVERAGE in that case. MEASURE_AVERAGE, as the name says, averages over all sites.

I'm confused. So say I'm doing a MEASURE_AVERAGE[mag] : 'Sz', am I expected to get $\sum_j <Sz(j)>$ ? I get a list of 12 values for a L=12 chain.

Is the chain open or periodic? If periodic you will get a single value.

Thanks again!

...

Look at the built-in documentation of these functions. This can. e,g, be done by:

from pydoc import help help(pyalps.flatten)

Best regards

Matthias Troyer

...

Also other functions like flatten etc that are used in the tutorials are not described on this page. Where can I find docs for them?

Thanks and sorry for the trouble! Deepak

On Thu, Dec 27, 2012 at 6:29 AM, Matthias Troyer troyer@phys.ethz.ch wrote:

...

Hi Deepak,

The pyalps functions are listed at http://alps.comp-phys.org/mediawiki/index.php/Documentation:The_palps_Python... . The hard coded measurements depend on the code that you run, and are documented with the codes.

Matthias Troyer

On Dec 27, 2012, at 4:04 AM, Deepak Iyer deepak.g.iyer@gmail.com wrote:

...

Hi

New user here.

I've been looking for some docs where there is a complete list of all the pyalps functions with descriptions. Also, is there some place I can find a list of all the hardcoded measurements, etc.?

Thanks! Deepak

Nope, never mind. I was misreading the data. Was looking at diagonal spin correlators instead of average spin. Sorry about that, and thanks for your help! I'll try to figure out why my loadObservableList and loadMeasurements produces nothing. I have to use loadEigenstateMeasurements.

Cheers! Deepak

On Thu, Dec 27, 2012 at 1:18 PM, Deepak Iyer deepak.g.iyer@gmail.comwrote:

On Thu, Dec 27, 2012 at 11:55 AM, Matthias Troyer troyer@phys.ethz.chwrote:

...

Is the chain open or periodic? If periodic you will get a single value.

I'm using LATTICE="chain lattice". The lattice.xml file indicates that it

is periodic.

D

...

Thanks again!

Look at the built-in documentation of these functions. This can. e,g, be

...

done by:

from pydoc import help help(pyalps.flatten)

Best regards

Matthias Troyer

Also other functions like flatten etc that are used in the tutorials are not described on this page. Where can I find docs for them?

Thanks and sorry for the trouble! Deepak

On Thu, Dec 27, 2012 at 6:29 AM, Matthias Troyer troyer@phys.ethz.chwrote:

...

Hi Deepak,

The pyalps functions are listed at http://alps.comp-phys.org/mediawiki/index.php/Documentation:The_palps_Python.... The hard coded measurements depend on the code that you run, and are documented with the codes.

Matthias Troyer

On Dec 27, 2012, at 4:04 AM, Deepak Iyer deepak.g.iyer@gmail.com wrote:

...

Hi

New user here.

I've been looking for some docs where there is a complete list of all

the pyalps functions with descriptions. Also, is there some place I can find a list of all the hardcoded measurements, etc.?

...

Thanks! Deepak

I see. Great, thanks!

On Thu, Dec 27, 2012 at 1:24 PM, Matthias Troyer troyer@phys.ethz.chwrote:

On Dec 27, 2012, at 7:22 PM, Deepak Iyer deepak.g.iyer@gmail.com wrote:

...

Nope, never mind. I was misreading the data. Was looking at diagonal

spin correlators instead of average spin. Sorry about that, and thanks for your help! I'll try to figure out why my loadObservableList and loadMeasurements produces nothing. I have to use loadEigenstateMeasurements.

If you're using the diag codes then indeed you need to use loadEigenstateMeasurements. loadMeasurements can be used there only if you evaluate (using fulldiag) a thermal average at one fixed temperature.

Dear All, I am running a large alps calculation. It has been running for 2 days, Until yesterday it seemed to work, but the last lines of the output are:

Checking if Simulation 41 is finished: not yet, next check in 900 seconds ( 35% done). Checking if Simulation 42 is finished: not yet, next check in 900 seconds ( 33% done). Checking if Simulation 43 is finished: not yet, next check in 900 seconds ( 32% done). Checking if Simulation 44 is finished: not yet, next check in 900 seconds ( 31% done). Checking if Simulation 45 is finished: not yet, next check in 900 seconds ( 29% done). Checking if Simulation 46 is finished: not yet, next check in 900 seconds ( 26% done). Checking if Simulation 47 is finished: not yet, next check in 900 seconds ( 23% done). Checking if Simulation 48 is finished: not yet, next check in 900 seconds ( 25% done). Checking if Simulation 49 is finished: not yet, next check in 900 seconds ( 29% done). Checking if Simulation 50 is finished: not yet, next check in 900 seconds ( 28% done). Checking if Simulation 51 is finished: not yet, next check in 900 seconds ( 30% done). Checking if Simulation 52 is finished: not yet, next check in 900 seconds ( 25% done). Checking if Simulation 53 is finished: not yet, next check in 900 seconds ( 29% done). Checking if Simulation 54 is finished: not yet, next check in 900 seconds ( 24% done). Checking if Simulation 55 is finished: not yet, next check in 900 seconds ( 24% done). Checking if Simulation 56 is finished: not yet, next check in 900 seconds ( 23% done). Checking if Simulation 57 is finished: not yet, next check in 900 seconds ( 23% done). Avoided problem Avoided problem Avoided problem

and from this point on several "Avoided problem" lines have been written (last one about 5 minutes ago), but nothingelse (np checking in particular). Is this normal? It this is not normal I can provide more data...

Regards, Mateusz Łącki

Dear All: Another update: it seems that it is possible to avoid the problem I mentioned by partitioning list of input cases into several files, that is

instead

parm5a: {T=1} {T=2} {T=3} ...

I have parm5a_1: {T=1} {T=2} parm5a_2: {T=3} {T=4} parm5a_3: {T=5} {T=6} ...

and this works.

I have no idea why though... All in all it seems I am able to do the computation within worm 2.0.2, but nevertheless I think I am still reporting the issue before as annoying problem.

Regards, Mateusz Łącki

Le Dec 28, 2012 à 10:03 AM, Mateusz Łącki a écrit :

One more thing: I am using worm 2.02 - perhaps this is something fixed in 2.1.....