commit 67fc88c3fc89f43e32417dacd1b547d98d1dcf9d
parent a06a68446eddaedc72394b85fdfdff4ca7f3e46e
Author: Vincent Forest <vincent.forest@meso-star.com>
Date: Sat, 4 Oct 2025 11:02:38 +0200
htrdr-atmosphere: exemple of the les2htcp command
Give the command line used to convert a NetCDF file, available for
download, into an htcp file, taking into account the spatial resolution
of the NetCDF file.
Diffstat:
1 file changed, 10 insertions(+), 1 deletion(-)
diff --git a/htrdr/htrdr-atmosphere-netcdf.md.in b/htrdr/htrdr-atmosphere-netcdf.md.in
@@ -9,12 +9,21 @@ developed to transform this data into the cloud file format required by
- DZVAR.1.ARMCU.008.diaKCL.nc
[[xz](downloads/DZVAR.1.ARMCU.008.diaKCL.nc.xz)]
[[pgp](downloads/DZVAR.1.ARMCU.008.diaKCL.nc.xz.sig)]
-
+
These NetCDF files illustrate what a user's data might look like,
produced by a specific toolchain, saved in a community file format, and
finally converted by an intermediate tool (in this case les2htcp)
into the input file format for htrdr-atmosphere.
+For example, the spatial unit of DZVAR clouds is the kilometer (this can
+be verified using the NetCDF tool `ncdump`).
+So, to convert its NetCDF file to htcp format, simply enter the
+following [les2htcp](man/man1/les2htcp.1.html) command:
+
+ les2htcp -m 1000 \
+ -i DZVAR.1.ARMCU.008.diaKCL.nc \
+ -o DZVAR.1.ARMCU.008.diaKCL.htcp
+
These files serve to illustrate htrdr's agnosticism to external tool
chains through file formats in which the user transforms their input
data to run htrdr.