Hi,
I am currently running chimera remotely on a computer using "ssh" commands. I have been using the "chimera --send" command to send cmd and python scripts to a computer running chimera. I was wondering if it were possible for me to run 2 or more instances of Chimera on a computer and control which instance of Chimera the "--send" script is executed by.
Thanks for your help,
Chris
Hi Chris,
There is currently no provision for "chimera --send file" to specify which Chimera the file should be sent to. If multiple Chimera instances are running on the same machine as the same user then the instance whose main window most recently had the input focus is the one that gets the file. You could exploit that by somehow giving the focus to the instance you want before doing the "chimera --send". This will be erratic unless you have a means of setting the focus that is synchronous so you can be sure it happened before the "chimera --send" is run. Another ugly approach is to run your Chimera instances under different user accounts on the same machine.
The chimera --send implementation uses a socket with a randomly assigned port number. The port number is put into a file on the local file system specific to the user. When "chimera --send" is run it looks for that file to get the port number. There's no provision in the code to keep track of multiple Chimera instances listening on different ports. Instead, when a Chimera instance gets the input focus, it overwrites the file containing the port number. This code is in
chimera/share/DBPuppet/__init__.py
see the portOnTop(), write_webinfo(), remove_webinfo() routines.
A better design to handle your case would allow you to specify the port number when you start a Chimera instance and also when you later use chimera --send.
I guess you are doing interesting stuff with Chimera on a tiled wall. I'd be interested in hearing some details.
Tom
-------- Original Message -------- Subject: [Chimera-users] Chimera --send command From: cdlau@ucsd.edu To: chimera-users@cgl.ucsf.edu Date: 7/12/09 7:32 PM
Hi,
I am currently running chimera remotely on a computer using "ssh" commands. I have been using the "chimera --send" command to send cmd and python scripts to a computer running chimera. I was wondering if it were possible for me to run 2 or more instances of Chimera on a computer and control which instance of Chimera the "--send" script is executed by.
Thanks for your help,
Chris _______________________________________________ Chimera-users mailing list Chimera-users@cgl.ucsf.edu http://www.cgl.ucsf.edu/mailman/listinfo/chimera-users
Hello! The recent chimera builds seem to ignore my standard molecule settings (ball and stick defaults to stick only) and the files to be read at startup. I normally read in a file with my custom colordefs, but when I set that, close chimera and open it again, this setting is lost. Is this a known issue, or is it just with my installation?
Thanks for any hints,
Thomas
Hi Thomas, We recently changed Chimera so that molecules are initially displayed in a fashion very similar to the "Interactive 1 (ribbons)" preset rather than wireframe. This behavior is controlled by a new "smart initial display" New Molecule preference, which defaults to true. When that preference is true, many of the other preferences in that category are overridden*. So to get back to the behavior you had before, set "smart initial display" to false. Perhaps this is also the issue with you problem with colordefs, but I don't completely understand your description of that. Are we talking about Command Line startup files? Do you mean that you put a file in the list of Command Line file to read at startup and it's not in the list the next time you start Chimera? (You did click the 'Save' button, right?)
--Eric
Eric Pettersen UCSF Computer Graphics Lab http://www.cgl.ucsf.edu
* all other prefs are overridden except for those dealing with initial model color, metal complexes, Mol2 model naming, line width, and ball/ stick scale.
On Aug 24, 2009, at 9:04 AM, Dipl.-Ing. Thomas Mitterfellner wrote:
Hello! The recent chimera builds seem to ignore my standard molecule settings (ball and stick defaults to stick only) and the files to be read at startup. I normally read in a file with my custom colordefs, but when I set that, close chimera and open it again, this setting is lost. Is this a known issue, or is it just with my installation?
On Aug 24, 2009, at 10:46 AM, Eric Pettersen wrote:
Are we talking about Command Line startup files? Do you mean that you put a file in the list of Command Line file to read at startup and it's not in the list the next time you start Chimera? (You did click the 'Save' button, right?)
Actually, if this is what you're describing then it is a known issue, namely ticket #7483 in our Trac database (http://socrates2.cgl.ucsf.edu/trac/chimera/ticket/7483 ). I believe it is in fact using your file, it's just not showing it in the list of files (which of course makes it hard to delete!). I will add you to the list of recipients for that Trac ticket, so you will be notified when it's fixed.
--Eric Eric Pettersen UCSF Computer Graphics Lab http://www.cgl.ucsf.edu
An alternative would be start chimera remotely with the ReadStdin tool (--start ReadStdin), and keep the socket open and write chimera commands on the socket. Then you could have as many chimeras as you want.
The existing --send mechanism would also work if each chimera were run by a different user.
- Greg
On Sun, 12 Jul 2009, cdlau@ucsd.edu wrote:
Hi,
I am currently running chimera remotely on a computer using "ssh" commands. I have been using the "chimera --send" command to send cmd and python scripts to a computer running chimera. I was wondering if it were possible for me to run 2 or more instances of Chimera on a computer and control which instance of Chimera the "--send" script is executed by.
Thanks for your help,
Chris
participants (5)
-
cdlau＠ucsd.edu -
Dipl.-Ing. Thomas Mitterfellner -
Eric Pettersen -
Greg Couch -
Thomas Goddard