New GOFS 3.1 Data - 48 hour delay

[Michael McDonald]

There is currently an upgrade being performed at the Navy that is
impacting our ability to acquire new HYCOM data. The outage should
last for about 48 hours and then we will be catching up where things
left off and (re)automating our data acquisition processes. We will
follow up with this thread once the data is flowing again.

--
Michael McDonald
HYCOM.org Administrator

[Michael McDonald]

Parker,
You will need to be more specific. Which FMRC are having difficulty
with (full access URLs are required)?

>
> Thanks for the note. I noticed that starting around March 4 my daily FMRC extraction failed. I was able to run my code by hand successfully yesterday, but today am having trouble connecting to the server.
>

[Michael McDonald]

Sorry, Parker, but I have been very clear about this in the forum/welcome/faqs,

* Do not subset more than 1 day at a time using ncss.hycom.org

https://groups.google.com/a/hycom.org/forum/#!forum/forum

one time at a time via NCSS (iterate/loop over your time range).

https://ncss.hycom.org/thredds/ncss/GLBy0.08/expt_93.0/FMRC/GLBy0.08_930_FMRC_best.ncd?var=surf_el,water_temp,salinity,water_u,water_v&north=53&south=39&west=229&east=239&time=2020-03-11-T00:00:00Z&addLatLon=true&accept=netcdf4




On Fri, Mar 13, 2020 at 7:02 PM <p.mac...@gmail.com> wrote:
>
> Michael, actually my extractions are still failing most mornings. Here is an example from today, from a cron job that runs at 12:10 AM PDT. Often when I run the same job later in the day it works. Any suggestions? Thanks, Parker
>
> MAIN start time = 2020.03.13 00:10:02
> Working on 2020.03.13
> - dt0 = 2020-03-11-T00:00:00Z
> - dt1 = 2020-03-18-T00:00:00Z
> https://ncss.hycom.org/thredds/ncss/GLBy0.08/expt_93.0/FMRC/GLBy0.08_930_FMRC_best.ncd?var=surf_el,water_temp,salinity,water_u,water_v&north=53&south=39&west=229&east=239&time_start=2020-03-11-T00:00:00Z&time_end=2020-03-18-T00:00:00Z&timeStride=8&addLatLon=true&accept=netcdf4
> Attempting to get data, counter = 1
> *We failed to reach a server.
> -Reason: 500
> -took 3.6 seconds
> Attempting to get data, counter = 2
> *We failed to reach a server.
> -Reason: 500
> -took 0.4 seconds
> Attempting to get data, counter = 3
> *We failed to reach a server.
> -Reason: 500
> -took 0.3 seconds
> - error getting forecast files
> **** Using planB ****

> --
> --
> You received this message because you are a member of HYCOM.org
> To ask a question, send an email to fo...@hycom.org