NCL and NCAR Graphics email lists
Please read these posting guidelines before posting to these email lists.
- ncl-install@ucar.edu
(subscribe/unsubscribe)
[archives]
For questions on installing, porting, or building NCL, or setting up your environment to run NCL. - ncl-talk@ucar.edu
(subscribe/unsubscribe)
[archives]
For users to exchange information, ask questions, and report bugs pertaining to NCL. Also for developers to share information about new releases, features, bug fixes, and other related information. - ncarg-talk@ucar.edu
(subscribe/unsubscribe)
[archives]
For users to exchange information, ask questions, and report bugs pertaining to NCAR Graphics only. Also for developers to share information about new releases, features, bug fixes, and other related information.
The NCL/NCARG team monitors all mailing lists, and we generally try to answer questions within a few hours. We encourage the community to pitch in with answers. Sometimes we will respond to a person offline, so if you don't see an answer right away, this doesn't necessarily mean we aren't looking into it. We will eventually post the resolution when we have all the information, and if it is appropriate.
To unsubscribe to either list, click on the above "unsubscribe" and your the exact email address that you subscribed with, next to the box that says "Edit options", and then click on the button. Then, follow the instructions for unsubscribing to the list.
Sending and replying to messages email lists
To send a message to any of these lists, use the appropriate email address: ncl-talk@ucar.edu, ncl-install@ucar.edu, or ncarg-talk@ucar.edu. If you would like to answer a question posted to a list, we ask that you send it to the whole list so that other people can benefit from the answer as well.Read these posting guidelines before posting to these email lists.
Submitting a bug report
To report an NCL bug, email ncl-talk@ucar.edu and provide:- The version of NCL you are running (ncl -V).
- The shortest NCL script possible that illustrates the bug.
- Any data files needed to run your script.
- A graphic (PostScript file, PDF file, NCGM file, etc.) that illustrates the problem.
- The exact error message (if any).
- The type of system you're on (usually "uname -a" is enough).