Differences between revisions 1 and 7 (spanning 6 versions)
⇤ ← Revision 1 as of 2017-10-30 10:08:39 →
Size: 335
Editor: EricPalmer
Comment:
← Revision 7 as of 2017-10-30 10:57:14 → ⇥
Size: 888
Editor: JohnWeirich
Comment:
Deletions are marked like this. Additions are marked like this.
Line 1: Line 1:
== Program ==

 * [[processLRO-orig.f]] (Received on 10 Oct 2013, renamed 9 Jan 2014).
   * Flag {{{"Bits == 16, not commented"}}}
   * Sets negative values to 0
   * Stretches the values from 0 to 32767

 * [[processLRO.f]] - used to generate processLRO-nostretch
   * Flag {{{"Bits == 16, commented"}}}
   * Allows 0 values
   * Allows negative values (stores the exact signed integer from the source file)



 Runs in the working directory. Looks for
   {{{../LRO/PROCESS_IMG.IN}}}

 * NEW_IMAGES -- located in working directory
Line 14: Line 32:
   ** NEW_IMAGES -- The directory to hold the images. No subdirectories needed.
Line 16: Line 34:
   * NEW_IMAGES -- The directory to hold the images. No subdirectories needed.

Program

  • processLRO-orig.f (Received on 10 Oct 2013, renamed 9 Jan 2014).

    • Flag "Bits == 16, not commented"

    • Sets negative values to 0
    • Stretches the values from 0 to 32767

  • processLRO.f - used to generate processLRO-nostretch

    • Flag "Bits == 16, commented"

    • Allows 0 values
    • Allows negative values (stores the exact signed integer from the source file)
    Runs in the working directory. Looks for

    • ../LRO/PROCESS_IMG.IN

  • NEW_IMAGES -- located in working directory

Directory Structure

  • LRO
    • DATA
      • kernels -- The kernels that are needed
        • ck
        • fk
        • spk
        • tspk
        • naif0010.tls
  • working
    • NEW_IMAGES -- The directory to hold the images. No subdirectories needed.

PROCESS_IMG.IN -- The configuration file used for LRO

LRO_setup (last edited 2017-10-30 10:57:14 by JohnWeirich)