thredds download problems

[Kenneth schaudt]

Hope someone may have a suggestion.  Downloads of Hycom fields as well
as point files have been failing the past few days.

Attempts to download information at a point are returning zero length files.

Wed Jul  9 08:54:01 CDT 2025
+ wget
'https://ncss.hycom.org/thredds/ncss/FMRC_ESPC-D-V02_uv3z/FMRC_ESPC-D-V02_uv3z_best.ncd?var=water_u&var=water_v&latitude=28.040&longitude=-89.080&time_start=2025-07-09T00:00:00Z&time_end=2025-07-16T23:00:00Z&accept=csv'
-O ../data/Titan.csv
--2025-07-09 08:54:01--
https://ncss.hycom.org/thredds/ncss/FMRC_ESPC-D-V02_uv3z/FMRC_ESPC-D-V02_uv3z_best.ncd?var=water_u&var=water_v&latitude=28.040&longitude=-89.080&time_start=2025-07-09T00:00:00Z&time_end=2025-07-16T23:00:00Z&accept=csv
Resolving ncss.hycom.org (ncss.hycom.org)... 144.174.97.9
Connecting to ncss.hycom.org (ncss.hycom.org)|144.174.97.9|:443...
connected.
HTTP request sent, awaiting response... 200 OK
Length: 0
Saving to: ‘../data/Titan.csv’

../data/Titan.csv       [ <=>                ]       0 --.-KB/s    in 0s

[Luisa Lopera]

Im also having problems with HYCOM-TSIS 1/100º Gulf of Mexico Reanalysis. I cant download .nc files or read them through opendap. 

[Michael McDonald]

Kenneth,

There was just a storage issue/outage during your query window that was impacting this ESPC-D-V02 dataset. The outage was this past Monday from around 5:30pm to midnight EST. The other outage was this past Tuesday from 9:30PM to Wed 11AM EST. Please let us know if the issue has not resolved itself. 

--

Michael McDonald
HYCOM.org Administrator

[Ken Schaudt]

Still failing as I noted in a recent post.   Worked Sat AM and has failed ever since.

[Ken Schaudt]

Still failing at 730 AM Central

+ ncks -D0 -d time,2025-07-15T00:00:00Z,2025-07-21T23:00:00Z -v water_temp -d lat,20.,35. -d lon,260.,280. -d depth,0. http://tds.hycom.org/thredds/dodsC/FMRC_ESPC-D-V02_ts3z/FMRC_ESPC-D-V02_ts3z_best.ncd -O ../data/FMRC_ESPC-D-V02_ts3z_best_0m.nc4

Error:curl error: Failure when receiving data from the peer

curl error details: 

Warning:oc_open: Could not read url

ncks: INFO DAP-access to http://tds.hycom.org/thredds/dodsC/FMRC_ESPC-D-V02_ts3z/FMRC_ESPC-D-V02_ts3z_best.ncd failed with error code -68. Translation into English with nc_strerror(-68) is "NetCDF: I/O failure"

ncks: WARNING not searching for http://tds.hycom.org/thredds/dodsC/FMRC_ESPC-D-V02_ts3z/FMRC_ESPC-D-V02_ts3z_best.ncd on remote filesystem, using local file hredds/dodsC/FMRC_ESPC-D-V02_ts3z/FMRC_ESPC-D-V02_ts3z_best.ncd instead

ERROR: nco__open() unable to open file "thredds/dodsC/FMRC_ESPC-D-V02_ts3z/FMRC_ESPC-D-V02_ts3z_best.ncd"

ERROR NC_ENOTNC Not a netCDF file

HINT: NC_ENOTNC errors can occur for many reasons. If your use-case matches one of the five listed below, take the corrective action indicated:

1. The netCDF file is truly corrupt, e.g., truncated. To verify whether the file is corrupt, try, e.g., printing its metadata with 'ncks -m in.nc'. This test will likely fail on a corrupt file

[David Aragon]

I have been having (what I think is opendap) problems since what appears to be last Thursday.  From Matlab:

ncdisp('https://tds.hycom.org/thredds/dodsC/FMRC_ESPC-D-V02_uv3z/FMRC_ESPC-D-V02_uv3z_best.ncd')

That succeeds 1/4 times roughly if I do the command several times.

[Ken Schaudt]

Same problem at 12:49 CDT.   

[Ken Schaudt]

Fails at 15:38CDT

Tue Jul 15 15:38:58 CDT 2025

+ ncks -D0 -d time,2025-07-15T00:00:00Z,2025-07-21T23:00:00Z -v water_temp -d lat,20.,35. -d lon,260.,280. -d depth,0. http://tds.hycom.org/thredds/dodsC/FMRC_ESPC-D-V02_ts3z/FMRC_ESPC-D-V02_ts3z_best.ncd -O ../data/FMRC_ESPC-D-V02_ts3z_best_0m.nc4

ncks: INFO DAP-access to http://tds.hycom.org/thredds/dodsC/FMRC_ESPC-D-V02_ts3z/FMRC_ESPC-D-V02_ts3z_best.ncd failed with error code -73. Translation into English with nc_strerror(-73) is "NetCDF: Malformed or inaccessible DAP2 DATADDS or DAP4 DAP response"

ncks: WARNING not searching for http://tds.hycom.org/thredds/dodsC/FMRC_ESPC-D-V02_ts3z/FMRC_ESPC-D-V02_ts3z_best.ncd on remote filesystem, using local file hredds/dodsC/FMRC_ESPC-D-V02_ts3z/FMRC_ESPC-D-V02_ts3z_best.ncd instead

ERROR: nco__open() unable to open file "thredds/dodsC/FMRC_ESPC-D-V02_ts3z/FMRC_ESPC-D-V02_ts3z_best.ncd"

ERROR NC_ENOTNC Not a netCDF file

[Michael McDonald]

Ken,

Please turn up that verbosity from "-D0" to "-D9" and report back on the output. 

[Ken Schaudt]

HERE'S THE LAST 3 ATTEMPTS

+ NCKS=ncks

+ DEBUG_LVL=-D0

+ WGET=wget

+ WGET_FLAGS=

+ RETRY_SLEEP=90

+ NCSS_BASE_URL=https://ncss.hycom.org/thredds/ncss/FMRC_ESPC-D-V02_uv3z/FMRC_ESPC-D-V02_uv3z_best.ncd

+ VARS='var=water_u&var=water_v'

+ LAT='&latitude=28.040'

+ LON='&longitude=-89.080'

++ TZ=GMT+00

++ date +%Y-%m-%dT00:00:00Z

+ TIME_START='&time_start=2025-07-15T00:00:00Z'

++ TZ=GMT-167

++ date +%Y-%m-%dT23:00:00Z

+ TIME_END='&time_end=2025-07-22T23:00:00Z'

+ ACCEPT='&accept=csv'

+ NCSS_FULL_URL='https://ncss.hycom.org/thredds/ncss/FMRC_ESPC-D-V02_uv3z/FMRC_ESPC-D-V02_uv3z_best.ncd?var=water_u&var=water_v&latitude=28.040&longitude=-89.080&time_start=2025-07-15T00:00:00Z&time_end=2025-07-22T23:00:00Z&accept=csv'

+ echo 'Site specific forecasts of conditions: acquiring data'

Site specific forecasts of conditions: acquiring data

+ OUT_FILE=../data/Titan.csv

+ true

+ date

Tue Jul 15 18:58:51 CDT 2025

+ wget 'https://ncss.hycom.org/thredds/ncss/FMRC_ESPC-D-V02_uv3z/FMRC_ESPC-D-V02_uv3z_best.ncd?var=water_u&var=water_v&latitude=28.040&longitude=-89.080&time_start=2025-07-15T00:00:00Z&time_end=2025-07-22T23:00:00Z&accept=csv' -O ../data/Titan.csv

--2025-07-15 18:58:51--  https://ncss.hycom.org/thredds/ncss/FMRC_ESPC-D-V02_uv3z/FMRC_ESPC-D-V02_uv3z_best.ncd?var=water_u&var=water_v&latitude=28.040&longitude=-89.080&time_start=2025-07-15T00:00:00Z&time_end=2025-07-22T23:00:00Z&accept=csv

Resolving ncss.hycom.org (ncss.hycom.org)... 144.174.97.9

Connecting to ncss.hycom.org (ncss.hycom.org)|144.174.97.9|:443... connected.

HTTP request sent, awaiting response... 200 OK

Length: unspecified [text/plain]

Saving to: ‘../data/Titan.csv’

../data/Titan.csv       [   <=>              ] 155.83K  3.00KB/s    in 52s     

2025-07-15 19:00:22 (3.00 KB/s) - ‘../data/Titan.csv’ saved [159570]

+ break

+ NCSS_BASE_URL=https://ncss.hycom.org/thredds/ncss/FMRC_ESPC-D-V02_uv3z/FMRC_ESPC-D-V02_uv3z_best.ncd

+ VARS='var=water_u&var=water_v'

+ LAT='&latitude=27.96'

+ LON='&longitude=-89.050'

++ TZ=GMT+00

++ date +%Y-%m-%dT00:00:00Z

+ TIME_START='&time_start=2025-07-16T00:00:00Z'

++ TZ=GMT-167

++ date +%Y-%m-%dT23:00:00Z

+ TIME_END='&time_end=2025-07-22T23:00:00Z'

+ ACCEPT='&accept=csv'

+ NCSS_FULL_URL='https://ncss.hycom.org/thredds/ncss/FMRC_ESPC-D-V02_uv3z/FMRC_ESPC-D-V02_uv3z_best.ncd?var=water_u&var=water_v&latitude=27.96&longitude=-89.050&time_start=2025-07-16T00:00:00Z&time_end=2025-07-22T23:00:00Z&accept=csv'

+ echo 'Site specific forecasts of conditions: acquiring data'

Site specific forecasts of conditions: acquiring data

+ OUT_FILE=../data/ICEMAX.csv

+ true

+ date

Tue Jul 15 19:00:22 CDT 2025

+ wget 'https://ncss.hycom.org/thredds/ncss/FMRC_ESPC-D-V02_uv3z/FMRC_ESPC-D-V02_uv3z_best.ncd?var=water_u&var=water_v&latitude=27.96&longitude=-89.050&time_start=2025-07-16T00:00:00Z&time_end=2025-07-22T23:00:00Z&accept=csv' -O ../data/ICEMAX.csv

--2025-07-15 19:00:22--  https://ncss.hycom.org/thredds/ncss/FMRC_ESPC-D-V02_uv3z/FMRC_ESPC-D-V02_uv3z_best.ncd?var=water_u&var=water_v&latitude=27.96&longitude=-89.050&time_start=2025-07-16T00:00:00Z&time_end=2025-07-22T23:00:00Z&accept=csv

Resolving ncss.hycom.org (ncss.hycom.org)... 144.174.97.9

Connecting to ncss.hycom.org (ncss.hycom.org)|144.174.97.9|:443... connected.

HTTP request sent, awaiting response... 200 OK

Length: unspecified [text/plain]

Saving to: ‘../data/ICEMAX.csv’

../data/ICEMAX.csv      [   <=>              ] 133.92K  6.93KB/s    in 19s     

