Differences between revisions 2 and 3
Revision 2 as of 2013-11-20 08:00:49
Size: 520
Editor: EricPalmer
Comment:
Revision 3 as of 2015-05-06 11:15:24
Size: 520
Editor: localhost
Comment: converted to 1.6 markup
Deletions are marked like this. Additions are marked like this.
Line 4: Line 4:
Here we store the images that will be used in SPC. They are created by ["process_img"], which is different for every flight mission. 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 6: Line 6:
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. 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.

= IMAGEFILES =

Here we store the images that will be used in SPC. They 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 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.

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