- Chimera-users - RBVI Mailing Lists

selecting
by John Nixon 18 Jan '05

18 Jan '05

Hi folks, I'm a newbie and am having trouble getting started. Sorry to be dense. Using the command line on a single protein chain O select :32-42,44-49.O or rep sphere :43:56:59:60:61:63:65:67:68:70:71:72:73:74:75:78:110:113.0 only seems to work on the last residue. Thus I'd have to write a separate command for each residue. Could you tell me what I've missed please! John

4 3

[Chimera-users] FW: [PyMOL] Stereo-3D in a Window: Not in MacOS X Tiger?!!
by Warren DeLano 14 Jan '05

14 Jan '05

Greetings Fellow Vendors and Software Developers! Is stereo 3D graphics support on MacOS X something you would like to see soon? If so, then please take just 30 seconds to respond to the following petition. We've received more than 300 compelling responses over the past 18 hours about the importance of supporting stereo 3D graphics today -- but we will need more to convince Apple, so please consider participating. It is as easy as clicking this following link, adding a few words with your personal perspective on the issue, and then hitting send! mailto:warren@delsci.com&subject=Stereo%203D%20Matters%20to%20Me%21 Cheers, Warren -----Original Message----- From: pymol-users-admin(a)lists.sourceforge.net [mailto:pymol-users-admin@lists.sourceforge.net] On Behalf Of Warren DeLano Sent: Thursday, January 13, 2005 5:59 PM To: pymol-users(a)lists.sourceforge.net Subject: [PyMOL] Stereo-3D in a Window: Not in MacOS X Tiger?!! Fellow Visualization Software Users: My #1 gripe with MacOS X Panther has been the lack of support for industry-standard stereo-3D graphics (in a window). So far, I and others have been unable to convince Apple that this feature matters enough to their bottom line to merit implementation. Candid discussions this week at MacWorld confirmed that Tiger (OS X 10.4) will likewise ship without this essential capability at a time when the opportunity for Apple is at its peak in this market. I believe this would be a serious error, and that Apple must now hear from us on this issue. If you agree, then please reply directly to me, RIGHT NOW (mailto:warren@delsci.com) with the words: "Stereo 3D matters to me." Your response will be printed, and I will hand-deliver them to Apple management in nearby Cupertino at the end of the month. We need AS MANY responses as we can get (ideally 1,000+), so please forward this email to all of your visualization-oriented colleagues (in any sector), and ask them to submit individual emails to me as well. Here's why: Stereoscopic 3D visualization increasingly matters in science, medicine, and engineering. Though arguably the ultimate technical computing platform, the Mac remains hopelessly crippled in this key respect when compared to Sun, HP, Dell, or IBM workstations running Linux, Solaris, or even Windows. Dual-Xeon and dual-Opteron systems now ship stereo-3D-ready thanks to powerful nVidia/Quadro and ATI/FireGL graphics cards. Thus, the competition WILL OWN THIS MARKET if Apple doesn't support stereo-3D in a window on MacOS X, ASAP. The disruptive market opportunity created by the implosion of SGI and the stopgap adoption of "home brew" Linux systems is about to end. Professional-grade stereoscopic visualization is now a standard OpenGL capability, it is vendor-supported on a variety of hardware, and it is present on every platform EXCEPT THE MAC. None of those "amazing features" in Tiger matter one bit to technical users whose basic needs remain unmet. Stereo-3D inadequacy is a show-stopper for many scientists and engineers. The Mac will not have a fair shot at this market unless Apple quickly follows though on it's assumed responsibility to support all OpenGL features, including quad-buffered stereo-3D graphics in a window. Case in point: my company just spent $5k on a dual-Opteron Sun workstation instead of a dual-G5 Mac solely because stereo-3D in a window is absent from MacOS X. This pattern will surely be amplified many thousand-fold if Apple does not take immediate corrective action. Responding together, we can insure that Apple understands what this deficiency means for the future of MacOS X in scientific, medical, and technical visualization. I do not believe that Apple management has made an informed decision regarding stereo-3D, and I think this is our last best chance to change things before the issue becomes moot. Please share your concerns by responding to this email (mailto:warren@delsci.com). It will only take a second, but the benefits could last for years to come if Apple listens well and then acts decisively. Input from current Linux and Windows users is especially welcome, since Apple would love to sell you the visualization platform of your dreams if you're willing to help define it. Thank you for your time. Cheers, Warren Author of PyMOL: http://pymol.sf.net (Note that MacPyMOL is currently shown on http://apple.com/science under "The Tools" -- cool!) DeLano Scientific LLC company profile: http://delanoscientific.com/about.html PS. An alternate way to be heard is to post on the Apple SciTech or Sci-Vis mailing lists, but please CC me too to be sure that you're counted. http://lists.apple.com/mailman/listinfo/scitech http://lists.apple.com/mailman/listinfo/sci-vis -- Warren L. DeLano, Ph.D. Principal Scientist . DeLano Scientific LLC . 400 Oyster Point Blvd., Suite 213 . South San Francisco, CA 94080 . Biz:(650)-872-0942 Tech:(650)-872-0834 . Fax:(650)-872-0273 Cell:(650)-346-1154 . mailto:warren@delsci.com ------------------------------------------------------- The SF.Net email is sponsored by: Beat the post-holiday blues Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek. It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt _______________________________________________ PyMOL-users mailing list PyMOL-users(a)lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/pymol-users

