Code Monkey home page Code Monkey logo

obsstrat's Introduction

Observing Strategy Task Force

Charter

To respond to the white paper call (https://www.lsst.org/call-whitepaper-2018) on behalf of the DESC.


Deliverables

-Two white papers, one focused on WFD and one focused on DDF and other mini-Surveys, to be led by Michelle Lochner and Dan Scolnic. These white papers are due Nov. 30. The overleaf for DDF is here: https://www.overleaf.com/read/xgpxqdmzydcc (publically viewable) and the overleaf for WFD is here: https://www.overleaf.com/read/ywbstqjtnctk.

-One internal DESC note that is a compendium of the large amount of work that has gone into the white paper studies.

-One journal article that details all the metrics established for the white papers. Expectation for timeline to be roughly one month behind the white papers.

-While not a set deliverable, there is an expectation that individual contributions will form their own papers which can go into significant detail of the analysis that relates to observing strategy.


Calendar

July 19, Task Force Meeting. Presentation of additional information needed for call response.

July 24, CMU ObsStrat XWG Session at 11:00. July 26, CMU ObsStrat XWG Session at 09:00.

July 25, Settled list of additional information needed for appropriate response to call

August 2, Task Force Meeting

August 10, First assessment of subset of WFD and mini-survey strategies, with metrics. Slides from each WG.

August 13-16, LSST Community Workshop including multiple ObsStrat sessions

August 16, Task Force Meeting

August 30, Task Force Meeting

September 17-19, LSST Cadence Hackathon at Flatiron (https://www.lsstcorporation.org/node/193). Need to apply.

September 21, Full assessment of strategies and metrics due for task force

Sep 27 - moved to weekly meetings every Thursday at 9am Central.

Oct 11 - First drafts of white papers shared with Task Force.

  • October 25, Revised white papers sent out to DESC reviewers.

  • October 30, DESC Seminar presentation on White Papers.

  • November 5, Responses from DESC due.

  • November 30, !!!!White Papers Due!!!

The key takeaways are a first take due August 10 before the community workshop so we can present to the Project any issues we might have, and a full assessment by September 15. Than iterations over the next two months with white papers sent out to DESC reviewers on Oct 25.


White Paper Template

The LSST Project wants to standardize responses to its call. The latex template provided is here: https://github.com/lsst-pst/survey_strategy_wp/blob/master/WP_submission_template.tex#L84. Its sections are as follows:

a. Abstract — Please provide a short summary of your scientific goals and survey strategy modifications here.

b. General Information — Author Info, Science Category, Survey Type Category, Observing Strategy Category

c. Scientific Motivation — Describe the scientific justification for this white paper in the context of your field, as well as the importance to the general program of astronomy, including the relevance over the next decade. Describe other relevant data, and justify why LSST is the best facility for these observations.

d. Technical Description — Describe your survey strategy modifications or proposed observations. Please comment on each observing constraint below, including the technical motivation behind any constraints. Where relevant, indicate if the constraint applies to all requested observations or a specific subset. Please note which constraints are not relevant or important for your science goals.

e. Performance Evaluation - Please describe how to evaluate the performance of a given survey in achieving your desired science goals, ideally as a heuristic tied directly to the observing strategy (e.g. number of visits obtained within a window of time with a specified set of filters) with a clear link to the resulting effect on science.

f. Special Data Processing -- Describe any data processing requirements beyond the standard LSST Data Management pipelines and how these will be achieved.

[Updated after talking to Lynne Jones] Here is what we feel we need to add to this template, and what we will be asking of each WG:

Add: A section on the strategies considered, including detailed information about all the information we needed to add to the white paper call (e.g., locations for different fields) that would be assessed by each group.

Add from each group a 2-3 page description:

i. Brief introduction of motivation of each probe and what is unique to LSST

ii. How analysis was done/ code was used [Please link to Jupyter notebook]

iii. Justification of the metric

iv. Explanation of preferences of working group with qualifiers about how good/bad strategies are

v. What is needed to know if people outside group use the metric as is without consultation

vi. How would external data change rankings/metric?

vii. What is further work / slight modifications to survey strategy thought about?

Add: Summary of how external (non-LSST) can be used, and what changes in terms of final rankings/preferences assuming external data


Summary of New OpSim Runs

The details of the new OpSim runs are here: https://docushare.lsst.org/docushare/dsweb/Get/Document-28716

Below they are listed as a handy summary (thanks Philippe!):

  1. baseline2018a - Project-official baseline (official opsim v4 baseline, 6/2018). No dome crawl.
  2. kraken_2026 - Unofficial baseline (expected next baseline, including dome crawl).
  3. kraken_2035 - Survey with 9 DD mini surveys instead of 5. Addition of 4 extra extragalactic DD fields.
  4. kraken_2036 - A rolling cadence in WFD. Three regions of declination, alernating on/off every third year from years 3-8. Standard WFD coverage in years 1-3, 8-10 (first two and last two years).
  5. colossus_2665 - Baseline style, with slightly expanded WFD footprint to better satisfy SRD constraints on fO
  6. colossus_2664 - No separated Galactic Plane proposal. Simply run WFD over galactic plane region.
  7. colossus_2667 - Survey with single visits only. Standard visits in pairs each night replaced with single visits per night.
  8. pontus_2002 - Very large WFD footprint (24,700 sq deg) and 5 DD mini-surveys (5 fields).
  9. pontus_2489 - Survey with more visits. Standard 2x15s visits replaced with 1x20s in grizy and 1x40s in u band.
  10. pontus_2502 - A rolling cadence in WFD. Two regions of declination, alternating on/off every other year throughout the entire survey, but the background WFD remains "on" at a 25% reward level.
  11. mothra_2045 - A rolling cadence in WFD. Two regions of declination, alternating on/off every other year throughout entire survey.

Additional Information

In the above, we mention additional information. By that we mean that there are a number of pieces of information we as a group need to fill in about the call. We are asking the following people to prepare this for our next meeting:

  1. Location of WFD - Humna Awan.

  2. Location of DDFs - David Rubin.

  3. List of WFD strategies not in white paper call - Michelle Lochner

  4. Cadence of DDF - Philippe Gris

  5. Special calibration observations - Nicolas Regnault

  6. ToO Capability - Marcelle Soares-Santos

1-4 will likely go in section C above. 5 and 6 may have their own dedicated place within the DDF and mini-surveys response.

For 1-4, we are asking these people to come up with a contained menu of options that each group can consider as part of their response. We would like to have this settled by the CMU meeting, with presentation on July 19.


Working with other surveys

  • For each of our white papers, we will have a dedicated section on the benefits of external datasets. This will include ones from Euclid, WFIRST and other spectroscopic surveys.
  • Our process will be totally transparent and our github page will be public - there is nothing that needs to be hidden about our deliberations. However, we want to maintain a ‘unified front’ within DESC, so we ask for everyone to refrain from stating any conclusions of the task force until these conclusions have been reached.
  • Endorsement of strategies outside of DESC will be done within the DESC white papers.

DESC work:

obsstrat's People

Contributors

drphilmarshall avatar dscolnic avatar ehneilsen avatar humnaawan avatar michellelochner avatar rbiswas4 avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

obsstrat's Issues

Modified (wider?) footprint for WFD

We'd like to change what is considered the Wide-Fast-Deep (WFD) area given that the current WFD region includes high-extinction area that is useless for extragalactic science. We also want to maximize the utility of the footprint, exploring more than 18K coverage after 10 years.

See some numbers/maps here.

descDithers

The idea is to allow access to descDithers (translational and rotational dithers; replace
fieldRA, fieldDec, rotTelPos), similar to those implemented in DC1/DC2. For MAF users, this would translate to instructions to the right Stackers, while for non-MAF users, csv files with descDithers will be produced.

Add urls for opsim output downloads

It is somewhat difficult to find the outputs of the 10 survey strategies that have been produced for the paper. @humnaawan has put these on nersc at /global/cscratch1/sd/awan/dbs_wp_unzipped/ . It may be good to add some of the urls here as well.

Write-up Results

Please write-up your results on the write-up branch. I'll create a set of tex files each group can edit and feel free to create addition tex files that can be \input into your group's main tex file. Don't worry about perfect writing, just get your results down and your figures in. We'll collate everything into the journal articles and white papers after we have everyone's results.

Have a look at the README for what we're expecting from each working group (points i to vii). Obviously we'll also have some subsections on combining probes, please add these as separate tex files with sensible names and \input them into the main file.

Please include your work on both WFD and DDF with clear section headings! Also please give your figures sensible names and consider creating a subdirectory if you have a lot of figures. Bear in mind there's a 99% chance we'll ask you to remake your figures to ensure consistency, so make sure they're in easily rerunable scripts.

Add compression to csv dither files.

@humnaawan I would like to suggest that the csv ditherfiles you produce be gzip compressed so that they are easier to store and transfer around. This will also be useful when we put them up as dataproducts at zenodo following our current trends.

There are two methods of doing this, Add something to the script saving the files
like for file in `ls descDither*.csv`; do echo "gzipping $file"; gzip $file; done
(a little inelegant but faster)
or adding a compression option to the saving (simpler, but takes a bit more time).

I have been doing this for my own purposes, so can add in these options, you can choose.

Add simlib files.

Some of the planned tasks here are using SNANA which requires the information from OpSim outputs in a particular format called simlibs. Obtain the set of simlibs for the 10 cadences released by the project and put them in nersc at /global/project/projectdirs/lsst/cadence_outputs. To read these, a user will want to belong to the lsst group. The plan is to also put these up on zenodo.

Fix license file

I'm told by Aaron Sauers, the person at Fermilab who handles licensing stuff, that the top level license file (where the copyright holder is listed as the DESC) is invalid because the DESC is not an entity that can legally hold copyrights; the institutions of each of the contributors need to be listed instead. For my contributions (simsee), that would be "Fermi Research Alliance, LLC".

Change translational dither frequency

Based on conversations at the Project & Community Workshop 2018, it was agreed that we'd like to not dither in between visits to the same field in the same night for better calibrations. This calls for less frequent translational dithers than per visit, as are currently implemented as descDithers. Rotational dithers frequency (after every filter change) is okay for now.

In an attempt to address this, the translational dithers need to be changed to perNight dithers. #3, #5

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.