Iván Párraga García wrote: > Hi, > > Most of the websites of our group use Jmol for visualizing pdb's but > I've found a little problem: Jmol seems to remove from visualization > those residues which have an insertion code. For example, we have the > pdb with id 1nmb: > <snp> > As you can see it has an inserted residue int he position 169 (you > have the residue 169 & the residue 169A), and Jmol decides to remove > residue 169A. > > This is a big problem for us, so I was wondering if you are aware of > that and if it will be corrected in new versions. Perhaps I'm doing > something wrong... >
I don't know which version of Jmol you are using, but we don't have observed the problem you described. Take for example a look at our Jmol Viewer page of '1NMB' at the 'JenaLib' using Jmol prerelease version 10.00.36: http://www.fli-leibniz.de/cgi-bin/3d_mapping.pl?CODE=1NMB You can also look at it with the official Jmol version 10.2.0: http://www.fli-leibniz.de/cgi-bin/3d_mapping.pl?CODE=1NMB&JMOLVERSION=10.2.0 If you copy and paste and the following script into the script input field, you will see that both residues are present: select [VAL]169; wireframe 70; color cartoon none; color red; select [TYR]169^A; wireframe 70; color cartoon none; color cyan; moveto 1 883 -364 297 116.6 3549 86 -154; select ([VAL]169, [TYR]169^A) and carbon and alpha; label on; Maybe you didn't use the correct syntax for specifying insertion codes. You must seperate the insertion code from the residue number by the '^' character (e.g.: 169^A) in order to distinguish it from the chain specification (e.g.: 169A means residue 169 in chain A). Regards, Rolf _______________________________________________ Jmol-developers mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jmol-developers
