Time Zone Conversion in Forcing Data and Model Output

[qiaochenglong]

My forcing and observation data are both in local time (UTC+8). During the model driving process, I convert them to UTC. Should the output be converted back to local time, or is it fine to keep it in UTC? What would be the consequences if the model does not perform time zone conversion during the driving process?

[cenlinhe]

The forcing data have to be in UTC, otherwise the model results will be wrong because the solar zenith angle calculation is based on UTC. It is fine to keep the model results in UTC. When you plot figures, keep in mind that the model output data are in UTC.

[qiaochenglong]

I want to obtain simulated multi-layer soil moisture data. The SOIL_M (volumetric soil moisture) you mentioned only provides a single-layer soil moisture value.

[tslin2]

SOIL_M has four layers from the top of the soil layer to the bottom of soil layer in the third dimension, soil_layers_stag
(Time, south_north, soil_layers_stag, west_east)

[qiaochenglong]

Can you explain the process in more detail? I still don't fully understand. Especially in my output results, SOIL_M only has a single data value.

[tslin2]

How do you get this excel file?
if you can use ncdump -h, there are variables and dimensions in the output NetCDF file

https://www.unidata.ucar.edu/software/netcdf/workshops/2011/utilities/NcdumpExamples.html

[qiaochenglong]

Thank you very much for your guidance. I overlooked the dimension issue when exporting the NetCDF data to a CSV file.