2025-07-15 19:00:55 (6.93 KB/s) - ‘../data/ICEMAX.csv’ saved [137132]

+ break

+ set +x

kennethschaudt@MP2019-BigSur scripts % sh /Volumes/SG8GB/Users/schaudt/R_Projects/ROFFS_SUS/scripts/GOMl_titanICEMAX.sh

+ NCKS=ncks

+ DEBUG_LVL=-D0

+ WGET=wget

+ WGET_FLAGS=

+ RETRY_SLEEP=90

+ NCSS_BASE_URL=https://ncss.hycom.org/thredds/ncss/FMRC_ESPC-D-V02_uv3z/FMRC_ESPC-D-V02_uv3z_best.ncd

+ VARS='var=water_u&var=water_v'

+ LAT='&latitude=28.040'

+ LON='&longitude=-89.080'

++ TZ=GMT+00

++ date +%Y-%m-%dT00:00:00Z

+ TIME_START='&time_start=2025-07-16T00:00:00Z'

++ TZ=GMT-167

++ date +%Y-%m-%dT23:00:00Z

+ TIME_END='&time_end=2025-07-23T23:00:00Z'

+ ACCEPT='&accept=csv'

+ NCSS_FULL_URL='https://ncss.hycom.org/thredds/ncss/FMRC_ESPC-D-V02_uv3z/FMRC_ESPC-D-V02_uv3z_best.ncd?var=water_u&var=water_v&latitude=28.040&longitude=-89.080&time_start=2025-07-16T00:00:00Z&time_end=2025-07-23T23:00:00Z&accept=csv'

+ echo 'Site specific forecasts of conditions: acquiring data'

Site specific forecasts of conditions: acquiring data

+ OUT_FILE=../data/Titan.csv

+ true

+ date

Tue Jul 15 20:09:38 CDT 2025

+ wget 'https://ncss.hycom.org/thredds/ncss/FMRC_ESPC-D-V02_uv3z/FMRC_ESPC-D-V02_uv3z_best.ncd?var=water_u&var=water_v&latitude=28.040&longitude=-89.080&time_start=2025-07-16T00:00:00Z&time_end=2025-07-23T23:00:00Z&accept=csv' -O ../data/Titan.csv

--2025-07-15 20:09:38--  https://ncss.hycom.org/thredds/ncss/FMRC_ESPC-D-V02_uv3z/FMRC_ESPC-D-V02_uv3z_best.ncd?var=water_u&var=water_v&latitude=28.040&longitude=-89.080&time_start=2025-07-16T00:00:00Z&time_end=2025-07-23T23:00:00Z&accept=csv

Resolving ncss.hycom.org (ncss.hycom.org)... 144.174.97.9

Connecting to ncss.hycom.org (ncss.hycom.org)|144.174.97.9|:443... connected.

HTTP request sent, awaiting response... 200 OK

Length: unspecified [text/plain]

Saving to: ‘../data/Titan.csv’

../data/Titan.csv       [   <=>              ] 155.75K  2.43KB/s    in 64s     

2025-07-15 20:11:29 (2.43 KB/s) - ‘../data/Titan.csv’ saved [159491]

+ break

+ NCSS_BASE_URL=https://ncss.hycom.org/thredds/ncss/FMRC_ESPC-D-V02_uv3z/FMRC_ESPC-D-V02_uv3z_best.ncd

+ VARS='var=water_u&var=water_v'

+ LAT='&latitude=27.96'

+ LON='&longitude=-89.050'

++ TZ=GMT+00

++ date +%Y-%m-%dT00:00:00Z

+ TIME_START='&time_start=2025-07-16T00:00:00Z'

++ TZ=GMT-167

++ date +%Y-%m-%dT23:00:00Z

+ TIME_END='&time_end=2025-07-23T23:00:00Z'

+ ACCEPT='&accept=csv'

+ NCSS_FULL_URL='https://ncss.hycom.org/thredds/ncss/FMRC_ESPC-D-V02_uv3z/FMRC_ESPC-D-V02_uv3z_best.ncd?var=water_u&var=water_v&latitude=27.96&longitude=-89.050&time_start=2025-07-16T00:00:00Z&time_end=2025-07-23T23:00:00Z&accept=csv'

+ echo 'Site specific forecasts of conditions: acquiring data'

Site specific forecasts of conditions: acquiring data

+ OUT_FILE=../data/ICEMAX.csv

+ true

+ date

Tue Jul 15 20:11:30 CDT 2025

+ wget 'https://ncss.hycom.org/thredds/ncss/FMRC_ESPC-D-V02_uv3z/FMRC_ESPC-D-V02_uv3z_best.ncd?var=water_u&var=water_v&latitude=27.96&longitude=-89.050&time_start=2025-07-16T00:00:00Z&time_end=2025-07-23T23:00:00Z&accept=csv' -O ../data/ICEMAX.csv

--2025-07-15 20:11:30--  https://ncss.hycom.org/thredds/ncss/FMRC_ESPC-D-V02_uv3z/FMRC_ESPC-D-V02_uv3z_best.ncd?var=water_u&var=water_v&latitude=27.96&longitude=-89.050&time_start=2025-07-16T00:00:00Z&time_end=2025-07-23T23:00:00Z&accept=csv

Resolving ncss.hycom.org (ncss.hycom.org)... 144.174.97.9

Connecting to ncss.hycom.org (ncss.hycom.org)|144.174.97.9|:443... connected.

HTTP request sent, awaiting response... 200 OK

Length: unspecified [text/plain]

Saving to: ‘../data/ICEMAX.csv’

../data/ICEMAX.csv      [   <=>              ] 157.51K  6.42KB/s    in 25s     

2025-07-15 20:12:08 (6.42 KB/s) - ‘../data/ICEMAX.csv’ saved [161293]

+ break

+ set +x

kennethschaudt@MP2019-BigSur scripts % sh /Volumes/SG8GB/Users/schaudt/R_Projects/ROFFS_SUS/scripts/SST_UV.sh          

+ NCKS=ncks

+ DEBUG_LVL=-D0

+ WGET=wget

+ WGET_FLAGS=

+ RETRY_SLEEP=90

+ DAP_URL=http://tds.hycom.org/thredds/dodsC/FMRC_ESPC-D-V02_ts3z/FMRC_ESPC-D-V02_ts3z_best.ncd

+ VARS='-v water_temp'

++ TZ=GMT+00

++ date +%Y-%m-%dT00:00:00Z

+ START_DATE=2025-07-16T00:00:00Z

++ TZ=GMT-144

++ date +%Y-%m-%dT23:00:00Z

+ END_DATE=2025-07-22T23:00:00Z

+ TIMERANGE='-d time,2025-07-16T00:00:00Z,2025-07-22T23:00:00Z'

+ LAT_RANGE='-d lat,20.,35.'

+ LON_RANGE='-d lon,260.,280.'

+ echo 'app1: acquiring 0m data'

app1: acquiring 0m data

+ DEPTH_METERS=0

+ DEPTH='-d depth,0.'

+ OUT_FILE=../data/FMRC_ESPC-D-V02_ts3z_best_0m.nc4

+ true

+ date

Tue Jul 15 20:14:21 CDT 2025

+ ncks -D0 -d time,2025-07-16T00:00:00Z,2025-07-22T23:00:00Z -v water_temp -d lat,20.,35. -d lon,260.,280. -d depth,0. http://tds.hycom.org/thredds/dodsC/FMRC_ESPC-D-V02_ts3z/FMRC_ESPC-D-V02_ts3z_best.ncd -O ../data/FMRC_ESPC-D-V02_ts3z_best_0m.nc4

oc_open: server error retrieving url: code=3 message="Invalid Parameter Exception: DArrayDimension.setProjection: Bad Projection Request: stop >= size: 128:121"ERROR: nco_get_vara() failed to nc_get_vara() variable "water_temp"

ERROR NC_EACCESS Access failure

HINT: NC_EACCESS errors signify a problem receiving data from a DAP server. This can occur in multiple ways, including 1) When NCO requests (with nco_var_get()) more data than the server is configured to dispense at one time. A workaround for this might be to request data in smaller amounts at one time. This can be accomplished by accessing hyperslabs or multi-slabs of data as described at http://nco.sf.net/nco.html#mlt. 2) When NCO requests data from a buggy DAP library. The DAP software built into netCDF versions 4.6.2 and 4.6.3 is known to be problematic. The only solution for this would be to use an NCO built with a newer version (at least 4.7.3) of netCDF.

nco_err_exit(): ERROR Short NCO-generated message (usually name of function that triggered error): nco_get_vara()

nco_err_exit(): ERROR Error code is -77. Translation into English with nc_strerror(-77) is "NetCDF: Access failure"

nco_err_exit(): ERROR NCO will now exit with system call exit(EXIT_FAILURE)

+ echo 'ERROR: sleeping for 90 seconds and then trying again...'

ERROR: sleeping for 90 seconds and then trying again...

+ sleep 90

+ true

+ date

Tue Jul 15 20:15:52 CDT 2025

+ ncks -D0 -d time,2025-07-16T00:00:00Z,2025-07-22T23:00:00Z -v water_temp -d lat,20.,35. -d lon,260.,280. -d depth,0. http://tds.hycom.org/thredds/dodsC/FMRC_ESPC-D-V02_ts3z/FMRC_ESPC-D-V02_ts3z_best.ncd -O ../data/FMRC_ESPC-D-V02_ts3z_best_0m.nc4

ncks: ERROR User-specified coordinate value range 228 <= time <= 395 does not fall within valid coordinate range 6.94078e-310 <= time <= 0

+ echo 'ERROR: sleeping for 90 seconds and then trying again...'

ERROR: sleeping for 90 seconds and then trying again...

+ sleep 90

[Ken Schaudt]

HERE'S THE TERMINAL SCRIPT BASED ON ONE YOU SUPPLIED LONG AGO.

#!/bin/bash
# Modified from work of: Michael....@HYCOM.org
# Date: 2020-06-14
# Description: Custom ncks query for kjsc...@schaudt.us
#

## begin BASH debug mode (commend out to disable)
set -x

## double ## are comments, single # used to disable lines below

## Common Variables
NCKS="ncks"
DEBUG_LVL="-D0"
WGET="wget"
WGET_FLAGS=""
RETRY_SLEEP=90

## Application 1) Create synoptic charts of the oceanographic situation in GOM at 0m.
## get SST

## Desired statement format
##  ncks -D5 -d time,2025-01-25T00:00:00Z,2025-01-31T23:00:00Z -v
####### water_temp -d lat,20.,35. -d lon,260.,280. -d depth,0.
####### "http://tds.hycom.org/thredds/dodsC/FMRC_ESPC-D-V02_ts3z/FMRC_ESPC-D-V02_ts3z_best.ncd"
## -O ../data/FMRC_ESPC-D-V02_ts3z_best_0m.nc4

## SST
 DAP_URL='http://tds.hycom.org/thredds/dodsC/FMRC_ESPC-D-V02_ts3z/FMRC_ESPC-D-V02_ts3z_best.ncd'
  VARS="-v water_temp"
 START_DATE=$( TZ=GMT+00 date +%Y-%m-%dT00:00:00Z )
 END_DATE=$( TZ=GMT-144 date +%Y-%m-%dT23:00:00Z )

 TIMERANGE="-d time,$START_DATE,$END_DATE"
