<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div>obs_diag is very complicated and difficult to maintain.</div><div>I'd like to simplify it.</div><div><br></div><div>Since we can get the location information from ANY observation sequence (obs_seq.in, obs_seq.out, obs_seq.final) by converting the observation sequences to a netCDF file (with obs_seq_to_netcdf) - I would like to remove the 'plot_locations' functionality from obs_diag.</div><div><br></div><div>How negatively would that impact people?</div><div><br></div><div>Speak up and tell me what you think!</div><div><br></div><div>Long version: If I can require that the [prior/posterior]_ensemble_mean and</div><div>[prior/posterior]_ensemble_spread are present in the file, I can remove a lot</div><div>of the checking. This means only "obs_seq.final" files would be supported in obs_diag.</div><div><br></div><div apple-content-edited="true">
<span class="Apple-style-span" style="border-collapse: separate; color: rgb(0, 0, 0); font-family: Monaco; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; font-size: medium; "><div>Tim Hoar, Associate Scientist</div><div>National Center for Atmospheric Research</div><div><a href="mailto:thoar@ucar.edu">thoar@ucar.edu</a></div><div>303.497.1708</div></span>
</div>
<br></body></html>