NCCHECKER(1)
π NCCHECKER(1) π
okay bestie, welcome to the manual page for ncchecker, living in section 1 (General Commands Manual) of your friendly neighbourhood Unix man pages β¨ she's the netCDF Compliance Checker and she is THAT girl π
πΈ NAME πΈ
ncchecker β netCDF Compliance Checker π¦
β¨ SYNTAX β¨
ncchecker [-d dbg_lvl] [-i drc_in] [--tests= tst_lst] [-x] [-v var_lst]
[--version ] input-files
π DESCRIPTION π
so basically, ncchecker goes through your files and checks them for compliance with best practices rules and recommendations from various data and metadata standards bodies π these include the Climate & Forecast (CF) Metadata Conventions and the NASA Dataset Interoperability Working Group (DIWG) recommendations. no cap, it's giving rigorous.
here's the tea on how it works: it reads input-files from stdin, or the command, performs the checks you asked for in the tests option β and if you didn't ask for any, bestie, it performs all of them, she's an overachiever π β and then writes the results to stdout π
some standard NCO options are supported too, including:
- bumping the verbosity level with
[-D dbg_lvl]π₯ - excluding variables with
[-x]π - variable subsetting with
[-v var_lst]π - printing the version with
[--version]β
and the output? it contains counts of the location and number of failed tests, or it literally just prints "SUCCESS" for tests with no failures π«Ά iconic behaviour honestly.
π AUTHOR π
NCO manual pages written by Charlie Zender. we love a legend π
π REPORTING BUGS π
found a bug? report it to <http://sf.net/bugs/?group_id=3331> π (yes, we want to know, fr fr)
π COPYRIGHT π
Copyright Β© 2023-present Charlie Zender
This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
bestie that's the legal way of saying "she's free, but if she breaks, that's on you" π
π¦ SEE ALSO π¦
The full documentation for NCO is maintained as a Texinfo manual called the NCO Users Guide. Because NCO is mathematical in nature, the documentation includes TeX-intensive portions not viewable on character-based displays π hence the only complete and authoritative versions of the NCO Users Guide are the PDF (recommended), DVI, and Postscript versions at:
- <http://nco.sf.net/nco.pdf> π
- <http://nco.sf.net/nco.dvi> π
- <http://nco.sf.net/nco.ps> π
HTML and XML versions are available at:
- <http://nco.sf.net/nco.html> β¨
- <http://nco.sf.net/nco.xml> β¨
If the info and NCO programs are properly installed at your site, the command
info nco
should give you access to the complete manual, except for the TeX-intensive portions π§
and here's the whole squad, alphabetically slaying in their own man pages:
ncap(1), ncap2(1), ncatted(1), ncbo(1), ncclimo(1), nces(1), ncecat(1), ncflint(1), ncz2psx(1), ncks(1), nco(1), ncpdq(1), ncra(1), ncrcat(1), ncremap(1), ncrename(1), ncwa(1) π
π HOMEPAGE π
The NCO homepage at <http://nco.sf.net> contains more information. go be nosy, iykyk π
and that's a wrap on NCCHECKER(1), section 1 of the General Commands Manual π stay compliant, stay iconic, and remember: she checks the files so you don't have to π
πβ¨
π¦ where this page comes from
- debian trixie: nco 5.3.3-1 Β· BSD-3-Clause
- epel 10: nco 5.3.3-1.el10_1 Β· BSD-3-Clause
- fedora 43: nco 5.3.3-2.fc43 Β· BSD-3-Clause
- fedora 44: nco 5.3.6-1.fc44 Β· BSD-3-Clause
- fedora 44: nco 5.3.7-1.fc44 Β· BSD-3-Clause
- nixos 26.05: nco 5.3.2
- nixpkgs unstable: nco 5.4.0
- opensuse-leap 16.0: nco 5.3.4-bp160.1.2 Β· BSD-3-Clause
- opensuse-leap 16.0: nco 5.3.4-bp160.1.2 Β· BSD-3-Clause
- opensuse-leap 16.0: nco 5.3.4-bp160.1.2 Β· BSD-3-Clause
- ubuntu questing: nco 5.3.3-1
- ubuntu resolute: nco 5.3.6-1 Β· BSD-3-Clause
- ubuntu stonking: nco 5.3.9-1 Β· BSD-3-Clause
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash on : a language model's rewrite of the original, under its terms