Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  • relevant links
    • Jira
      serverJIRA
      serverId9da94fb6-5771-303d-a785-1b6c5ab0f2d2
      keyDM-1150
  • SciSQL does not support what we need for searching images
  • concerned about indexing (finding fast whether polygons overlap)
  • if images of different size, need to pick some coarse level of htm, that is suboptimal
    • can store multiple htm levels
  • likely need special index, eg 3-d R-tree
  • Talk to mysql GIS experts at: http://www.percona.com/live/mysql-conference-2015/
  • in Fermi, dealing with "events" that are point, we deal with areas 
  • science question: what do we need to support in terms of searching / selecting images. E.g., point in image enough? Polygons overlapping images. Jacek will ask Mario Juric. Via JIRA ticket.
  • Serge will update JIRA ticket: add notes what to test

Raw images

  • Related links
    Jira
    serverJIRA
    columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
    serverId9da94fb6-5771-303d-a785-1b6c5ab0f2d2
    keyDM-2241
  • Format?
    • SUI can always request the image as FITS
  • Returned data?
    • Raw pixel plus metadata we obtained from obs control system and telescope control system (which will include "where telescope was pointing" – approx WCS)
    • few years later, when we have precise WCS, we might want to return that with image. But might want to call it differently ("augmented raw image") 
  • Size units?
    • typically amplifier level
    • ok to request smaller than amplifier (although it is usually not useful)
    • There is no such thing as CCD raw image. No plans to do stitching raw images
  • Typical uses of raw images? What metadata should go with raw data? Xiuqin will ask Mario Juric. Via JIRA ticket

...