add description of CONUS404 changed variables

_sources/dataset_access/README.md

@@ -4,6 +4,8 @@ This section contains notebooks that demonstrate how to access and perform basic
 
 In the CONUS404 intake sub-catalog (see [here](../dataset_catalog/README.md) for an explainer of our intake data catalog), you will see entries for four CONUS404 datasets: conus404-hourly, conus404-daily, conus404-monthly, and conus404-daily-diagnostic data. Each of these datasets is duplicated in three different storage locations (as the [intake catalog section](../dataset_catalog/README.md) also describes). The conus404-hourly data is a subset of the wrfout model output and conus404-daily-diagnostic is a subset from the wrfxtrm model output, both of which are described in the official [CONUS404 data release](https://doi.org/10.5066/P9PHPK4F). We also have conus404-daily and conus404-monthly files, which are just resampled from the conus404-hourly data.
 
+**Please note that the values in the ACLWDNB, ACLWUPB, ACSWDNB, ACSWDNT, and ACSWUPB variables available in the zarr store differ from the original model output.** These variables have been re-calculated to reflect the accumulated value since the model start, as directed in the WRF manual. An attribute has been added to each of these variables in the zarr store to denote the accumulation period for the variable. 
+
 We currently have five notebooks to help demonstrate how to work with these datasets in a python workflow:
 - [Explore CONUS404 Dataset](./conus404_explore.ipynb): opens the CONUS404 dataset, loads and plots the entire spatial 
    domain of a specified variable at a specfic time step, and loads and plots a time series of a variable at a specified coordinate pair.

dataset_access/README.html

@@ -401,6 +401,7 @@ <h1>CONUS404 Access</h1>
 <h1>CONUS404 Access<a class="headerlink" href="#conus404-access" title="Permalink to this heading">#</a></h1>
 <p>This section contains notebooks that demonstrate how to access and perform basic data manipulation for the <a class="reference external" href="https://doi.org/10.5066/P9PHPK4F">CONUS404 dataset</a>.</p>
 <p>In the CONUS404 intake sub-catalog (see <a class="reference internal" href="../dataset_catalog/README.html"><span class="doc std std-doc">here</span></a> for an explainer of our intake data catalog), you will see entries for four CONUS404 datasets: conus404-hourly, conus404-daily, conus404-monthly, and conus404-daily-diagnostic data. Each of these datasets is duplicated in three different storage locations (as the <a class="reference internal" href="../dataset_catalog/README.html"><span class="doc std std-doc">intake catalog section</span></a> also describes). The conus404-hourly data is a subset of the wrfout model output and conus404-daily-diagnostic is a subset from the wrfxtrm model output, both of which are described in the official <a class="reference external" href="https://doi.org/10.5066/P9PHPK4F">CONUS404 data release</a>. We also have conus404-daily and conus404-monthly files, which are just resampled from the conus404-hourly data.</p>
+<p><strong>Please note that the values in the ACLWDNB, ACLWUPB, ACSWDNB, ACSWDNT, and ACSWUPB variables available in the zarr store differ from the original model output.</strong> These variables have been re-calculated to reflect the accumulated value since the model start, as directed in the WRF manual. An attribute has been added to each of these variables in the zarr store to denote the accumulation period for the variable.</p>
 <p>We currently have five notebooks to help demonstrate how to work with these datasets in a python workflow:</p>
 <ul class="simple">
 <li><p><a class="reference internal" href="conus404_explore.html"><span class="doc std std-doc">Explore CONUS404 Dataset</span></a>: opens the CONUS404 dataset, loads and plots the entire spatial