# LAT_RANGE="-d lat,35,20."
 LAT_RANGE="-d lat,20.,35."
 LON_RANGE="-d lon,260.,280."
# LON_RANGE="-d lon,-80.,-100."

echo "app1: acquiring 0m data"

DEPTH_METERS=0
DEPTH="-d depth,${DEPTH_METERS}."
OUT_FILE="../data/FMRC_ESPC-D-V02_ts3z_best_${DEPTH_METERS}m.nc4"

while true; do
 date

 $NCKS $DEBUG_LVL $TIMERANGE $VARS $LAT_RANGE $LON_RANGE $DEPTH $DAP_URL -O $OUT_FILE && break
 echo "ERROR: sleeping for $RETRY_SLEEP seconds and then trying again..."
 sleep $RETRY_SLEEP
done


## get U V
## Desired statement format

# + ncks -D5 -d time,2025-01-25T00:00:00Z,2025-01-31T23:00:00Z -v
# water_u,water_v -d lat,20.,35. -d lon,260.,280. -d depth,0.
# "http://tds.hycom.org/thredds/dodsC/FMRC_ESPC-D-V02_uv3z/FMRC_ESPC-D-V02_uv3z_best.ncd"
# -O ../data/FMRC_ESPC-D-V02_uv3z_best_0m.nc4


 DAP_URL='http://tds.hycom.org/thredds/dodsC/FMRC_ESPC-D-V02_uv3z/FMRC_ESPC-D-V02_uv3z_best.ncd'
  VARS="-v water_u,water_v"
  START_DATE=$( TZ=GMT+00 date +%Y-%m-%dT00:00:00Z )
  END_DATE=$( TZ=GMT-144 date +%Y-%m-%dT23:00:00Z )

 TIMERANGE="-d time,$START_DATE,$END_DATE"
# LAT_RANGE="-d lat,35,20."
  LAT_RANGE="-d lat,20.,35."
  LON_RANGE="-d lon,260.,280."
# LON_RANGE="-d lon,-80.,-100."

echo "app1: acquiring 0m data"

DEPTH_METERS=0
DEPTH="-d depth,${DEPTH_METERS}."
OUT_FILE="../data/FMRC_ESPC-D-V02_uv3z_best_${DEPTH_METERS}m.nc4"

while true; do
 date

 $NCKS $DEBUG_LVL $TIMERANGE $VARS $LAT_RANGE $LON_RANGE $DEPTH $DAP_URL -O $OUT_FILE && break
 echo "ERROR: sleeping for $RETRY_SLEEP seconds and then trying again..."
 sleep $RETRY_SLEEP
done


## Application 3) Create synoptic charts of the oceanographic situation in GOM at 200m.
## get SST


## 200mT
 DAP_URL='http://tds.hycom.org/thredds/dodsC/FMRC_ESPC-D-V02_ts3z/FMRC_ESPC-D-V02_ts3z_best.ncd'
  VARS="-v water_temp"
 START_DATE=$( TZ=GMT+00 date +%Y-%m-%dT00:00:00Z )
 END_DATE=$( TZ=GMT-144 date +%Y-%m-%dT23:00:00Z )

 TIMERANGE="-d time,$START_DATE,$END_DATE"
# LAT_RANGE="-d lat,35,20."
 LAT_RANGE="-d lat,20.,35."
 LON_RANGE="-d lon,260.,280."
# LON_RANGE="-d lon,-80.,-100."

echo "app1: acquiring 200m data"
DEPTH_METERS=200
DEPTH="-d depth,${DEPTH_METERS}."
OUT_FILE="../data/FMRC_ESPC-D-V02_ts3z_best_${DEPTH_METERS}m.nc4"

while true; do
 date

 $NCKS $DEBUG_LVL $TIMERANGE $VARS $LAT_RANGE $LON_RANGE $DEPTH $DAP_URL -O $OUT_FILE && break
 echo "ERROR: sleeping for $RETRY_SLEEP seconds and then trying again..."
 sleep $RETRY_SLEEP
done


## get U V
## Desired statement format

# + ncks -D5 -d time,2025-01-25T00:00:00Z,2025-01-31T23:00:00Z -v
# water_u,water_v -d lat,20.,35. -d lon,260.,280. -d depth,0.
# "http://tds.hycom.org/thredds/dodsC/FMRC_ESPC-D-V02_uv3z/FMRC_ESPC-D-V02_uv3z_best.ncd"
# -O ../data/FMRC_ESPC-D-V02_uv3z_best_0m.nc4


 DAP_URL='http://tds.hycom.org/thredds/dodsC/FMRC_ESPC-D-V02_uv3z/FMRC_ESPC-D-V02_uv3z_best.ncd'
  VARS="-v water_u,water_v"
  START_DATE=$( TZ=GMT+00 date +%Y-%m-%dT00:00:00Z )
  END_DATE=$( TZ=GMT-144 date +%Y-%m-%dT23:00:00Z )

 TIMERANGE="-d time,$START_DATE,$END_DATE"
# LAT_RANGE="-d lat,35,20."
  LAT_RANGE="-d lat,20.,35."
  LON_RANGE="-d lon,260.,280."
# LON_RANGE="-d lon,-80.,-100."

echo "app1: acquiring 200m data"
DEPTH_METERS=200
DEPTH="-d depth,${DEPTH_METERS}."
OUT_FILE="../data/FMRC_ESPC-D-V02_uv3z_best_${DEPTH_METERS}m.nc4"

while true; do
 date

 $NCKS $DEBUG_LVL $TIMERANGE $VARS $LAT_RANGE $LON_RANGE $DEPTH $DAP_URL -O $OUT_FILE && break
 echo "ERROR: sleeping for $RETRY_SLEEP seconds and then trying again..."
 sleep $RETRY_SLEEP
done





## end BASH debug mode
set +x

[Ken Schaudt]

SUCCESS!  FIRST VALID DOWNLOAD SINCE THE WEEKEND    

Last login: Tue Jul 15 18:58:30 on ttys000

kennethschaudt@MP2019-BigSur ~ % cd /Volumes/SG8GB/Users/schaudt/R_Projects/ROFFS_SUS/scripts                    

kennethschaudt@MP2019-BigSur scripts % sh /Volumes/SG8GB/Users/schaudt/R_Projects/ROFFS_SUS/scripts/SST_UV.sh

+ NCKS=ncks

+ DEBUG_LVL=-D0

+ WGET=wget

+ WGET_FLAGS=

+ RETRY_SLEEP=90

+ DAP_URL=http://tds.hycom.org/thredds/dodsC/FMRC_ESPC-D-V02_ts3z/FMRC_ESPC-D-V02_ts3z_best.ncd

+ VARS='-v water_temp'

++ TZ=GMT+00

++ date +%Y-%m-%dT00:00:00Z

+ START_DATE=2025-07-16T00:00:00Z

++ TZ=GMT-144

++ date +%Y-%m-%dT23:00:00Z

+ END_DATE=2025-07-22T23:00:00Z

+ TIMERANGE='-d time,2025-07-16T00:00:00Z,2025-07-22T23:00:00Z'

+ LAT_RANGE='-d lat,20.,35.'

+ LON_RANGE='-d lon,260.,280.'

+ echo 'app1: acquiring 0m data'

app1: acquiring 0m data

+ DEPTH_METERS=0

+ DEPTH='-d depth,0.'

+ OUT_FILE=../data/FMRC_ESPC-D-V02_ts3z_best_0m.nc4

+ true

+ date

Tue Jul 15 20:46:50 CDT 2025

+ ncks -D0 -d time,2025-07-16T00:00:00Z,2025-07-22T23:00:00Z -v water_temp -d lat,20.,35. -d lon,260.,280. -d depth,0. http://tds.hycom.org/thredds/dodsC/FMRC_ESPC-D-V02_ts3z/FMRC_ESPC-D-V02_ts3z_best.ncd -O ../data/FMRC_ESPC-D-V02_ts3z_best_0m.nc4

+ break

+ DAP_URL=http://tds.hycom.org/thredds/dodsC/FMRC_ESPC-D-V02_uv3z/FMRC_ESPC-D-V02_uv3z_best.ncd

+ VARS='-v water_u,water_v'

++ TZ=GMT+00

++ date +%Y-%m-%dT00:00:00Z

+ START_DATE=2025-07-16T00:00:00Z

++ TZ=GMT-144

++ date +%Y-%m-%dT23:00:00Z

+ END_DATE=2025-07-22T23:00:00Z

+ TIMERANGE='-d time,2025-07-16T00:00:00Z,2025-07-22T23:00:00Z'

+ LAT_RANGE='-d lat,20.,35.'

+ LON_RANGE='-d lon,260.,280.'

+ echo 'app1: acquiring 0m data'

app1: acquiring 0m data

+ DEPTH_METERS=0

+ DEPTH='-d depth,0.'

+ OUT_FILE=../data/FMRC_ESPC-D-V02_uv3z_best_0m.nc4

+ true

+ date

Tue Jul 15 20:46:57 CDT 2025

+ ncks -D0 -d time,2025-07-16T00:00:00Z,2025-07-22T23:00:00Z -v water_u,water_v -d lat,20.,35. -d lon,260.,280. -d depth,0. http://tds.hycom.org/thredds/dodsC/FMRC_ESPC-D-V02_uv3z/FMRC_ESPC-D-V02_uv3z_best.ncd -O ../data/FMRC_ESPC-D-V02_uv3z_best_0m.nc4

ncks: ERROR User-specified coordinate value range 324 <= time <= 491 does not fall within valid coordinate range 6.94669e-310 <= time <= 0

+ echo 'ERROR: sleeping for 90 seconds and then trying again...'

ERROR: sleeping for 90 seconds and then trying again...

+ sleep 90

+ true

+ date

Tue Jul 15 20:48:28 CDT 2025

+ ncks -D0 -d time,2025-07-16T00:00:00Z,2025-07-22T23:00:00Z -v water_u,water_v -d lat,20.,35. -d lon,260.,280. -d depth,0. http://tds.hycom.org/thredds/dodsC/FMRC_ESPC-D-V02_uv3z/FMRC_ESPC-D-V02_uv3z_best.ncd -O ../data/FMRC_ESPC-D-V02_uv3z_best_0m.nc4

+ break

+ DAP_URL=http://tds.hycom.org/thredds/dodsC/FMRC_ESPC-D-V02_ts3z/FMRC_ESPC-D-V02_ts3z_best.ncd

+ VARS='-v water_temp'

++ TZ=GMT+00

++ date +%Y-%m-%dT00:00:00Z

+ START_DATE=2025-07-16T00:00:00Z

++ TZ=GMT-144

++ date +%Y-%m-%dT23:00:00Z

+ END_DATE=2025-07-22T23:00:00Z

+ TIMERANGE='-d time,2025-07-16T00:00:00Z,2025-07-22T23:00:00Z'

+ LAT_RANGE='-d lat,20.,35.'

+ LON_RANGE='-d lon,260.,280.'

+ echo 'app1: acquiring 200m data'

