<div dir="ltr"><div><div><div><div>Arun and All,<br><br></div>Despite being a community model, the WW3 code package is by copyright property of the US National Weather Service/NOAA (eg, see licensing terms, and headers in all parts of the code itself). Therefore, it would make more sense if the authorship of the manual is attributed to the US National Weather Service/NOAA. This would fall into the APA citation style knows as "corporate authorship" (<a href="http://libguides.tru.ca/c.php?g=194005&p=1418555">http://libguides.tru.ca/c.php?g=194005&p=1418555</a>). There are a few different ways to go about that. One is to simply state in the manual that reference should be made in the form:<br><br><span><span style="font-size:10pt;font-family:"arial","sans-serif""><span style="color:black">US National Weather Service, NOAA, 2016: User
manual and system documentation of WAVEWATCH III® version 5.16. Tech.
Note 329, NOAA/NWS/NCEP/MMAB, College Park, MD, USA, 326 pp. +
Appendices.</span></span></span><br><br></div><div>And a list of collaborators, as well as the project lead, would be provided within the manual. This would be in line with the idea of using "<span><span style="font-size:10pt;font-family:"arial","sans-serif""><span style="color:black">The WAVEWATCH III® Development Group (WW3DG)", except that the latter does not formally exist, and would have to be formalized somehow within NOAA. If this is the case, the citation would be:<br></span></span></span><br><span><span style="font-size:10pt;font-family:"arial","sans-serif""><span style="color:black">The WAVEWATCH III® Development Group (WW3DG)</span></span></span><span><span style="font-size:10pt;font-family:"arial","sans-serif""><span style="color:black">, 2016: User
manual and system documentation of WAVEWATCH III® version 5.16. </span></span></span><span><span style="font-size:10pt;font-family:"arial","sans-serif""><span style="color:black"><span><span style="font-size:10pt;font-family:"arial","sans-serif""><span style="color:black">NCEP/MMAB </span></span></span>Tech.
Note 329, </span></span></span><span><span style="font-size:10pt;font-family:"arial","sans-serif""><span style="color:black"><span><span style="font-size:10pt;font-family:"arial","sans-serif""><span style="color:black">US National Weather Service, NOAA</span></span></span>, College Park, MD, USA, 326 pp. +
Appendices.</span></span></span></div><div><br></div><div>A form adopted by several organizations for this type of report/manual, including ECMWF, UNESCO etc, would be consistent with the above, but in the line with what Alex suggested, whereby the group lead (eg, the person who would be held accountable/responsible for the development effort) appears as the corresponding author, and a list of collaborators is provided within the report (as done now), thus:<br><br></div><div>Chawla, A., <span><span style="font-size:10pt;font-family:"arial","sans-serif""><span style="color:black">US National Weather Service, NOAA, 2016: User
manual and system documentation of WAVEWATCH III® version 5.16. NCEP/MMAB Tech.
Note 329, College Park, MD, USA, 326 pp. +
Appendices.</span></span></span><br></div><br></div>The corresponding author would change reflecting the person at NOAA who could be held responsible/accountable for the development work referring to that report. <br><br></div>Finally, another option for authorship that we discussed in a WW3 meeting a couple of years ago, was to establish a steering committee representative of the main groups involved in the development effort. This steering committee would somehow be formalized within NOAA, composed of a smaller number of leads. Authorship in this case would be attributed to the steering committee (such as what was done in a couple of NOPP papers recently), and additional collaborators would be acknowledge inside the report (as seen now). This would lead to:<br><br><div>Chawla, A., Aname, A., Bname, B., Cname, C.,<span><span style="font-size:10pt;font-family:"arial","sans-serif""><span style="color:black"> 2016: User
manual and system documentation of WAVEWATCH III® version 5.16. </span></span></span><span><span style="font-size:10pt;font-family:"arial","sans-serif""><span style="color:black"></span></span></span><span><span style="font-size:10pt;font-family:"arial","sans-serif""><span style="color:black"><span><span style="font-size:10pt;font-family:"arial","sans-serif""><span style="color:black">NCEP/MMAB </span></span></span>Tech.
Note 329, </span></span></span><span><span style="font-size:10pt;font-family:"arial","sans-serif""><span style="color:black"><span><span style="font-size:10pt;font-family:"arial","sans-serif""><span style="color:black">US National Weather Service, NOAA</span></span></span>, College Park, MD, USA, 326 pp. +
Appendices.</span></span></span></div><br><div><div>with as many co-authors as steering group members. Changes in steering group members, as also the case for the WW3 project lead, would be documented at NOAA and reflected in the authorship of subsequent manuals/reports.<br><br></div><div>Cheers<br><br></div><div>Henrique<br><div class="gmail_extra"><br clear="all"><div><div class="gmail-m_-8276686003962299173gmail_signature"><div dir="ltr"><div><div dir="ltr"><div>--<br>*Dr Jose-Henrique Alves<br><br>SRG Technical Lead at EMC/NCEP/NOAA<br>NOAA Center for Weather and Climate Prediction<br>5830 University Research Court<br>College Park, Maryland 20740, USA<br>Phone: <a href="tel:%28301%29%20683-3762" value="+13016833762" target="_blank">(301) 683-3762</a>*<br><br><br></div></div></div></div></div></div>
<br><div class="gmail_quote">On Thu, Nov 17, 2016 at 9:12 AM, Arun Chawla - NOAA Federal <span dir="ltr"><<a href="mailto:arun.chawla@noaa.gov" target="_blank">arun.chawla@noaa.gov</a>></span> wrote:<br><blockquote style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex" class="gmail_quote"><div dir="ltr"><div><div><div><div><div><div>Thanks Jianguo<br><br></div>You bring up important points. Jessica was speaking for me so let me elaborate my preference for the Group name further<br><br></div>a) The first name, and hence ownership issue becomes central. This to me is an anathema to community model development. If there has to be a first author right now Hendrik is the obvious choice. But what happens in a few years ? There will come a time (and I am hoping for it) when code development is diversified enough that no single group / person could take the mantle of major developer. In fact that is already the case with v 5.16<br><br></div>b) While the list of authors at near 40 is still manageable, the contributor list is only expected to grow and I hope exponentially. At what time do we say this is too many names to put on a citation ? <br><br></div>c) Alex and others have brought out the example of the WISE Group paper that is referred to as Cavelieri et al as opposed to the WISE paper as Luigi initially intended. Fair enough. However, the difference between the WW3 manual and these other seminal papers is that the former is expected to be a regular release (once every 2 years, earlier if we have many contributions)<br><br></div>I am not trying to deny the importance of ownership and being cited. These things are important to me as well. And I am well aware of how citations can make careers, specially for younger scientists. I am not sure we need to do that for a regularly released manual. <br><br>Again my aim to move towards a development group framework is to make all feel as owners of this code and take pride in the contributions. However, if the anonymity of group name based referencing has the opposite intent and people feel less inclined to be part of the development group then that defeats the purpose. I will be more than happy to comply with what ever the group decides. <br><br> <br></div></div><div class="gmail_extra"><br clear="all"><div><div class="gmail-m_-8276686003962299173gmail-m_-3170462529933025722gmail_signature"><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><div><div>------------------------------<wbr>------------------------------<wbr>---<br>Arun Chawla <wbr> <wbr> <br></div>Chief<br></div>Marine Modelling & Analysis Branch <wbr> <br><div><div>Room 2109<br>National Center for Weather & Climate Prediction<br>5830 University Research Court<br>College Park, MD 20740<br>Ph: <a value="+13016833740" href="tel:301-683-3740" target="_blank">301-683-3740</a><br>Fx: <a value="+13016833703" href="tel:301-683-3703" target="_blank">301-683-3703</a><br>------------------------------<wbr>------------------------------<br><br></div></div></div></div></div></div></div></div></div></div></div>
<br><div class="gmail_quote">On Thu, Nov 17, 2016 at 7:09 AM, Li, JianGuo <span dir="ltr"><<a href="mailto:jian-guo.li@metoffice.gov.uk" target="_blank">jian-guo.li@metoffice.gov.uk</a>></span> wrote:<br><blockquote style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex" class="gmail_quote">
<div lang="EN-GB">
<div class="gmail-m_-8276686003962299173gmail-m_-3170462529933025722m_-6901046615199597492WordSection1">
<p class="MsoNormal"><span style="font-size:11pt;font-family:"calibri","sans-serif"">All</span></p>
<p class="MsoNormal"><span style="font-size:11pt;font-family:"calibri","sans-serif""> </span></p>
<p class="MsoNormal"><span style="font-size:11pt;font-family:"calibri","sans-serif"">I appreciate Jessica’s work to manage such a large development group and get the public release out in time but I could not agree with Jessica on that “</span><span style="font-size:9.5pt;font-family:"arial","sans-serif"">it
would be unrealistic to keep up the continually growing list of names in so many different places (first page, Section 1.4, bibtex entries in multiple places, etc etc.)” </span></p>
<p class="MsoNormal"><span style="font-size:9.5pt;font-family:"arial","sans-serif""> </span></p>
<p class="MsoNormal"><span style="font-size:9.5pt;font-family:"arial","sans-serif"">Most of those people have spent years developing this model. It took them ages to code it and validate it before we get to the present state of the model. Comparing with their
hard work, compiling a full list of them on one page of the manual is trivial, extremely trivial. I have extracted the full list from the manual in 5 minutes by just copy and paste plus some minor editing (see the attachment).</span></p>
<p class="MsoNormal"><span style="font-size:9.5pt;font-family:"arial","sans-serif""> </span></p>
<p class="MsoNormal"><span style="font-size:9.5pt;font-family:"arial","sans-serif"">Putting the author list right is showing the basic respect to those people who have contributed to the model development. This is the only way to formally recognise people’s
contributions in today’s scientific world. First author is a honour to the main contributor and I agree with Arun at that Hendrik is the undisputable first author of this model. Although this manual is not a formal publication, it is used as a reference
to the model. So we should treat it as a formal scientific paper/book.</span></p>
<p class="MsoNormal"><span style="font-size:9.5pt;font-family:"arial","sans-serif""> </span></p>
<p class="MsoNormal"><span style="font-size:9.5pt;font-family:"arial","sans-serif"">It is acceptable the others quote this manual as Tolman et al … but it is not appropriate for us to do that at the very original place. Two similar papers for the WAM and WISE
groups have provided the full author list right after the group name. We could follow the examples if you prefer a development group name.</span></p>
<p class="MsoNormal"><span style="font-size:9.5pt;font-family:"arial","sans-serif""> </span></p>
<p class="MsoNormal"><span style="font-size:9.5pt;font-family:"arial","sans-serif"">This is my opinion and I am exercising my democracy right.</span></p>
<p class="MsoNormal"><span style="font-size:9.5pt;font-family:"arial","sans-serif""> </span></p>
<p class="MsoNormal"><span style="font-size:9.5pt;font-family:"arial","sans-serif"">Kind regards.</span></p>
<p class="MsoNormal"><span style="font-size:9.5pt;font-family:"arial","sans-serif"">Jian-Guo</span></p>
<p class="MsoNormal"><span style="font-size:11pt;font-family:"calibri","sans-serif""> </span></p>
<div style="border-width:1pt medium medium;border-style:solid none none;border-color:rgb(181,196,223) -moz-use-text-color -moz-use-text-color;padding:3pt 0cm 0cm">
<p class="MsoNormal"><b><span style="font-size:10pt;font-family:"tahoma","sans-serif"" lang="EN-US">From:</span></b><span style="font-size:10pt;font-family:"tahoma","sans-serif"" lang="EN-US"> <a href="mailto:ncep.list.wwatch3.discussion-group-bounces@lstsrv.ncep.noaa.gov" target="_blank">ncep.list.wwatch3.discussion-g<wbr>roup-bounces@lstsrv.ncep.noaa.<wbr>gov</a>
[mailto:<a href="mailto:ncep.list.wwatch3.discussion-group-bounces@lstsrv.ncep.noaa.gov" target="_blank">ncep.list.wwatch3.disc<wbr>ussion-group-bounces@lstsrv.nc<wbr>ep.noaa.gov</a>] <b>On Behalf Of
</b>Jessica Meixner - NOAA Affiliate<br>
<b>Sent:</b> 17 November 2016 03:12<br>
<b>To:</b> <a href="mailto:ncep.list.wwatch3.discussion-group@lstsrv.ncep.noaa.gov" target="_blank">ncep.list.wwatch3.discussion-g<wbr>roup@lstsrv.ncep.noaa.gov</a><br>
<b>Subject:</b> [Ncep.list.wwatch3.discussion-<wbr>group] WWIII Developer Meeting Minutes -- Wed Nov 16 (IMPORTANT info inside)</span></p>
</div>
<p class="MsoNormal"> </p>
<div><span>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<p style="margin-bottom:12pt" class="MsoNormal"><span style="font-size:10pt;font-family:"arial","sans-serif"">Hi Everyone, </span><span style="font-size:9.5pt"></span></p>
</div>
<p style="margin-bottom:12pt" class="MsoNormal"><b><span style="font-size:10pt;font-family:"arial","sans-serif"">IMPORTANT: LAST CALL FOR UPDATES TO SECTION 1.4 OF THE MANUAL BY FRIDAY</span></b><span style="font-size:10pt;font-family:"arial","sans-serif"">.
Please go through and confirm that your contributions are correct and accounted for. For quick reference see <a href="http://polar.ncep.noaa.gov/waves/wavewatch/manual.v5.16.pdf" target="_blank">http://polar.ncep.noaa.gov<wbr>/waves/wavewatch/manual.v5.16.<wbr>pdf</a>
You can either put your updates directly into the doc_edits branch or email them to me. </span><span style="font-size:9.5pt"></span></p>
</div>
<p style="margin-bottom:12pt" class="MsoNormal"><b><span style="font-size:10pt;font-family:"arial","sans-serif"">OPTIONS for citing manual</span></b><span style="font-size:10pt;font-family:"arial","sans-serif"">: </span><span style="font-size:9.5pt"></span></p>
</div>
<p style="margin-bottom:12pt" class="MsoNormal"><u><span style="font-size:10pt;font-family:"arial","sans-serif"">Option 1</span></u><span style="font-size:10pt;font-family:"arial","sans-serif"">: <br>
<span style="color:black">The WAVEWATCH III® Development Group (WW3DG), 2016: User manual and system documentation of WAVEWATCH III® version 5.16. Tech. Note 329, NOAA/NWS/NCEP/MMAB, College Park, MD, USA, 326 pp. + Appendices. </span></span><span style="font-size:9.5pt"></span></p>
</div>
<p class="MsoNormal"><span style="font-size:10pt;font-family:"arial","sans-serif";color:black">--- The reasons for this option is to emphasize that WAVEWATCH III is now a community code and solves this issue for future issues as well. A further example for
support of this is Linux for example no longer is citing Linus. </span><span style="font-size:9.5pt"></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:9.5pt"> </span></p>
</div>
<p style="margin-bottom:12pt" class="MsoNormal"><u><span style="font-size:10pt;font-family:"arial","sans-serif";color:black">Option 2</span></u><span style="font-size:10pt;font-family:"arial","sans-serif";color:black">: </span><span style="font-size:10pt;font-family:"arial","sans-serif""><br>
<span style="color:black">Tolman, H.L. and The WAVEWATCH III® Development Group (WW3DG), 2016: User manual and system documentation of WAVEWATCH III® version 5.16. Tech. Note 329, NOAA/NWS/NCEP/MMAB, College Park, MD, USA, 326 pp. + Appendices.</span></span><span style="font-size:9.5pt"></span></p>
</div>
<p style="margin-bottom:12pt" class="MsoNormal"><span style="font-size:9.5pt;font-family:"arial","sans-serif";color:black">-- This option would give a person for the first author, which helps some of the concerns when citing on certain websites/publishers
which might force a "human" and keeps the Development Group to emphasize the community. An open </span><span style="font-family:"arial","sans-serif";color:black">question</span><span style="font-size:9.5pt;font-family:"arial","sans-serif";color:black"> is
if a fake human "WW3DG" could be entered in these places, making this potentially unnecessary. </span><br>
<br>
<u><span style="font-size:9.5pt;font-family:"arial","sans-serif";color:black">Option 3</span></u><span style="font-size:9.5pt;font-family:"arial","sans-serif";color:black">: </span><br>
<span style="font-size:9.5pt;font-family:"arial","sans-serif";color:black">Tolman, H.L., et al., 2016: User manual and system documentation of WAVEWATCH III® version 5.16. Tech. Note 329, NOAA/NWS/NCEP/MMAB, College Park, MD, USA, 326 pp. + Appendices.</span><br>
<br>
<span style="font-size:9.5pt;font-family:"arial","sans-serif";color:black">- There are some that have a desire to have a full list of authors, which realistically would be shorted to Tolman et al by most if not all websites/publishers/people. Also it would
be unrealistic to keep up the continually growing list of names in so many different places (first page, Section 1.4, bibtex entries in multiple places, etc etc.) So we would probably just say Tolman et al with the list authors still being maintained only
in Section 1.4 and any individuals who wish to list the whole list other places. </span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10pt;font-family:"arial","sans-serif";color:black">The only consensus we had on the call was that if there is a person first, Tolman would be that author, and to take this discussion off-line. I would venture to
say option 1 is fine with the majority and option 2 if a person for first author is a must, but I could be wrong and this is a democracy, so feel free to voice other opinions. A choice one way or another will be made by Friday. </span><span style="font-size:9.5pt"></span></p>
</div>
</div>
<p class="MsoNormal"> </p>
</div>
<p class="MsoNormal"><span style="font-size:10pt;font-family:"arial","sans-serif";color:black">Other manual updates will include a "Please refer as" on the front page with the agreed upon citation. We will also provide a text file with the bibtex reference
of the manual as a cheat sheet so anyone who downloads the code will have an easy reference. We will also update Section 1.4's heading with "The WAVEWATCH III Development Group". </span></p>
</span><div><span>
<div>
<p class="MsoNormal"><span style="font-size:9.5pt"> </span></p>
</div>
<div>
<p style="margin-bottom:12pt" class="MsoNormal"><b><span style="font-size:10pt;font-family:"arial","sans-serif";color:black">OTHER MEETING NOTES: </span></b><span style="font-size:9.5pt"></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10pt;font-family:"arial","sans-serif";color:black">The items missed from version 5, which now seem to be the priorities for version 6: </span><span style="font-size:9.5pt"></span></p>
</div>
<div>
<p style="margin-left:47.25pt" class="MsoNormal">
<span style="font-size:10pt;font-family:symbol"><span>·<span style="font:7pt "times new roman"">
</span></span></span><span style="font-size:10pt;font-family:"arial","sans-serif"">implicit integration </span><span style="font-size:9.5pt"></span></p>
<p style="margin-left:47.25pt" class="MsoNormal">
<span style="font-size:10pt;font-family:symbol"><span>·<span style="font:7pt "times new roman"">
</span></span></span><span style="font-size:10pt;font-family:"arial","sans-serif"">namelist for input files </span><span style="font-size:9.5pt"></span></p>
<p style="margin-left:47.25pt" class="MsoNormal">
<span style="font-size:10pt;font-family:symbol"><span>·<span style="font:7pt "times new roman"">
</span></span></span><span style="font-size:10pt;font-family:"arial","sans-serif"">breaking probabilities </span><span style="font-size:9.5pt"></span></p>
<p style="margin-left:47.25pt" class="MsoNormal">
<span style="font-size:10pt;font-family:symbol"><span>·<span style="font:7pt "times new roman"">
</span></span></span><span style="font-size:10pt;font-family:"arial","sans-serif"">ESMF interface </span><span style="font-size:9.5pt"></span></p>
<p style="margin-bottom:12pt" class="MsoNormal"><span style="font-size:10pt;font-family:"arial","sans-serif"">There are many other milestones and plans for version 6, that are on the wiki page. Please add your milestones that are not included and details
for the ones that are. Also, please add tickets for bugs that you have found, so we can all keep track of issues together. For example, if you have details on the memory footprint issues or NC4 issues you have encountered put them in a ticket. </span><span style="font-size:9.5pt"></span></p>
</div>
<div>
<p style="margin-bottom:12pt" class="MsoNormal"><span style="font-size:10pt;font-family:"arial","sans-serif"">Fabrice, at NCEP our only "forum" is the wiki we currently have. If you would like to create any other forums, feel free. </span><span style="font-size:9.5pt"></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10pt;font-family:"arial","sans-serif"">Something that got left out of the meeting is that the trunk will be updated to version 6.00 after the updated manual goes out. I will send out an email update when that happens.</span><span style="font-size:9.5pt"></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:9.5pt"> </span></p>
</div>
<div>
<p class="MsoNormal"><b><span style="font-size:10pt;font-family:"arial","sans-serif"">REMINDERS:</span></b><span style="font-size:10pt;font-family:"arial","sans-serif""> </span><span style="font-size:9.5pt"></span></p>
</div>
</span><div>
<p style="margin-left:47.25pt" class="MsoNormal">
<span style="font-size:9.5pt"><span>1.<span style="font:7pt "times new roman"">
</span></span></span><span style="font-size:10pt;font-family:"arial","sans-serif"">Check section 1.4 for your contribution by Friday.</span><span style="font-size:9.5pt"></span></p>
<p style="margin-left:47.25pt" class="MsoNormal">
<span style="font-size:9.5pt"><span>2.<span style="font:7pt "times new roman"">
</span></span></span><span style="font-size:10pt;font-family:"arial","sans-serif"">Voice your opinion on citation of manual by Friday. </span><span style="font-size:9.5pt"></span></p>
<p style="margin-left:47.25pt" class="MsoNormal">
<span style="font-size:9.5pt"><span>3.<span style="font:7pt "times new roman"">
</span></span></span><span style="font-size:10pt;font-family:"arial","sans-serif"">Add/update milestones/tickets on the wiki page.</span><span style="font-size:9.5pt"></span></p>
<p style="margin-left:47.25pt" class="MsoNormal">
<span style="font-size:9.5pt"><span>4.<span style="font:7pt "times new roman"">
</span></span></span><span style="font-size:10pt;font-family:"arial","sans-serif"">Monthly calls are every third Wednesday at 10:30am EDT (Next one being Wednesday, December 21st). Let me know if you have anything you would like to present at this
or future group calls. </span><span style="font-size:9.5pt"></span></p>
</div><span>
<div>
<p style="margin-bottom:12pt" class="MsoNormal"><span style="font-size:10pt;font-family:"arial","sans-serif"">As always please let me know if you have any questions. </span><span style="font-size:9.5pt"></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10pt;font-family:"arial","sans-serif"">Best, </span><span style="font-size:9.5pt"></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10pt;font-family:"arial","sans-serif"">Jessica</span><span style="font-size:9.5pt"></span></p>
</div>
</span></div><span>
<div>
<p class="MsoNormal"> </p>
</div>
<p class="MsoNormal">-- </p>
<div>
<div>
<div>
<div>
<p class="MsoNormal">Jessica Meixner</p>
<div>
<p class="MsoNormal">IMSG Support Scientist </p>
</div>
<div>
<p class="MsoNormal">NCEP/EMC Marine Modeling and Analysis Branch </p>
</div>
<div>
<p class="MsoNormal">NOAA Center for Weather and Climate Prediction </p>
</div>
</div>
</div>
</div>
</div>
</span></div>
</div>
</div>
<br>______________________________<wbr>_________________<br>
Ncep.list.wwatch3.discussion-g<wbr>roup mailing list<br>
<a href="mailto:Ncep.list.wwatch3.discussion-group@lstsrv.ncep.noaa.gov" target="_blank">Ncep.list.wwatch3.discussion-g<wbr>roup@lstsrv.ncep.noaa.gov</a><br>
<a rel="noreferrer" href="https://www.lstsrv.ncep.noaa.gov/mailman/listinfo/ncep.list.wwatch3.discussion-group" target="_blank">https://www.lstsrv.ncep.noaa.g<wbr>ov/mailman/listinfo/ncep.list.<wbr>wwatch3.discussion-group</a><br>
<br></blockquote></div><br></div>
<br>______________________________<wbr>_________________<br>
Ncep.list.wwatch3.discussion-g<wbr>roup mailing list<br>
<a href="mailto:Ncep.list.wwatch3.discussion-group@lstsrv.ncep.noaa.gov" target="_blank">Ncep.list.wwatch3.discussion-g<wbr>roup@lstsrv.ncep.noaa.gov</a><br>
<a rel="noreferrer" href="https://www.lstsrv.ncep.noaa.gov/mailman/listinfo/ncep.list.wwatch3.discussion-group" target="_blank">https://www.lstsrv.ncep.noaa.g<wbr>ov/mailman/listinfo/ncep.list.<wbr>wwatch3.discussion-group</a><br>
<br></blockquote></div><br></div></div></div></div>