Thanks, Bob, but that's not the case.
1. The ligands affected are similarly buried to the ones that work.
2. I had forgotten about "only", but I guess it does the same as using the
select & ignore pair, which also has the problem --although with different
ligands.
See the example PDB IDs that I provided, 1hho (with two symmetric heme
groups) and 2ejf
> it might be highly fragmentary or even not present if buried because you have
> not added the
> keyword ONLY after that selection.
isosurface select(ligand) only molecular;
isosurface delete;
isosurface select(ligand) ignore(not ligand) molecular;
On 1hho , "select ligand" or "select "[HEM]" selects the two groups, but
isosurface chooses only one (in the B chain).
------------------------------------------------------------------------------
Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer
Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports
Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper
Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer
http://pubads.g.doubleclick.net/gampad/clk?id=154622311&iu=/4140/ostg.clktrk
_______________________________________________
Jmol-users mailing list
Jmol-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jmol-users
