NERI Air Models OSPM Description of Updates

History of WinOSPM Updates and Fixes

Latest Update:

Bugs fix July 8, 2003

• If an hourly input file contained a variable list with an error in the List, and this file was opened in the Format File Window, and the window was closed without correcting the error, the subsequent opening of an hourly output file in the Format File Window resulted in not correct updating of the List of available Output Variables.

• When in the "Special Mode" the values of wind speeds or the range of wind directions were changed, the User was not prompted to save the project file with the changed values and the changed values were not saved with the Project File.

• If an hourly input file was provided as an Excel file, and the date variable contained also specification of the hour (e.g. in the form: 13.01.99 22:00), an output of the DateTime variable in an hourly output file resulted in an error.

• If the OSPM Project was created using the option "Accept no input files" and some hourly input files were added subsequently to the project in the "Calculation" window, it was not possible to run the project without re-opening it.

• If WinOSPM was run on a computer where the Regional Settings of the Date format were not "Day-Month-Year" this resulted in wrong date values for the computation period in the Results Summary Table. Also the Start and End Dates specified in the "Calculation" window were in this case not interpreted correctly.

• If values for the "Wind Sectors with Building Height Exceptions" were provided with more then 2 decimal digits, the Project file become corrupted after it had been saved. This was due to insufficient space reserved for the wind sector values in the Project file. Although, any number of decimal digits will now be accepted, using too many digits is not recommended.

• If a Vehicle or a Fuel List file was specified without explicitly providing the path of the file, the location of the file was correctly interpreted as being the same as the OSPM Project File. However, when the List was opened from within a WinOSPM project and closed without any changes, the User was incorrectly prompted to confirm if the "New" List should be used with the Project.