Here is a look at the input files that go in to a DIRSIG simulation. Each icon in the dirsig_edit tool corresponds to an XML file: Behind the scenes, these files are given the following extensions: .scene .atm .platform .ppd .tasks .options The options file is, by happenstance, optional. So what goes in to the ".sim" manifest file? It's simply a list of the files assigned to each component. A typical sim file looks as follows: <simulation> <scene externalfile="../../warehouse.scene" /> <atmosphericconditions externalfile="./warehouse.atm" /> <platform externalfile="./warehouse.platform" /> <platformmotion externalfile="./warehouse.ppd" /> <tasklist externalfile="./warehouse.tasks" /> </simulation> See? Nothing more than a list of files. You can also see the relationship between files and components from within dirsig_edit. Jus...
A blog about the Digital Imaging and Remote Sensing Image Generation (DIRSIG) model featuring posts contributed by the developers. This is not a user manual and it is not a training class. But, it is a place to see what the developers are doing and a little about how we do it. So think of this as a place to learn cool tips, tricks, etc.