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

Make visit definition more permissive

    XMLWordPrintable

    Details

    • Story Points:
      1
    • Team:
      Architecture
    • Urgent?:
      No

      Description

      Visits can currently only be defined for "science" on-sky observations. This is causing difficulties for people doing engineering and focus tests that are on sky. Rather than using a list of allowed observation types that support visits, Jim Bosch suggests that we allow any on-sky observation to have visits defined and gate the decision entirely on the presence of ra/dec in the registry.

        Attachments

          Issue Links

          blocks

          Story - Created by Jira Software - do not edit or delete. Issue type for a user story. DM-31655 Run AOS loop with AuxTel images

          • Done

            Activity

            Ascending order - Click to sort in descending order
            Hide
            Permalink
            ksuberlak Krzysztof Suberlak added a comment -

            Tested with

            butler define-visits --collections  LATISS/raw/all  /repo/main lsst.obs.lsst.Latiss  -C /project/scichris/dev/obs_lsst/config/defineVisits.py --where "exposure.day_obs = 20210908 and exposure.seq_num=487"

            where the config override contains config.groupExposures.name = "one-to-one"
            It worked, so that 

            butler query-data-ids /repo/main exposure visit --where "instrument='LATISS'  and exposure=2021090800487"

            shows that indeed a visit got defined 

            band instrument physical_filter visit_system    exposure       visit    
            ---- ---------- --------------- ------------ ------------- -------------
            		 
               r     LATISS  FELH0600~empty            0 2021090800487 2021090800487
            		 
             

            Show
            ksuberlak Krzysztof Suberlak added a comment - Tested with butler define - visits - - collections LATISS / raw / all / repo / main lsst.obs.lsst.Latiss - C / project / scichris / dev / obs_lsst / config / defineVisits.py - - where "exposure.day_obs = 20210908 and exposure.seq_num=487" where the config override contains config.groupExposures.name = "one-to-one" It worked, so that butler query - data - ids / repo / main exposure visit - - where "instrument='LATISS' and exposure=2021090800487" shows that indeed a visit got defined band instrument physical_filter visit_system exposure visit ---- ---------- --------------- ------------ ------------- ------------- r LATISS FELH0600~empty 0 2021090800487 2021090800487  
            Hide
            Permalink
            tjenness Tim Jenness added a comment - - edited

            A couple of quick changes: define visits for anything that looks on sky and add a where clause to the command line so that people can run the visits on a small subset.

            Show
            tjenness Tim Jenness added a comment - - edited A couple of quick changes: define visits for anything that looks on sky and add a where clause to the command line so that people can run the visits on a small subset.

              People

              Assignee:
              tjenness Tim Jenness
              Reporter:
              tjenness Tim Jenness
              Reviewers:
              Jim Bosch
              Watchers:
              Jim Bosch, Krzysztof Suberlak, Tiago Ribeiro, Tim Jenness
              Votes:
              1 Vote for this issue
              Watchers:
              4 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved:

                  Jenkins

                  No builds found.