Debug Team Procedures

New Tickets

• When a new ticket arrives, the debug team leader will assign a debug team member to the ticket.
• 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.
• The debug team member should then try to isolate the source of the problem by:
  • Running with debug flags turned on (and fixing any pointer/allocation issues)
  • If no errors turn up then they should
    • Lower the resolution.
    • Turn off AMR (i.e., set MaxLevel in global.data to 0).
    • Turn off source terms.
    • Set {lGudonov to true.
    • Set InterpOpts to 0 in physics.data.
    • Use a different problem module.
  • Once the problem goes away, then try switching back on things that had been turned off until you have the closest thing to the original setup that still works.
• Prepare a report (summary comment on the ticket) for weekly debug meetings describing the results with possible courses of action.