<html><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class="">Hello,<div class=""><br class=""></div><div class=""><blockquote type="cite" class=""><div dir="ltr" class=""><div class=""><div class="">Q1: Are the indices, (i_11, ...i_1n), the vertex ids or vertex coordinates or the index of the vertex in some array, or sth else?</div></div></div></blockquote><div class=""><br class=""></div><div class="">They are correspond to the sequential index of the lattice vertexes.</div><div class="">The best way to understand the sequence is by using the “printgraph” application.</div><div class=""><br class=""></div><br class=""><blockquote type="cite" class=""><div dir="ltr" class=""><div class=""><div class="">Q2: I understand that the restriction i_1 < i_2 < i_3 ... is probably there to simplify the MPS contraction but is there a simple way to go around it?</div></div></div></blockquote><div class=""><br class=""></div><div class="">I would suggest to make a script to generate all the different measurements.</div><div class="">You could put them in the same parameter file, but usually I suggest to make different runs, such that you can launch all in parallel on a cluster.</div><div class=""><br class=""></div><br class=""><blockquote type="cite" class=""><div dir="ltr" class=""><div class=""><div class="">Q3: There is no limit on the number of measurement or the number of operators that can be defined, right?</div></div></div></blockquote></div><div class=""><div dir="ltr" class=""><div class=""><div class=""><br class=""></div><div class="">No, I don’t think there is an actual limit, if not the memory that they will require.</div><div class=""><br class=""></div></div></div></div><div class=""><br class=""></div><div class="">Best,<br class=""><div class="">
<span class="Apple-style-span" style="border-collapse: separate; font-variant-ligatures: normal; font-variant-east-asian: normal; font-variant-position: normal; line-height: normal; border-spacing: 0px;"><div class="">Michele</div><div class=""><br class=""></div></span><br class="Apple-interchange-newline">
</div>
<div><br class=""><blockquote type="cite" class=""><div class="">On 22 Nov 2017, at 20:38, Amir M.Aghaei <<a href="mailto:amir.maghaei@gmail.com" class="">amir.maghaei@gmail.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div dir="ltr" class=""><div class="">Hi,<br class=""></div><div class=""><br class=""></div><div class="">This is the documentation for 'MEASURE_LOCAL_AT'</div><div class=""><br class=""></div><div class=""><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><code class="">MEASURE_LOCAL_AT[NAME]</code> <br class="">Syntax for the value:<div class="gmail-image">
<img src="http://alps.comp-phys.org/static/mps_doc/local_at_value.svg" alt="local_at_value.svg" class="">
</div>Defines a new measurement called <code class="">NAME</code> where the sequence of operators <code class="">op_1:...:op_n</code> is applied to all tuples of indices (of length <em class="">n</em> like the number of operators) listed after the vertical bar symbol.<br class=""></blockquote><div class=""><br class=""></div><div class="">I have three question:</div><div class=""><br class=""></div><div class="">Q1: Are the indices, (i_11, ...i_1n), the vertex ids or vertex coordinates or the index of the vertex in some array, or sth else?</div><div class=""><br class=""></div><div class="">Q2: I understand that the restriction i_1 < i_2 < i_3 ... is probably there to simplify the MPS contraction but is there a simple way to go around it?</div><div class=""><br class=""></div><div class="">Q3: There is no limit on the number of measurement or the number of operators that can be defined, right?</div><div class=""><br class=""></div><div class="">Amir<br class=""></div><br class=""><div class=""><code class=""><code class=""><code class=""><br class=""></code></code></code></div><span class="gmail-gI"><span class=""></span></span></div></div>
<br class=""><br class="">----<br class="">Comp-phys-alps-users Mailing List for the ALPS Project<br class=""><a href="http://alps.comp-phys.org/" class="">http://alps.comp-phys.org/</a><br class=""><br class="">List info: https://lists.phys.ethz.ch//listinfo/comp-phys-alps-users<br class="">Archive: https://lists.phys.ethz.ch//pipermail/comp-phys-alps-users<br class=""><br class="">Unsubscribe by writing a mail to comp-phys-alps-users-leave@lists.phys.ethz.ch.</div></blockquote></div><br class=""></div></body></html>