This tab allows users to add and to remove SIMMOD scenarios from the selected conversion setting. This tab consists of a list and a table. Available SIMMOD Scenarios List: The list displays all subdirectories in the simmod directory. This directory is either the directory S2I is executing in or is passed in as a command-line parameter. The assumption is that these subdirectories are SIMMOD simulations. Should a list entry lack a critical element for a SIMMOD scenario, e.g. the history file or SIMU40 file, then an error occurs when the problem is detected and the conversion into INM, if any, is terminated. Included Scenarios Configuration Table: On the right side is a table containing all of the included iterations. Its columns are as follows: % of Days Occurring: The percentage of days in the year that the airport's activity should mirror the iteration in this row. Days Occurring: The number of days in a year that this airport's activity should mirror the iteration in this row. Scenario: The name of the included scenario. Iteration: The specific included SIMMOD iteration within this scenario. Multiplier Value: A number allowing users to increase of decrease the affect this iteration has in the INM model. Add scenarios by selecting one or more items in the list and then clicking the button with the arrow pointing towards the table. SIMMOD scenarios can be included at most once within the same conversion setting. Scenarios are deleted by selecting any column in the indicated table row and then clicking the button with the arrow pointing towards the list. Above the table is a label indicating the total days covered by the included scenarios. If this number is below 365, then the resulting INM study may not be correct. To change a percentage, select and edit the first column in the row for the scenario the user wishes to change. The value must be between 0 and 1, inclusive. If there is more than one included scenario, the total of percentages must be between 0 and 1, inclusive. The iteration column is a drop down combo box including all iterations defined within the SIMMOD scenario. Only one iteration can be selected at any time. Why allow only one iteration per scenario in one conversion setting? SIMMOD examines airport operations while INM looks at airport noise. Each SIMMOD scenario contains a fixed sequence of operations. Each iteration within this scenario contains a different set of random events. In this fashion, SIMMOD simulates the impact chance has on the given sequence of events. For example, aircraft 114 enters the model at 10:03AM in iterations 1 and 2. 114 takes longer loading in 1 than in 2. 114 then waits 15 minutes longer before taking off in iteration 2 while it does not wait in iteration 1. Unlike SIMMOD, these variations rarely, if ever, impact the amount of noise the operation makes. Hence, including the same SIMMOD scenario more than once is redundant for an INM study. Why have the first two columns? While SIMMOD simulations are based on a day's activity, INM studies are based on a year's activity. These columns tell S2I how many times each SIMMOD scenario's data should be copied to mimic the year. e.g. One scenario, SAN_east, covers airport activity 80% of the time when the wind blows out of the east. SAN_south covers the same airport on the other 20% of the time when the wind blows out of the south. SAN_east should be listed with a 0.8 percent of days occurring and SAN_south should be listed with 0.2. The Multiplier Value lets the user emphasize or de-emphasize a SIMMOD scenario in the resulting INM study. The default value is 1.0; at this value the multiplier does not affect the output. Setting it to 2.0 has the same result as doubling the number of daily airport operations witihin the SIMMOD iteration. Setting it to 0.5 has the affect of halving the number of operations.