app1: acquiring 200m data

+ DEPTH_METERS=200

+ DEPTH='-d depth,200.'

+ OUT_FILE=../data/FMRC_ESPC-D-V02_ts3z_best_200m.nc4

+ true

+ date

Tue Jul 15 20:48:34 CDT 2025

+ ncks -D0 -d time,2025-07-16T00:00:00Z,2025-07-22T23:00:00Z -v water_temp -d lat,20.,35. -d lon,260.,280. -d depth,200. http://tds.hycom.org/thredds/dodsC/FMRC_ESPC-D-V02_ts3z/FMRC_ESPC-D-V02_ts3z_best.ncd -O ../data/FMRC_ESPC-D-V02_ts3z_best_200m.nc4

+ break

+ DAP_URL=http://tds.hycom.org/thredds/dodsC/FMRC_ESPC-D-V02_uv3z/FMRC_ESPC-D-V02_uv3z_best.ncd

+ VARS='-v water_u,water_v'

++ TZ=GMT+00

++ date +%Y-%m-%dT00:00:00Z

+ START_DATE=2025-07-16T00:00:00Z

++ TZ=GMT-144

++ date +%Y-%m-%dT23:00:00Z

+ END_DATE=2025-07-22T23:00:00Z

+ TIMERANGE='-d time,2025-07-16T00:00:00Z,2025-07-22T23:00:00Z'

+ LAT_RANGE='-d lat,20.,35.'

+ LON_RANGE='-d lon,260.,280.'

+ echo 'app1: acquiring 200m data'

app1: acquiring 200m data

+ DEPTH_METERS=200

+ DEPTH='-d depth,200.'

+ OUT_FILE=../data/FMRC_ESPC-D-V02_uv3z_best_200m.nc4

+ true

+ date

Tue Jul 15 20:48:42 CDT 2025

+ ncks -D0 -d time,2025-07-16T00:00:00Z,2025-07-22T23:00:00Z -v water_u,water_v -d lat,20.,35. -d lon,260.,280. -d depth,200. http://tds.hycom.org/thredds/dodsC/FMRC_ESPC-D-V02_uv3z/FMRC_ESPC-D-V02_uv3z_best.ncd -O ../data/FMRC_ESPC-D-V02_uv3z_best_200m.nc4

+ break

+ set +x

kennethschaudt@MP2019-BigSur scripts % 

[Ken Schaudt]

Ran the script again but set debug to D9.  Getting errors again.  Am downloading data but there are errors when plotted.

Last login: Tue Jul 15 20:46:42 on ttys000

kennethschaudt@MP2019-BigSur ~ % cd /Volumes/SG8GB/Users/schaudt/R_Projects/ROFFS_SUS/scripts

kennethschaudt@MP2019-BigSur scripts % sh /Volumes/SG8GB/Users/schaudt/R_Projects/ROFFS_SUS/scripts/SST_UV.sh

+ NCKS=ncks

+ DEBUG_LVL=-D9

+ WGET=wget

+ WGET_FLAGS=

+ RETRY_SLEEP=90

+ DAP_URL=http://tds.hycom.org/thredds/dodsC/FMRC_ESPC-D-V02_ts3z/FMRC_ESPC-D-V02_ts3z_best.ncd

+ VARS='-v water_temp'

++ TZ=GMT+00

++ date +%Y-%m-%dT00:00:00Z

+ START_DATE=2025-07-16T00:00:00Z

++ TZ=GMT-144

++ date +%Y-%m-%dT23:00:00Z

+ END_DATE=2025-07-22T23:00:00Z

+ TIMERANGE='-d time,2025-07-16T00:00:00Z,2025-07-22T23:00:00Z'

+ LAT_RANGE='-d lat,20.,35.'

+ LON_RANGE='-d lon,260.,280.'

+ echo 'app1: acquiring 0m data'

app1: acquiring 0m data

+ DEPTH_METERS=0

+ DEPTH='-d depth,0.'

+ OUT_FILE=../data/FMRC_ESPC-D-V02_ts3z_best_0m.nc4

+ true

+ date

Tue Jul 15 21:20:27 CDT 2025

+ ncks -D9 -d time,2025-07-16T00:00:00Z,2025-07-22T23:00:00Z -v water_temp -d lat,20.,35. -d lon,260.,280. -d depth,0. http://tds.hycom.org/thredds/dodsC/FMRC_ESPC-D-V02_ts3z/FMRC_ESPC-D-V02_ts3z_best.ncd -O ../data/FMRC_ESPC-D-V02_ts3z_best_0m.nc4

ncks: INFO nco_cnk_csh_ini() reports chunk cache size = cnk_csh_byt = 16777216 B, # of slots in raw data chunk cache has table = nelemsp = 4133, pre-emption favor fraction = pmp_fvr_frc = 0.75

ncks: INFO Build compiler lacked (or user turned-off) OpenMP support. Code will execute with single thread in Uni-Processor (UP) mode.

ncks: INFO nco_fl_mk_lcl() successfully accessed this file using the DAP protocol

ncks: INFO nco_fl_open() reports nc__open() will request file buffer of default size

ncks: INFO nco_fl_open() reports nc__open() opened file with buffer size = 0 bytes

ncks: INFO nco_fl_open() reports extended filetype of http://tds.hycom.org/thredds/dodsC/FMRC_ESPC-D-V02_ts3z/FMRC_ESPC-D-V02_ts3z_best.ncd is NC_FORMATX_DAP2, mode = 0 (oct) = 0 (dec) = 0000 (hex) 

ncks: INFO nco_fl_open() will not print any more INFO messages if this file is opened again. (Many NCO operators open the same file multiple times when OpenMP is enabled, nco_fl_open() prints INFO messages only the first time because successive messages are usually redundant).

ncks: INFO nco_grp_itr() found group / at level 0

ncks: INFO nco_xtr_mk() reports following groups match sub-setting and regular expressions:

ncks: INFO nco_xtr_mk() reports variable water_temp meets additional conditions for variable match with /water_temp.

ncks: INFO nco_xtr_mk() reports following variables match sub-setting and regular expressions:

nm_fll=/water_temp

ncks: CONVENTION File "Conventions" attribute is "CF-1.4, NAVO_netcdf_v1.0"

ncks: DEBUG nco_xtr_cf_var_add() reports nbr_cf = 5,cf_lst[0] = time_run

ncks: DEBUG nco_xtr_cf_var_add() reports nbr_cf = 5,cf_lst[0] = time_run

ncks: nco_fl_out_open() reports sizeof(pid_t) = 4 bytes, pid = 31697, pid_sng_lng = 6 bytes, strlen(pid_sng) = 5 bytes, fl_out_tmp_lng = 59 bytes, strlen(fl_out_tmp) = 58, fl_out_tmp = ../data/FMRC_ESPC-D-V02_ts3z_best_0m.nc4.pid31697.ncks.tmp

ncks: nco_fl_out_open() reports strlen(fl_out_tmp_sys) = 46, fl_out_tmp_sys = ../data/FMRC_ESPC-D-V02_ts3z_best_0m.nc42B9xj7, 

ncks: WARNING nco_mss_val_get() reports that variable time has attribute "missing_value" but not "_FillValue". To comply with netCDF conventions, NCO ignores values that equal the _FillValue attribute when performing arithmetic. Confusingly, values equal to the missing_value should also be neglected. However, it is tedious and (possibly) computationally expensive to check each value against multiple missing values during arithmetic on large variables. So NCO thinks that processing variables with a "missing_value" attribute and no "_FillValue" attribute may produce undesired arithmetic results (i.e., where values that were intended to be neglected were not, in fact, neglected). We suggest you rename all "missing_value" attributes to "_FillValue" or include both "missing_value" and "_FillValue" attributes (with the _same values_) for all variables that have either attribute. Because it is long, this message is only printed once per operator even though multiple variables may have the same attribute configuration. More information on missing values is given at:

http://nco.sf.net/nco.html#mss_val

Examples of renaming attributes are at:

http://nco.sf.net/nco.html#xmp_ncrename

Examples of creating and deleting attributes are at:

http://nco.sf.net/nco.html#xmp_ncatted

ncks: INFO nco_aed_prc() examining variable "Global"

ncks: TIMER Metadata setup and file layout before main loop took    0.07 s

oc_open: server error retrieving url: code=3 message="Invalid Parameter Exception: DArrayDimension.setProjection: Bad Projection Request: stop >= size: 128:121"ERROR: nco_get_vara() failed to nc_get_vara() variable "water_temp"

ERROR NC_EACCESS Access failure

HINT: NC_EACCESS errors signify a problem receiving data from a DAP server. This can occur in multiple ways, including 1) When NCO requests (with nco_var_get()) more data than the server is configured to dispense at one time. A workaround for this might be to request data in smaller amounts at one time. This can be accomplished by accessing hyperslabs or multi-slabs of data as described at http://nco.sf.net/nco.html#mlt. 2) When NCO requests data from a buggy DAP library. The DAP software built into netCDF versions 4.6.2 and 4.6.3 is known to be problematic. The only solution for this would be to use an NCO built with a newer version (at least 4.7.3) of netCDF.

nco_err_exit(): ERROR Short NCO-generated message (usually name of function that triggered error): nco_get_vara()

nco_err_exit(): ERROR Error code is -77. Translation into English with nc_strerror(-77) is "NetCDF: Access failure"

nco_err_exit(): ERROR NCO will now exit with system call exit(EXIT_FAILURE)

+ echo 'ERROR: sleeping for 90 seconds and then trying again...'

ERROR: sleeping for 90 seconds and then trying again...

+ sleep 90

+ true

+ date

Tue Jul 15 21:21:58 CDT 2025

+ ncks -D9 -d time,2025-07-16T00:00:00Z,2025-07-22T23:00:00Z -v water_temp -d lat,20.,35. -d lon,260.,280. -d depth,0. http://tds.hycom.org/thredds/dodsC/FMRC_ESPC-D-V02_ts3z/FMRC_ESPC-D-V02_ts3z_best.ncd -O ../data/FMRC_ESPC-D-V02_ts3z_best_0m.nc4

ncks: INFO nco_cnk_csh_ini() reports chunk cache size = cnk_csh_byt = 16777216 B, # of slots in raw data chunk cache has table = nelemsp = 4133, pre-emption favor fraction = pmp_fvr_frc = 0.75

ncks: INFO Build compiler lacked (or user turned-off) OpenMP support. Code will execute with single thread in Uni-Processor (UP) mode.

ncks: INFO nco_fl_mk_lcl() successfully accessed this file using the DAP protocol

ncks: INFO nco_fl_open() reports nc__open() will request file buffer of default size

ncks: INFO nco_fl_open() reports nc__open() opened file with buffer size = 0 bytes

ncks: INFO nco_fl_open() reports extended filetype of http://tds.hycom.org/thredds/dodsC/FMRC_ESPC-D-V02_ts3z/FMRC_ESPC-D-V02_ts3z_best.ncd is NC_FORMATX_DAP2, mode = 0 (oct) = 0 (dec) = 0000 (hex) 

ncks: INFO nco_fl_open() will not print any more INFO messages if this file is opened again. (Many NCO operators open the same file multiple times when OpenMP is enabled, nco_fl_open() prints INFO messages only the first time because successive messages are usually redundant).

