Snow fraction obs converter documentation

Open
#531 2 comments 0 reactions 1 assignee View on GitHub

@braczka is already working on this.

Since Aug 23, 2023.

Assessment

This issue has not been assessed yet.

Description

Discussion Documentation obs_converters

The snow fraction obs converter documentation is incomplete. This applies for both snow_to_obs.f90 (text file) and snow_to_obs_netcdf.f90 (netcdf file). Although it appears both converters are meant to operate on the same data, the original source data formatting (HDF-EOS) presents problems, requiring a 2 step conversion to text or netcdf formatting prior to using the main converters.

At the very least the documentation needs to identify the source data and scripting used for the 1st conversion step.

It seems the direct conversion of HDF-EOS format to obs.seq is a common challenge for DART converters very similar to what is described for the AMSU/AIR converters., in which an incompatibility exists between HDF-EOS and HDF5, necessitating a 2-step conversion. In that case the HDF-EOS tools scripting is used to convert to netcdf formatting.

These HDF-EOS converters could very well be used for the snow fraction obs converter as well, but this needs to be demonstrated and documented. Also, it is unclear if the HDF5 and HDF-EOS incompatibility issue for the AMSU converter applies to the snow converters. The AMSU converter obs_seq files use the RTTOV forward operators (which require HDF5) whereas the snow converters do not.

Given we currently have collaborators working with SNODAS SWE (snow water equivalent) obs converters its a good time to get our snow fraction converters sorted out.

Dominant language
Fortran
Stars
263
Forks
182
Avg merge
11d 12h
Merged PRs (30d)
7

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from NCAR/DART

All issues in NCAR/DART

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.