|
FireFamilyPlus Known Bugs |
|
|
Bug Reports: If you think you have found a bug within FireFamilyPlus, we would appreciate hearing from you. Please check below to make sure that this problem has not already been resolved. Then, send us a copy of any screenshots or a detailed error message describing the problem and what you were doing with the problem arose. This will help us to recreate the problem and then fix it.
Bug Reports for Version 3.0.5 should be sent to the National Support Desk.
Bug Reports for the Version 4.0.0 Beta test should be sent to Larry Bradshaw.
Thank you very much for your help!
Known Bugs with FireFamilyPlus:
| FireFamilyPlus Version 4.0.0 Beta 3 test |
|
| Generating Repeated Fire Analysis Reports or Graphs from Interactive Batch |
| Description |
Generating repeated (~ 20 to 80) Fire Analysis Reports or Fire Analysis Graphs from Interactive Batch will cause FFP to crash.
|
| Status |
This is being reworked. There is no intermediate fix.
|
|
| Generic Fire Import Delimiter/Date Formats may not be restored correctly |
| Description |
Generic Fire Import Delimiter/Date Formats may not be restored correctly on repeated imports for an agency.
|
| Status |
The defaults are always added in addition to what you might have selected. On repeated imports, make sure only your delimiter/date format is selected before importing data.
|
|
| Importing Station Catalog files are causing FFP 4.0 to crash. |
| Description |
Some catalog files are accumulating many lines of comments that are causing the file to have a second 'header' line. FFP thinks it should be looking for another station in the file.
|
| Status |
This will be accounted for in the release version.
Temporary Resolution:- FFP 4.0 has almost all catalogs internal so you may not need to import it. Once you have brought in the weather, the station information will be available.
- The query at FAMWEB/KCFAST has been modified to not include the second header line. You can get a new file via KCFAST and it will load correctly. (This change will not be reflected in the FAMWB Fire and Weather Data files until next year.)
- You can delete the second header line (starts with WLSTINV1) in your existing file with a text editor and the file should load correctly.
|
|
| Fire Reports exported in Text format return the message "ERROR: No associations specified." |
| Description |
Fire Reports exported in Text format from a SIG Association or from Fires->General return the message "ERROR: No associations specified."
|
| Status |
Bug has been fixed for release version.
Workaround: Associate same fires with a single station to export into a text file. Make sure the station has data for at least the same year range as your fires and have data years set to that range. This does not affect exporting to shapefiles. |
|
Fire summary graphs for DOI agencies are missing the 1st word of the Agency Unit Name.
|
| Description |
Wind Cave National Park is displayed as Cave National Park in fire summary graphs.
|
| Status |
Bug has been fixed for release version.
Workaround: The program is trimming the 1st word in the unit name because FFP3 had the unit code as the 1st word in the name. You could use MS Access to modify the FireUnit table to edit the unit name by inserting a word in front of the unit name. (Example, edit "Wind Cave National Park" to "SDWC Wind Cave National Park"). If you do this you would want to remove the SDWC when the release version is available. |
|
|
|
Last Updated ( Wednesday, 20 August 2008 )
|
FireFamilyPlus 
