Hi, My [quick-and-ugly] solution to this was to make ad hoc xslt worksheets. For example, I was running a series of simulations for a set of system sizes, so that there is a set of xml output files with different values of L. Then I first archive them all using the archivecat utility, and then run xslttransform ene_L.xsl archive.xml where ene_L.xsl is listed below. I'm sure there are more elegant and more generic solutions. Cheers, Zhenya ----------------------- cut me ------------------------------ <?xml version="1.0" encoding="ISO-8859-1"?> <xsl:stylesheet version="1.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform"> <xsl:output method="text"/> <xsl:template match="/"> <xsl:for-each select="/ARCHIVE"> <xsl:for-each select="SIMULATION"> <xsl:value-of select="PARAMETERS/PARAMETER[@name='L']"/> <xsl:text> </xsl:text> <xsl:for-each select="EIGENSTATES/EIGENSTATE[@number=0]/SCALAR_AVERAGE"> <xsl:if test="@name='Energy'"> <xsl:value-of select="MEAN"/> </xsl:if> </xsl:for-each> </xsl:for-each> </xsl:for-each> <xsl:text> </xsl:text> </xsl:template> </xsl:stylesheet> ------------------------------ cut me ---------------------- João Manuel Viana Parente Lopes wrote:
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