[McIDAS #RHQ-229966]: Missing (/mis-configured?) SHIPBUOY data files

Hi Kwan,

re:
> Thank you very much for looking into this.  In this case, I will consider
> running a SHIP/BUOY MD file decoder since IA state has the "original" data
> files in text format here
> https://mtarchive.geol.iastate.edu/2019/09/07/text/boy.  

OK.

re:
> Do you know how I might be able to do that?

Hmm... a LONG time ago, we added support for running the METAR decoder
from "historical data".  I can't remember if the same modification was
added for SHIPBUOY data, but I suspect that it was not since there was
no demand for it.  On top of that, at some point, I reverted to using
the SSEC version of the XCD POINT decoders, and I don't think that they
are setup for processing non-real-time data.

What is interesting to me is it seems to me that the SHIPBUOY MD files
we are making available are viable for (at least most of) the time
period you are interested in.  The exception to this is a set of files
that are very small on disk.  Here is the list of "short" files that
I am referring to:

-rw-rw-r--  1 mcidas ustaff     6656 Apr 30  2020 SHIPBUOY_20200429
-rw-rw-r--  1 mcidas ustaff     6656 Apr 20  2020 SHIPBUOY_20200419
-rw-rw-r--  1 mcidas ustaff     6656 Apr 10  2020 SHIPBUOY_20200409
-rw-rw-r--  1 mcidas ustaff     6656 Mar 31  2020 SHIPBUOY_20200330
-rw-rw-r--  1 mcidas ustaff     6656 Mar 21  2020 SHIPBUOY_20200320
-rw-rw-r--  1 mcidas ustaff     6656 Mar 11  2020 SHIPBUOY_20200310
-rw-rw-r--  1 mcidas ustaff     6656 Mar  1  2020 SHIPBUOY_20200229
-rw-rw-r--  1 mcidas ustaff     6656 Feb 20  2020 SHIPBUOY_20200219
-rw-rw-r--  1 mcidas ustaff     6656 Feb 10  2020 SHIPBUOY_20200209
-rw-rw-r--  1 mcidas ustaff     6656 Jan 31  2020 SHIPBUOY_20200130
-rw-rw-r--  1 mcidas ustaff     6656 Jan 21  2020 SHIPBUOY_20200120
-rw-rw-r--  1 mcidas ustaff     6656 Jan 11  2020 SHIPBUOY_20200110
-rw-rw-r--  1 mcidas ustaff     6656 Dec 27  2019 SHIPBUOY_20191226
-rw-rw-r--  1 mcidas ustaff     6656 Dec 17  2019 SHIPBUOY_20191216
-rw-rw-r--  1 mcidas ustaff     6656 Dec  7  2019 SHIPBUOY_20191206
-rw-rw-r--  1 mcidas ustaff     6656 Nov 27  2019 SHIPBUOY_20191126
-rw-rw-r--  1 mcidas ustaff     6656 Nov 17  2019 SHIPBUOY_20191116
-rw-rw-r--  1 mcidas ustaff     6656 Nov  7  2019 SHIPBUOY_20191106
-rw-rw-r--  1 mcidas ustaff     6656 Oct 28  2019 SHIPBUOY_20191027
-rw-rw-r--  1 mcidas ustaff     6656 Oct 18  2019 SHIPBUOY_20191017
-rw-rw-r--  1 mcidas ustaff     6656 Oct  8  2019 SHIPBUOY_20191007
-rw-rw-r--  1 mcidas ustaff     6656 Sep 28  2019 SHIPBUOY_20190927
-rw-rw-r--  1 mcidas ustaff     6656 Sep 18  2019 SHIPBUOY_20190917
-rw-rw-r--  1 mcidas ustaff     6656 Sep  8  2019 SHIPBUOY_20190907
-rw-rw-r--  1 mcidas ustaff     6656 Aug 29  2019 SHIPBUOY_20190828

When I converted the dates in this list to CCYYJJJ (Julian dates),
I see that they are all end in a Julian day of '0':

/home/mcidas/util% date -d 2019/08/28 +%Y%j
2019240
/home/mcidas/util% date -d 2019/09/07 +%Y%j
2019250
/home/mcidas/util% date -d 2019/09/17 +%Y%j
2019260
/home/mcidas/util% date -d 2019/09/27 +%Y%j
2019270
/home/mcidas/util% date -d 2019/10/07 +%Y%j
2019280
/home/mcidas/util% date -d 2019/10/17 +%Y%j
2019290
/home/mcidas/util% date -d 2019/10/27 +%Y%j
2019300
/home/mcidas/util% date -d 2019/11/06 +%Y%j
2019310
/home/mcidas/util% date -d 2019/11/16 +%Y%j
2019320
/home/mcidas/util% date -d 2019/11/26 +%Y%j
2019330
/home/mcidas/util% date -d 2019/12/06 +%Y%j
2019340
/home/mcidas/util% date -d 2019/12/16 +%Y%j
2019350
/home/mcidas/util% date -d 2019/12/26 +%Y%j
2019360
/home/mcidas/util% date -d 2020/02/09 +%Y%j
2020040
/home/mcidas/util% date -d 2020/02/19 +%Y%j
2020050
/home/mcidas/util% date -d 2020/02/29 +%Y%j
2020060
/home/mcidas/util% date -d 2020/03/10 +%Y%j
2020070
/home/mcidas/util% date -d 2020/03/20 +%Y%j
2020080
/home/mcidas/util% date -d 2020/03/30 +%Y%j
2020090
/home/mcidas/util% date -d 2020/04/09 +%Y%j
2020100
/home/mcidas/util% date -d 2020/04/19 +%Y%j
2020110
/home/mcidas/util% date -d 2020/04/29 +%Y%j
2020120

This should mean that they were not properly saved after MD file
rotation.  If this is true, it is something that I need to look
into.

Cheers,

Tom
--
****************************************************************************
Unidata User Support                                    UCAR Unidata Program
(303) 497-8642                                                 P.O. Box 3000
address@hidden                                   Boulder, CO 80307
----------------------------------------------------------------------------
Unidata HomePage                       http://www.unidata.ucar.edu
****************************************************************************


Ticket Details
===================
Ticket ID: RHQ-229966
Department: Support McIDAS
Priority: Normal
Status: Closed
===================
NOTE: All email exchanges with Unidata User Support are recorded in the Unidata 
inquiry tracking system and then made publicly available through the web.  If 
you do not want to have your interactions made available in this way, you must 
let us know in each email you send to us.