Section 2: second run-through #57

sphuber · 2019-05-09T16:32:45Z

Added a new section near the beginning where the user is instructed to
import an export archive, that will be made available at a permanent
public URL later. This will contain the calculations on perovskites
using Quantum ESPRESSO that will be used later in the query builder
section. In this section, this data will also serve to illustrate the
verdi process commands.

I have rewritten quite a bit of text concerning the language around and
the explanation of identifiers. Since identifiers play such a big role
in verdi and this section is about how to use the command line, I
thought it merited some more detail.

Added a new section near the beginning where the user is instructed to import an export archive, that will be made available at a permanent public URL later. This will contain the calculations on perovskites using Quantum ESPRESSO that will be used later in the query builder section. In this section, this data will also serve to illustrate the `verdi process` commands. I have rewritten quite a bit of text concerning the language around and the explanation of identifiers. Since identifiers play such a big role in `verdi` and this section is about how to use the command line, I thought it merited some more detail.

docs/pages/2019_MARVEL_Psik_MaX/sections/verdi_cmdline.rst

ltalirz

thanks a lot @sphuber !
a few more suggestions from my side

ltalirz

thanks a lot for the thorough read!

sphuber · 2019-05-09T17:22:01Z

thanks a lot for the thorough read!

Right back at ya for the thorough PR. Now go get some sleep! ;)

sphuber · 2019-05-09T17:37:09Z

The latex builds are failing because of the unicode symbols in the verdi process list output. These are the typical solutions but they require access to the actual tex document. Not sure how the latex build works and how to tell it to expect utf-8 characters

ltalirz · 2019-05-09T23:55:42Z

For a proper explanation of what to do see here.
I just tried switching to xelatex for the build which would have simply ignored the error (and not shown the character in the pdf) but it turns out xelatex isn't available on travis.

The proper way to fix it would be to define a latex representation of the character as
\newunicodechar{⏹}{\ensuremath{\square}}

+ provide latex representation of square character

sphuber requested a review from ltalirz May 9, 2019 16:32