GUI and X servers
Hi, I am accessing our linux server (where phenix sits) via Exceed X server from Windows machine, and everything used to work fine until recent (I think from v.1-5-2) versions of phenix. Now if I launch new GUI, mouse position is not recognised anymore not only by phenix, but then also by other programs - so if I click on something, something else completely gets activated. I did not change any Exceed settings, so the problem seems to be due to phenix. Also, same thing happens with Xming server. If I access from Mac machine, everything seems to be OK. Has anybody seen it and what could be the reason for that? Thanks! -- Dr. Leonid A. Sazanov Research group leader Medical Research Council Mitochondrial Biology Unit Wellcome Trust / MRC Building Hills Road Cambridge CB2 0XY WEB: www.mrc-mbu.cam.ac.uk Tel: +44-1223-252910 Fax: +44-1223-252915
On Oct 30, 2009, at 11:10 AM, Leo Sazanov wrote:
Hi, I am accessing our linux server (where phenix sits) via Exceed X server from Windows machine, and everything used to work fine until recent (I think from v.1-5-2) versions of phenix. Now if I launch new GUI, mouse position is not recognised anymore not only by phenix, but then also by other programs - so if I click on something, something else completely gets activated. I did not change any Exceed settings, so the problem seems to be due to phenix. Also, same thing happens with Xming server. If I access from Mac machine, everything seems to be OK. Has anybody seen it and what could be the reason for that?
I had never tried this until now, but I experienced a similar problem on our lone Windows system here (XP and Exceed 9, I think). The GUI wasn't really designed to be run remotely over X11 - it should work, mostly, but it's not really the most robust method and anything involving OpenGL may cause problems. A better solution is to use desktop virtualization software: NoMachine's NX Server is an excellent product, which we use extensively. They have a free version, which lacks support but (according to Paul) is otherwise fully functional. (The server is only for Linux and Solaris, but there are clients for Mac and Windows too.) -Nat ------------------- Nathaniel Echols Lawrence Berkeley Lab 510-486-5136 [email protected]
Hi Nat I try to use a shiny new GUI for Phaser I stuck with the definition of a component mass. Line command accept "None" for mass of component, but not GUI. It claims that the mass calculated value I supply is not integer number, for the sake of argument I have tried 14, 14.0 etc. (BTW as a sequence is also supplied, why just not to calculate it?). So for a wile back to line commands until you will suggest a solution Dr Felix Frolow Professor of Structural Biology and Biotechnology Department of Molecular Microbiology and Biotechnology Tel Aviv University 69978, Israel Acta Crystallographica D, co-editor e-mail: [email protected] Tel: ++972 3640 8723 Fax: ++972 3640 9407 Cellular: ++972 547 459 608
On Nov 2, 2009, at 3:38 AM, Felix Frolow wrote:
I try to use a shiny new GUI for Phaser I stuck with the definition of a component mass. Line command accept "None" for mass of component, but not GUI. It claims that the mass calculated value I supply is not integer number, for the sake of argument I have tried 14, 14.0 etc. (BTW as a sequence is also supplied, why just not to calculate it?).
Just to clarify for the list, there is a new AutoMR GUI in the current nightly builds. (Not for Phaser itself - that's on the to-do list.) It will feed results directly to AutoSol if you are trying to phase with MR-SAD. Felix already figured out the answer, but it's a little confusing: AutoMR (like Phaser) is flexible about how you specify the component mass, but you can only use one source of information - defining both the sequence and the mass will result in an error message. More generally, in the GUI 'None' (which is really the standard Python null value, not some Phenix-specific keyword) is translated to a blank string, so if you want to set a parameter to None, just leave the field blank. -Nat ------------------- Nathaniel Echols Lawrence Berkeley Lab 510-486-5136 [email protected]
participants (3)
-
Felix Frolow -
Leo Sazanov -
Nathaniel Echols