Am able to apparently obtain single point data in CSV format but the
download of the NCD files fail. Most recent log is shown below.
Best,
Ken
Last login: Sun Mar 24 22:21:43 on ttys000
(base) cMP12:~ schaudt$ cd
/volumes/sg8gb/users/schaudt/r_projects/roffs_sus/scripts
(base) cMP12:scripts schaudt$ sh
/Volumes/SG8GB/Users/schaudt/R_Projects/ROFFS_SUS/scripts/GOMlores.sh
+ NCKS=ncks
+ DEBUG_LVL=-D0
+ WGET=wget
+ WGET_FLAGS=
+ RETRY_SLEEP=90
+
NCSS_BASE_URL=
http://ncss.hycom.org/thredds/ncss/GLBy0.08/expt_93.0/FMRC/GLBy0.08_930_FMRC_best.ncd
+ VARS=var=salinity,water_temp,water_u,water_v
+ LAT='&latitude=26.65696083'
+ LON='&longitude=-91.57923286'
++ TZ=GMT+00
++ date +%Y-%m-%dT00:00:00Z
+ TIME_START='&time_start=2024-03-25T00:00:00Z'
++ TZ=GMT-167
++ date +%Y-%m-%dT23:00:00Z
+ TIME_END='&time_end=2024-04-01T23:00:00Z'
+ ACCEPT='&accept=csv'
+
NCSS_FULL_URL='
http://ncss.hycom.org/thredds/ncss/GLBy0.08/expt_93.0/FMRC/GLBy0.08_930_FMRC_best.ncd?var=salinity,water_temp,water_u,water_v&latitude=26.65696083&longitude=-91.57923286&time_start=2024-03-25T00:00:00Z&time_end=2024-04-01T23:00:00Z&accept=csv'
+ echo 'Site specific forecasts of conditions: acquiring data'
Site specific forecasts of conditions: acquiring data
+ OUT_FILE=../data/WR515.csv
+ true
+ date
Sun Mar 24 22:33:55 CDT 2024
+ wget
'
http://ncss.hycom.org/thredds/ncss/GLBy0.08/expt_93.0/FMRC/GLBy0.08_930_FMRC_best.ncd?var=salinity,water_temp,water_u,water_v&latitude=26.65696083&longitude=-91.57923286&time_start=2024-03-25T00:00:00Z&time_end=2024-04-01T23:00:00Z&accept=csv'
-O ../data/WR515.csv
--2024-03-24 22:33:55--
http://ncss.hycom.org/thredds/ncss/GLBy0.08/expt_93.0/FMRC/GLBy0.08_930_FMRC_best.ncd?var=salinity,water_temp,water_u,water_v&latitude=26.65696083&longitude=-91.57923286&time_start=2024-03-25T00:00:00Z&time_end=2024-04-01T23: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|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: unspecified [text/plain]
Saving to: ‘../data/WR515.csv’
../data/WR515.csv [ <=> ]
232.16K 1.24KB/s in 2m 49s
2024-03-24 22:36:51 (1.38 KB/s) - ‘../data/WR515.csv’ saved [237731]
+ break
+
NCSS_BASE_URL=
http://ncss.hycom.org/thredds/ncss/GLBy0.08/expt_93.0/FMRC/GLBy0.08_930_FMRC_best.ncd
+ VARS=var=salinity,water_temp,water_u,water_v
+ LAT='&latitude=28.040'
+ LON='&longitude=-89.080'
++ TZ=GMT+00
++ date +%Y-%m-%dT00:00:00Z
+ TIME_START='&time_start=2024-03-25T00:00:00Z'
++ TZ=GMT-167
++ date +%Y-%m-%dT23:00:00Z
+ TIME_END='&time_end=2024-04-01T23:00:00Z'
+ ACCEPT='&accept=csv'
+
NCSS_FULL_URL='
http://ncss.hycom.org/thredds/ncss/GLBy0.08/expt_93.0/FMRC/GLBy0.08_930_FMRC_best.ncd?var=salinity,water_temp,water_u,water_v&latitude=28.040&longitude=-89.080&time_start=2024-03-25T00:00:00Z&time_end=2024-04-01T23: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
Sun Mar 24 22:36:51 CDT 2024
+ wget
'
http://ncss.hycom.org/thredds/ncss/GLBy0.08/expt_93.0/FMRC/GLBy0.08_930_FMRC_best.ncd?var=salinity,water_temp,water_u,water_v&latitude=28.040&longitude=-89.080&time_start=2024-03-25T00:00:00Z&time_end=2024-04-01T23:00:00Z&accept=csv'
-O ../data/Titan.csv
--2024-03-24 22:36:51--
http://ncss.hycom.org/thredds/ncss/GLBy0.08/expt_93.0/FMRC/GLBy0.08_930_FMRC_best.ncd?var=salinity,water_temp,water_u,water_v&latitude=28.040&longitude=-89.080&time_start=2024-03-25T00:00:00Z&time_end=2024-04-01T23: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|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: unspecified [text/plain]
Saving to: ‘../data/Titan.csv’
../data/Titan.csv [ <=> ] 205.03K 5.59KB/s in 39s
2024-03-24 22:37:36 (5.32 KB/s) - ‘../data/Titan.csv’ saved [209952]
+ break
+
http://tds.hycom.org/thredds/dodsC/GLBy0.08/expt_93.0/FMRC/runs/GLBy0.08_930_FMRC_RUN_2023-01-31T12:00:00Z
/Volumes/SG8GB/Users/schaudt/R_Projects/ROFFS_SUS/scripts/GOMlores.sh:
line 71:
http://tds.hycom.org/thredds/dodsC/GLBy0.08/expt_93.0/FMRC/runs/GLBy0.08_930_FMRC_RUN_2023-01-31T12:00:00Z:
No such file or directory
+
DAP_URL=
http://tds.hycom.org/thredds/dodsC/GLBy0.08/expt_93.0/FMRC/GLBy0.08_930_FMRC_best.ncd
+ VARS='-v water_temp,water_u,water_v'
++ TZ=GMT+00
++ date +%Y-%m-%dT00:00:00Z
+ START_DATE=2024-03-25T00:00:00Z
++ TZ=GMT-144
++ date +%Y-%m-%dT23:00:00Z
+ END_DATE=2024-03-31T23:00:00Z
+ TIMERANGE='-d time,2024-03-25T00:00:00Z,2024-03-31T23: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/GLBy0.08_930_FMRC_tuv_0m.nc4
+ true
+ date
Sun Mar 24 22:37:36 CDT 2024
+ ncks -D0 -d time,2024-03-25T00:00:00Z,2024-03-31T23:00:00Z -v
water_temp,water_u,water_v -d lat,20.,35. -d lon,260.,280. -d depth,0.
http://tds.hycom.org/thredds/dodsC/GLBy0.08/expt_93.0/FMRC/GLBy0.08_930_FMRC_best.ncd
-O ../data/GLBy0.08_930_FMRC_tuv_0m.nc4
oc_open: server error retrieving url: code=? message="Error {
code = 500;
message = "java.io.IOException: Stale file handle";
}"ERROR: nco_get_vara() failed to nc_get_vara() variable "water_temp"
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 -90. Translation into English with
nc_strerror(-90) is "NetCDF: file not found"
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
Sun Mar 24 22:39:08 CDT 2024
+ ncks -D0 -d time,2024-03-25T00:00:00Z,2024-03-31T23:00:00Z -v
water_temp,water_u,water_v -d lat,20.,35. -d lon,260.,280. -d depth,0.
http://tds.hycom.org/thredds/dodsC/GLBy0.08/expt_93.0/FMRC/GLBy0.08_930_FMRC_best.ncd
-O ../data/GLBy0.08_930_FMRC_tuv_0m.nc4
ncks: INFO DAP-access to
http://tds.hycom.org/thredds/dodsC/GLBy0.08/expt_93.0/FMRC/GLBy0.08_930_FMRC_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/GLBy0.08/expt_93.0/FMRC/GLBy0.08_930_FMRC_best.ncd
on remote filesystem, using local file
hredds/dodsC/GLBy0.08/expt_93.0/FMRC/GLBy0.08_930_FMRC_best.ncd instead
ERROR: nco__open() unable to open file
"thredds/dodsC/GLBy0.08/expt_93.0/FMRC/GLBy0.08_930_FMRC_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
2. An NCO operator linked only to the classic netCDF3 library attempts
to read netCDF4 (or HDF5) files. However, this executable seems to have
been built with the capability to manipulate netCDF4 files, so it is
unlikely that this command failed only because the input datasets are
netCDF4 format. Something else is going wrong.
3. NCO attempts to read other filetypes (HDF4, HDF-EOS2, PnetCDF/CDF5)
for which support must be (but was not) enabled at netCDF build-time.
NCO can access HDF4 files if NCO is first re-linked to a version of
netCDF configured with the --enable-hdf4 option. This is a non-standard
netCDF build option described here:
http://www.unidata.ucar.edu/software/netcdf/docs/build_hdf4.html. NCO
can access PnetCDF/CDF5 files if NCO is first re-linked to netCDF
version 4.4.0 or later.
4. NCO attempts to utilize diskless (i.e., RAM) files. In this case
remove the diskless switches (e.g., --ram or --diskless) and then
re-issue the command.
5. Access to a DAP URL fails, and the backup method of downloading the
URL using wget obtains a data aggregation file (e.g., a .ncml file)
instead of an actual netCDF file. In this case the problem is with the
DAP server or URL.
nco_err_exit(): ERROR Short NCO-generated message (usually name of
function that triggered error): nco__open()
nco_err_exit(): ERROR Error code is -51. Translation into English with
nc_strerror(-51) is "NetCDF: Unknown file format"
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