2,652
edits
XDSGUI: Difference between revisions
Jump to navigation
Jump to search
no edit summary
(→TOOLS) |
No edit summary |
||
| Line 58: | Line 58: | ||
== Availability == | == Availability == | ||
The program is under development and has bugs. If it crashes, it should simply be restarted. A crash of the program does not interfere with the operation of [[XDS]]. | The program is under development and probably has bugs. If it crashes, it should simply be restarted. A crash of the program does not interfere with the operation of [[XDS]]. | ||
The current version of the program can be downloaded from [ftp://turn5.biologie.uni-konstanz.de/pub/xdsGUI.rhel6.64] (Linux 64bit), [ftp://turn5.biologie.uni-konstanz.de/pub/xdsGUI.rhel6.32] (Linux 32bit), or [ftp://turn5.biologie.uni-konstanz.de/pub/xds-gui.dmg] (Mac OSX 10.7). | The current version of the program can be downloaded from [ftp://turn5.biologie.uni-konstanz.de/pub/xdsGUI.rhel6.64] (Linux 64bit), [ftp://turn5.biologie.uni-konstanz.de/pub/xdsGUI.rhel6.32] (Linux 32bit), or [ftp://turn5.biologie.uni-konstanz.de/pub/xds-gui.dmg] (Mac OSX 10.7). | ||
== Dependencies == | === Dependencies === | ||
XDSgui depends on | XDSgui depends on [[generate_XDS.INP]], [[XDS-viewer]], and of course [[xds|xds_par]], [[xds]], and [[xdsconv]]. The XDSSTAT tab requires [[xdsstat]]. One of the items in the TOOLS tab calls a graphical file comparison program; if the default (xdiff) is not available, [http://furius.ca/xxdiff xxdiff] or [http://sourceforge.net/projects/tkdiff tkdiff] may be used - please adjust the commandline below the button accordingly. | ||
Technically, the word "dependency" means that these scripts/programs should be in your $PATH - an 'alias' is often not good enough because the TOOLS commands use bash as a shell, and that shell does not inherit the aliases from e.g. (t)csh. | |||
== Known bugs / problems / workarounds == | == Known bugs / problems / workarounds == | ||
# ''Question concerning TOOLS: "Show frame..." on Mac: it creates everything shown in the commandline but it seem to us that everything runs in the background. Therefore xds-viewer does not open anywhere as it is not seen. Also, it would be great if this image together with the predictions would be re-directed to the FRAME tab.'' <br> Answer: On Linux, the xds-viewer window is brought to the foreground automatically, whereas on the Mac this does not seem to happen. However, an icon for xds-viewer appears in the dock (on the right) and I can double-click it to see the xds-viewer window. I have no idea how to bring xds-viewer to the foreground automatically, and I need input from people who know Macs and tell me how to do it (on the commandline!). The reason why we do not open automatically in the FRAME tab is that one can have several xds-viewer windows open at the same time, and compare the patterns. As a '''workaround''', you can manually open the resulting temp/FRAME_$X.cbf in the FRAME tab. | # ''Question concerning TOOLS: "Show frame..." on Mac: it creates everything shown in the commandline but it seem to us that everything runs in the background. Therefore xds-viewer does not open anywhere as it is not seen. Also, it would be great if this image together with the predictions would be re-directed to the FRAME tab.'' <br> Answer: On Linux, the xds-viewer window is brought to the foreground automatically, whereas on the Mac this does not seem to happen. However, an icon for xds-viewer appears in the dock (on the right) and I can double-click it to see the xds-viewer window. I have no idea how to bring xds-viewer to the foreground automatically, and I need input from people who know Macs and tell me how to do it (on the commandline!). The reason why we do not open automatically in the FRAME tab is that one can have several xds-viewer windows open at the same time, and compare the patterns. As a '''workaround''', you can manually open the resulting temp/FRAME_$X.cbf in the FRAME tab. | ||
# ''Another question concerning TOOLS: "Further analyses" on Mac: again pointless runs nicely but there is no output for the user.'' <br> Answer: Could it be that you started xds-gui by double-clicking its icon in the Finder? In that case, there is no output visible, because there is no console. Unfortunately, for all the Tools, the output is in the console window where xds-gui was started. We will try to find out how to open a window where the output is then shown. Thus, currently the '''workaround''' for this problem is to start xds-gui in a console window. | # ''Another question concerning TOOLS: "Further analyses" on Mac: again pointless runs nicely but there is no output for the user.'' <br> Answer: Could it be that you started xds-gui by double-clicking its icon in the Finder? In that case, there is no output visible, because there is no console. Unfortunately, for all the Tools, the output is in the console window where xds-gui was started. We will try to find out how to open a window where the output is then shown. Thus, currently the '''workaround''' for this problem is to start xds-gui in a console window. | ||
If you find a bug, please send email to Kay dot Diederichs at uni-konstanz dot de , ideally with enough information/data to reproduce the bug. | |||
== News == | |||
program updated May 22, May 28, June 5. | |||