| | 156 | |
| | 157 | == GPC1 database to Nebulous key translation == |
| | 158 | |
| | 159 | Each component product in the GPC1 database (warpSkyfile, stackSumSkyfile, diffSkyfile, etc.) contains a path_base field. This contains the initial nebulous key for the output files for that product. Appending the extension listed in the table above to that path_base produces the full nebulous key that points to the disk file. The {FILE_ID} field for the skycal catalog is substituted with the stack_id associated with that skycal run. |
| | 160 | |
| | 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. |
| | 162 | |
