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

Catalog overlay: review interaction of row selection with decimation

    XMLWordPrintable

    Details

    • Type: Story
    • Status: To Do
    • Resolution: Unresolved
    • Fix Version/s: None
    • Component/s: SUIT
    • Labels:
      None

      Description

      (Original title: Catalog overlay: selected points should not be displayed with decimated data)

      Test case:

      • Load large catalog (m31 2000'')
      • Select a small area on the chart, and apply the filter
      • Select all points in the table (all points in catalog are selected)
      • Remove the filter (the selected points - wrong points - are still displayed in the image)

      When catalog overlay data are decimated (dataTooBigForSelection=true), the points do not have one-to-one correspondence to table rows. In this case, we should not display the selected points.

      (2023-06-23: Strikethroughs indicate that the desired behavior needs to be reviewed more carefully, with science team input.)

        Attachments

          Issue Links

            Activity

            Hide
            tatianag Tatiana Goldina added a comment -

            Emmanuel Joliet  I am not sure if it's a known issue and there is a ticket already. 

            Show
            tatianag Tatiana Goldina added a comment - Emmanuel Joliet   I am not sure if it's a known issue and there is a ticket already. 
            Hide
            ejoliet Emmanuel Joliet added a comment -

            No, it's new one but minor i guess. The selection feature should be cleared in the chart after removing the filter i guess.

            Show
            ejoliet Emmanuel Joliet added a comment - No, it's new one but minor i guess. The selection feature should be cleared in the chart after removing the filter i guess.
            Hide
            gpdf Gregory Dubois-Felsmann added a comment -

            This ticket was pinged by the 2023-01-11 CCB meeting.

            It's not clear to me what the correct behavior in this situation really is. Trey Roby is recommending that we take a deep dive into rethinking the whole "decimation" scheme sometime in the next year, so this ticket is still valid as a reminder, but I am not endorsing the specific recommendation in the ticket.

            For instance, if a small fraction of rows are currently visible, because of a filter, and are selected, and then the filter is removed, taking the table size above the decimation threshold, it is arguable that perhaps any selected rows at that moment should be retained, as long as they are still selected, and not subjected to the decimation.

            Show
            gpdf Gregory Dubois-Felsmann added a comment - This ticket was pinged by the 2023-01-11 CCB meeting. It's not clear to me what the correct behavior in this situation really is. Trey Roby is recommending that we take a deep dive into rethinking the whole "decimation" scheme sometime in the next year, so this ticket is still valid as a reminder, but I am not endorsing the specific recommendation in the ticket. For instance, if a small fraction of rows are currently visible, because of a filter, and are selected, and then the filter is removed, taking the table size above the decimation threshold, it is arguable that perhaps any selected rows at that moment should be retained, as long as they are still selected, and not subjected to the decimation.

              People

              Assignee:
              Unassigned Unassigned
              Reporter:
              tatianag Tatiana Goldina
              Watchers:
              Emmanuel Joliet, Gregory Dubois-Felsmann, Tatiana Goldina, Trey Roby, Xiuqin Wu [X] (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

                Dates

                Created:
                Updated:

                  Jenkins

                  No builds found.