1 0

Re: [Chimera-users] Mol2 Trajectory Reader?
by Eric Pettersen 06 Jan '05

06 Jan '05

Hi Joshua, Given that what you really want to do is assemble a movie of your conformations rather than actually analyze them as a trajectory, what we've decided to do is write an extension that will allow you to record whatever is going on in Chimera as a series of frames (it will have a "Start" and a "Stop" button) and will assemble those frames into an mpeg. It will optionally allow you to keep the frames in case you want to assemble them into a format that is harder for us to support across all platforms (e.g. Quicktime), and may also support generating an animated GIF. A preliminary version will probably be done in a couple of weeks and we could send that to you if you want to be a guinea pig. Otherwise, it will be in the next release, which will probably be April or so. --Eric On Dec 25, 2004, at 8:15 PM, S Joshua Swamidass wrote: > Good point. > > I didn't notice the move menu. The ultimate goal of all this for me is > to literally make some movies, either with screen shots in sequence or > ideally if chimera can output an avi automatically. So i guess, > viewdock should work IF there is a way to capture all the images to > disk rather than just play them to the screen. > > S Joshua Swamidass > > > On Sat, 25 Dec 2004 09:29:55 -0800, Eric Pettersen <pett(a)cgl.ucsf.edu> > wrote: >> Hi Joshua, >> Implementing the Mol2 trajectory format looks perfectly doable >> with >> the data file you provided. Before proceeding with the work, I guess >> I >> have a question as to why you want to use the molecular-dynamics Movie >> tool on the file rather than ViewDock tool. You do know that the >> ViewDock tool has a "Movie" menu >> (http://www.cgl.ucsf.edu/chimera/1.2065/docs/ContributedSoftware/ >> viewdock/viewdock.html#movmenu) that allows you to step through docked >> conformers one by one? I guess I'm trying to determine if I should >> really be adding this fomat to the Movie tool or if we should somehow >> be improving the capabilities of ViewDock instead. >> >> --Eric

1 0

Just fixed Re: [Chimera-users] WinXP SP1 python error on File -> Open
by Li Wang 04 Jan '05

04 Jan '05

Dear all, I forgot to attach the python code in my previous email. Please let me know if there is anything wrong with the code. By the way, I am using the Chimera beta version 1, build 1917, 2004/03/08. Should I download the newer version, version 1 build 2065? Thank you so much for your help in advance. Li

2 1

Just fixed Re: [Chimera-users] WinXP SP1 python error on File -> Open
by Li Wang 04 Jan '05

04 Jan '05

Dear Eric, I just join the Chimera-users discussion group and haven't got reply email. However I checked the archive and found your reply email related to the WinXP SP1 python error on File -> Open. I have been using Chimera to generate the colorful ribbon picture for the pdb file using command line. Now I am tring to figure out the general way of defining the bfactor range corresponding to the different colors. I found the flexible python code for making the rainbow color by bfactor and tried it out. But it ended up with the file/open error message as I didn't see any problem in the code. Attached please find the copy of the python code. I did replace bo and b1 by min and max of bfactors in the pdb file. Your help and suggestion are greatly appreciated. Li Wang Biomedical Informatics of OSU Columbus, OH (w) (614)688-3236

2 1

Mol2 Trajectory Reader?
by S Joshua Swamidass 22 Dec '04

22 Dec '04

Hello, How hard would it be to write an extension to chimera that read a multimolecule mol2 file into chimera as a trajectory? That would be really useful for me. Please let me know if you can do it or some advice on how to procede. S Joshua Swamidass

2 1

Chimera Guassian Cube Extension
by S Joshua Swamidass 20 Dec '04

20 Dec '04

Hello, I have a bit of code to contribute. It allows chimera to read grid files in the GUASSIAN ascii grid format described here: http://www.ks.uiuc.edu/Research/vmd/plugins/molfile/cubeplugin.html It ignores any bond information. Who should i send it to so it will be incorporated into future releases? S Joshua Swamidass

2 1

production release
by Eric Pettersen 18 Dec '04

18 Dec '04

Hail fellow Chimerians, We just put out a production release (version 1.2065). It is basically the same as the preceding release candidate (1.2056) except for a lot of bug fixes. The only new features are support for saving scenes in X3D format [but see the release notes for caveats], and some changes in how the label/rlabel commands interact. The release notes are at: http://www.cgl.ucsf.edu/chimera/docs/relnotes/1.2065.html Eric Pettersen UCSF Computer Graphics Lab pett(a)cgl.ucsf.edu http://www.cgl.ucsf.edu

1 0

Chimera Multiscale using VRML?
by Thomas Goddard 13 Dec '04

13 Dec '04

Hi Dong, Here is an example VRML file that contains a virus particle model. It uses a cone as the icosahedral asymmetric unit. You could change the definition of the asymmetric unit at the top of the VRML. This file will display in Chimera 1.2056. Tom ----- File icos.vrml follows: #VRML V2.0 utf8 Transform { children [ DEF asymmetric_unit Transform { translation 0 5 0 children [ Shape { geometry Cone {} } ] } Transform { rotation 0.00000000 0.00000000 1.00000000 0.00000000 children USE asymmetric_unit } Transform { rotation -0.30901699 0.80901699 -0.50000000 3.14159265 children USE asymmetric_unit } Transform { rotation 0.57735027 0.57735027 -0.57735027 2.09439510 children USE asymmetric_unit } Transform { rotation 0.93417236 -0.35682209 -0.00000000 2.09439510 children USE asymmetric_unit } Transform { rotation 0.85065081 0.00000000 -0.52573111 2.51327412 children USE asymmetric_unit } Transform { rotation 0.52573111 -0.85065081 0.00000000 2.51327412 children USE asymmetric_unit } Transform { rotation 0.30901699 0.80901699 -0.50000000 3.14159265 children USE asymmetric_unit } Transform { rotation -0.00000000 -0.52573111 0.85065081 2.51327412 children USE asymmetric_unit } Transform { rotation 0.35682209 0.00000000 -0.93417236 2.09439510 children USE asymmetric_unit } Transform { rotation 0.52573111 -0.85065081 0.00000000 1.25663706 children USE asymmetric_unit } Transform { rotation 0.57735027 -0.57735027 -0.57735027 2.09439510 children USE asymmetric_unit } Transform { rotation 0.00000000 -0.93417236 0.35682209 2.09439510 children USE asymmetric_unit } Transform { rotation -0.50000000 -0.30901699 0.80901699 3.14159265 children USE asymmetric_unit } Transform { rotation -0.35682209 0.00000000 0.93417236 2.09439510 children USE asymmetric_unit } Transform { rotation 0.00000000 -0.52573111 -0.85065081 2.51327412 children USE asymmetric_unit } Transform { rotation -0.52573111 -0.85065081 -0.00000000 1.25663706 children USE asymmetric_unit } Transform { rotation 0.00000000 -0.93417236 -0.35682209 2.09439510 children USE asymmetric_unit } Transform { rotation -0.57735027 -0.57735027 0.57735027 2.09439510 children USE asymmetric_unit } Transform { rotation -0.50000000 0.30901699 0.80901699 3.14159265 children USE asymmetric_unit } Transform { rotation -0.57735027 0.57735027 0.57735027 2.09439510 children USE asymmetric_unit } Transform { rotation 0.30901699 0.80901699 0.50000000 3.14159265 children USE asymmetric_unit } Transform { rotation -0.93417236 -0.35682209 0.00000000 2.09439510 children USE asymmetric_unit } Transform { rotation -0.52573111 -0.85065081 0.00000000 2.51327412 children USE asymmetric_unit } Transform { rotation -0.85065081 0.00000000 0.52573111 2.51327412 children USE asymmetric_unit } Transform { rotation -0.30901699 0.80901699 0.50000000 3.14159265 children USE asymmetric_unit } Transform { rotation -0.52573111 0.85065081 0.00000000 2.51327412 children USE asymmetric_unit } Transform { rotation 0.52573111 0.85065081 0.00000000 2.51327412 children USE asymmetric_unit } Transform { rotation 1.00000000 0.00000000 0.00000000 3.14159265 children USE asymmetric_unit } Transform { rotation 0.80901699 0.50000000 -0.30901699 3.14159265 children USE asymmetric_unit } Transform { rotation 0.80901699 -0.50000000 -0.30901699 3.14159265 children USE asymmetric_unit } Transform { rotation 0.00000000 1.00000000 0.00000000 3.14159265 children USE asymmetric_unit } Transform { rotation 0.85065081 -0.00000000 -0.52573111 1.25663706 children USE asymmetric_unit } Transform { rotation 0.57735027 -0.57735027 0.57735027 2.09439510 children USE asymmetric_unit } Transform { rotation -0.00000000 0.52573111 -0.85065081 2.51327412 children USE asymmetric_unit } Transform { rotation 0.50000000 -0.30901699 0.80901699 3.14159265 children USE asymmetric_unit } Transform { rotation 0.00000000 0.52573111 -0.85065081 1.25663706 children USE asymmetric_unit } Transform { rotation 0.85065081 0.00000000 0.52573111 1.25663706 children USE asymmetric_unit } Transform { rotation 0.93417236 0.35682209 0.00000000 2.09439510 children USE asymmetric_unit } Transform { rotation 0.80901699 -0.50000000 0.30901699 3.14159265 children USE asymmetric_unit } Transform { rotation 0.00000000 0.93417236 -0.35682209 2.09439510 children USE asymmetric_unit } Transform { rotation -0.57735027 0.57735027 -0.57735027 2.09439510 children USE asymmetric_unit } Transform { rotation 0.52573111 0.85065081 -0.00000000 1.25663706 children USE asymmetric_unit } Transform { rotation 0.85065081 0.00000000 0.52573111 2.51327412 children USE asymmetric_unit } Transform { rotation 0.80901699 0.50000000 0.30901699 3.14159265 children USE asymmetric_unit } Transform { rotation -0.93417236 0.35682209 -0.00000000 2.09439510 children USE asymmetric_unit } Transform { rotation 0.00000000 0.93417236 0.35682209 2.09439510 children USE asymmetric_unit } Transform { rotation -0.52573111 0.85065081 0.00000000 1.25663706 children USE asymmetric_unit } Transform { rotation 0.57735027 0.57735027 0.57735027 2.09439510 children USE asymmetric_unit } Transform { rotation -0.85065081 0.00000000 -0.52573111 2.51327412 children USE asymmetric_unit } Transform { rotation -0.57735027 -0.57735027 -0.57735027 2.09439510 children USE asymmetric_unit } Transform { rotation -0.85065081 -0.00000000 0.52573111 1.25663706 children USE asymmetric_unit } Transform { rotation 0.00000000 0.52573111 0.85065081 2.51327412 children USE asymmetric_unit } Transform { rotation -0.00000000 0.52573111 0.85065081 1.25663706 children USE asymmetric_unit } Transform { rotation 0.50000000 0.30901699 0.80901699 3.14159265 children USE asymmetric_unit } Transform { rotation -0.85065081 0.00000000 -0.52573111 1.25663706 children USE asymmetric_unit } Transform { rotation -0.00000000 -0.52573111 -0.85065081 1.25663706 children USE asymmetric_unit } Transform { rotation 0.00000000 -0.52573111 0.85065081 1.25663706 children USE asymmetric_unit } Transform { rotation 0.00000000 0.00000000 1.00000000 3.14159265 children USE asymmetric_unit } Transform { rotation 0.35682209 0.00000000 0.93417236 2.09439510 children USE asymmetric_unit } Transform { rotation -0.35682209 0.00000000 -0.93417236 2.09439510 children USE asymmetric_unit } ] }

1 0

Chimera export surfaces as VRML questions
by Thomas Goddard 11 Dec '04

11 Dec '04

Hi Dong, I have fixed the grayed out "Open" button in Chimera 1.2056 "Export surfaces as VRML" extenstion and that fix will be in our upcoming release (a few weeks). We are working on being able to export molecules (ribbons, ball and stick, ...) as well. We have written code that exports X3D format which is a successor to VRML format. There is no Chimera user interface for writing an X3D file yet. Few programs are able to read X3D so we may need to find a way to convert the X3D to VRML. Greg Couch on the Chimera development team is working on the X3D output. I don't know if it will be available in our next release. You mention that you had to eliminate the outermost part of the VRML code that Chimera exports Transform { children [ ] } in order to get some programs to read it. The Transform node is very common. I'm surprised it is causing trouble. What program is unable to read the unedited version of the Chimera VRML output? The Transform node usually positions the enclosing model (rotating and translating). Our current VRML output doesn't specify any rotation or translation so the VRML output does not preserve the orientation you have in the Chimera graphics window. It should. So instead of removing the Transform node I think the next step will be to add the correct rotation and translation information. I'll respond to your Multiscale questions in a separate email. Tom > Dear my concern > > Thank you for the distribution of this nice program, Chimera! > > Recently I downloaded new version of Chimera for Win32, 2056 build. > > Most of all function is fine but when I tried to export surface as VRML, the > button for "save" is not activated. > > Instead of "save" there is "open" button. This button could be activated > only by clicking "present file". > > If user clicks that activated button, the original file has gone and > replaced with new content's keeping its name. > > Is there any way to export other model, like ribbon or space fill model as > VRML? > > I think it will be very helpful. > > I tried lots of program, but the other programs are not good as Chimera at > least in terms of VRML export. > > My main purpose of using this program is "Multiscale modeling" ; I am so > interested in virus capsid model. > > It is so fabulous!!. > > I have never seen this function before and I love this.. > > However is it possible to make multiscale model from other format like VRML? > > I don't know exactly how chimera makes multiscale model, but I think chimera > may use the matrix. > > If then, I can guess we can make model from any format file whatever it is. > > Would you help me how to do this work? > > > And one more thing... > > The exported surface file VRML format from chimera starts with > > #VRML V2.0 utf8 > > Transform { > > children [ > > Shape { > > .... > > And ended with ]} > > > However without > > > Transform { > > Children [ > > > > ] } > > Sentence there is no problem to view this file. > > Moreover, some program which can import VRML file does not recognize > original exported file. > > After delete above sentence they could import VRML file. > > > Thank you > > > Dong Hoon Chung

1 0