VMD-L Mailing List

From: John Stone (johns_at_ks.uiuc.edu)
Date: Tue Mar 15 2011 - 10:35:28 CDT

Hi,
  VMD currently assigns the isovalue slider ranges per-dataset, rather
than per-representation. So, when you create two representations for
the same cube file, and set the "Range" controls for one representation,
they are affecting the range controls for the representation(s) that
reference the same dataset. You can avoid the problem you descirbed
either by loading the cube file twice (thus each instance will get its own
value range), or by setting the "Range" control to the full value range,
and just selecting the isovalue appropriately in each representation.

Cheers,
  John Stone
  vmd_at_ks.uiuc.edu

On Tue, Mar 15, 2011 at 10:34:48AM +0100, Passerone, Daniele wrote:
> Dear developers,
> I noticed in version 1.9 (but also in 1.8.7) a strange bug or feature.
> I load a cubefile with 3d data with range say between ?0.5 and 0.5
> Then I want to have two separate representations, one with range between ?0.5 and 0 so that the slider can select between those values,
> And the other one with range between 0 and +0.5
>
> The problem is that as soon as I change the range in the SECOND isosurface representation, the range is copied into the first, so I end up with two representations with the same range 0 : +0.5
>
> Any ideas?
>
> Thank you,
>
> Daniele Passerone
> 

-- 
NIH Resource for Macromolecular Modeling and Bioinformatics
Beckman Institute for Advanced Science and Technology
University of Illinois, 405 N. Mathews Ave, Urbana, IL 61801
Email: johns_at_ks.uiuc.edu                 Phone: 217-244-3349
  WWW: http://www.ks.uiuc.edu/~johns/      Fax: 217-244-6078