 |
 |
|
|
|
|
Bugs /
SubmitNewBugThe first thing to do in submitting a new bug is to make sure it really is a new bug. In particular, you could try searching this website for some keywords. If there are related bugs in the system, you might want to jot down their numbers and include it in your own submission -- this may help the development team to sort out where the bug actually resides. You will be asked for operating system version information, see OpsysInfo for some helpful hints. If you are reporting a bug or program error (as opposed to, e.g., documention issues), then you should include a cut-and-paste copy of your program output (if it is not excessively long), and also the CardioWave module information (see CwaveInfo for some hints). Also, try to copy version information, etc., from a run of the code. You can also tag your submission with a "SeverityLevel": ProgramCrashes, NumericalError, CompileError, LinkError. Optionally, you can use the IEEE classifications: ProactiveCorrection, ProactiveEnhancement, ReactiveCorrection, ReactiveEnhancement. If you have done a search and still cannot solve the issue, then feel free to submit a new bug to the system. If you know of related pages or bugs, you can include links to them by simply typing the WikiWord that references the related page. For references to other sections, precede the page name with the section name and a period: User.OutputText would link to the User documentation, Code.OutputText? would link to the code. To link directly to other bugs, you must use the format "[[Bugs.00001]]" which will show up as Bugs.00001. CLICK HERE to submit a new bug |