NCL and NCAR Graphics email listsPlease read these posting guidelines before posting to these email lists.
(07/2014 - present)|
(07/2014 - present)|
|This list is for NCL users to exchange information, ask questions, and report bugs pertaining to NCL. Developers use it to share information about new releases, features, bug fixes, training, and other related information.||This list is for questions on installing, porting, or building NCL, or setting up your environment to run NCL.||This list is for users to exchange information, ask questions, and report bugs pertaining to NCAR Graphics only.|
|Note: subscription requests have to be approved by an NCL developer. This is to avoid spammers getting in. We usually try to approve requests right away, but if you subscribe over the weekend or at night time, it may take several hours before we can approve it.|
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 listsTo send a message to any of these lists, use the appropriate email address: email@example.com, firstname.lastname@example.org, or email@example.com. 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 reportTo report an NCL bug, email firstname.lastname@example.org 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 ("uname -a", "gcc --version", what flavor/version of Linux/MacOS, etc)
You cannot not attach large files (> 1.5 megabytes) to an ncl-talk email, so if you can put your script, data, and/or images on a website and then just provide a URL, that would be ideal. Ftp also works for us. You can use our our ftp account if needed.