Uploaded image for project: 'Data Management'
  1. Data Management
  2. DM-16457

Firefly image stretch panel: remove maximum and minimum limits on stretch dialog

    XMLWordPrintable

Details

    Description

      krughoff noted that the Firefly image stretch dialog enforces that the "min" and "max" values in the dialog must be within the range of actual values in the image.

      This was undoubtedly aimed at providing support to users in not entering nonsensical values. However, there are valid use cases for entering ranges that fall outside the range in the particular image being displayed.

      The most obvious case would be when setting up a stretch for a set of images from the same instrument, each with somewhat different maximum actual values, so that a common value in every image is displayed with the same color in every image. (Imagine, say, images with a potential maximum - saturation - value of 4000. For different spots on the sky, the actual range in a particular image might not get anywhere close to that - it might be 17 to 850 in one image, and 16 to 3500 in another - but I would like "521" to display as the same color in each one.)

      It's clear that this should apply when the "units" menu is set to "Data". It's not clear that it's useful when using "%", but that could be discussed, and it might be quite confusing to users to have limits applied in one case and not the other.

      This argument arose from LSST but is pretty clearly applicable to, e.g., looking at a set of WISE images in IRSA as well.

       

      IPAC Firefly ticket https://jira.ipac.caltech.edu/browse/FIREFLY-48 (see also https://jira.ipac.caltech.edu/browse/FIREFLY-139)

      Attachments

        Issue Links

          Activity

            gpdf Gregory Dubois-Felsmann created issue -
            gpdf Gregory Dubois-Felsmann made changes -
            Field Original Value New Value
            Link This issue relates to DM-16458 [ DM-16458 ]
            gpdf Gregory Dubois-Felsmann made changes -
            Link This issue duplicates DM-14797 [ DM-14797 ]
            xiuqin Xiuqin Wu [X] (Inactive) made changes -
            Epic Link DM-8737 [ 28574 ]
            xiuqin Xiuqin Wu [X] (Inactive) made changes -
            Sprint SUIT Sprint 2019-06 [ 875 ]
            xiuqin Xiuqin Wu [X] (Inactive) made changes -
            Description [~krughoff] noted that the Firefly image stretch dialog enforces that the "min" and "max" values in the dialog must be within the range of actual values in the image.

            This was undoubtedly aimed at providing support to users in not entering nonsensical values. However, there are valid use cases for entering ranges that fall outside the range in the particular image being displayed.

            The most obvious case would be when setting up a stretch for a set of images from the same instrument, each with somewhat different maximum actual values, so that a common value in every image is displayed with the same color in every image. (Imagine, say, images with a potential maximum - saturation - value of 4000. For different spots on the sky, the actual range in a particular image might not get anywhere close to that - it might be 17 to 850 in one image, and 16 to 3500 in another - but I would like "521" to display as the same color in each one.)

            It's clear that this should apply when the "units" menu is set to "Data". It's not clear that it's useful when using "%", but that could be discussed, and it might be quite confusing to users to have limits applied in one case and not the other.

            This argument arose from LSST but is pretty clearly applicable to, e.g., looking at a set of WISE images in IRSA as well.
            [~krughoff] noted that the Firefly image stretch dialog enforces that the "min" and "max" values in the dialog must be within the range of actual values in the image.

            This was undoubtedly aimed at providing support to users in not entering nonsensical values. However, there are valid use cases for entering ranges that fall outside the range in the particular image being displayed.

            The most obvious case would be when setting up a stretch for a set of images from the same instrument, each with somewhat different maximum actual values, so that a common value in every image is displayed with the same color in every image. (Imagine, say, images with a potential maximum - saturation - value of 4000. For different spots on the sky, the actual range in a particular image might not get anywhere close to that - it might be 17 to 850 in one image, and 16 to 3500 in another - but I would like "521" to display as the same color in each one.)

            It's clear that this should apply when the "units" menu is set to "Data". It's not clear that it's useful when using "%", but that could be discussed, and it might be quite confusing to users to have limits applied in one case and not the other.

            This argument arose from LSST but is pretty clearly applicable to, e.g., looking at a set of WISE images in IRSA as well.

             

            IPAC FIREFLY_48
            gpdf Gregory Dubois-Felsmann made changes -
            Watchers Gregory Dubois-Felsmann [ Gregory Dubois-Felsmann ] Gregory Dubois-Felsmann, Simon Krughoff, Trey Roby, Vandana Desai, Xiuqin Wu [ Gregory Dubois-Felsmann, Simon Krughoff, Trey Roby, Vandana Desai, Xiuqin Wu ]
            gpdf Gregory Dubois-Felsmann made changes -
            Reviewers Simon Krughoff, Trey Roby, Vandana Desai, Xiuqin Wu [ krughoff, roby, desai, xiuqin ]
            gpdf Gregory Dubois-Felsmann made changes -
            Watchers Gregory Dubois-Felsmann, Simon Krughoff, Trey Roby, Vandana Desai, Xiuqin Wu [ Gregory Dubois-Felsmann, Simon Krughoff, Trey Roby, Vandana Desai, Xiuqin Wu ] David Shupe, Gregory Dubois-Felsmann, Jim Bosch, Simon Krughoff, Trey Roby, Vandana Desai, Xiuqin Wu [ David Shupe, Gregory Dubois-Felsmann, Jim Bosch, Simon Krughoff, Trey Roby, Vandana Desai, Xiuqin Wu ]
            xiuqin Xiuqin Wu [X] (Inactive) made changes -
            Epic Link DM-8737 [ 28574 ] DM-10570 [ 32500 ]
            xiuqin Xiuqin Wu [X] (Inactive) made changes -
            Sprint SUIT Sprint 2019-06 [ 875 ]
            gpdf Gregory Dubois-Felsmann made changes -
            Description [~krughoff] noted that the Firefly image stretch dialog enforces that the "min" and "max" values in the dialog must be within the range of actual values in the image.

            This was undoubtedly aimed at providing support to users in not entering nonsensical values. However, there are valid use cases for entering ranges that fall outside the range in the particular image being displayed.

            The most obvious case would be when setting up a stretch for a set of images from the same instrument, each with somewhat different maximum actual values, so that a common value in every image is displayed with the same color in every image. (Imagine, say, images with a potential maximum - saturation - value of 4000. For different spots on the sky, the actual range in a particular image might not get anywhere close to that - it might be 17 to 850 in one image, and 16 to 3500 in another - but I would like "521" to display as the same color in each one.)

            It's clear that this should apply when the "units" menu is set to "Data". It's not clear that it's useful when using "%", but that could be discussed, and it might be quite confusing to users to have limits applied in one case and not the other.

            This argument arose from LSST but is pretty clearly applicable to, e.g., looking at a set of WISE images in IRSA as well.

             

            IPAC FIREFLY_48
            [~krughoff] noted that the Firefly image stretch dialog enforces that the "min" and "max" values in the dialog must be within the range of actual values in the image.

            This was undoubtedly aimed at providing support to users in not entering nonsensical values. However, there are valid use cases for entering ranges that fall outside the range in the particular image being displayed.

            The most obvious case would be when setting up a stretch for a set of images from the same instrument, each with somewhat different maximum actual values, so that a common value in every image is displayed with the same color in every image. (Imagine, say, images with a potential maximum - saturation - value of 4000. For different spots on the sky, the actual range in a particular image might not get anywhere close to that - it might be 17 to 850 in one image, and 16 to 3500 in another - but I would like "521" to display as the same color in each one.)

            It's clear that this should apply when the "units" menu is set to "Data". It's not clear that it's useful when using "%", but that could be discussed, and it might be quite confusing to users to have limits applied in one case and not the other.

            This argument arose from LSST but is pretty clearly applicable to, e.g., looking at a set of WISE images in IRSA as well.

             

            IPAC Firefly ticket https://jira.ipac.caltech.edu/browse/FIREFLY-139
            IPAC FIREFLY_48
            gpdf Gregory Dubois-Felsmann made changes -
            Epic Link DM-10570 [ 32500 ] DM-25751 [ 436764 ]
            gpdf Gregory Dubois-Felsmann made changes -
            Description [~krughoff] noted that the Firefly image stretch dialog enforces that the "min" and "max" values in the dialog must be within the range of actual values in the image.

            This was undoubtedly aimed at providing support to users in not entering nonsensical values. However, there are valid use cases for entering ranges that fall outside the range in the particular image being displayed.

            The most obvious case would be when setting up a stretch for a set of images from the same instrument, each with somewhat different maximum actual values, so that a common value in every image is displayed with the same color in every image. (Imagine, say, images with a potential maximum - saturation - value of 4000. For different spots on the sky, the actual range in a particular image might not get anywhere close to that - it might be 17 to 850 in one image, and 16 to 3500 in another - but I would like "521" to display as the same color in each one.)

            It's clear that this should apply when the "units" menu is set to "Data". It's not clear that it's useful when using "%", but that could be discussed, and it might be quite confusing to users to have limits applied in one case and not the other.

            This argument arose from LSST but is pretty clearly applicable to, e.g., looking at a set of WISE images in IRSA as well.

             

            IPAC Firefly ticket https://jira.ipac.caltech.edu/browse/FIREFLY-139
            IPAC FIREFLY_48
            [~krughoff] noted that the Firefly image stretch dialog enforces that the "min" and "max" values in the dialog must be within the range of actual values in the image.

            This was undoubtedly aimed at providing support to users in not entering nonsensical values. However, there are valid use cases for entering ranges that fall outside the range in the particular image being displayed.

            The most obvious case would be when setting up a stretch for a set of images from the same instrument, each with somewhat different maximum actual values, so that a common value in every image is displayed with the same color in every image. (Imagine, say, images with a potential maximum - saturation - value of 4000. For different spots on the sky, the actual range in a particular image might not get anywhere close to that - it might be 17 to 850 in one image, and 16 to 3500 in another - but I would like "521" to display as the same color in each one.)

            It's clear that this should apply when the "units" menu is set to "Data". It's not clear that it's useful when using "%", but that could be discussed, and it might be quite confusing to users to have limits applied in one case and not the other.

            This argument arose from LSST but is pretty clearly applicable to, e.g., looking at a set of WISE images in IRSA as well.

             

            IPAC Firefly ticket https://jira.ipac.caltech.edu/browse/FIREFLY-48 (see also https://jira.ipac.caltech.edu/browse/FIREFLY-139)
            gpdf Gregory Dubois-Felsmann made changes -
            Epic Link DM-25751 [ 436764 ] DM-37505 [ 2920499 ]

            People

              Unassigned Unassigned
              gpdf Gregory Dubois-Felsmann
              David Shupe, Gregory Dubois-Felsmann, Jim Bosch, Simon Krughoff (Inactive), Trey Roby, Vandana Desai, Xiuqin Wu [X] (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              7 Start watching this issue

              Dates

                Created:
                Updated:

                Jenkins

                  No builds found.