On Thu, 4 Dec 2003, Brent Bailey wrote: > Sorry, maybe I didn't explain the problem correctly. How can I show > _two_ data set in the same space with only _one_ color? I need the > colormap so that I can have more than one data set displayed.
Eh? I dont understand this - but your question below is answered again (below). I thought you had two imports, displaying both can be done using the Collect module, and of course you can re-use the Colormap for a second Color module input. > On Thu, 2003-12-04 at 16:09, Richard Guenther wrote: > > On Thu, 4 Dec 2003, Brent Bailey wrote: > > > > > I have been fighting with Colormap for the last couple of days and I > > > can't figure out if I'm wrong or it's mis-behaving. I have two sets of > > > connection dependent data that can vary between zero and one for each > > > type, but the total will never be greater than one (though it can be > > > less than one.) I have a problem trying to get to display in dx, but > > > what I have found that sort of works is each data set goes through > > > something like the following: > > > > > > Import -> Include -> AutoGrayScale ------------ Color -> > > > | | > > > -> Colormap - > > > > > > This now allows me a continuous range between zero and one, then color > > > it according to the Colormap. The problem is that the Colormap keeps > > > losing my min and max values. I don't know if this is due to the fact This is due to the fact you are connecting your data to the Colormap module which then uses this data to set min/max. If you dont connect it, it will respect your min/max. > > > that I import a large sequence of values, but it seems to "revert" to > > > the min/max of the values of the current data set and not my user > > > specified min/max. I have the min/max values set in the Include, > > > AutoGrayScale and Colormap itself, but the Colormap is not repecting > > > these. After I run the sequence, I go back to the min/max values in > > > Colormap and they have changed! > > > > Dont connect AutoGrayScale to Colormap then. > > > > Richard. > -- > Brent Bailey <[EMAIL PROTECTED]> >
