| Summary: | Matrix values are all zero | ||
|---|---|---|---|
| Product: | [Applications] kst | Reporter: | Andrew Walker <arwalker> |
| Component: | general | Assignee: | kst |
| Status: | RESOLVED FIXED | ||
| Severity: | normal | ||
| Priority: | NOR | ||
| Version: | 1.x | ||
| Target Milestone: | --- | ||
| Platform: | Compiled Sources | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
|
Description
Andrew Walker
2005-03-25 19:57:53 UTC
Fixed for now, more proper fix to come later The exact same problem can still be produced by simply not including the last step of the "steps to reproduce" i.e. don't create the image. If you create a matrix, and then open the dialog to create an image, select the matrix recently created and hit Auto Threshold the limits produced are incorrect, as the matrix has no values. Also, viewing the matrix values (Data... View Matrix Values) shows that the matrix is empty. On Monday 28 March 2005 13:38, Andrew Walker wrote: > ------- The exact same problem can still be produced by simply not > including the last step of the "steps to reproduce" i.e. don't create the > image. > > If you create a matrix, and then open the dialog to create an image, select > the matrix recently created and hit Auto Threshold the limits produced are > incorrect, as the matrix has no values. Also, viewing the matrix values > (Data... View Matrix Values) shows that the matrix is empty. That's by design. It's unused so no need to update and waste cpu cycles. Sadly this design makes auto-threshold useless, but auto-threshold is necessary as the user may not know the range of their data. I would propose that we revert to the original design. On March 28, 2005 01:42 pm, George Staikos wrote: > On Monday 28 March 2005 13:38, Andrew Walker wrote: > > ------- The exact same problem can still be produced by simply not > > including the last step of the "steps to reproduce" i.e. don't create the > > image. > > > > If you create a matrix, and then open the dialog to create an image, > > select the matrix recently created and hit Auto Threshold the limits > > produced are incorrect, as the matrix has no values. Also, viewing the > > matrix values (Data... View Matrix Values) shows that the matrix is > > empty. > > That's by design. It's unused so no need to update and waste cpu cycles. With the new design, clearly auto threshold and view values need to be preceeded by an update on objects being viewed and autothresholded... Same as scalar accesses. George, is this in the works? On Monday 28 March 2005 13:55, Andrew Walker wrote:
> ------- Sadly this design makes auto-threshold useless, but auto-threshold
> is necessary as the user may not know the range of their data. I would
> propose that we revert to the original design.
Let's slow down and take this one step at a time. It's quite possible that
the matrix and image code has to be redesigned. I'm already working on part
of it.
On Monday 28 March 2005 14:00, netterfield@astro.utoronto.ca wrote: > With the new design, clearly auto threshold and view values need to be > preceeded by an update on objects being viewed and autothresholded... > > Same as scalar accesses. George, is this in the works? No plan for it yet. I wasn't aware of this stuff. However the updates -have- to happen in the update thread. The first answer that comes to mind is that anything that depends on the content of an object has to check the dirty flag and delay its action until the object is no longer dirty. Just like with vectors, there is no guarantee of any content at the start. *** Bug has been marked as fixed ***. |