Chapter 35. Frequently Asked Questions

Table of Contents
35.1. General
35.2. Installation
35.3. Materials
35.4. Property Mapping Techniques
35.5. Thermal Modeling
35.6. Atmospheric Modeling
35.7. Sensor Modeling
35.8. Platform Modeling
35.9. Scene Construction
35.10. Plume Modeling

35.1. General

35.1.1. History and Learning More

35.1.1.1. How long has the model been around?

The DIRSIG was formally created in the late 80's at RIT as a project by a group of students. Since then, the model has been improved and maintained by a combination of full-time research staff and graduate student projects.

35.1.1.2. How do I learn even more about how the model works?

The faculty, staff and students attempt to publish in-depth papers on various aspects of the model on regular basis. We believe that this is an important difference between this model and others. We attempt to keep copies of recent papers on the DIRSIG website on the "Documentation" page (http://www.dirsig.org/docs). On this webpage you will also find a list of published journal and conference papers.

35.1.2. Model Capabilties

35.1.2.1. What wavelengths/frequencies can I model?

The model is generally limited to the same wavelength regions as the MODTRAN and FASCODE atmospheric models, which is approximately 0.4 - 20 microns, or 450 - 15,000 wavenumbers.

35.1.2.2. What is the spectral resolution limit of the model?

Again, the model is generally limited by wavelength restrictions of the MODTRAN and FASCODE atmospheric models. If you are using MODTRAN exclusively, then you are restricted to the 1 wavenumber resolution limit of MODTRAN4 or the 0.1 wavenumber resolution limit of MODTRAN5. By also using FASCODE, you can increase your resolution in some special cases.

35.1.2.3. What are the system requirements for the software?

The DIRSIG software is distributed as binary executables only for the following supported architectures:

  • Sun Microsystems UltraSparc Servers and Workstations running Solaris 2.9+ (machine must be up-to-date with all patches)

  • Silicon Graphics (SGI) Servers and Workstations running IRIX 6.X

  • Intel Pentium and AMD Athlon Workstations running the Linux 2.4+ Kernel and Glibc 2.0+ (for example, RedHat 8+, Suse 8+, etc.).

For more information, read the Installation chapter.

35.1.2.4. How do I buy a support contract for the software?

At this time, we encourage that you become a funding source for an academic research project. This will entitle you to some degree of support. At this time, the university does not have the labor power nor stability in funding (for this type of work) to maintain a dedicated staff for support.

In some cases, we have worked directly for organizations to help them incorporate the use of the model into their efforts.

35.1.2.5. How long does it take to run a simulation?

The run time for a simulation varies based on the type of simulation being performed. A small-format, low-spatial resolution sensor looking at a simple scene may take a few minutes. A large-format, high-spatial resolution sensor looking at a bigger scene may take as long as a few days.

The parameters that dictate run-time are the total number of pixels to be modeled, the amount of sub-pixel sampling, the spectral resolution, the scene complexity (number of objects, number of facets in each object, etc.), the number of materials, the size of the images used for material, texture, etc. maps and if the thermal model is turned on.

35.1.2.6. What language is DIRSIG written in?

DIRSIG3 was written entirely in C with the exception of the radiometry library which was written in primative C++. DIRSIG4 is entirely written in C++ using a very object-oriented, modular design consisting of 250+ individual classes.