 
 ;; In developing the time period conversion functions, we noticed that
 ;; as long as the time period remained consistent from dataset to
-;; dataset, the ability to 0-index became irrelevant.  Our choice of
-;; January 1st, 2000 ensures that, regardless of the date on which the
-;; specific MODIS product became active, datasets at the same temporal
-;; resolution will match up. With that in mind, we chose January 1st
-;; 2000.
+;; dataset, the ability to 0-index each dataset became irrelevant.
+;; Our choice of January 1st, 2000 as a common reference date ensures
+;; that, regardless of the date on which the specific MODIS product
+;; became active, datasets at the same temporal resolution will match
+;; up.
 
 (def ref-date (date-time 2000))
 

;; first of each month, while the others mark off blocks of 16 or 8
;; julian days from the beginning of the year.
;;
;;(It's important to note that time periods are NOT measured from the
;; activation date of a specific product. The first available NDVI
;; 16-day composite, for example, has a beginning date of February
;; 18th 2001, or Julian day 49, the 1st day of the 4th period as

;; further validation for our choice of January 1st, 2000 as a
;; consistent reference point.
;;
;; Additionally, it should be noted that the final dataset is never
;; full; the 23rd 16-day dataset of the year holds data for either 13
;; or 14 days, depending on leap year.)
;;
;; So! To construct a date, the user supplies a number of date
;; "pieces", ranging from year down to microsecond. To compare two
;; times on julian day, we use the clj-time library to calculate the
;; interval between a given date and January 1st of the year in which
;; the date occurs.

(defn in-days
  "Returns the number of days spanned by the given time interval."
