Hi Carol,
re:
> Ok, thanks for helping with my curiosity!
No worries.
re:
> The output of ldd `which ncdump`
>
> address@hidden:/mnt/satellite/mcidas$ ldd `which ncdump`
> linux-vdso.so.1 => (0x00007fff79b56000)
> libnetcdf.so.7 => /usr/lib64/libnetcdf.so.7 (0x000000375b200000)
> libhdf5.so.8 => /usr/lib64/libhdf5.so.8 (0x00007f8b38edd000)
> libdl.so.2 => /lib64/libdl.so.2 (0x0000003759e00000)
> libm.so.6 => /lib64/libm.so.6 (0x0000003759a00000)
> libz.so.1 => /lib64/libz.so.1 (0x000000375aa00000)
> libc.so.6 => /lib64/libc.so.6 (0x0000003759600000)
> libcurl.so.4 => /usr/lib64/libcurl.so.4 (0x000000375d200000)
> librt.so.1 => /lib64/librt.so.1 (0x000000375a600000)
> /lib64/ld-linux-x86-64.so.2 (0x0000557fc83a0000)
> libidn.so.11 => /lib64/libidn.so.11 (0x000000375ca00000)
> libldap-2.4.so.2 => /lib64/libldap-2.4.so.2 (0x000000375c200000)
> libgssapi_krb5.so.2 => /lib64/libgssapi_krb5.so.2 (0x0000003763a00000)
> libkrb5.so.3 => /lib64/libkrb5.so.3 (0x0000003763200000)
> libk5crypto.so.3 => /lib64/libk5crypto.so.3 (0x0000003762e00000)
> libcom_err.so.2 => /lib64/libcom_err.so.2 (0x0000003761600000)
> libssl3.so => /usr/lib64/libssl3.so (0x0000003765600000)
> libsmime3.so => /usr/lib64/libsmime3.so (0x0000003764a00000)
> libnss3.so => /usr/lib64/libnss3.so (0x000000375fa00000)
> libnssutil3.so => /usr/lib64/libnssutil3.so (0x000000375fe00000)
> libplds4.so => /lib64/libplds4.so (0x000000375ee00000)
> libplc4.so => /lib64/libplc4.so (0x000000375e600000)
> libnspr4.so => /lib64/libnspr4.so (0x000000375ea00000)
> libpthread.so.0 => /lib64/libpthread.so.0 (0x000000375a200000)
> libssh2.so.1 => /usr/lib64/libssh2.so.1 (0x000000375ce00000)
> liblber-2.4.so.2 => /lib64/liblber-2.4.so.2 (0x000000375c600000)
> libresolv.so.2 => /lib64/libresolv.so.2 (0x000000375b600000)
> libsasl2.so.2 => /usr/lib64/libsasl2.so.2 (0x000000375be00000)
> libkrb5support.so.0 => /lib64/libkrb5support.so.0 (0x0000003761a00000)
> libkeyutils.so.1 => /lib64/libkeyutils.so.1 (0x0000003761e00000)
> libssl.so.10 => /usr/lib64/libssl.so.10 (0x0000003764600000)
> libcrypto.so.10 => /usr/lib64/libcrypto.so.10 (0x0000003762600000)
> libcrypt.so.1 => /lib64/libcrypt.so.1 (0x000000375f200000)
> libselinux.so.1 => /lib64/libselinux.so.1 (0x000000375ae00000)
> libfreebl3.so => /lib64/libfreebl3.so (0x000000375e200000)
Hmm... I was expecting to see an undefined reference to a shared library,
but I don't see anything unusual about this listing other than it being
rather long.
As a comparison, here is 'ldd' output for the 'ncdump' that gets built
and installed as part of McIDAS:
% which ncdump
/home/mcidas/bin/ncdump
% ldd `which ncdump`
linux-vdso.so.1 => (0x00007fff79548000)
libnetcdf.so.7 =>
/home/mcidas/mcidas2018/netcdf/liblib/.libs/libnetcdf.so.7 (0x00007f76a7fc9000)
libhdf5.so.8 => /home/mcidas/mcidas2018/hdf5/src/.libs/libhdf5.so.8
(0x00007f76a7aff000)
libdl.so.2 => /lib64/libdl.so.2 (0x0000003cf1e00000)
libm.so.6 => /lib64/libm.so.6 (0x0000003cf2600000)
libz.so.1 => /lib64/libz.so.1 (0x0000003cf2a00000)
libc.so.6 => /lib64/libc.so.6 (0x0000003cf1600000)
librt.so.1 => /lib64/librt.so.1 (0x0000003cf2200000)
/lib64/ld-linux-x86-64.so.2 (0x000055941dbe9000)
Have you tried running the version of 'ncdump' that gets built as part
of a McIDAS installation? If yes, what are/were the results?
re: large and consistently sized netCDF output files; wrong?
> Yes, I think this is incorrect. When I create area files for meteosat, the
> file sizes are all different for all the bands.
We'll know more when you can do an 'ncdump' on the files you are creating.
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: LSJ-196213
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.
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.