Modifying Ingestor Options

SSEC sets the amount of retained data, the AREA storage path, and data storage convention option defaults prior to shipment. This section contain procedures for:

These options are set in the /etc/rc3.d/S99inge file, which starts on power-up or reboot, and the /etc/init.d/ingcntl file. These files are normally hard linked together. If they are linked, as is normally the case, and you make changes to /etc/rc3.d/S99inge, you will automatically make the same changes to /etc/init.d/ingcntl. If, through editing, etc., the link becomes broken, your changes will only be applied to the file you edited. In this case, you must manually make identical changes to the other file. Failure to do so may cause the ingestor to operate in an unexpected manner.

To change a particular option, you must perform the following in the order shown:

edit /etc/rc3.d/S99inge using a vi or other suitable editor
make changes and save the file
verify that the same changes were made to /etc/init.d/ingcntl using a vi or other suitable editor
if /etc/init.d/ingcntl is unchanged (broken link), make changes and save the file
restart the ingestor

Changing the Amount of Retained Data

The ingestor stores data in round-robin AREA buffers, one for visible images and one for IR images. Once the buffer has filled, the ingestor overwrites the oldest image AREA with next image it ingests.

The following line sets the visible and IR buffer size to 28 AREAs each. The 28 visible AREAs will be numbered from 1 to 28 and then wrap back around to 1; the 28 IR AREAs will be numbered 29 to 56 and then wrap back to 29.

AREAS=28;export AREAS

This is the default buffer size. Changing 28 to some other number will change the size of the AREA buffer loops, and if you make this number too large, you will exhaust the space in the file system.

Changing the AREA Storage Path

The following line sets the path to the AREAs.

cd /home/mcadde/mcidas/data

This is the default path; it allows the ingestor computer to also function as the ADDE server for the data. As an alternative, some other path can be chosen, allowing the areas to be written via NFS to some other machine. Because the GMS data rate is quite modest, NFS is a viable approach if you want the data on a system with more available disk storage than the ingestor system itself.

Changing the Data Storage Convention

A # symbol at the beginning of a lines indicates that the line is commented out. The following line controls the little-endian/big-endian convention. As delivered, the line is:

#BIG_ENDIAN=yes;export BIG_ENDIAN

The # symbol makes this line a comment. It should remain commented out unless the AREAs are being NFS mounted to a machine where they will be served from a big-endian computer. If this is the case, edit the file and remove the # symbol. This causes the ingestor to write the area data in big-endian convention.

[Search Manual] [Table of Contents] [FAQ] [Go to Previous] [Go to Next]