Differences between revisions 13 and 18 (spanning 5 versions)
Revision 13 as of 2017-12-20 14:17:14
Size: 1950
Editor: EricPalmer
Comment:
Revision 18 as of 2017-12-22 10:59:59
Size: 2308
Editor: EricPalmer
Comment:
Deletions are marked like this. Additions are marked like this.
Line 2: Line 2:
||Category B ||Version 3.0.1 ||
Line 3: Line 4:
||Category B||Version 3.0.1||
Line 6: Line 6:
This program
Line 7: Line 8:
This program
Line 16: Line 16:
Line 20: Line 19:
Line 30: Line 28:
Line 38: Line 35:
 * 16 image(s) are stored to [[IMAGEFILES]] directory. Stretched from 0 to 65536  * 16 image(s) are stored to [[IMAGEFILES]] directory.(JRW edit: Do you mean 16-bit image?) Stretched from 0 to 65536
Line 40: Line 37:
= WARNING == 
 * The program [[Display]] will put the 0,0 position of the image in the top left, but OREx wants 0,0 to be in the bottom left.
= WARNING ==

 * The program [[display]] will put the 0,0 position of the image in the top left, but OREx wants 0,0 to be in the bottom left.
Line 46: Line 44:
process_fits can be run in two modes

 * Single file - just give the FITS filename at the prompt
 * Batch mode
  * If the file [[newpic.txt]] exists, then process_fits will search through ../OSIRIS_REX/NEW_IMAGES to find the image and process. [[NEW_IMAGES]] is configured as YYYY/DOY/<source images>
Line 57: Line 60:
   5.0000000000000000         5.0000000000000000
Line 60: Line 63:


Line 64: Line 64:
Line 69: Line 68:
CategoryPrograms ----
CategoryThreeOhOne CategoryThreeAlphaTwo

PROCESS_FITS

Category B

Version 3.0.1

Description

This program

  • reads a FITS image file
  • extracts relevant information from the header
  • adds a record to the make_sumfiles.in file

  • adds a raw 16- bit unsigned integer image to the IMAGEFILES directory

OREx Naming convention

Level 0

The data stored in each image file contained in the IMAGEFILES directory is a scaled unsigned integer (as 14 bits folded into 16 bits), with the exclusion of values less than 0. Acceptable values are from 0 to 16,383.

Level 1

If the source is a real (or 32-bit float) value process_fits takes the original images' data float and calculates the maximum value. Then it scales the data to spread from 0 to 65536 to maximize the accuracy of the stored data.

ECR Changes from 3.0A2

  • Support OREx level 0 images
    • Trim the second channel from the image to make it 1024x1024
    • Remove dark/bias -- This comes from the shielded overscan region
    • Correct the flat field
    • Desmear the image

Required Files

Outputs

  • a row for the image is appended to make_sumfiles.in

  • 16 image(s) are stored to IMAGEFILES directory.(JRW edit: Do you mean 16-bit image?) Stretched from 0 to 65536

= WARNING ==

  • The program display will put the 0,0 position of the image in the top left, but OREx wants 0,0 to be in the bottom left.


Using process_fits

process_fits can be run in two modes

  • Single file - just give the FITS filename at the prompt
  • Batch mode
    • If the file newpic.txt exists, then process_fits will search through ../OSIRIS_REX/NEW_IMAGES to find the image and process. NEW_IMAGES is configured as YYYY/DOY/<source images>

Here is a sample of the standard input:

 Input filename
2019-01-20T22-47-05.541_PCAM_L0b_V004.fits
 OKAY
2019 JAN 20 22:47:05.050
EXPOSURE(ms) =    100.000
 MSB SIGNED
      0.00      0.00      0.00      0.00      0.00
   5.0000000000000000
P601296494J3


process_fits-3.0A2

(Compiled by KD)


CategoryThreeOhOne CategoryThreeAlphaTwo

process_fits (last edited 2020-03-10 13:53:18 by EricPalmer)