ncks: INFO nco_grp_itr() found group / at level 0

ncks: INFO nco_xtr_mk() reports following groups match sub-setting and regular expressions:

ncks: INFO nco_xtr_mk() reports variable water_temp meets additional conditions for variable match with /water_temp.

ncks: INFO nco_xtr_mk() reports following variables match sub-setting and regular expressions:

nm_fll=/water_temp

ncks: CONVENTION File "Conventions" attribute is "CF-1.4, NAVO_netcdf_v1.0"

ncks: DEBUG nco_xtr_cf_var_add() reports nbr_cf = 5,cf_lst[0] = time_run

ncks: DEBUG nco_xtr_cf_var_add() reports nbr_cf = 5,cf_lst[0] = time_run

ncks: nco_fl_out_open() reports sizeof(pid_t) = 4 bytes, pid = 31706, pid_sng_lng = 6 bytes, strlen(pid_sng) = 5 bytes, fl_out_tmp_lng = 59 bytes, strlen(fl_out_tmp) = 58, fl_out_tmp = ../data/FMRC_ESPC-D-V02_ts3z_best_0m.nc4.pid31706.ncks.tmp

ncks: nco_fl_out_open() reports strlen(fl_out_tmp_sys) = 46, fl_out_tmp_sys = ../data/FMRC_ESPC-D-V02_ts3z_best_0m.nc4otGtTy, 

ncks: WARNING nco_mss_val_get() reports that variable time has attribute "missing_value" but not "_FillValue". To comply with netCDF conventions, NCO ignores values that equal the _FillValue attribute when performing arithmetic. Confusingly, values equal to the missing_value should also be neglected. However, it is tedious and (possibly) computationally expensive to check each value against multiple missing values during arithmetic on large variables. So NCO thinks that processing variables with a "missing_value" attribute and no "_FillValue" attribute may produce undesired arithmetic results (i.e., where values that were intended to be neglected were not, in fact, neglected). We suggest you rename all "missing_value" attributes to "_FillValue" or include both "missing_value" and "_FillValue" attributes (with the _same values_) for all variables that have either attribute. Because it is long, this message is only printed once per operator even though multiple variables may have the same attribute configuration. More information on missing values is given at:

http://nco.sf.net/nco.html#mss_val

Examples of renaming attributes are at:

http://nco.sf.net/nco.html#xmp_ncrename

Examples of creating and deleting attributes are at:

http://nco.sf.net/nco.html#xmp_ncatted

ncks: INFO nco_aed_prc() examining variable "Global"

ncks: TIMER Metadata setup and file layout before main loop took    0.06 s

ncks: INFO Moving ../data/FMRC_ESPC-D-V02_ts3z_best_0m.nc4.pid31706.ncks.tmp to ../data/FMRC_ESPC-D-V02_ts3z_best_0m.nc4...done

ncks: TIMER Elapsed clock() time for command is    0.20 s

+ break

+ DAP_URL=http://tds.hycom.org/thredds/dodsC/FMRC_ESPC-D-V02_uv3z/FMRC_ESPC-D-V02_uv3z_best.ncd

+ VARS='-v water_u,water_v'

++ TZ=GMT+00

++ date +%Y-%m-%dT00:00:00Z

+ START_DATE=2025-07-16T00:00:00Z

++ TZ=GMT-144

++ date +%Y-%m-%dT23:00:00Z

+ END_DATE=2025-07-22T23:00:00Z

+ TIMERANGE='-d time,2025-07-16T00:00:00Z,2025-07-22T23:00:00Z'

+ LAT_RANGE='-d lat,20.,35.'

+ LON_RANGE='-d lon,260.,280.'

+ echo 'app1: acquiring 0m data'

app1: acquiring 0m data

+ DEPTH_METERS=0

+ DEPTH='-d depth,0.'

+ OUT_FILE=../data/FMRC_ESPC-D-V02_uv3z_best_0m.nc4

+ true

+ date

Tue Jul 15 21:22:06 CDT 2025

+ ncks -D9 -d time,2025-07-16T00:00:00Z,2025-07-22T23:00:00Z -v water_u,water_v -d lat,20.,35. -d lon,260.,280. -d depth,0. http://tds.hycom.org/thredds/dodsC/FMRC_ESPC-D-V02_uv3z/FMRC_ESPC-D-V02_uv3z_best.ncd -O ../data/FMRC_ESPC-D-V02_uv3z_best_0m.nc4

ncks: INFO nco_cnk_csh_ini() reports chunk cache size = cnk_csh_byt = 16777216 B, # of slots in raw data chunk cache has table = nelemsp = 4133, pre-emption favor fraction = pmp_fvr_frc = 0.75

ncks: INFO Build compiler lacked (or user turned-off) OpenMP support. Code will execute with single thread in Uni-Processor (UP) mode.

ncks: INFO nco_fl_mk_lcl() successfully accessed this file using the DAP protocol

ncks: INFO nco_fl_open() reports nc__open() will request file buffer of default size

ncks: INFO nco_fl_open() reports nc__open() opened file with buffer size = 0 bytes

ncks: INFO nco_fl_open() reports extended filetype of http://tds.hycom.org/thredds/dodsC/FMRC_ESPC-D-V02_uv3z/FMRC_ESPC-D-V02_uv3z_best.ncd is NC_FORMATX_DAP2, mode = 0 (oct) = 0 (dec) = 0000 (hex) 

ncks: INFO nco_fl_open() will not print any more INFO messages if this file is opened again. (Many NCO operators open the same file multiple times when OpenMP is enabled, nco_fl_open() prints INFO messages only the first time because successive messages are usually redundant).

ncks: INFO nco_grp_itr() found group / at level 0

ncks: INFO nco_xtr_mk() reports following groups match sub-setting and regular expressions:

ncks: INFO nco_xtr_mk() reports variable water_u meets additional conditions for variable match with /water_u.

ncks: INFO nco_xtr_mk() reports variable water_v meets additional conditions for variable match with /water_v.

ncks: INFO nco_xtr_mk() reports following variables match sub-setting and regular expressions:

nm_fll=/water_v

nm_fll=/water_u

ncks: CONVENTION File "Conventions" attribute is "CF-1.4, NAVO_netcdf_v1.0"

ncks: DEBUG nco_xtr_cf_var_add() reports nbr_cf = 5,cf_lst[0] = time_run

ncks: DEBUG nco_xtr_cf_var_add() reports nbr_cf = 5,cf_lst[0] = time_run

ncks: DEBUG nco_xtr_cf_var_add() reports nbr_cf = 5,cf_lst[0] = time_run

ncks: DEBUG nco_xtr_cf_var_add() reports nbr_cf = 5,cf_lst[0] = time_run

ncks: nco_fl_out_open() reports sizeof(pid_t) = 4 bytes, pid = 31712, pid_sng_lng = 6 bytes, strlen(pid_sng) = 5 bytes, fl_out_tmp_lng = 59 bytes, strlen(fl_out_tmp) = 58, fl_out_tmp = ../data/FMRC_ESPC-D-V02_uv3z_best_0m.nc4.pid31712.ncks.tmp

ncks: nco_fl_out_open() reports strlen(fl_out_tmp_sys) = 46, fl_out_tmp_sys = ../data/FMRC_ESPC-D-V02_uv3z_best_0m.nc4KShlwX, 

ncks: WARNING nco_mss_val_get() reports that variable time has attribute "missing_value" but not "_FillValue". To comply with netCDF conventions, NCO ignores values that equal the _FillValue attribute when performing arithmetic. Confusingly, values equal to the missing_value should also be neglected. However, it is tedious and (possibly) computationally expensive to check each value against multiple missing values during arithmetic on large variables. So NCO thinks that processing variables with a "missing_value" attribute and no "_FillValue" attribute may produce undesired arithmetic results (i.e., where values that were intended to be neglected were not, in fact, neglected). We suggest you rename all "missing_value" attributes to "_FillValue" or include both "missing_value" and "_FillValue" attributes (with the _same values_) for all variables that have either attribute. Because it is long, this message is only printed once per operator even though multiple variables may have the same attribute configuration. More information on missing values is given at:

http://nco.sf.net/nco.html#mss_val

Examples of renaming attributes are at:

http://nco.sf.net/nco.html#xmp_ncrename

Examples of creating and deleting attributes are at:

http://nco.sf.net/nco.html#xmp_ncatted

ncks: INFO nco_aed_prc() examining variable "Global"

ncks: TIMER Metadata setup and file layout before main loop took    0.07 s

ncks: INFO Moving ../data/FMRC_ESPC-D-V02_uv3z_best_0m.nc4.pid31712.ncks.tmp to ../data/FMRC_ESPC-D-V02_uv3z_best_0m.nc4...done

ncks: TIMER Elapsed clock() time for command is    0.16 s

+ break

+ DAP_URL=http://tds.hycom.org/thredds/dodsC/FMRC_ESPC-D-V02_ts3z/FMRC_ESPC-D-V02_ts3z_best.ncd

+ VARS='-v water_temp'

++ TZ=GMT+00

++ date +%Y-%m-%dT00:00:00Z

+ START_DATE=2025-07-16T00:00:00Z

++ TZ=GMT-144

++ date +%Y-%m-%dT23:00:00Z

+ END_DATE=2025-07-22T23:00:00Z

+ TIMERANGE='-d time,2025-07-16T00:00:00Z,2025-07-22T23:00:00Z'

+ LAT_RANGE='-d lat,20.,35.'

+ LON_RANGE='-d lon,260.,280.'

+ echo 'app1: acquiring 200m data'

app1: acquiring 200m data

+ DEPTH_METERS=200

+ DEPTH='-d depth,200.'

+ OUT_FILE=../data/FMRC_ESPC-D-V02_ts3z_best_200m.nc4

+ true

+ date

Tue Jul 15 21:22:07 CDT 2025

+ ncks -D9 -d time,2025-07-16T00:00:00Z,2025-07-22T23:00:00Z -v water_temp -d lat,20.,35. -d lon,260.,280. -d depth,200. http://tds.hycom.org/thredds/dodsC/FMRC_ESPC-D-V02_ts3z/FMRC_ESPC-D-V02_ts3z_best.ncd -O ../data/FMRC_ESPC-D-V02_ts3z_best_200m.nc4

ncks: INFO nco_cnk_csh_ini() reports chunk cache size = cnk_csh_byt = 16777216 B, # of slots in raw data chunk cache has table = nelemsp = 4133, pre-emption favor fraction = pmp_fvr_frc = 0.75

ncks: INFO Build compiler lacked (or user turned-off) OpenMP support. Code will execute with single thread in Uni-Processor (UP) mode.

ncks: INFO nco_fl_mk_lcl() successfully accessed this file using the DAP protocol

ncks: INFO nco_fl_open() reports nc__open() will request file buffer of default size

ncks: INFO nco_fl_open() reports nc__open() opened file with buffer size = 0 bytes

ncks: INFO nco_fl_open() reports extended filetype of http://tds.hycom.org/thredds/dodsC/FMRC_ESPC-D-V02_ts3z/FMRC_ESPC-D-V02_ts3z_best.ncd is NC_FORMATX_DAP2, mode = 0 (oct) = 0 (dec) = 0000 (hex) 

