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

Try switching to using Gaia for motion corection

    XMLWordPrintable

Details

    • Story
    • Status: To Do
    • Resolution: Unresolved
    • None
    • atmospec
    • None
    • 2
    • Data Release Production
    • No

    Description

      Dumping the TODO diff I dumped:

      [mfl@lsst-devl03 atmospec]$ gd
      diff --git a/python/lsst/atmospec/utils.py b/python/lsst/atmospec/utils.py
      index 1ff0392..2893cd9 100644
      --- a/python/lsst/atmospec/utils.py
      +++ b/python/lsst/atmospec/utils.py
      @@ -417,6 +417,8 @@ def vizierLocationForTarget(exp, target, doMotionCorrection):
           result = Vizier.query_object(target)  # result is an empty table list for an unknown target
           try:
               star = result['I/311/hip2']
      +        # TODO: try changing failover from simbad to just using Gaia via vizier
      +        # i.e. try result['I/345/gaia2] and see how that goes.
           except TypeError:  # if 'I/311/hip2' not in result (result doesn't allow easy checking without a try)
               raise ValueError
       
      

      The work here will be in getting the right order to try things in, given that Gaia's completeness at the bright end will drop off too soon (we look at very bright things quite often), and also working out the column names in that catalog.

      Attachments

        Activity

          No work has yet been logged on this issue.

          People

            mfisherlevine Merlin Fisher-Levine
            mfisherlevine Merlin Fisher-Levine
            Merlin Fisher-Levine
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

              Created:
              Updated:

              Jenkins

                No builds found.