Bug/Problem Reporting

When reporting a bug or usage problem in software developed by ACME, use this guide.

Reporting a bug in the ACME model source code

Only bugs found in code on the "master" or "maint" branches should be reported as below.  You will need an ACME github developer account.  See the first 3 steps in Development Quick Guide

1. Create a new issue in https://github.com/ACME-Climate/ACME/issues
2. In the issue title, briefly describe what the bug does.
3. In the body, give more detail on the bug including files involved (if known), the output of "git describe --dirty" and how to reproduce the bug.
4. Using the "Labels" menu, add the "bug" label to the issue.
5. Also add a label for what component the bug appears in (atmosphere, land, ocean, etc.).
6. Using the "Assignee" menu, assign the bug to one of the component integrators.
7. If necessary, work with the integrator to better describe the bug or how to reproduce it.

See also:

• Fixing a bug:  Development Reference#Creatinganewbranch:bugfix
• Making a pull request for bug fix: Development Reference#Submittingapullrequest
• Processing a bug: Integrator Guide#Processingabug
• /wiki/spaces/SE/pages/3997737
  
  

Reporting a bug in UV-CDAT or diagnostic scripts.

1. Create a new issue in https://github.com/UV-CDAT/uvcdat/issues
2. In the issue title, briefly describe the bug or problem.
3. Choose appropriate tags. For ACME project related issues add label ACME to the issue. If you are a lead or a scientist mark the priority as High or Low.
4. In the body, give more detail including how to reproduce the bug.

Reporting a bug in the UVCDAT diagnostics package (uvcmetrics)

Follow the general UV-CDAT reporting procedures, but report issues in https://github.com/UV-CDAT/uvcmetrics/issues

Reporting a bug in the ACME regridder

Follow the general UV-CDAT reporting procedures, but report issues in https://github.com/doutriaux1/regrid/issues

Related articles