## page was renamed from Block 2 - Ingest V0
= Block 2 - Ingest V2 =

== Description ==

This block additionally ingests images from FITS files into the SPC world.  

Basic steps
 1. Copy FITS images
 * Make a list of images
 * Update kernels
 * Set up [[process_fits]]
 * Set up [[make_sumfiles]]
 * Run [[process_fits]] and [[make_sumfiles]]
 * Run [[dynamics]]


== Procedure ==
=== Copy FITS images ===
Install a copy of the FITS images for each day into the NEW_IMAGES_YYYY_DDD location.
{{{
  cp <files> /[path]/OSIRIS_REx/NEW_IMAGES_YYYY_DDD
}}}





=== Make a list of images ===
SPC can ingest images one at a time via [[process_fits]], but we prefer to run it in batch.  If [[newpix.txt]] exists, then [[process_fits]] will use that as input.  It will search through all directories in the form of ../OSIRIS_REx/NEW_IMAGES_YYY_DDD .

For tracking purposes, we will name the list of images via data shortName and put it into lsupport.  The shortName is the short hand for mission name (Ap, PS, OA, DS, OB, Re) and the sequence number of the images set, i.e. the first delivery is 1, the next is 2, etc.
{{{
  cd /path/ops/OSIRIS_REx/NEW_IMAGES_YYYY_DD D 
  ls > ../newpix.Ap4
  cd ../Approch150B.v1
  mv ../newpix.Ap4 lsupport/
  relink lsupport/newpix.Ap4 newpix.txt
  ls -l newpix.txt
}}}



=== Updated kernels ===
Typically, you will need to update the spacecraft (SPK or file extension bsp) and pointing (CK or file extension bc).  It may be necessary to update the spacecraft leap second clock also (lsp).  Finally, if you get a new POLE, the planetary constants kernel for Bennu needs to be updated (PCK or file extension tpc).

 * Remember that many spacecraft kernels have both a reconstructed past history and a future predicted plan.  As such, if you forget to update the SPKs, you could have images that are ingested using the predicted part of an outdated kernel, which won't throw an error.  

 * Remember that SPICE will load kernels in order and use the last loaded kernel for a given time, so the newest kernels should always be at the end of a list.

 1. Edit [[make_sumfiles.txt]].  We want to use chmod to avoid mistakenly over writing such an important file.
{{{ 
   chmod 664 make_sumfiles.txt
   vi make_sumfiles.txt               # add the new kernels
   chmod 444 make_sumfiles.txt
}}}


 * If the PCK has changed, update [[INIT_LITHOS.TXT]] also.


=== Setup process_fits ===

Provided [[newpix.txt]] is in the working directory, then [[process_fits]] will run through all of those images.  

Review the following
{{{
 ls -l DATA/DN2TEMP.TXT
 ls -l DATA/FLATFILES.TXT
 ls -l newpix.txt
}}}


=== Setup make_sumfiles ===

Review the following
{{{
 ls -l DATA/BIAS.TXT                # seldom used
 ls -l DATA/SCOBJ_SHIFT.TXT
 ls -l DATA/TMP2FOCLEN.TXT 
}}}



=== Run process_fits, make_sumfiles ===
For this step, we want to log the output to ensure flat field etc are properly applied.  We want to capture the output from [[make_sumfiles]] to get the list of new image name, which we put in lsupport/imageList.<shortName>
{{{
   chmod 664 make_sumfiles.in
   PROCESS_FITS | tee ingest
   chmod 444 make_sumfiles.in
   echo 0 | MAKE_SUMFILES | tee out
   cut -c 1-12 out > lsupport/imageList.Ap\
}}}
eep - Why did I put this in?  It seems to totally be a waste.   echo 1 | MAKE_SUMFILES 

=== Run dynamics ===
Before running [[dynamics]], you need to make sure that [[DYNAMICS.TXT]] has been updated with the new images.  Take the image list (lsupport/imageList.<shortName>) and add it into [[DYNAMICS.TXT]] before the "END".  Update the uncertainties as required (for the new images and any update for the old images if needed.  Note, if an image is not listed [[DYNAMICS.TXT]], then it will not have it's uncertainties updated.  

{{{
  vi DYNAMICS.TXT
  Gk:rlsupport/imageList.Ap_
}}}
{{{
  ZZ
  DYNAMICS
}}}

=== Finish the block ===
We use [[blockFinish]] to store all needed artifacts to the log directory.  

{{{
   blockFinish Ap6
}}}

----------

''(Compiled by EEP)''