Changes between Version 5 and Version 6 of ps1_public_release_pstamp_issues

Timestamp:

May 4, 2015, 12:45:21 PM (11 years ago)

Author:

bills

Comment:

--

ps1_public_release_pstamp_issues

@@ -78 +78 @@
 
 === Data products that will not be included in the public release ===
-* detrended chip stage images
-* difference images
-* catalogs (except staticsky)
-These were not preserved by the IPP for PV3 because of insufficient space.
+ * raw gpc1 images
+ * detrended chip stage images
+ * difference images
+ * catalogs (except staticsky)
+
+The chip and diff stage images were not preserved by the IPP for PV3 because of insufficient space.
 
 === Metadata Required to Support the implementation of an Image Server ===
@@ -93 +95 @@
 
 There are several issues that need to be resolved before these systems are delivered.
-* Data that must stay in the IPP cluster will need to be shuffled off to other systems or replicated.
-* Some system that implements the Nebulous interfaces or a subset thereof will need to be delivered. Of course that could be nebulous but:
+ * Data that must stay in the IPP cluster will need to be shuffled off to other systems or replicated.
+ * Some system that implements the Nebulous interfaces or a subset thereof will need to be delivered. Of course that could be nebulous but:
   * The full nebulous database currently takes up 3.7 TB and contains information on files that are not part of the delivery
   * Nebulous contains many features that might not be relevant to the new owners
   * It introduces depencies on NFS, apache, and mysql. These might not be issues but should be noted.
   * Management requires expertise that does not currently exist outside of the IPP team.
-* Information describing the composition of the delivered IPP data products is required. 
+ * Information describing the composition of the delivered IPP data products is required. 
   * This could be a modified copy of the GPC1 mysql database  (594 GB) with the states of various data is modified to match the data being shipped.
   * Alternatively a database with a simplfied structure (single frame data represented by warp tables augmented with exposure metadata from rawExp) could be loaded