Changeset 41401 for trunk/doc/release.2015/ps1.dataproducts/report.v0.txt

Timestamp:

Aug 15, 2020, 10:41:44 AM (6 years ago)

Author:

eugene

Message:

finished revisions for referee

File:

• trunk/doc/release.2015/ps1.dataproducts/report.v0.txt (modified) (10 diffs)

trunk/doc/release.2015/ps1.dataproducts/report.v0.txt

@@ -22 +22 @@
 it is also still a *relational* SQL database, so that should be mentioned as well.
 
->> TBD
+>> the use of the word 'hierarchical' in that sentence was irrelevant.
+   We've removed that word, but added a following paragraph to
+   introduce these database concepts to the reader.
 
 * Page 2, Section 3: The release dates for DR1 and DR2 are mentioned here.
@@ -42 +44 @@
 http with https wherever that changeover has been made.
 
->> TBD
+>> Fixed this one and checked all URLs
 
 * Page 6, Section 5.1.6, last paragraph: Has the reconstruction of
@@ -48 +50 @@
 reference or give an example in the sample queries appendix.
 
->> TBD
+>> reconstruction of difference images within the IPP is regularly
+   used, but an implementation of this process at MAST has not been
+   developed.  The text has been modified to explain the concept and
+   current status within the IPP.
 
 * Page 10, Section 6.5: Isn't it Simple Object Access? Please provide a
 reference and/or URL for SOAP.
 
->> TBD
+>> correct -- URL to W3C specification added
 
 * Page 19, Section 7.7: I understand the reason for using a number such as
@@ -63 +68 @@
 developers can probably assist with that.
 
->> TBD
+>> The linked microsoft technical report has not been published in a
+refereed journal, but it has been placed on the arxiv, so we have adjusted the
+reference to cite that article.
 
 * Page 21, Section 8.1.1: What total area of the sky is affected by the polar
@@ -69 +76 @@
 described in Paper IV, but it's worth including a single sentence here.
 
+>> Added words to describe the affected area.
+
 * Appendix, Table Schema: The authors should detail how they ensure that all
 the table and column descriptions are accurate. For example, what automation,
 if any, is used to convert SQL table definitions into these LaTeX tables?
+
+>> added a mention of the XML-to-LaTeX translation code.
 
 SQL Examples
@@ -82 +93 @@
 * It is not clear from this section which specific context to use. I used DR2.
 
+>> yes, these queries are meant for DR2.  Text updated to reflect this.
+
 A particular database context should be explicitly mentioned and some names
 should be checked for consistency with that context. You could also state
@@ -91 +104 @@
 an arithmetic overflow exception.
 
+>>> yes, we added a word of warning.
+
 * Example 2: This query returned 3868 rows in DR2, not 3867.
 
@@ -97 +112 @@
 * Example 5: This query returned 1806 objects in DR2, not 1805.
 
+>>> our retry confirms these numbers: numbers in text updated (for all three).
+
 * Example 9: Most of the objects selected have -999 for gMeanPSFMag.
 Is this expected?
+
+>> It is expected, added text to note and explain.
 
 * Example 10: The name of the MyDB table implies DR2. Again, choose a specific
 context or rename to be data-release agnostic.
 
+>> context for all examples is DR2
+
 * Example 12: Is there a reason the MyDB table name is enclosed in brackets in
 one example and not the other? Also the '_PS1' name doesn't seem to be
 consistent with the apparent DR2 context.
+
+>> the square brackets are always allowed, but are needed to protect
+   table names with spaces or special words.  changed the examples to
+   all used square brackets.  The _PS1 addition is meant to identify
+   the table containing results for PS1 (vs Gaia) and would be
+   appropriate for either DR1 or DR2 (both from PS1).
 
 Spelling, Typos, etc.
@@ -115 +142 @@
 * In general: Hawaii or Hawai'i?
 
+>> should be all Hawai`i, except in the adjective Hawaiian
+
 * In general: Check terms like 'Section', 'Table', 'Figure' (vs. 'Fig') for
 consistency.
 
+>> fixed
+
 * In general: Spell Sérsic consistently throughout the paper.
+
+>> fixed
 
 * In general: Choose a single notation for RA (RA vs. R.A.).
 
+>> fixed (to R.A.)
+
 * Page 1, 1st paragraph: "perform as set of astronomical" -> "as a set".
+
+>> "perform a set of..."
 
 * Page 2, Table 1: There seem to be several different quotation conventions in
 the paper, e.g. `Release'. Elsewhere double quotes are used.
 
+>> fixed (all double quotes)
+
 * Page 2, Table 1: "Tessellation Type" -> "TessellationType"
+
+>> fixed
 
 * Page 5, Section 5.1.4: in the description of SDSS apertures, double prime
@@ -134 +175 @@
 both notations are used in the paper.
 
+>> converted instances of XX arcsec to XX" where XX is numerical.
+   Entries as units in tables and the rare case of a word (one
+   arcsecond) are written out.
+
 * Page 10: "csv, FITS or xml"; CSV and XML are acronyms just like FITS, so the
 same typography should be used.
 
+>> fixed
+
 * Page 21, Section 8.1.1: "This issues" -> "This issue".
 
+>> fixed
+
 * Page 22, Section 9: Use official IAU designation for Oumuamua.
+
+>> fixed