CANSARP Problem Reporting Form Help

Contact Fields: The JRCC/MRSC, name, email address and phone number fields allow them to contact the reporter for futher information and to provide feedback as to the issue's resolution.
Program Fields: Version helps to isolate when the issue arose and to determine whether it might have been resolved previously. The case number and scenario name fields give programmers the information required to locate a problematic scenario and open it themselves to investigate an isssue further.

Note: None of the contact fields or program fields are required.

Back to Problem Report Form

Nature of Defect Menu - indicates what type of issue is being documented.

PROGRAM BUG: An error that causes the program to behave incorrectly. E.g. buttons that don't work properly, data or values that change unexpectedly, windows that close when they shouldn't or don't when they should. NB: If the bug causes the program to crash, please include the word CRASHER in your detailed description.
IMPLEMENTATION ERROR: An error in the implementation of SAR theory or search planning practice, or something that makes it difficult to follow correct SAR procedure. E.g. incorrect default values, missing search object or SRU types.
DOCUMENTATION: An error or omission in the documentation, including user manual and help system within the program. E.g. undefined terms that should appear in the glossary, incomplete or incorrect instructions, tips that should appear in status bar.

Back to Problem Report Form

Severity Menu - indicates how urgently a resolution is required.

EMERGENCY: Affecting a live SAR case, fix immediately.
URGENT: Extremely important, fix as quickly as possible.
ROUTINE: Fix with routine priority.

Back to Problem Report Form

Program Component Menu - indicates what part of the program the issue is related to. If more than one category applies, choose the one most directly related to the problem, or any applicable category. If no categories apply, use the "Other" option.

MENUS / INFO OR TOOL BARS / SIDEBARS: Any item on a menu (File, View, Managers, Help) or submenu that extends from one of these; any of the info or tool bars (Title bar, Manager bar, Tool bar, Status bar) apart from the VMS tool bar; any of the sidebars (Display Options, Current Forces, Wind forces); anything that's accessed via a menu or tool bar rather than a manager (e.g. Autosave, ruler tools).
WIZARD: Anything related to the Wizard.
SCENARIO MANAGER: Anything related to the Scenario Manager, including file management (top half) and scenario parameters (bottom half).
SEARCH OBJECTS / SEARCH OBJECT MANAGER: Anything to do with search objects or the Search Object Manager that isn't specifically related to track lines.
TRACK LINES / TRACKLINE MANAGER: Anything related to track lines, to the Trackline Manager or to its interaction with the Search Object Manager.
WIND DATA / WIND MANAGER: Anything related to wind data apart from opening or editing time series, including CMC winds and user entered winds (subjective winds); anything related to turning wind data on and off in drifts; anything connected to the Wind Manager.
CURRENT DATA / CURRENT MANAGER: Anything related to current data apart from apart from opening or editing time series or SLDMBs, including static data models (Tidal and Sea), dynamic models (IML and Grand Banks) and user entered currents (measured and subjective); anything related to turning current data on or off in drifts; anything connected to the Current Manager apart from the SLDMB tab and its dependent windows.
SLDMBS: Anything related to SLDMBs or SLDMB data; anything related to the SLDMB tab of the Current Manager.
TIME SERIES EDITOR: Anything related to the Time Series Editor or to opening, reading or modifying environmental data of any kind in the Time Series Editor.
SRUS / SRU MANAGER: Anything related to SRUs or the SRU Manager that isn't related to search patterns or the Transit Editor, including SRU tasking and the SRU Database.
SEARCH PATTERN EDITOR: Anything related to search patterns, including Probability of Detection.
TRANSIT EDITOR: Anything related to the Transit Editor.
MARKERS / MARKERS MANAGER: Anything related to markers or the Markers Manager.
SEARCH POLYGON / POLYGON MANAGER: Anything related to manipulating the search polygon; anything related to the Polygon Manager.
MARINE CHARTS / CHART MANAGER: Anything related to marine charts or the Chart Manager.
VMS MANAGER: Anything related to the VMS, including the VMS database and the VMS tool bar.
NOTES EDITOR / LOG MANAGER: Anything related to the Notes Editor; anything related to the Log Manager, including actions that should be logged but are not currently.
PRINTING / REPORTS MANAGER: Anything related to printing or to the Reports Manager.
TRANSLATION / LANGUAGE: French translation issues; incorrect terminology; typos or strange characters appearing in widget labels.
OTHER: Anything not covered by another category above, including the Problem Report Form itself and other online resources.

Back to Problem Report Form

Detailed Description

Enter a description of the bug that occurred or the issue of concern. The most important thing is that the problem be reported so all that is strictly required is a sentence or two describing it - if you are pressed for time just fill in whatever you can and hit the Send button.

If you have time to provide more detail and are reporting a program bug, especially one that causes the program to crash or one that only happens intermittently, please explain what you think might have triggered the problem and give as much detail as you can about what you were doing when the problem occured. See the Bug Description Check List for a list of questions to address.

If you are interested in investigating the problem further and have some time to devote to the exercise, please see the Guide to Problem Reporting for suggestions on how to reproduce the bug and isolate the underlying cause. Your extra effort could help speed up fixing the bug considerably and is very much appreciated!

If you are requesting an enhancement or a new feature, please explain how the change will improve the performance or utility of the software. This will help us to prioritize requests.

Back to Problem Report Form