Changes between Initial Version and Version 1 of PublicPages/MayallZbandLegacy/Principles


Ignore:
Timestamp:
Apr 26, 2015 12:40:19 AM (10 years ago)
Author:
Robert Blum
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • PublicPages/MayallZbandLegacy/Principles

    v1 v1  
     1= Mayall z-Band Legacy Survey Principles =
     2
     3[[PageOutline]]
     4
     5PIs : Dey & Schlegel \\
     6 
     7Survey Leads:
     8- Observing team lead: Arjun Dey
     9- Scheduling team lead: Anna Patej
     10- Data team lead: Peter Nugent
     11- Tractor team lead: Dustin Lang
     12- Photometric calibration lead: Doug Finkbeiner
     13 
     14== Project Goals ==
     15
     16The Mayall z-Band Legacy Survey (MzLS) of the north Galactic cap will create
     17a public z-band imaging survey to provide targets for the DESI survey.  We will image 5500 deg^2^ in the north Galactic cap with the Mosaic 3 imager on the Mayall 4m telescope. The z-band survey will be done in parallel with
     18''g'' and ''r'' bands using the 90Prime instrument at the Steward Observatory Bok telescope. 
     19
     20NOAO has committed
     21250  nights to this project; time will be assigned during 2016A and 2017A.  The collaboration is responsible for delivering reduced and calibrated data and catalogs to project Co-Investigators and NOAO and to make these data products publicly available in a timely manner. The PIs are committed
     22to enabling a scientifically productive and open collaboration and aim to provide the data required to support the science cases of Co-Investigators and the DESI target catalog.
     23 
     24== Membership ==
     25
     26MzLS !CoIs will be drawn from DESI Participants.
     27 
     28== Data access ==
     29
     30The raw data for this program is immediately public.  A set of reductions as laid out in the Data Release Plan will be made public on approximately 3-month timescales.
     31!CoIs will have access to the contents of these releases prior to those releases, with the only restriction that proper citations be included in papers.
     32
     33Data products, software, analyses, and ancillary data sets produced by any group of !CoIs and not
     34included in the Data Release Plan are proprietary to that group, unless and until explicitly shared with other !CoIs.
     35 
     36== Project announcements ==
     37
     38We require that technical and scientific projects and papers be announced on the MzLS
     39e-mail list and posted on the Projects page of the wiki.  Projects can be proposed only by !CoIs and
     40their students and postdocs. The invitation to involve other !CoIs is
     41encouraged but not required.  The list of !CoIs in each project will be maintained on this page.
     42
     43Projects can include both !CoIs and "external participants". An external participant is someone who is not an official CoI but is identified by the project lead as providing value to the project.
     44A project "participant" list (which includes all members of the project, both official !CoIs and external participants) should be posted to the wiki and maintained by the project lead.
     45
     46The e-mail list, wiki, and svn repository will provide collaboration tools for projects. Project titles and
     47abstracts should be posted at least 14 days before a paper on the topic is posted in order to allow for
     48useful contributions from other !CoIs.
     49
     50== Publications ==
     51
     52Technical and scientific publications will be expected to follow the standards of scholarly
     53publications.  The standards for AAS journals can be found here:
     54   http://iopscience.iop.org/0004-637X/page/Ethics%20policy
     55There is no notion of key projects or “builders” with authorship rights.  There is an expectation
     56that authorship be extended to any !CoIs and external participants who have contributed to any paper beyond already-published work. Papers must be announced and posted at least 14 days prior to journal submission to allow other !CoIs to provide comments and to request authorship when appropriate. Posting of conference proceedings is encouraged.
     57 
     58
     59[[BackLinks]]