[Ncep.list.wwatch3.discussion-group] NetCDF variable names for partitions coming out of ww3_ounf

[Jessica Meixner - NOAA Federal]

Hi Fabrice & everyone -

We are back (for at least three weeks)!

I will just second what Andy said and point you to the issue that we had
for this: https://vlab.ncep.noaa.gov/redmine/issues/55541

And also say that 'c' was chosen because Mickael said that '_' broke his
scripts.   I know we have discussed this on at least one if not multiple of
the discussion group calls.  If we need to set up a call to discuss this
further let me know.

Best,
Jessica



On Wed, Jan 23, 2019 at 4:45 PM Saulter, Andrew <
andrew.saulter at metoffice.gov.uk> wrote:

> Hi Fabrice,
>
> This did get raised via the developers group to see if anyone had any
> complaints, prior to me updating the variable names. There weren't any at
> the time...
>
> If it ain't broken why fix it? For phs it might not be broken, but for
> other variables we've needed to introduce (e.g. pt01, pt02) I'd suggest it
> is - pt010, pt011, pt012 would make no sense to me as a set of component
> names for a t01 variable type.
>
> So it seemed more consistent to add a 'c' for component to all the
> partition variables in order to make sense of this, rather than just
> introduce this into any new variables.
>
> We can, of course revise, should the rest of the group change their minds
> on this and that nice Mr Trump and friends allow people to get back to work
> (I'm slightly agnostic as we are working operationally with stupid CMEMS
> variable names, which are different again).
>
> Cheers
> Andy
>
>
>
> -----Original Message-----
> From: ardhuin <Fabrice.Ardhuin at ifremer.fr>
> Sent: 23 January 2019 16:29
> To: Saulter, Andrew <andrew.saulter at metoffice.gov.uk>
> Cc: Mickael Accensi <mickael.accensi at ifremer.fr>; jessica.meixner at noaa.gov;
> ali.abdolali at noaa.gov; ncep.list.wwatch3.discussion-group at noaa.gov
> Subject: NetCDF variable names for partitions coming out of ww3_ounf
>
> Hi guys,
>
> I know some of you are shut down... I hope it gets solved.
>
> I just found another issue that is easier to solve: somebody (looks like
> it is you Andy) had the idea of changing the names of some variables. In
> some cases that could be defended... but in the case of the partitions ,
> changing 'phs0' for 'phsc0' makes no sense to me.
>
> If it ain't broken why fix it?
>
> We have terabytes of files on our ftp server with partition output ... I
> do not see me renaming this or explaining my users they should have a "if
> file produced before 2019/07/01 then variable=... " in their reading
> routines. OK, there is obviously long_names ... but why make a short name
> less short?
>
> So, I think we should stick to phs0 and all these.
>
> Fabrice
>
> --
>                        Fabrice Ardhuin
> UMR 6523 Univ. Brest-CNRS-IFREMER-IRD, IUEM  http://www.umr-lops.fr/
>            IUEM,  Rue Dumont d'Urville, 29280 Plouzané
>                  Phone: (33) 2 90 91 55 20
> --
> SKIM for EE9: Twitter: #SKIM4EE9     http://tinyurl.com/SKIMonRG
>          https://www.researchgate.net/profile/Fabrice_Ardhuin
>
>
>

-- 
Jessica Meixner
NCEP/EMC
NOAA Center for Weather and Climate Prediction
-------------- next part --------------
An HTML attachment was scrubbed...
URL: https://www.lstsrv.ncep.noaa.gov/pipermail/ncep.list.wwatch3.discussion-group/attachments/20190128/4d734894/attachment.html