Cheat sheet: Difference between revisions

Line 1:

{| class="wikitable"

|+

!~~Processing~~ workflow. The links given like e.g. [[XDSGUI#Frame]] refer to the XDSwiki at

!<big>XDS processing workflow</big>. The links given like e.g. [[XDSGUI#Frame]] refer to the XDSwiki at

https://wiki.uni-konstanz.de/xds/index.php/

!The programs must have been properly installed - see [[Installation]]. Troubleshooting hints are at [[Problems]].

Line 17:

Type <code>xdsgui</code> and move its window so that you still see the left half of the terminal window.

|Keeping the terminal window to the left of the XDSGUI window makes it possible to see some screen output of XDSGUI, e.g. error messages, or the <code>pointless</code> output.~~~~

|Keeping the terminal window to the left of the XDSGUI window makes it possible to see some screen output of XDSGUI, e.g. error messages, or the <code>pointless</code> output. For HDF5 data from DIAMOND, use <code>export DURIN_PATH= /usr/local/lib64/durin-plugin.so</code>instead (of course with the correct path). The actual path must appear in "Generic frame library" under <code>xdsgui / Preferences ../ Paths</code> on macOS, or <code>Menu / Settings / Paths</code> on Linux, and should appear after LIB= in <code>XDS.INP</code> (below). Optionally, before typing <code>xdsgui</code> : <code>cd</code> to an existing XDS directory, or create a new (empty) directory:<code>cd <toplevel-directory></code>;<code>mkdir <xds-directory>; cd <xds-directory></code>

~~~~For HDF5 data from DIAMOND, use <code>export DURIN_PATH= /usr/local/lib64/durin-plugin.so</code>instead (of course with the correct path). The actual path must appear in "Generic frame library" under <code>xdsgui / Preferences ../ Paths</code> on macOS, or <code>Menu / Settings / Paths</code> on Linux, and should appear after LIB= in <code>XDS.INP</code> (below).~~~~

~~~~Optionally, before typing <code>xdsgui</code> : <code>cd</code> to an existing XDS directory, or create a new (empty) directory:<code>cd <toplevel-directory></code>;<code>mkdir <xds-directory>; cd <xds-directory></code>

|-

|2. click the <code>Projects</code> tab and either choose an existing entry (if there is a list of previous projects) or browse to an existing XDS directory, or create a new (empty) directory

@@ Line 1: / Line 1: @@
 {| class="wikitable"
 |+
-!Processing workflow. The links given like e.g. [[XDSGUI#Frame]] refer to the XDSwiki at
+!<big>XDS processing workflow</big>. The links given like e.g. [[XDSGUI#Frame]] refer to the XDSwiki at
 https://wiki.uni-konstanz.de/xds/index.php/
 !The programs must have been properly installed - see [[Installation]]. Troubleshooting hints are at [[Problems]].
@@ Line 17: / Line 17: @@
 Type <code>xdsgui</code> and move its window so that you still see the left half of the terminal window.
-|<small>Keeping the terminal window to the left of the XDSGUI window makes it possible to see some screen output of XDSGUI, e.g. error messages, or the <code>pointless</code> output.</small>
+|<small>Keeping the terminal window to the left of the XDSGUI window makes it possible to see some screen output of XDSGUI, e.g. error messages, or the <code>pointless</code> output. For HDF5 data from DIAMOND, use <code>export DURIN_PATH= /usr/local/lib64/durin-plugin.so</code>instead (of course with the correct path). The actual path must appear in "Generic frame library" under <code>xdsgui / Preferences ../ Paths</code> on macOS, or <code>Menu / Settings / Paths</code> on Linux, and should appear after LIB= in <code>XDS.INP</code> (below). Optionally, before typing <code>xdsgui</code> : <code>cd</code> to an existing XDS directory, or create a new (empty) directory:<code>cd <toplevel-directory></code>;<code>mkdir <xds-directory>; cd <xds-directory></code></small>
-<small>For HDF5 data from DIAMOND, use <code>export DURIN_PATH= /usr/local/lib64/durin-plugin.so</code>instead (of course with the correct path). The actual path must appear in "Generic frame library" under <code>xdsgui / Preferences ../ Paths</code> on macOS, or <code>Menu / Settings / Paths</code> on Linux, and should appear after LIB= in <code>XDS.INP</code> (below).</small>
-<small>Optionally, before typing <code>xdsgui</code> : <code>cd</code> to an existing XDS directory, or create a new (empty) directory:<code>cd <toplevel-directory></code>;<code>mkdir <xds-directory>; cd <xds-directory></code></small>
 |-
 |2. click the <code>Projects</code> tab and either choose an existing entry (if there is a list of previous projects) or browse to an existing XDS directory, or create a new (empty) directory