ncks: INFO nco_fl_open() will not print any more INFO messages if this file is opened again. (Many NCO operators open the same file multiple times when OpenMP is enabled, nco_fl_open() prints INFO messages only the first time because successive messages are usually redundant).

ncks: INFO nco_grp_itr() found group / at level 0

ncks: INFO nco_xtr_mk() reports following groups match sub-setting and regular expressions:

ncks: INFO nco_xtr_mk() reports variable water_temp meets additional conditions for variable match with /water_temp.

ncks: INFO nco_xtr_mk() reports following variables match sub-setting and regular expressions:

nm_fll=/water_temp

ncks: CONVENTION File "Conventions" attribute is "CF-1.4, NAVO_netcdf_v1.0"

ncks: DEBUG nco_xtr_cf_var_add() reports nbr_cf = 5,cf_lst[0] = time_run

ncks: DEBUG nco_xtr_cf_var_add() reports nbr_cf = 5,cf_lst[0] = time_run

ncks: ERROR User-specified coordinate value range 228 <= time <= 395 does not fall within valid coordinate range 6.93285e-310 <= time <= 0

ncks: ERROR Exiting through nco_exit() which will now call exit(EXIT_FAILURE)

+ echo 'ERROR: sleeping for 90 seconds and then trying again...'

ERROR: sleeping for 90 seconds and then trying again...

+ sleep 90

+ true

+ date

Tue Jul 15 21:23:38 CDT 2025

+ ncks -D9 -d time,2025-07-16T00:00:00Z,2025-07-22T23:00:00Z -v water_temp -d lat,20.,35. -d lon,260.,280. -d depth,200. http://tds.hycom.org/thredds/dodsC/FMRC_ESPC-D-V02_ts3z/FMRC_ESPC-D-V02_ts3z_best.ncd -O ../data/FMRC_ESPC-D-V02_ts3z_best_200m.nc4

ncks: INFO nco_cnk_csh_ini() reports chunk cache size = cnk_csh_byt = 16777216 B, # of slots in raw data chunk cache has table = nelemsp = 4133, pre-emption favor fraction = pmp_fvr_frc = 0.75

ncks: INFO Build compiler lacked (or user turned-off) OpenMP support. Code will execute with single thread in Uni-Processor (UP) mode.

ncks: INFO nco_fl_mk_lcl() successfully accessed this file using the DAP protocol

ncks: INFO nco_fl_open() reports nc__open() will request file buffer of default size

ncks: INFO nco_fl_open() reports nc__open() opened file with buffer size = 0 bytes

ncks: INFO nco_fl_open() reports extended filetype of http://tds.hycom.org/thredds/dodsC/FMRC_ESPC-D-V02_ts3z/FMRC_ESPC-D-V02_ts3z_best.ncd is NC_FORMATX_DAP2, mode = 0 (oct) = 0 (dec) = 0000 (hex) 

ncks: INFO nco_fl_open() will not print any more INFO messages if this file is opened again. (Many NCO operators open the same file multiple times when OpenMP is enabled, nco_fl_open() prints INFO messages only the first time because successive messages are usually redundant).

ncks: INFO nco_grp_itr() found group / at level 0

ncks: INFO nco_xtr_mk() reports following groups match sub-setting and regular expressions:

ncks: INFO nco_xtr_mk() reports variable water_temp meets additional conditions for variable match with /water_temp.

ncks: INFO nco_xtr_mk() reports following variables match sub-setting and regular expressions:

nm_fll=/water_temp

ncks: CONVENTION File "Conventions" attribute is "CF-1.4, NAVO_netcdf_v1.0"

ncks: DEBUG nco_xtr_cf_var_add() reports nbr_cf = 5,cf_lst[0] = time_run

ncks: DEBUG nco_xtr_cf_var_add() reports nbr_cf = 5,cf_lst[0] = time_run

ncks: ERROR User-specified coordinate value range 228 <= time <= 395 does not fall within valid coordinate range 6.92689e-310 <= time <= 0

ncks: ERROR Exiting through nco_exit() which will now call exit(EXIT_FAILURE)

+ echo 'ERROR: sleeping for 90 seconds and then trying again...'

ERROR: sleeping for 90 seconds and then trying again...

+ sleep 90

+ true

+ date

Tue Jul 15 21:25:09 CDT 2025

+ ncks -D9 -d time,2025-07-16T00:00:00Z,2025-07-22T23:00:00Z -v water_temp -d lat,20.,35. -d lon,260.,280. -d depth,200. http://tds.hycom.org/thredds/dodsC/FMRC_ESPC-D-V02_ts3z/FMRC_ESPC-D-V02_ts3z_best.ncd -O ../data/FMRC_ESPC-D-V02_ts3z_best_200m.nc4

ncks: INFO nco_cnk_csh_ini() reports chunk cache size = cnk_csh_byt = 16777216 B, # of slots in raw data chunk cache has table = nelemsp = 4133, pre-emption favor fraction = pmp_fvr_frc = 0.75

ncks: INFO Build compiler lacked (or user turned-off) OpenMP support. Code will execute with single thread in Uni-Processor (UP) mode.

ncks: INFO nco_fl_mk_lcl() successfully accessed this file using the DAP protocol

ncks: INFO nco_fl_open() reports nc__open() will request file buffer of default size

ncks: INFO nco_fl_open() reports nc__open() opened file with buffer size = 0 bytes

ncks: INFO nco_fl_open() reports extended filetype of http://tds.hycom.org/thredds/dodsC/FMRC_ESPC-D-V02_ts3z/FMRC_ESPC-D-V02_ts3z_best.ncd is NC_FORMATX_DAP2, mode = 0 (oct) = 0 (dec) = 0000 (hex) 

ncks: INFO nco_fl_open() will not print any more INFO messages if this file is opened again. (Many NCO operators open the same file multiple times when OpenMP is enabled, nco_fl_open() prints INFO messages only the first time because successive messages are usually redundant).

ncks: INFO nco_grp_itr() found group / at level 0

ncks: INFO nco_xtr_mk() reports following groups match sub-setting and regular expressions:

ncks: INFO nco_xtr_mk() reports variable water_temp meets additional conditions for variable match with /water_temp.

ncks: INFO nco_xtr_mk() reports following variables match sub-setting and regular expressions:

nm_fll=/water_temp

ncks: CONVENTION File "Conventions" attribute is "CF-1.4, NAVO_netcdf_v1.0"

ncks: DEBUG nco_xtr_cf_var_add() reports nbr_cf = 5,cf_lst[0] = time_run

ncks: DEBUG nco_xtr_cf_var_add() reports nbr_cf = 5,cf_lst[0] = time_run

ncks: nco_fl_out_open() reports sizeof(pid_t) = 4 bytes, pid = 31728, pid_sng_lng = 6 bytes, strlen(pid_sng) = 5 bytes, fl_out_tmp_lng = 61 bytes, strlen(fl_out_tmp) = 60, fl_out_tmp = ../data/FMRC_ESPC-D-V02_ts3z_best_200m.nc4.pid31728.ncks.tmp

ncks: nco_fl_out_open() reports strlen(fl_out_tmp_sys) = 48, fl_out_tmp_sys = ../data/FMRC_ESPC-D-V02_ts3z_best_200m.nc4ZTQsj4, 

ncks: WARNING nco_mss_val_get() reports that variable time has attribute "missing_value" but not "_FillValue". To comply with netCDF conventions, NCO ignores values that equal the _FillValue attribute when performing arithmetic. Confusingly, values equal to the missing_value should also be neglected. However, it is tedious and (possibly) computationally expensive to check each value against multiple missing values during arithmetic on large variables. So NCO thinks that processing variables with a "missing_value" attribute and no "_FillValue" attribute may produce undesired arithmetic results (i.e., where values that were intended to be neglected were not, in fact, neglected). We suggest you rename all "missing_value" attributes to "_FillValue" or include both "missing_value" and "_FillValue" attributes (with the _same values_) for all variables that have either attribute. Because it is long, this message is only printed once per operator even though multiple variables may have the same attribute configuration. More information on missing values is given at:

http://nco.sf.net/nco.html#mss_val

Examples of renaming attributes are at:

http://nco.sf.net/nco.html#xmp_ncrename

Examples of creating and deleting attributes are at:

http://nco.sf.net/nco.html#xmp_ncatted

ncks: INFO nco_aed_prc() examining variable "Global"

ncks: TIMER Metadata setup and file layout before main loop took    0.06 s

ncks: INFO Moving ../data/FMRC_ESPC-D-V02_ts3z_best_200m.nc4.pid31728.ncks.tmp to ../data/FMRC_ESPC-D-V02_ts3z_best_200m.nc4...done

ncks: TIMER Elapsed clock() time for command is    0.18 s

+ break

+ DAP_URL=http://tds.hycom.org/thredds/dodsC/FMRC_ESPC-D-V02_uv3z/FMRC_ESPC-D-V02_uv3z_best.ncd

+ VARS='-v water_u,water_v'

++ TZ=GMT+00

++ date +%Y-%m-%dT00:00:00Z

+ START_DATE=2025-07-16T00:00:00Z

++ TZ=GMT-144

++ date +%Y-%m-%dT23:00:00Z

+ END_DATE=2025-07-22T23:00:00Z

+ TIMERANGE='-d time,2025-07-16T00:00:00Z,2025-07-22T23:00:00Z'

+ LAT_RANGE='-d lat,20.,35.'

+ LON_RANGE='-d lon,260.,280.'

+ echo 'app1: acquiring 200m data'

app1: acquiring 200m data

+ DEPTH_METERS=200

+ DEPTH='-d depth,200.'

+ OUT_FILE=../data/FMRC_ESPC-D-V02_uv3z_best_200m.nc4

+ true

+ date

Tue Jul 15 21:25:17 CDT 2025

+ ncks -D9 -d time,2025-07-16T00:00:00Z,2025-07-22T23:00:00Z -v water_u,water_v -d lat,20.,35. -d lon,260.,280. -d depth,200. http://tds.hycom.org/thredds/dodsC/FMRC_ESPC-D-V02_uv3z/FMRC_ESPC-D-V02_uv3z_best.ncd -O ../data/FMRC_ESPC-D-V02_uv3z_best_200m.nc4

ncks: INFO nco_cnk_csh_ini() reports chunk cache size = cnk_csh_byt = 16777216 B, # of slots in raw data chunk cache has table = nelemsp = 4133, pre-emption favor fraction = pmp_fvr_frc = 0.75

ncks: INFO Build compiler lacked (or user turned-off) OpenMP support. Code will execute with single thread in Uni-Processor (UP) mode.

ncks: INFO nco_fl_mk_lcl() successfully accessed this file using the DAP protocol

ncks: INFO nco_fl_open() reports nc__open() will request file buffer of default size

ncks: INFO nco_fl_open() reports nc__open() opened file with buffer size = 0 bytes

ncks: INFO nco_fl_open() reports extended filetype of http://tds.hycom.org/thredds/dodsC/FMRC_ESPC-D-V02_uv3z/FMRC_ESPC-D-V02_uv3z_best.ncd is NC_FORMATX_DAP2, mode = 0 (oct) = 0 (dec) = 0000 (hex) 

