| 4 | | * When a new ticket arrives, the debug team leader will assign a debug team member to the ticket. |
| 5 | | * The debug team member should establish contact with the reporter and work with them to make sure that their environment settings/compile flags/submission scripts look ok and that they are using the most current version of the code. If everything looks ok then they should obtain the necessary info to reproduce the error themselves. |
| 6 | | * The debug team member should then try to isolate the source of the problem by: |
| 7 | | * Running with debug flags turned on (and fixing any pointer/allocation issues) |
| 8 | | * If no errors turn up then they should |
| | 4 | 1. ''Assignment:'' When a new ticket arrives, the debug team leader will assign a debug team member (owner) to the ticket. |
| | 5 | |
| | 6 | 2. ''Triage:'' The ticket owner should establish contact with the reporter and verify: |
| | 7 | * That their environment settings, compiler flags, and submission scripts are correct. |
| | 8 | * They are using the most current version of the code. |
| | 9 | |
| | 10 | 3. ''Reproduction:'' The ticket owner should work with the reporter to reproduce the bug. This will involve access to some or all of the following: |
| | 11 | * The reporter's data files. |
| | 12 | * The reporter's AstroBEAR build. |
| | 13 | * The cluster on which the error occurred. |
| | 14 | * The PBS script used to submit the job. |
| | 15 | * The reporter's {{{.bashrc}}} and {{{.bash_profile}}} contents. |
| | 16 | |
| | 17 | 4. ''Isolation:'' The debug team member should then try to isolate the source of the problem by: |
| | 18 | * Running with debug flags turned on (and fixing any pointer/allocation issues). |
| | 19 | * If no errors turn up then they should try the following: |
