Changes between Version 14 and Version 15 of ps1_public_release_pstamp_issues

Timestamp:

Jun 19, 2015, 12:24:37 PM (11 years ago)

Author:

watersc1

Comment:

--

ps1_public_release_pstamp_issues

@@ -161 +161 @@
 The nebulous keys produced are all of the form {{{neb://OPTIONAL_DISK_VOLUME/arbitrary/directory/path/file.extension}}}.  The IPP source code contains the parsing code in the parse_neb_key function of {{{Nebulous-Server/lib/Nebulous/Key.pm}}}.  The quick version is that everything up to the third {{{/}}} can be removed, yielding the nebulous ext_id, which is simply the directory structure and filename.  For the prototype, the ext_id would be {{{arbitrary/directory/path/file.extension}}}.  The GPC1 database path_base entries generally have an explicit disk volume listed (such as stsci02.0), as those were the attempted targets for the files.  The actual disk location listed in the manifest file will be correct, and may disagree with the path_base location.
 
+=== Example ===
+
+For the example, warp_id = 644431:
+select path_base from warpSkyfile WHERE warp_id = 644431 AND quality = 0 LIMIT 1;
+
+path_base
+neb://stsci07.2/gpc1/LAP.ThreePi.20120706/2012/11/09/o5449g0532o.222926/o5449g0532o.222926.wrp.644431.skycell.1233.020
+
+For the warp image for this product, the extension is just .fits, and after removing the volume, the ext_id is
+gpc1/LAP.ThreePi.20120706/2012/11/09/o5449g0532o.222926/o5449g0532o.222926.wrp.644431.skycell.1233.020.fits
+
+This is listed in the manifest as having real disk location
+/data/stsci00.1/nebulous/b0/69/7208475404.gpc1:LAP.ThreePi.20120706:2012:11:09:o5449g0532o.222926:o5449g0532o.222926.wrp.644431.skycell.1233.020.fits