Screen Tabs

Here are my notes on what I think needs to be present in the configurator. You might find ElectronicFootlocker a useful crossreference. -- BobKrzaczek - 12 Aug 2005

DEM

A "DEM" tab needs to be presented that lets a user specify which DEM is to be used for the in-flight georectification. Because the Leica software cannot switch to a new DEM once started, selecting the DEM becomes a "pre flight" rather than "in flight" activity.

DEMs can be found by going to the electronic footlocker, and scanning the contents of the dems directory. Each DEM consists of two files, one ending with .img and the other with .rrd Ignore the rrd file, and instead let the user select among whatever .img files can be found. Bonus points if you check and limit the selection to only those that have both .img and .rrd files available.

On the same tab as the DEM, probably ought to be the expected average altitude for this flight. 10,000 feet is a good default here.

Controller

The Applanix device must be specified. The configuration should begin with a default value of 10.0.0.10:5603 but allow the user to change it to whatever they need. This is passed to the --aplx option.

Normally, the controller starts up in a paused state; the GUI must be used to enable the triggering of the cameras. Optionally, the controller can be starting "running", instead of paused. If selected, add a --run to the controller's command line.

The camera triggering period is 4.5 seconds. If the user wants to trigger the camera every t seconds (where t is a decimal real), supply it to the --every option.

The selection of the gimbal driver uses one of the following letters, supplied to the controller via the --gimbal option.

The selection of the camera drivers should be supplied to the --indigo and --terrapix options, which should get i and t (respectively) in order to communicate with the real hardware. Alternatively, one of the following can be given as well.

The logfile that captures output from this process can contain messages of a given severity and higher. This "lowest priority" message is supplied via the --log option, and can be one of the following words, in ascending order: trace debug info notice warning error The default value is notice.

For testing purposes, all writing activity from the flight recorder can be disabled by supplying the --nodata option. This will disable camera data, log files, flight legs, and so on. It disables all writing activity by the controller. This option is also implied by the --replay options, since we want to minimize the chance that a previous flight's data is overwritten.

When replaying a previous flight, the --datadir option is used to tell the controller where to obtain the raw camera files saved from a previous flight. If you select the replay driver for either camera driver above, you must also supply the --datadir options, and you may also very likely want to use the --nodata option.

The --replay option is a convenience option. You supply a data directory to it, and this option then implies --datadir along with --nodata and --indigo=r and --terrapix=r.

Band to Band Registration

By default, this object will subscribe to swir, mwir, and lwir objects in the default naming context. You can specify a different context (the default is wasp) via the --context option, but you can't change the camera names (yet).

Eventually, the 180 degree rotation of the MWIR and LWIR data will be handled through the registration tables. Until then, you can select to have reg do the image rotation explicitly (instead of relying on the tables) with one of the following options. Not both.

--tablerotate

performs table based rotations. Faster, but broken at present.

--imagerotate

performs image based rotations. Slower, but correct.

By default, the registration object assumes 510 row images, and will truncate larger tables and images to that size. If you want to try for a larger value, say 512, use the --rows option. 510 and 512 are the only values likely to make any sense here.

By default, the registration object pulls its tables from a directory that is the concatenation of treg and the decimal number of rows in the data it expects. So, the default table directory in the electronic footlocker is treg510. However, you can override this default with the --tables option. The user should select from any directory in the footlocker that begins with the string treg. There will always be a directory named treg510. See ElectronicFootlocker for more details.

The --savedir option can be given the name of a directory into which the registration object should record any data it generates. This is easier than starting a filer object, as the adp script currently does. This option should be set to C:/adp/products if reg is the last tool in the ADP chain; that is to say, if reg is set to run, and fire is not running, and geo is not running, then set this flag on reg.

Fire Detection

There is an optional parameter to set the parameter file -f parameterfilename. to have it generate bogus data (the circle), use -f bogus.

Geo Rectification

The DEM, selected above, should be supplied to the geo process via a --dem option.

The expected average altitude for the current flight should be supplied via the --alt option. I'm still thinking about how to handle multi-altitude flights.

Miscellaneous

I don't know what else to call these.

The root of the electronic footlocker needs to be established for the rest of the system. This typically has the value e:/footlocker but the user could potentially choose any directory. This is propagated to the rest of the ADP, not through command line options, but through the environment, under the name FOOTLOCKER.

The Name Service needs to be selectable as well. With the exception of the flight GUI, this is propagated to the rest of the ADP via an environment variable named NameServiceIOR. On one hand, the user needs to be able to enter anything. On the other hand, the two most common settings are

• corbaloc:iiop:localhost:14444/NameService
• corbaloc:iiop:chapman.cis.rit.edu:25/NameService

The context for all ADP objects is by default, wasp. Another context could be supplied here as well. Gradually, I'm adding support to this to all the ADP objects, and their wrapper programs will all support this through the same command line option, --context.

Other Stuff?