ncks: INFO nco_fl_open() will not print any more INFO messages if this file is opened again. (Many NCO operators open the same file multiple times when OpenMP is enabled, nco_fl_open() prints INFO messages only the first time because successive messages are usually redundant).

ncks: INFO nco_grp_itr() found group / at level 0

ncks: INFO nco_xtr_mk() reports following groups match sub-setting and regular expressions:

ncks: INFO nco_xtr_mk() reports variable water_u meets additional conditions for variable match with /water_u.

ncks: INFO nco_xtr_mk() reports variable water_v meets additional conditions for variable match with /water_v.

ncks: INFO nco_xtr_mk() reports following variables match sub-setting and regular expressions:

nm_fll=/water_u

nm_fll=/water_v

ncks: CONVENTION File "Conventions" attribute is "CF-1.4, NAVO_netcdf_v1.0"

ncks: DEBUG nco_xtr_cf_var_add() reports nbr_cf = 5,cf_lst[0] = time_run

ncks: DEBUG nco_xtr_cf_var_add() reports nbr_cf = 5,cf_lst[0] = time_run

ncks: DEBUG nco_xtr_cf_var_add() reports nbr_cf = 5,cf_lst[0] = time_run

ncks: DEBUG nco_xtr_cf_var_add() reports nbr_cf = 5,cf_lst[0] = time_run

ncks: nco_fl_out_open() reports sizeof(pid_t) = 4 bytes, pid = 31734, pid_sng_lng = 6 bytes, strlen(pid_sng) = 5 bytes, fl_out_tmp_lng = 61 bytes, strlen(fl_out_tmp) = 60, fl_out_tmp = ../data/FMRC_ESPC-D-V02_uv3z_best_200m.nc4.pid31734.ncks.tmp

ncks: nco_fl_out_open() reports strlen(fl_out_tmp_sys) = 48, fl_out_tmp_sys = ../data/FMRC_ESPC-D-V02_uv3z_best_200m.nc47h554z, 

ncks: WARNING nco_mss_val_get() reports that variable time has attribute "missing_value" but not "_FillValue". To comply with netCDF conventions, NCO ignores values that equal the _FillValue attribute when performing arithmetic. Confusingly, values equal to the missing_value should also be neglected. However, it is tedious and (possibly) computationally expensive to check each value against multiple missing values during arithmetic on large variables. So NCO thinks that processing variables with a "missing_value" attribute and no "_FillValue" attribute may produce undesired arithmetic results (i.e., where values that were intended to be neglected were not, in fact, neglected). We suggest you rename all "missing_value" attributes to "_FillValue" or include both "missing_value" and "_FillValue" attributes (with the _same values_) for all variables that have either attribute. Because it is long, this message is only printed once per operator even though multiple variables may have the same attribute configuration. More information on missing values is given at:

http://nco.sf.net/nco.html#mss_val

Examples of renaming attributes are at:

http://nco.sf.net/nco.html#xmp_ncrename

Examples of creating and deleting attributes are at:

http://nco.sf.net/nco.html#xmp_ncatted

ncks: INFO nco_aed_prc() examining variable "Global"

ncks: TIMER Metadata setup and file layout before main loop took    0.08 s

oc_open: server error retrieving url: code=3 message="Invalid Parameter Exception: DArrayDimension.setProjection: Bad Projection Request: stop >= size: 128:121"ERROR: nco_get_vara() failed to nc_get_vara() variable "water_v"

ERROR NC_EACCESS Access failure

HINT: NC_EACCESS errors signify a problem receiving data from a DAP server. This can occur in multiple ways, including 1) When NCO requests (with nco_var_get()) more data than the server is configured to dispense at one time. A workaround for this might be to request data in smaller amounts at one time. This can be accomplished by accessing hyperslabs or multi-slabs of data as described at http://nco.sf.net/nco.html#mlt. 2) When NCO requests data from a buggy DAP library. The DAP software built into netCDF versions 4.6.2 and 4.6.3 is known to be problematic. The only solution for this would be to use an NCO built with a newer version (at least 4.7.3) of netCDF.

nco_err_exit(): ERROR Short NCO-generated message (usually name of function that triggered error): nco_get_vara()

nco_err_exit(): ERROR Error code is -77. Translation into English with nc_strerror(-77) is "NetCDF: Access failure"

nco_err_exit(): ERROR NCO will now exit with system call exit(EXIT_FAILURE)

+ echo 'ERROR: sleeping for 90 seconds and then trying again...'

ERROR: sleeping for 90 seconds and then trying again...

+ sleep 90

+ true

+ date

Tue Jul 15 21:26:51 CDT 2025

+ ncks -D9 -d time,2025-07-16T00:00:00Z,2025-07-22T23:00:00Z -v water_u,water_v -d lat,20.,35. -d lon,260.,280. -d depth,200. http://tds.hycom.org/thredds/dodsC/FMRC_ESPC-D-V02_uv3z/FMRC_ESPC-D-V02_uv3z_best.ncd -O ../data/FMRC_ESPC-D-V02_uv3z_best_200m.nc4

ncks: INFO nco_cnk_csh_ini() reports chunk cache size = cnk_csh_byt = 16777216 B, # of slots in raw data chunk cache has table = nelemsp = 4133, pre-emption favor fraction = pmp_fvr_frc = 0.75

ncks: INFO Build compiler lacked (or user turned-off) OpenMP support. Code will execute with single thread in Uni-Processor (UP) mode.

ncks: INFO nco_fl_mk_lcl() successfully accessed this file using the DAP protocol

ncks: INFO nco_fl_open() reports nc__open() will request file buffer of default size

ncks: INFO nco_fl_open() reports nc__open() opened file with buffer size = 0 bytes

ncks: INFO nco_fl_open() reports extended filetype of http://tds.hycom.org/thredds/dodsC/FMRC_ESPC-D-V02_uv3z/FMRC_ESPC-D-V02_uv3z_best.ncd is NC_FORMATX_DAP2, mode = 0 (oct) = 0 (dec) = 0000 (hex) 

ncks: INFO nco_fl_open() will not print any more INFO messages if this file is opened again. (Many NCO operators open the same file multiple times when OpenMP is enabled, nco_fl_open() prints INFO messages only the first time because successive messages are usually redundant).

ncks: INFO nco_grp_itr() found group / at level 0

ncks: INFO nco_xtr_mk() reports following groups match sub-setting and regular expressions:

ncks: INFO nco_xtr_mk() reports variable water_u meets additional conditions for variable match with /water_u.

ncks: INFO nco_xtr_mk() reports variable water_v meets additional conditions for variable match with /water_v.

ncks: INFO nco_xtr_mk() reports following variables match sub-setting and regular expressions:

nm_fll=/water_v

nm_fll=/water_u

ncks: CONVENTION File "Conventions" attribute is "CF-1.4, NAVO_netcdf_v1.0"

ncks: DEBUG nco_xtr_cf_var_add() reports nbr_cf = 5,cf_lst[0] = time_run

ncks: DEBUG nco_xtr_cf_var_add() reports nbr_cf = 5,cf_lst[0] = time_run

ncks: DEBUG nco_xtr_cf_var_add() reports nbr_cf = 5,cf_lst[0] = time_run

ncks: DEBUG nco_xtr_cf_var_add() reports nbr_cf = 5,cf_lst[0] = time_run

ncks: nco_fl_out_open() reports sizeof(pid_t) = 4 bytes, pid = 31739, pid_sng_lng = 6 bytes, strlen(pid_sng) = 5 bytes, fl_out_tmp_lng = 61 bytes, strlen(fl_out_tmp) = 60, fl_out_tmp = ../data/FMRC_ESPC-D-V02_uv3z_best_200m.nc4.pid31739.ncks.tmp

ncks: nco_fl_out_open() reports strlen(fl_out_tmp_sys) = 48, fl_out_tmp_sys = ../data/FMRC_ESPC-D-V02_uv3z_best_200m.nc4gxFTOA, 

ncks: WARNING nco_mss_val_get() reports that variable time has attribute "missing_value" but not "_FillValue". To comply with netCDF conventions, NCO ignores values that equal the _FillValue attribute when performing arithmetic. Confusingly, values equal to the missing_value should also be neglected. However, it is tedious and (possibly) computationally expensive to check each value against multiple missing values during arithmetic on large variables. So NCO thinks that processing variables with a "missing_value" attribute and no "_FillValue" attribute may produce undesired arithmetic results (i.e., where values that were intended to be neglected were not, in fact, neglected). We suggest you rename all "missing_value" attributes to "_FillValue" or include both "missing_value" and "_FillValue" attributes (with the _same values_) for all variables that have either attribute. Because it is long, this message is only printed once per operator even though multiple variables may have the same attribute configuration. More information on missing values is given at:

http://nco.sf.net/nco.html#mss_val

Examples of renaming attributes are at:

http://nco.sf.net/nco.html#xmp_ncrename

Examples of creating and deleting attributes are at:

http://nco.sf.net/nco.html#xmp_ncatted

ncks: INFO nco_aed_prc() examining variable "Global"

ncks: TIMER Metadata setup and file layout before main loop took    0.08 s

ncks: INFO Moving ../data/FMRC_ESPC-D-V02_uv3z_best_200m.nc4.pid31739.ncks.tmp to ../data/FMRC_ESPC-D-V02_uv3z_best_200m.nc4...done

ncks: TIMER Elapsed clock() time for command is    0.41 s

+ break

+ set +x

kennethschaudt@MP2019-BigSur scripts % 

[David Aragon]

Don't intend to hijack, but problem appears fixed for me today, queries pass through currently.

Testing with simple matlab ncdisplay

ncdisp('https://tds.hycom.org/thredds/dodsC/FMRC_ESPC-D-V02_uv3z/FMRC_ESPC-D-V02_uv3z_best.ncd')

[Ken Schaudt]

Obtained all requested data at 0m.   At 200m, only received 1/2 of the requested data.  Normally, I would assume that the data are still being transferred from the Navy but .....

Here is the log for the 200m run.

+ DAP_URL=http://tds.hycom.org/thredds/dodsC/FMRC_ESPC-D-V02_ts3z/FMRC_ESPC-D-V02_ts3z_best.ncd

+ VARS='-v water_temp'

++ TZ=GMT+00

++ date +%Y-%m-%dT00:00:00Z

+ START_DATE=2025-07-16T00:00:00Z

++ TZ=GMT-144

++ date +%Y-%m-%dT23:00:00Z

+ END_DATE=2025-07-22T23:00:00Z

+ TIMERANGE='-d time,2025-07-16T00:00:00Z,2025-07-22T23:00:00Z'

+ LAT_RANGE='-d lat,20.,35.'

+ LON_RANGE='-d lon,260.,280.'

+ echo 'app1: acquiring 200m data'

app1: acquiring 200m data

+ DEPTH_METERS=200

+ DEPTH='-d depth,200.'

+ OUT_FILE=../data/FMRC_ESPC-D-V02_ts3z_best_200m.nc4

+ true

+ date

Wed Jul 16 09:22:56 CDT 2025

