Differences between revisions 1 and 9 (spanning 8 versions)
Revision 1 as of 2013-11-20 07:59:35
Size: 518
Editor: EricPalmer
Comment:
Revision 9 as of 2016-02-01 13:02:46
Size: 625
Editor: BMittan
Comment:
Deletions are marked like this. Additions are marked like this.
Line 1: Line 1:
= IMAGEFILES =  = IMAGEFILES =
Line 3: Line 3:
Here we store the images that will be used in SPC. They are created by ["process_img"], which is different for every flight mission.
Line 5: Line 4:
The key data stored in IMAGEFILES is a scaled signed integer (2 bytes or 16 bits), with the exclusion of values less than 0. Acceptable values are 0 to 32767.  ['process_img"] will take the original images' data (float or int) and calculate the maximum value. Then it will scale the data to spread from 0 to 32767 to maximize the accuracy of the stored data. == Description ==

'''
IMAGEFILES/''' stores images that will be used in SPC. These images are created by [[process_img]], which is different for every flight mission.

The key data stored in '''IMAGEFILES/'''
is a scaled signed integer (2 bytes or 16 bits), with the exclusion of values less than 0. Acceptable values are from 0 to 32767.

[[process_img]] takes the original images' data (float or int) and calculates the maximum value. Then it scales the data to spread from 0 to 32767 to maximize the accuracy of the stored data.

------------

''(Compiled by KD)''

CategoryDirectories

IMAGEFILES

Description

IMAGEFILES/ stores images that will be used in SPC. These images are created by process_img, which is different for every flight mission.

The key data stored in IMAGEFILES/ is a scaled signed integer (2 bytes or 16 bits), with the exclusion of values less than 0. Acceptable values are from 0 to 32767.

process_img takes the original images' data (float or int) and calculates the maximum value. Then it scales the data to spread from 0 to 32767 to maximize the accuracy of the stored data.


(Compiled by KD)

CategoryDirectories

IMAGEFILES (last edited 2016-07-23 07:14:01 by BMittan)