<html>
<head>
<meta content="text/html; charset=utf-8" http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<p>Hello Thorsten <br>
</p>
<p>Thanks for signaling us these issues. We will try to fix them
soon. <br>
</p>
<p>If the version you have deployed is the tagged 6.1 version the
new format is activated only if you set the "--enable-xml=yes"
option while running the configure script (the default value for
this option in 6.1 is no). This option in 6.1 version defines
the preprocessor flag -D__XSD inside the make.inc file. When
this flag is not defined the program is compiled using the old
XML format and discards all code related to new XML output. If you
are using 6.1 check that the -D__XSD option is not there, and
you will be using the old xml format. <br>
</p>
<p>The situation has been reversed in SVN revisions following the
6.1 release; the default value for the --enable-xml option has
been set to "yes" and you must specify it as "no" for
reverting to the old XML format. <br>
</p>
<p>In the development version you can check inside the make.inc
file that the -D__OLDXML preprocessor flag is appended to the
DFLAGS. If it is, you are using old xml format. In case it is
not it is sufficient to append it and recompile from scratch. <br>
</p>
<p> thanks again, greetings Pietro </p>
<p><br>
</p>
<div class="moz-cite-prefix">On 15/05/2017 18:01, Stefano Baroni
wrote:<br>
</div>
<blockquote cite="mid:E9161AC9-FCF9-4CEF-BECD-6DEFB211CFCC@sissa.it"
type="cite">
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
Thank you for your note, Kurth. Please, note that the appropriate
address to report this kind of problems is <a
moz-do-not-send="true" href="mailto:q-e-developers@qe-forge.org"
class="">q-e-developers@qe-forge.org</a>, to I which I am
forwarding this email. I am forwarding to Pietro Delugas as well,
who may give you direct advice on the reported issue. best regards
- Stefano B
<div class=""><br class="">
<div>
<blockquote type="cite" class="">
<div class="">On 15 May 2017, at 17:42, Thorsten Kurth <<a
moz-do-not-send="true" href="mailto:tkurth@lbl.gov"
class="">tkurth@lbl.gov</a>> wrote:</div>
<br class="Apple-interchange-newline">
<div class="">
<title class=""></title>
<div class="">
<div name="messageBodySection" style="font-size: 14px;
font-family: -apple-system, BlinkMacSystemFont,
sans-serif;" class="">Dear developers, QE maintainers,<br
class="">
<br class="">
we deployed QE 6.1 on Cori at NERSC and get a lot of
error reports which are IO related. Most of them might
be attributed to migrating to a new file form. The
main errors include:<br class="">
<br class="">
1) files written by pw.x cannot be read by pw2bgw.x,
it complains about a missing XML.<br class="">
<br class="">
2) files written by pw.x cannot be processed by gipaw
either.
<div class=""><br class="">
</div>
<div class="">Do I need to specify a certain flag to
switch to the old formats as long as the new one is
not fully implemented? Or are these two cases
supposed to work?</div>
<div class=""><br class="">
</div>
<div class="">Best Regards</div>
<div class="">Thorsten Kurth</div>
</div>
</div>
</div>
</blockquote>
</div>
<br class="">
</div>
<br class="">
<br class="">
<div class="">
<div style="color: rgb(0, 0, 0); letter-spacing: normal;
orphans: auto; text-align: start; text-indent: 0px;
text-transform: none; white-space: normal; widows: auto;
word-spacing: 0px; -webkit-text-stroke-width: 0px; word-wrap:
break-word; -webkit-nbsp-mode: space; -webkit-line-break:
after-white-space;" class="">
<div style="color: rgb(0, 0, 0); letter-spacing: normal;
orphans: auto; text-align: start; text-indent: 0px;
text-transform: none; white-space: normal; widows: auto;
word-spacing: 0px; -webkit-text-stroke-width: 0px;
word-wrap: break-word; -webkit-nbsp-mode: space;
-webkit-line-break: after-white-space;" class="">
<div style="orphans: auto; text-align: start; text-indent:
0px; widows: auto; word-wrap: break-word;
-webkit-nbsp-mode: space; -webkit-line-break:
after-white-space;" class="">
<div style="orphans: auto; text-align: start; text-indent:
0px; widows: auto; word-wrap: break-word;
-webkit-nbsp-mode: space; -webkit-line-break:
after-white-space;" class="">
<div style="word-wrap: break-word; -webkit-nbsp-mode:
space; -webkit-line-break: after-white-space;"
class="">
<div style="orphans: auto; text-align: start;
text-indent: 0px; widows: auto;"><span
style="font-size: 12px;" class="">—</span></div>
<div style="orphans: auto; text-align: start;
text-indent: 0px; widows: auto;"><span
style="font-size: 12px;" class="">Stefano Baroni -
SISSA, Trieste - <a moz-do-not-send="true"
href="http://stefano.baroni.me" class="">http://stefano.baroni.me</a>, stefanobaroni (skype)</span></div>
<div style="orphans: auto; text-align: start;
text-indent: 0px; widows: auto;"><span
style="font-size: 12px;" class=""><br class="">
</span></div>
<div style="color: rgb(0, 0, 0); letter-spacing:
normal; text-transform: none; white-space: normal;
word-spacing: 0px; -webkit-text-stroke-width: 0px;
font-variant-caps: normal; orphans: auto;
text-align: start; text-indent: 0px; widows: auto;"><span
style="font-size: 12px;" class="">There are two
ways of doing a theoretical calculation: you
should have either a clear physical model in mind,
or a rigorous mathematical basis. You have
neither. [E. Fermi to F.J. Dyson, as humbly
reported by the latter]</span></div>
</div>
</div>
</div>
</div>
</div>
</div>
<br class="">
</blockquote>
<br>
</body>
</html>