+ ncks -D9 -d time,2025-07-16T00:00:00Z,2025-07-22T23:00:00Z -v water_temp -d lat,20.,35. -d lon,260.,280. -d depth,200. http://tds.hycom.org/thredds/dodsC/FMRC_ESPC-D-V02_ts3z/FMRC_ESPC-D-V02_ts3z_best.ncd -O ../data/FMRC_ESPC-D-V02_ts3z_best_200m.nc4

ncks: INFO nco_cnk_csh_ini() reports chunk cache size = cnk_csh_byt = 16777216 B, # of slots in raw data chunk cache has table = nelemsp = 4133, pre-emption favor fraction = pmp_fvr_frc = 0.75

ncks: INFO Build compiler lacked (or user turned-off) OpenMP support. Code will execute with single thread in Uni-Processor (UP) mode.

ncks: INFO nco_fl_mk_lcl() successfully accessed this file using the DAP protocol

ncks: INFO nco_fl_open() reports nc__open() will request file buffer of default size

ncks: INFO nco_fl_open() reports nc__open() opened file with buffer size = 0 bytes

ncks: INFO nco_fl_open() reports extended filetype of http://tds.hycom.org/thredds/dodsC/FMRC_ESPC-D-V02_ts3z/FMRC_ESPC-D-V02_ts3z_best.ncd is NC_FORMATX_DAP2, mode = 0 (oct) = 0 (dec) = 0000 (hex) 

ncks: INFO nco_fl_open() will not print any more INFO messages if this file is opened again. (Many NCO operators open the same file multiple times when OpenMP is enabled, nco_fl_open() prints INFO messages only the first time because successive messages are usually redundant).

ncks: INFO nco_grp_itr() found group / at level 0

ncks: INFO nco_xtr_mk() reports following groups match sub-setting and regular expressions:

ncks: INFO nco_xtr_mk() reports variable water_temp meets additional conditions for variable match with /water_temp.

ncks: INFO nco_xtr_mk() reports following variables match sub-setting and regular expressions:

nm_fll=/water_temp

ncks: CONVENTION File "Conventions" attribute is "CF-1.4, NAVO_netcdf_v1.0"

ncks: DEBUG nco_xtr_cf_var_add() reports nbr_cf = 5,cf_lst[0] = time_run

ncks: DEBUG nco_xtr_cf_var_add() reports nbr_cf = 5,cf_lst[0] = time_run

ncks: nco_fl_out_open() reports sizeof(pid_t) = 4 bytes, pid = 1091, pid_sng_lng = 5 bytes, strlen(pid_sng) = 4 bytes, fl_out_tmp_lng = 60 bytes, strlen(fl_out_tmp) = 59, fl_out_tmp = ../data/FMRC_ESPC-D-V02_ts3z_best_200m.nc4.pid1091.ncks.tmp

ncks: nco_fl_out_open() reports strlen(fl_out_tmp_sys) = 48, fl_out_tmp_sys = ../data/FMRC_ESPC-D-V02_ts3z_best_200m.nc4tQlNxw, 

ncks: WARNING nco_mss_val_get() reports that variable time has attribute "missing_value" but not "_FillValue". To comply with netCDF conventions, NCO ignores values that equal the _FillValue attribute when performing arithmetic. Confusingly, values equal to the missing_value should also be neglected. However, it is tedious and (possibly) computationally expensive to check each value against multiple missing values during arithmetic on large variables. So NCO thinks that processing variables with a "missing_value" attribute and no "_FillValue" attribute may produce undesired arithmetic results (i.e., where values that were intended to be neglected were not, in fact, neglected). We suggest you rename all "missing_value" attributes to "_FillValue" or include both "missing_value" and "_FillValue" attributes (with the _same values_) for all variables that have either attribute. Because it is long, this message is only printed once per operator even though multiple variables may have the same attribute configuration. More information on missing values is given at:

http://nco.sf.net/nco.html#mss_val

Examples of renaming attributes are at:

http://nco.sf.net/nco.html#xmp_ncrename

Examples of creating and deleting attributes are at:

http://nco.sf.net/nco.html#xmp_ncatted

ncks: INFO nco_aed_prc() examining variable "Global"

ncks: TIMER Metadata setup and file layout before main loop took    0.06 s

ncks: INFO Moving ../data/FMRC_ESPC-D-V02_ts3z_best_200m.nc4.pid1091.ncks.tmp to ../data/FMRC_ESPC-D-V02_ts3z_best_200m.nc4...done

ncks: TIMER Elapsed clock() time for command is    0.18 s

+ break

+ DAP_URL=http://tds.hycom.org/thredds/dodsC/FMRC_ESPC-D-V02_uv3z/FMRC_ESPC-D-V02_uv3z_best.ncd

+ VARS='-v water_u,water_v'

++ TZ=GMT+00

++ date +%Y-%m-%dT00:00:00Z

+ START_DATE=2025-07-16T00:00:00Z

++ TZ=GMT-144

++ date +%Y-%m-%dT23:00:00Z

+ END_DATE=2025-07-22T23:00:00Z

+ TIMERANGE='-d time,2025-07-16T00:00:00Z,2025-07-22T23:00:00Z'

+ LAT_RANGE='-d lat,20.,35.'

+ LON_RANGE='-d lon,260.,280.'

+ echo 'app1: acquiring 200m data'

app1: acquiring 200m data

+ DEPTH_METERS=200

+ DEPTH='-d depth,200.'

+ OUT_FILE=../data/FMRC_ESPC-D-V02_uv3z_best_200m.nc4

+ true

+ date

Wed Jul 16 09:23:00 CDT 2025

+ ncks -D9 -d time,2025-07-16T00:00:00Z,2025-07-22T23:00:00Z -v water_u,water_v -d lat,20.,35. -d lon,260.,280. -d depth,200. http://tds.hycom.org/thredds/dodsC/FMRC_ESPC-D-V02_uv3z/FMRC_ESPC-D-V02_uv3z_best.ncd -O ../data/FMRC_ESPC-D-V02_uv3z_best_200m.nc4

ncks: INFO nco_cnk_csh_ini() reports chunk cache size = cnk_csh_byt = 16777216 B, # of slots in raw data chunk cache has table = nelemsp = 4133, pre-emption favor fraction = pmp_fvr_frc = 0.75

ncks: INFO Build compiler lacked (or user turned-off) OpenMP support. Code will execute with single thread in Uni-Processor (UP) mode.

ncks: INFO nco_fl_mk_lcl() successfully accessed this file using the DAP protocol

ncks: INFO nco_fl_open() reports nc__open() will request file buffer of default size

ncks: INFO nco_fl_open() reports nc__open() opened file with buffer size = 0 bytes

ncks: INFO nco_fl_open() reports extended filetype of http://tds.hycom.org/thredds/dodsC/FMRC_ESPC-D-V02_uv3z/FMRC_ESPC-D-V02_uv3z_best.ncd is NC_FORMATX_DAP2, mode = 0 (oct) = 0 (dec) = 0000 (hex) 

ncks: INFO nco_fl_open() will not print any more INFO messages if this file is opened again. (Many NCO operators open the same file multiple times when OpenMP is enabled, nco_fl_open() prints INFO messages only the first time because successive messages are usually redundant).

ncks: INFO nco_grp_itr() found group / at level 0

ncks: INFO nco_xtr_mk() reports following groups match sub-setting and regular expressions:

ncks: INFO nco_xtr_mk() reports variable water_u meets additional conditions for variable match with /water_u.

ncks: INFO nco_xtr_mk() reports variable water_v meets additional conditions for variable match with /water_v.

ncks: INFO nco_xtr_mk() reports following variables match sub-setting and regular expressions:

nm_fll=/water_u

nm_fll=/water_v

ncks: CONVENTION File "Conventions" attribute is "CF-1.4, NAVO_netcdf_v1.0"

ncks: DEBUG nco_xtr_cf_var_add() reports nbr_cf = 5,cf_lst[0] = time_run

ncks: DEBUG nco_xtr_cf_var_add() reports nbr_cf = 5,cf_lst[0] = time_run

ncks: DEBUG nco_xtr_cf_var_add() reports nbr_cf = 5,cf_lst[0] = time_run

ncks: DEBUG nco_xtr_cf_var_add() reports nbr_cf = 5,cf_lst[0] = time_run

ncks: nco_fl_out_open() reports sizeof(pid_t) = 4 bytes, pid = 1097, pid_sng_lng = 5 bytes, strlen(pid_sng) = 4 bytes, fl_out_tmp_lng = 60 bytes, strlen(fl_out_tmp) = 59, fl_out_tmp = ../data/FMRC_ESPC-D-V02_uv3z_best_200m.nc4.pid1097.ncks.tmp

ncks: nco_fl_out_open() reports strlen(fl_out_tmp_sys) = 48, fl_out_tmp_sys = ../data/FMRC_ESPC-D-V02_uv3z_best_200m.nc4QBzKw8, 

ncks: WARNING nco_mss_val_get() reports that variable time has attribute "missing_value" but not "_FillValue". To comply with netCDF conventions, NCO ignores values that equal the _FillValue attribute when performing arithmetic. Confusingly, values equal to the missing_value should also be neglected. However, it is tedious and (possibly) computationally expensive to check each value against multiple missing values during arithmetic on large variables. So NCO thinks that processing variables with a "missing_value" attribute and no "_FillValue" attribute may produce undesired arithmetic results (i.e., where values that were intended to be neglected were not, in fact, neglected). We suggest you rename all "missing_value" attributes to "_FillValue" or include both "missing_value" and "_FillValue" attributes (with the _same values_) for all variables that have either attribute. Because it is long, this message is only printed once per operator even though multiple variables may have the same attribute configuration. More information on missing values is given at:

http://nco.sf.net/nco.html#mss_val

Examples of renaming attributes are at:

http://nco.sf.net/nco.html#xmp_ncrename

Examples of creating and deleting attributes are at:

http://nco.sf.net/nco.html#xmp_ncatted

ncks: INFO nco_aed_prc() examining variable "Global"

ncks: TIMER Metadata setup and file layout before main loop took    0.07 s

ncks: INFO Moving ../data/FMRC_ESPC-D-V02_uv3z_best_200m.nc4.pid1097.ncks.tmp to ../data/FMRC_ESPC-D-V02_uv3z_best_200m.nc4...done

ncks: TIMER Elapsed clock() time for command is    0.16 s

+ break

+ set +x

[Ken Schaudt]

Appears to be working.  Got the requested data at all levels for the requested time.  

Thanks for the help Mike!

[Michael McDonald]

Ken,

Thanks for the detailed command output. I think that I located the issue. There was one server that had a stuck FMRC and was not updating even when a trigger was sent to it (it was stuck on 2025-07-10). So now we are running a THREDDS catalog reinit when new data arrives to (hopefully) properly refresh the THREDDS servers FMRC catalogs. We also now have nagios alerts in place looking at the "runs" for each aggregation and alerting when yesterday's date is not found in the list. 

This error helped pinpoint the issue, as you were asking for a date that should have been present and was not.

ncks: ERROR User-specified coordinate value range 228 <= time <= 395 does not fall within valid coordinate range 6.93285e-310 <= time <= 0

Let us know if this error returns in the future.