<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE article PUBLIC "-//NLM//DTD Journal Publishing with OASIS Tables v3.0 20080202//EN" "journalpub-oasis3.dtd">
<article xmlns:xlink="http://www.w3.org/1999/xlink" xmlns:mml="http://www.w3.org/1998/Math/MathML" xmlns:oasis="http://docs.oasis-open.org/ns/oasis-exchange/table" xml:lang="en" dtd-version="3.0">
  <front>
    <journal-meta><journal-id journal-id-type="publisher">HESS</journal-id><journal-title-group>
    <journal-title>Hydrology and Earth System Sciences</journal-title>
    <abbrev-journal-title abbrev-type="publisher">HESS</abbrev-journal-title><abbrev-journal-title abbrev-type="nlm-ta">Hydrol. Earth Syst. Sci.</abbrev-journal-title>
  </journal-title-group><issn pub-type="epub">1607-7938</issn><publisher>
    <publisher-name>Copernicus Publications</publisher-name>
    <publisher-loc>Göttingen, Germany</publisher-loc>
  </publisher></journal-meta>
    <article-meta>
      <article-id pub-id-type="doi">10.5194/hess-25-2599-2021</article-id><title-group><article-title>A wavelet-based approach to streamflow event identification <?xmltex \hack{\break}?> and modeled timing error evaluation</article-title><alt-title>A wavelet-based approach to streamflow event identification</alt-title>
      </title-group><?xmltex \runningtitle{A wavelet-based approach to streamflow event identification}?><?xmltex \runningauthor{E.~Towler and J.~L.~McCreight}?>
      <contrib-group>
        <contrib contrib-type="author" corresp="yes">
          <name><surname>Towler</surname><given-names>Erin</given-names></name>
          <email>Erin Towler</email>
        <ext-link>https://orcid.org/0000-0002-1784-1346</ext-link></contrib>
        <contrib contrib-type="author" corresp="no">
          <name><surname>McCreight</surname><given-names>James L.</given-names></name>
          
        <ext-link>https://orcid.org/0000-0001-6018-425X</ext-link></contrib>
        <aff id="aff1"><institution>National Center for Atmospheric Research (NCAR), P.O. Box 3000,
Boulder, CO 80307, USA</institution>
        </aff>
      </contrib-group>
      <author-notes><corresp id="corr1">Erin Towler</corresp></author-notes><pub-date><day>19</day><month>May</month><year>2021</year></pub-date>
      
      <volume>25</volume>
      <issue>5</issue>
      <fpage>2599</fpage><lpage>2615</lpage>
      <history>
        <date date-type="received"><day>26</day><month>June</month><year>2020</year></date>
           <date date-type="rev-request"><day>22</day><month>September</month><year>2020</year></date>
           <date date-type="rev-recd"><day>24</day><month>February</month><year>2021</year></date>
           <date date-type="accepted"><day>7</day><month>April</month><year>2021</year></date>
      </history>
      <permissions>
        <copyright-statement>Copyright: © 2021 Erin Towler</copyright-statement>
        <copyright-year>2021</copyright-year>
      <license license-type="open-access"><license-p>This work is licensed under the Creative Commons Attribution 4.0 International License. To view a copy of this licence, visit <ext-link ext-link-type="uri" xlink:href="https://creativecommons.org/licenses/by/4.0/">https://creativecommons.org/licenses/by/4.0/</ext-link></license-p></license></permissions><self-uri xlink:href="https://hess.copernicus.org/articles/25/2599/2021/hess-25-2599-2021.html">This article is available from https://hess.copernicus.org/articles/25/2599/2021/hess-25-2599-2021.html</self-uri><self-uri xlink:href="https://hess.copernicus.org/articles/25/2599/2021/hess-25-2599-2021.pdf">The full text article is available as a PDF file from https://hess.copernicus.org/articles/25/2599/2021/hess-25-2599-2021.pdf</self-uri>
      <abstract><title>Abstract</title>
    <p id="d1e89">Streamflow timing errors (in the units of time) are rarely explicitly
evaluated but are useful for model evaluation and development. Wavelet-based approaches have been shown to reliably quantify timing errors
in streamflow simulations but have not been applied in a systematic way
that is suitable for model evaluation. This paper provides a step-by-step
methodology that objectively identifies events, and then estimates timing
errors for those events, in a way that can be applied to large-sample,
high-resolution predictions. Step 1 applies the wavelet transform to the
observations and uses statistical significance to identify observed events. Step 2 utilizes the cross-wavelet transform to calculate the timing errors for the events identified in step 1; this includes the diagnostic of model event hits, and timing errors are only assessed for hits. The
methodology is illustrated using real and simulated stream discharge data
from several locations to highlight key method features. The method groups
event timing errors by dominant timescales, which can be used to identify
the potential processes contributing to the timing errors and the associated model development needs. For instance, timing errors that are associated with the diurnal melt cycle are identified. The method is also useful for documenting and evaluating model performance in terms of defined standards. This is illustrated by showing the version-over-version performance of the National Water Model (NWM) in terms of timing errors.</p>
  </abstract>
    </article-meta>
  </front>
<body>
      

<sec id="Ch1.S1" sec-type="intro">
  <label>1</label><title>Introduction</title>
      <p id="d1e101">Common verification metrics used to evaluate streamflow simulations are
typically aggregated measures of model performance, e.g., the Nash–Sutcliffe
Efficiency (NSE) and the related root mean square error (RMSE). Although
typically used to assess errors in amplitude, these statistical metrics
include contributions from errors in both amplitude and timing (Ehret and
Zehe, 2011), making them difficult to use for diagnostic model evaluation
(Gupta et al., 2008). Furthermore, common verification metrics are calculated
using the entire time series, whereas timing errors require a comparison of
localized features or events in the data. This paper focuses explicitly on
event timing error estimation, which is not routinely evaluated despite its
potential benefit for model diagnostics (Gupta et al., 2008) and practical
forecast guidance (Liu et al., 2011).</p>
      <p id="d1e104">The fundamental challenge with evaluating timing errors is identifying what
constitutes an event in the two time series being compared.
Identifying events is typically subjective, time consuming, and not
practical for large-sample hydrological applications (Gupta et al., 2014). A
variety of baseflow separation methods, ranging from physically based to
empirical, have been developed to identify hydrologic events (see Mei and
Anagnostou, 2015, for a summary), though many of these approaches require some manual inspection of the hydrographs. Merz et al. (2006) put forth an
automated approach, but it requires a calibrated hydrologic model, which is
a limitation in data-poor regions. Koskelo et al. (2012) developed a simple,
empirical approach that only requires rainfall and runoff time series, but it
is limited to small watersheds and daily data. Mei and Anagnostou (2015)
introduced an automated, physically based approach which is demonstrated for
hourly data, though one caveat is that basin events need to have a clearly
detectable recession period. Additional methods have focused on identifying
flooding events using peak-over-threshold methods. The thresholds used for
such analyses are often either based on historical percentiles (e.g.,<?pagebreak page2600?> the
95th percentile) or on local impact levels (river stage), such as the
National Weather Service (NWS) flood categories (NOAA National Weather
Service, 2012). Timing error metrics are often calculated from the peaks of
these identified events. For example, the peak time error, or its derivative of the mean absolute peak time error, requires matching observed and simulated
event peaks and calculating their offset (Ehret and Zehe, 2011). While this
may be straightforward visually, it can be difficult to automate; some of
the reasons for this are discussed below.</p>
      <p id="d1e107">Difficulties arise when using thresholds for event identification. For example, exceedances can cluster if a hydrograph vacillates above and below a
threshold, leading to the following questions: is it one or multiple events? Which peak should be used for the assessment? In the statistics of extremes,
declustering approaches can be applied to extract independent peaks (e.g.,
Coles, 2001), but this reductionist approach may miss relevant features. For
instance, if background flows are elevated for a longer period of time
before and after the occurrence of these events, the threshold-based
analysis identifies features of the flow separately from the primary
hydrologic process responsible for the event. If one focuses just on peak
timing differences in this example, then that timing error may only apply to some small fraction of the total flow of the larger event which happens mainly below the threshold. Furthermore, for overall model diagnosis that focuses on model performance for all events, not just flood events, variable thresholds would be needed to account for different kinds of events (e.g., a daily melt event versus a convective precipitation event).</p>
      <p id="d1e110">Using a threshold approach to identify events and timing error assessment,
Ehret and Zehe (2011) develop an intuitive assessment of hydrograph
similarity, i.e., the series distance. This algorithm is later improved upon by Seibert et al. (2016). The procedure matches observed and simulated segments (rise or recession) of an event and then calculates the amplitude and timing errors and the frequency of the event agreement. The series
distance requires smoothing the time series, identifying an event threshold,
and selecting a time range in which to consider the matching of two segments.</p>
      <p id="d1e114">Liu et al. (2011) developed a wavelet-based method for estimating model
timing errors. Although wavelets have been applied in many hydrologic
applications, such as model analysis (e.g., Lane, 2007; Weedon et al., 2015;
Schaefli and Zehe, 2009; Rathinasamy et al., 2014) and post-processing (Bogner and Kalas, 2008; Bogner and Pappenberger, 2011), Liu et al. (2011) were the first to use it for timing error estimation. Liu et al. (2011) apply a cross-wavelet transform technique to streamflow time series for 11 headwater basins in Texas. Timing errors are estimated for medium- to high-flow events that are determined a priori by threshold exceedance. They use synthetic and real streamflow simulations to test the utility of the approach. They show that the technique can reliably estimate timing errors, though they conclude that it is less reliable for multi-peak or consecutive events (defined qualitatively). ElSaadani and Krajewski (2017) followed the cross-wavelet approach used by Liu et al. (2011) to provide similar analysis and further investigate the effect of the choice of mother wavelet on the timing error analysis. Ultimately, they recommended that, in the situation of multiple adjoining flow peaks, the improved time localization of the Paul wavelet might justify its poorer frequency localization compared the Morlet wavelet.</p>
      <p id="d1e117">Liu et al. (2011) provide a starting point for the work in this paper in which we develop the following two new bases for their method: (1) objective event identification
for timing error evaluation and (2) the use of observed events as the basis
for the model timing error calculations. The latter is important for model
benchmarking, i.e., the practice of evaluating models in terms of defined
standards (e.g., Luo et al., 2012; Newman et al., 2017). Here, the use of
observed events provides a baseline by which to evaluate changes and to
compare multiple versions or experimental designs.</p>
      <p id="d1e120">This paper provides a methodology for using wavelet analysis to quantify
timing errors in hydrologic simulations. Our contribution is a systematic
approach that integrates (1) statistical significance to identify events with
(2) a basis for timing error calculations independent of model simulations
(i.e., benchmarking). We apply our method to a timing error evaluation of
high-resolution streamflow prediction. The paper is organized as follows:
Sect. 2 describes the observational and simulated data used. Section 3
provides the detailed methodology of using wavelets to identify events and
estimate timing errors in a synthetic example. In Sect. 4, we demonstrate
the method using real and simulated streamflow data for several use cases
and then illustrate the application of the method for version-over-version
comparisons. Section 5 is the discussion and conclusions, including how
specific methodological choices may vary by application.</p>
</sec>
<sec id="Ch1.S2">
  <label>2</label><title>Data</title>
      <p id="d1e131">The application of the methodology is illustrated using real and simulated
stream discharge (streamflow in cubic meters per second) data at three US Geological Survey (USGS) stream gauge locations in different geographic regions, i.e., Onion Creek at US Highway 183, Austin, Texas, for the South Central region (Onion Creek, TX; USGS site no. 08159000), Taylor River at Taylor Park, Colorado, for the Intermountain West (Taylor River, CO; USGS site no. 09107000), and Pemigewasset River at Woodstock, New Hampshire, for New England (Pemigewasset River, NH; USGS site no. 01075000). We use the USGS instantaneous observations averaged on an hourly basis.</p>

      <?xmltex \floatpos{t}?><fig id="Ch1.F1" specific-use="star"><?xmltex \currentcnt{1}?><?xmltex \def\figurename{Figure}?><label>Figure 1</label><caption><p id="d1e136">Flow chart of steps in the methodology. Although steps 1a–b and
2a–b can happen in parallel, step 2c needs to be preceded by step 1c.</p></caption>
        <?xmltex \igopts{width=341.433071pt}?><graphic xlink:href="https://hess.copernicus.org/articles/25/2599/2021/hess-25-2599-2021-f01.png"/>

      </fig>

      <p id="d1e145">NOAA's National Water Model (NWM; <uri>https://www.nco.ncep.noaa.gov/pmb/products/nwm/</uri>, last access: 8 May 2021) is an operational model that produces hydrologic analyses and forecasts over the continental United States (CONUS)<?pagebreak page2601?> and Hawaii (as of version 2.0). The model is forced by downscaled atmospheric states and fluxes from NOAA's operational weather models. Next, the Noah-MP (Noah-multiparameterization; Niu et al., 2011) land surface model calculates energy and water states and fluxes. Water fluxes propagate down the model chain through overland and subsurface (soil and aquifer representations) water routing schemes to reach a stream channel model. The NWM applies the three-parameter Muskingum–Cunge river routing scheme to a modified version of the National Hydrography Dataset Plus (NHDPlus) version 2 (McKay et al., 2012) river network representation (Gochis et al., 2020).</p>
      <p id="d1e152">In this study, NWM simulations are taken from each version's retrospective
runs (<uri>https://docs.opendata.aws/nwm-archive/readme.html</uri>, last access: 8 May 2021). These are continuous simulations (not cycles) run for the period from October 2010 to November 2016 and forced by the National Land Data Assimilation System (NLDAS)-2 product as atmospheric conditions. The nudging data assimilation was not applied in these runs. We use NWM discharge simulations from versions V1.0, V1.1, and V1.2 (not all versions may be publicly available).</p>
      <p id="d1e158">The methodology developed in this paper is implemented in the R language and
is made publicly available, as detailed in the code availability section at
the end of the paper.</p>
</sec>
<sec id="Ch1.S3">
  <label>3</label><title>Methodology</title>
      <p id="d1e169">This section provides the description of the methodology using wavelets to
identify events and estimate timing errors. The steps can be seen in the
accompanying flowchart (Fig. 1) and nomenclature (Table 1), which define the key terms of the approach. To facilitate understanding, the steps
are illustrated by an application of the methodology to an observed time
series of an isolated peak in Onion Creek, TX, (Fig. 2a) and the synthetic
modeled time series, which is identical to the observation time series but
shifted 5 h in to the future (Fig. 3a; note the log scale).</p>

      <?xmltex \floatpos{t}?><fig id="Ch1.F2" specific-use="star"><?xmltex \currentcnt{2}?><?xmltex \def\figurename{Figure}?><label>Figure 2</label><caption><p id="d1e174">An isolated peak from Onion Creek, TX, showing the <bold>(a)</bold> observed time series, <bold>(b)</bold> observed wavelet power spectrum (left), and average power by timescale for all points (right). Panel  <bold>(c)</bold>  shows the statistically significant wavelet power spectrum of events (left) and average power by timescale for all events, with maxima shown by gray dots (right). Panel <bold>(d)</bold> shows the characteristic scale event cluster (horizontal green line) and cluster maximum (asterisk).</p></caption>
        <?xmltex \igopts{width=398.338583pt}?><graphic xlink:href="https://hess.copernicus.org/articles/25/2599/2021/hess-25-2599-2021-f02.png"/>

      </fig>

      <?xmltex \floatpos{t}?><fig id="Ch1.F3" specific-use="star"><?xmltex \currentcnt{3}?><?xmltex \def\figurename{Figure}?><label>Figure 3</label><caption><p id="d1e197">An isolated peak from Onion Creek, TX, and a synthetic <inline-formula><mml:math id="M1" display="inline"><mml:mo>+</mml:mo></mml:math></inline-formula> 5 h
offset, showing the <bold>(a)</bold> observed and synthetic time series (note the logged <inline-formula><mml:math id="M2" display="inline"><mml:mi>y</mml:mi></mml:math></inline-formula> axis), <bold>(b)</bold> cross-wavelet (XWT) power spectrum, phase angles (arrows), and XWT significance (gray line). Panel <bold>(c)</bold>  shows the sampled timing errors for observed events (inside dashed contour indicates the intersection of XWT events with observed events), and the gray asterisk shows the cluster maximum from Fig. 2d.</p></caption>
        <?xmltex \igopts{width=398.338583pt}?><graphic xlink:href="https://hess.copernicus.org/articles/25/2599/2021/hess-25-2599-2021-f03.png"/>

      </fig>

<?xmltex \floatpos{t}?><table-wrap id="Ch1.T1" specific-use="star"><?xmltex \currentcnt{1}?><label>Table 1</label><caption><p id="d1e233">Nomenclature of terms used in the paper.</p></caption><oasis:table frame="topbot"><oasis:tgroup cols="4">
     <oasis:colspec colnum="1" colname="col1" align="left"/>
     <oasis:colspec colnum="2" colname="col2" align="left"/>
     <oasis:colspec colnum="3" colname="col3" align="left"/>
     <oasis:colspec colnum="4" colname="col4" align="left"/>
     <oasis:thead>
       <oasis:row rowsep="1">
         <oasis:entry colname="col1">Term and acronym</oasis:entry>
         <oasis:entry colname="col2">Synonyms</oasis:entry>
         <oasis:entry colname="col3">Units</oasis:entry>
         <oasis:entry colname="col4">Comments</oasis:entry>
       </oasis:row>
     </oasis:thead>
     <oasis:tbody>
       <oasis:row>
         <oasis:entry colname="col1">Time series</oasis:entry>
         <oasis:entry colname="col2">Input data</oasis:entry>
         <oasis:entry colname="col3">m<inline-formula><mml:math id="M3" display="inline"><mml:msup><mml:mi/><mml:mn mathvariant="normal">3</mml:mn></mml:msup></mml:math></inline-formula> s<inline-formula><mml:math id="M4" display="inline"><mml:msup><mml:mi/><mml:mrow><mml:mo>-</mml:mo><mml:mn mathvariant="normal">1</mml:mn></mml:mrow></mml:msup></mml:math></inline-formula> for</oasis:entry>
         <oasis:entry colname="col4">We analyze streamflow observations and simulations, which</oasis:entry>
       </oasis:row>
       <oasis:row rowsep="1">
         <oasis:entry colname="col1"/>
         <oasis:entry colname="col2"/>
         <oasis:entry colname="col3">streamflow</oasis:entry>
         <oasis:entry colname="col4">are ordered by the time dimension (Fig. 2a).</oasis:entry>
       </oasis:row>
       <oasis:row rowsep="1">
         <oasis:entry colname="col1">Time</oasis:entry>
         <oasis:entry colname="col2"/>
         <oasis:entry colname="col3">h</oasis:entry>
         <oasis:entry colname="col4">Dimension of the input time series (<inline-formula><mml:math id="M5" display="inline"><mml:mi>x</mml:mi></mml:math></inline-formula> axis in all Fig. 2 panels).</oasis:entry>
       </oasis:row>
       <oasis:row>
         <oasis:entry colname="col1">Timescale</oasis:entry>
         <oasis:entry colname="col2">Period</oasis:entry>
         <oasis:entry colname="col3">h</oasis:entry>
         <oasis:entry colname="col4">Dimension introduced at each time by the wavelet transform</oasis:entry>
       </oasis:row>
       <oasis:row rowsep="1">
         <oasis:entry colname="col1"/>
         <oasis:entry colname="col2"/>
         <oasis:entry colname="col3"/>
         <oasis:entry colname="col4">(<inline-formula><mml:math id="M6" display="inline"><mml:mi>y</mml:mi></mml:math></inline-formula> axis in Fig. 2b–d).</oasis:entry>
       </oasis:row>
       <oasis:row>
         <oasis:entry colname="col1">Wavelet</oasis:entry>
         <oasis:entry colname="col2">Wavelet power</oasis:entry>
         <oasis:entry colname="col3">m<inline-formula><mml:math id="M7" display="inline"><mml:msup><mml:mi/><mml:mn mathvariant="normal">6</mml:mn></mml:msup></mml:math></inline-formula> s<inline-formula><mml:math id="M8" display="inline"><mml:msup><mml:mi/><mml:mrow><mml:mo>-</mml:mo><mml:mn mathvariant="normal">2</mml:mn></mml:mrow></mml:msup></mml:math></inline-formula></oasis:entry>
         <oasis:entry colname="col4">In this paper, we employ the continuous WT (Fig. 2b) with</oasis:entry>
       </oasis:row>
       <oasis:row>
         <oasis:entry colname="col1">transform (WT)</oasis:entry>
         <oasis:entry colname="col2">spectrum (result of</oasis:entry>
         <oasis:entry colname="col3"/>
         <oasis:entry colname="col4">scale-normalized energy (Liu et al., 2007).</oasis:entry>
       </oasis:row>
       <oasis:row rowsep="1">
         <oasis:entry colname="col1"/>
         <oasis:entry colname="col2">the transform)</oasis:entry>
         <oasis:entry colname="col3"/>
         <oasis:entry colname="col4"/>
       </oasis:row>
       <oasis:row>
         <oasis:entry colname="col1">Cone of</oasis:entry>
         <oasis:entry colname="col2">COI</oasis:entry>
         <oasis:entry colname="col3"/>
         <oasis:entry colname="col4">This is where the wavelet analysis is affected by the wavelet</oasis:entry>
       </oasis:row>
       <oasis:row rowsep="1">
         <oasis:entry colname="col1">influence (COI)</oasis:entry>
         <oasis:entry colname="col2"/>
         <oasis:entry colname="col3"/>
         <oasis:entry colname="col4">extending beyond the time domain of the input (muted colors in Fig. 2b).</oasis:entry>
       </oasis:row>
       <oasis:row>
         <oasis:entry colname="col1">Event</oasis:entry>
         <oasis:entry colname="col2"/>
         <oasis:entry colname="col3"/>
         <oasis:entry colname="col4">We define events in terms of both time and timescales that</oasis:entry>
       </oasis:row>
       <oasis:row rowsep="1">
         <oasis:entry colname="col1"/>
         <oasis:entry colname="col2"/>
         <oasis:entry colname="col3"/>
         <oasis:entry colname="col4">are significant in the WT and outside the COI (Fig. 2c).</oasis:entry>
       </oasis:row>
       <oasis:row>
         <oasis:entry colname="col1">Characteristic</oasis:entry>
         <oasis:entry colname="col2">Dominant</oasis:entry>
         <oasis:entry colname="col3">h</oasis:entry>
         <oasis:entry colname="col4">We define characteristic timescales by local maxima in time-</oasis:entry>
       </oasis:row>
       <oasis:row rowsep="1">
         <oasis:entry colname="col1">timescale</oasis:entry>
         <oasis:entry colname="col2">timescale</oasis:entry>
         <oasis:entry colname="col3"/>
         <oasis:entry colname="col4">averaged, significant wavelet power (e.g., over events; Fig. 2d).</oasis:entry>
       </oasis:row>
       <oasis:row>
         <oasis:entry colname="col1">Event cluster</oasis:entry>
         <oasis:entry colname="col2"/>
         <oasis:entry colname="col3"/>
         <oasis:entry colname="col4">For a single (e.g., characteristic) timescale and contiguous</oasis:entry>
       </oasis:row>
       <oasis:row rowsep="1">
         <oasis:entry colname="col1"/>
         <oasis:entry colname="col2"/>
         <oasis:entry colname="col3"/>
         <oasis:entry colname="col4">events in time (Fig. 2d).</oasis:entry>
       </oasis:row>
       <oasis:row>
         <oasis:entry colname="col1">Cross-wavelet</oasis:entry>
         <oasis:entry colname="col2">Cross-wavelet</oasis:entry>
         <oasis:entry colname="col3">Power – m<inline-formula><mml:math id="M9" display="inline"><mml:msup><mml:mi/><mml:mn mathvariant="normal">6</mml:mn></mml:msup></mml:math></inline-formula> s<inline-formula><mml:math id="M10" display="inline"><mml:msup><mml:mi/><mml:mrow><mml:mo>-</mml:mo><mml:mn mathvariant="normal">2</mml:mn></mml:mrow></mml:msup></mml:math></inline-formula>;</oasis:entry>
         <oasis:entry colname="col4">The complex, cross-wavelet transform has properties of</oasis:entry>
       </oasis:row>
       <oasis:row>
         <oasis:entry colname="col1">transform</oasis:entry>
         <oasis:entry colname="col2">power spectrum</oasis:entry>
         <oasis:entry colname="col3">phase – radians</oasis:entry>
         <oasis:entry colname="col4">power and phase. The significance of the XWT can also be</oasis:entry>
       </oasis:row>
       <oasis:row>
         <oasis:entry colname="col1">(XWT)</oasis:entry>
         <oasis:entry colname="col2">(result of the</oasis:entry>
         <oasis:entry colname="col3"/>
         <oasis:entry colname="col4">computed (e.g., Torrence and Compo, 1998) as shown in</oasis:entry>
       </oasis:row>
       <oasis:row rowsep="1">
         <oasis:entry colname="col1"/>
         <oasis:entry colname="col2">transform)</oasis:entry>
         <oasis:entry colname="col3"/>
         <oasis:entry colname="col4">Fig. 3b. XWT events are outlined by a dashed line in Fig. 3c.</oasis:entry>
       </oasis:row>
       <oasis:row>
         <oasis:entry colname="col1">Timing error</oasis:entry>
         <oasis:entry colname="col2"/>
         <oasis:entry colname="col3">h</oasis:entry>
         <oasis:entry colname="col4">Timing errors are calculated from the phase offset of the</oasis:entry>
       </oasis:row>
       <oasis:row>
         <oasis:entry colname="col1"/>
         <oasis:entry colname="col2"/>
         <oasis:entry colname="col3"/>
         <oasis:entry colname="col4">XWT (e.g., Liu et al., 2011) and have dimensions of both time</oasis:entry>
       </oasis:row>
       <oasis:row>
         <oasis:entry colname="col1"/>
         <oasis:entry colname="col2"/>
         <oasis:entry colname="col3"/>
         <oasis:entry colname="col4">and timescale. Several statistics of timing errors (over time)</oasis:entry>
       </oasis:row>
       <oasis:row>
         <oasis:entry colname="col1"/>
         <oasis:entry colname="col2"/>
         <oasis:entry colname="col3"/>
         <oasis:entry colname="col4">for characteristic timescales can be computed (Fig. 2c).</oasis:entry>
       </oasis:row>
     </oasis:tbody>
   </oasis:tgroup></oasis:table></table-wrap>

<sec id="Ch1.S3.SS1">
  <label>3.1</label><title>Step 1 – identify observed events</title>
      <p id="d1e681">The first step is to identify a set of observed events for which the timing
error should be calculated. We break this step into the following three substeps: 1a – apply the wavelet transform to observations; 1b – determine all observed events using significance testing; and 1c – sample observed events to an event set relevant to analysis.</p>
<sec id="Ch1.S3.SS1.SSS1">
  <label>3.1.1</label><title>Step 1a – apply wavelet transform to observations</title>
      <p id="d1e691">First, we apply the continuous wavelet transform (WT) to the observed time
series. The main steps and equations for the WT are provided here, though
the reader is referred to Torrence and Compo (1998) and Liu et al. (2011)
for more details.</p>
      <p id="d1e694">Before applying the WT, a mother wavelet needs to be selected. In Torrence
and Compo (1998), they discuss the key factors that should be considered
when choosing the mother wavelet. There are four main considerations,
including (i) orthogonal or nonorthogonal, (ii) complex or real, (iii) width, and (iv) shape. In this study, we follow Liu et al. (2011) in selecting the nonorthogonal and complex Morlet wavelet as follows:
              <disp-formula id="Ch1.E1" content-type="numbered"><label>1</label><mml:math id="M11" display="block"><mml:mrow><mml:mi mathvariant="italic">ψ</mml:mi><mml:mo>(</mml:mo><mml:mi>n</mml:mi><mml:mo>)</mml:mo><mml:mo>=</mml:mo><mml:msup><mml:mi mathvariant="italic">π</mml:mi><mml:mrow><mml:mo>-</mml:mo><mml:mn mathvariant="normal">1</mml:mn><mml:mo>/</mml:mo><mml:mn mathvariant="normal">4</mml:mn></mml:mrow></mml:msup><mml:msup><mml:mi>e</mml:mi><mml:mrow><mml:mi>i</mml:mi><mml:msub><mml:mi>w</mml:mi><mml:mn mathvariant="normal">0</mml:mn></mml:msub><mml:mi>n</mml:mi></mml:mrow></mml:msup><mml:msup><mml:mi>e</mml:mi><mml:mrow><mml:mo>-</mml:mo><mml:msup><mml:mi>n</mml:mi><mml:mn mathvariant="normal">2</mml:mn></mml:msup><mml:mo>/</mml:mo><mml:mn mathvariant="normal">2</mml:mn></mml:mrow></mml:msup><mml:mo>,</mml:mo></mml:mrow></mml:math></disp-formula>
            where <inline-formula><mml:math id="M12" display="inline"><mml:mrow><mml:msub><mml:mi>w</mml:mi><mml:mn mathvariant="normal">0</mml:mn></mml:msub></mml:mrow></mml:math></inline-formula> is the nondimensional frequency with a value of 6 (Torrence
and Compo, 1998).</p>
      <?pagebreak page2602?><p id="d1e766">Once the mother wavelet is selected, the WT is applied to a time series, <inline-formula><mml:math id="M13" display="inline"><mml:mrow><mml:msub><mml:mi>x</mml:mi><mml:mi>n</mml:mi></mml:msub></mml:mrow></mml:math></inline-formula>, in which <inline-formula><mml:math id="M14" display="inline"><mml:mi>n</mml:mi></mml:math></inline-formula> goes from <inline-formula><mml:math id="M15" display="inline"><mml:mrow><mml:mi>n</mml:mi><mml:mo>=</mml:mo><mml:mn mathvariant="normal">0</mml:mn></mml:mrow></mml:math></inline-formula> to <inline-formula><mml:math id="M16" display="inline"><mml:mrow><mml:mi>n</mml:mi><mml:mo>=</mml:mo><mml:mi>N</mml:mi><mml:mo>-</mml:mo><mml:mn mathvariant="normal">1</mml:mn></mml:mrow></mml:math></inline-formula> with a time step of <inline-formula><mml:math id="M17" display="inline"><mml:mrow><mml:mi mathvariant="italic">δ</mml:mi><mml:mi>t</mml:mi></mml:mrow></mml:math></inline-formula>. The WT is the convolution of the time series with the mother wavelet that has been scaled and normalized as follows:
<?xmltex \hack{\newpage}?><?xmltex \hack{\vspace*{-6mm}}?>
              <disp-formula id="Ch1.E2" content-type="numbered"><label>2</label><mml:math id="M18" display="block"><mml:mrow><mml:msub><mml:mi>W</mml:mi><mml:mi>n</mml:mi></mml:msub><mml:mo>(</mml:mo><mml:mi>s</mml:mi><mml:mo>)</mml:mo><mml:mo>=</mml:mo><mml:munderover><mml:mo movablelimits="false">∑</mml:mo><mml:mrow><mml:msup><mml:mi>n</mml:mi><mml:mo>′</mml:mo></mml:msup><mml:mo>=</mml:mo><mml:mn mathvariant="normal">0</mml:mn></mml:mrow><mml:mrow><mml:mi>N</mml:mi><mml:mo>-</mml:mo><mml:mn mathvariant="normal">1</mml:mn></mml:mrow></mml:munderover><mml:msub><mml:mi>x</mml:mi><mml:mrow><mml:msup><mml:mi>n</mml:mi><mml:mo>′</mml:mo></mml:msup></mml:mrow></mml:msub><mml:msup><mml:mi mathvariant="italic">ψ</mml:mi><mml:mo>*</mml:mo></mml:msup><mml:mfenced close="]" open="["><mml:mstyle displaystyle="true"><mml:mfrac style="display"><mml:mrow><mml:mo>(</mml:mo><mml:msup><mml:mi>n</mml:mi><mml:mo>′</mml:mo></mml:msup><mml:mo>-</mml:mo><mml:mi>n</mml:mi><mml:mi>t</mml:mi><mml:mo>)</mml:mo><mml:mi mathvariant="italic">δ</mml:mi><mml:mi>t</mml:mi></mml:mrow><mml:mi>s</mml:mi></mml:mfrac></mml:mstyle></mml:mfenced><mml:mo>,</mml:mo></mml:mrow></mml:math></disp-formula>
            where <inline-formula><mml:math id="M19" display="inline"><mml:mrow><mml:msup><mml:mi>n</mml:mi><mml:mo>′</mml:mo></mml:msup></mml:mrow></mml:math></inline-formula> is the localized time in [0, <inline-formula><mml:math id="M20" display="inline"><mml:mrow><mml:mi>N</mml:mi><mml:mo>-</mml:mo><mml:mn mathvariant="normal">1</mml:mn></mml:mrow></mml:math></inline-formula>], <inline-formula><mml:math id="M21" display="inline"><mml:mi>s</mml:mi></mml:math></inline-formula> is the scale parameter, and the asterisk indicates the complex conjugate of the wavelet function. The
wavelet power is defined as <inline-formula><mml:math id="M22" display="inline"><mml:mrow><mml:mo>|</mml:mo><mml:msubsup><mml:mi>W</mml:mi><mml:mi>n</mml:mi><mml:mn mathvariant="normal">2</mml:mn></mml:msubsup><mml:mo>|</mml:mo></mml:mrow></mml:math></inline-formula>, which represents the squared amplitude of an imaginary number when a complex wavelet is used as in this study. We use the bias-corrected wavelet power (Liu et al., 2007; Veleda et al., 2012), which ensures that the power is comparable across timescales. We also identify a maximum timescale a priori that corresponds to our application. We select 256 h (<inline-formula><mml:math id="M23" display="inline"><mml:mrow><mml:mo>∼</mml:mo><mml:mn mathvariant="normal">10</mml:mn></mml:mrow></mml:math></inline-formula> d), but this number could be higher
or lower for other applications, and there are no real penalties for using too high a maximum (lower than the annual cycle).</p>
      <p id="d1e966">The wavelet transform (WT) expands the dimensionality of the original time
series by introducing the timescale (or period) dimension. Wavelet power is
also a function of both time and timescale (e.g., Torrence and Compo, 1998).
This is illustrated in Fig. 2. The streamflow time series (Fig. 2a) is
expanded into a 2-dimensional (2-D) wavelet power spectrum (Fig. 2b). Wavelet analysis can detect localized signals in the time series (Daubechies, 1990), including hydrologic time series, which are often irregular or aperiodic (i.e., events may be isolated and do not regularly repeat) or nonstationary. We note that, in many wavelet applications, timescale is referred to as “period”, and this axis is indeed the Fourier<?pagebreak page2603?> period in our plots. However, to emphasize that our study is more focused on irregular events and less on periodic behavior of time series, we use the term timescale to denote the Fourier period (and not wavelet scale).</p>
      <p id="d1e970">Because we are applying the WT to a finite time series, there are timescale-dependent errors at the beginning and end times of the power
spectrum, where the entirety of the wavelet at each scale is not fully
contained within the time series. This region of the WT is referred to as
the cone of influence or COI (Torrence and Compo, 1998). Figure 2b
illustrates the COI as the regions in which the colors are muted; we ignore all
results within the COI in this study.</p>
      <p id="d1e973">We make several additional notes on the wavelet power and its representation
in the figures. The units of the wavelet power are those of the time series
variance (m<inline-formula><mml:math id="M24" display="inline"><mml:msup><mml:mi/><mml:mn mathvariant="normal">6</mml:mn></mml:msup></mml:math></inline-formula> s<inline-formula><mml:math id="M25" display="inline"><mml:msup><mml:mi/><mml:mrow><mml:mo>-</mml:mo><mml:mn mathvariant="normal">2</mml:mn></mml:mrow></mml:msup></mml:math></inline-formula> – meters to the sixth power per square second  for streamflow), and it is natural to want to cast the power in a physical light or relate it to the time series variance. Indeed, the power is often normalized by the time series variance when presented graphically. However, it must be noted that the wavelet convolved with the time series frames the resulting power in terms of itself at a given scale. Wavelet power is a (normalized) measure of how well the wavelet and the time series match at a given time and scale. The power can only be compared to other values of power resulting from a similarly constructed WT. There are various transforms that can be applied to aid the graphical interpretation of the power (log and variance scaling), but the utility of these often depends on the nature of the individual time series analyzed. For simplicity, we plot the raw bias-rectified wavelet power in this paper.</p>
</sec>
<?pagebreak page2604?><sec id="Ch1.S3.SS1.SSS2">
  <label>3.1.2</label><title>Step 1b – determine all observed events using significant testing</title>
      <p id="d1e1005">In their seminal wavelet study, Torrence and Compo (1998) outline a method
for objectively identifying statistical significance in the wavelet power by
comparing the wavelet power spectra with a power spectra from a red noise
process. Specifically, the observed time series is fitted with an order 1
autoregressive (AR1 or red noise) model, and the WT is applied to the AR1
time series. The power spectrum of the AR1 model provides the basis for the
statistical significance testing. Significance is determined if the power
spectra are statistically different using a chi-squared test.</p>
      <p id="d1e1008">Figure 2b shows significant (<inline-formula><mml:math id="M26" display="inline"><mml:mrow><mml:mi mathvariant="italic">&gt;=</mml:mi><mml:mn mathvariant="normal">95</mml:mn></mml:mrow></mml:math></inline-formula> % confidence level) regions of wavelet power inside black contours. Statistical significance indicates wavelet power that falls outside the time series background statistical power based on an AR1 model of the time series. Statistical significance of the wavelet power can be thought of as events in the wavelet domain. We define events as regions of significant wavelet power outside the COI. Figure 2c displays the wavelet power for the events in this time series. We emphasize that events defined in this way are a function of both time and timescale and that, at a given time, events of different timescales can occur simultaneously.</p>
</sec>
<sec id="Ch1.S3.SS1.SSS3">
  <label>3.1.3</label><title>Step 1c – sample observed events to an event set relevant to analysis</title>
      <p id="d1e1029">Step 1b results in the identification of all events at all timescales and
times. In this substep, the event space is sampled to suit the particular
evaluation. Torrence and Compo (1998) offer the following two methods for smoothing the
wavelet plot that can increase significance and confidence: (i) averaging in
time (over timescale) or (ii) averaging in timescale (over time). Because
the goal of this paper is to evaluate model timing errors over long
simulation periods, we choose to sample the event space based on averaging
in timescale. Although for some locations there may be physical reasons to
expect certain timescales to be important (e.g., the seasonal cycle of
snowmelt), the most important timescales at which hydrologic signals occur
at a particular location are not necessarily known a priori. Averaging events in timescale can provide a useful diagnostic by identifying<?pagebreak page2605?> the dominant, or characteristic, timescales for a given time series. Averaging many events in a timescale can filter noise and help reveal the expected timescales of dominant variability corresponding to different processes or sets of processes.</p>
      <p id="d1e1032">In our analysis, we seek to uncover the dominant event timescales and to
evaluate modeled timing errors on them. The following points articulate
our methodological choices for summarizing the observed events:
<list list-type="bullet"><list-item>
      <p id="d1e1037"><italic>Calculate the average event power in each timescale</italic>. Considering only the statistically significant areas of the observed wavelet spectrum, calculate the average power in each timescale (Fig. 2c, right panel). We point out that calculating the average power over events is different to what is found by averaging across all time points, which does not take statistical significance into consideration (Fig. 2b, right panel).</p></list-item><list-item>
      <p id="d1e1043"><italic>Identify timescales of absolute and local maxima in time-averaged power</italic>. After obtaining the average event power as a function timescale (Fig. 2c, right panel), the local and absolute maximums for average event power can be determined. In the Onion Creek case, there is a single maximum at 22 h (gray dot in Fig. 2c, right panel). The timescales corresponding to the absolute and local maxima of the average power of the observed time series are called the characteristic timescales used for evaluation. This is the first subset of the events, i.e., all events that fall within the characteristic timescales. For a single characteristic timescale, contiguous events in time are called event clusters (horizontal line in Fig. 2d).</p></list-item><list-item>
      <p id="d1e1049"><italic>Identify events with maximum power in each event cluster</italic>. For all timescales, we identify the event with maximum power in each event cluster. This is the second event subset, i.e., all events with maximum power in each cluster that fall within a characteristic timescale (asterisk in Fig. 2d); these are called cluster maxima.</p></list-item></list></p>
</sec>
</sec>
<sec id="Ch1.S3.SS2">
  <label>3.2</label><title>Step 2 – calculate timing errors</title>
      <p id="d1e1063">Step 1 identifies observed events by applying a wavelet transform to the
observed time series. To calculate the timing error of a modeled time series, we perform its cross-wavelet transform with the observed time series. Figure 3a shows the observed and modeled time series used in our illustration of the methodology, i.e., the observed is the same isolated peak from Onion Creek, TX, as in Fig. 2a, and the synthetic modeled time series adds a prescribed timing error of <inline-formula><mml:math id="M27" display="inline"><mml:mrow><mml:mo>+</mml:mo><mml:mn mathvariant="normal">5</mml:mn></mml:mrow></mml:math></inline-formula> h to the observed. (Note that while the observed time series is identical in both, Figs. 2a and 3a have linear and <inline-formula><mml:math id="M28" display="inline"><mml:mrow><mml:msub><mml:mi>log⁡</mml:mi><mml:mn mathvariant="normal">10</mml:mn></mml:msub></mml:mrow></mml:math></inline-formula> axes, respectively.)</p><?xmltex \hack{\newpage}?>
<sec id="Ch1.S3.SS2.SSS1">
  <label>3.2.1</label><title>Step 2a – apply cross-wavelet transform (XWT) to observations and simulations</title>
      <p id="d1e1095">The cross-wavelet transform (XWT) is performed between the observed and
synthetic time series. Given the WTs of an observed time series <inline-formula><mml:math id="M29" display="inline"><mml:mrow><mml:msubsup><mml:mi>W</mml:mi><mml:mi>n</mml:mi><mml:mi>X</mml:mi></mml:msubsup><mml:mo>(</mml:mo><mml:mi>s</mml:mi><mml:mo>)</mml:mo></mml:mrow></mml:math></inline-formula> and a modeled time series <inline-formula><mml:math id="M30" display="inline"><mml:mrow><mml:msubsup><mml:mi>W</mml:mi><mml:mi>n</mml:mi><mml:mi>Y</mml:mi></mml:msubsup><mml:mo>(</mml:mo><mml:mi>s</mml:mi><mml:mo>)</mml:mo></mml:mrow></mml:math></inline-formula>, the cross-wavelet spectrum can be defined as follows:
              <disp-formula id="Ch1.E3" content-type="numbered"><label>3</label><mml:math id="M31" display="block"><mml:mrow><mml:msubsup><mml:mi>W</mml:mi><mml:mi>n</mml:mi><mml:mrow><mml:mi>X</mml:mi><mml:mi>Y</mml:mi></mml:mrow></mml:msubsup><mml:mo>(</mml:mo><mml:mi>s</mml:mi><mml:mo>)</mml:mo><mml:mo>=</mml:mo><mml:msubsup><mml:mi>W</mml:mi><mml:mi>n</mml:mi><mml:mi>X</mml:mi></mml:msubsup><mml:mo>(</mml:mo><mml:mi>s</mml:mi><mml:mo>)</mml:mo><mml:msubsup><mml:mi>W</mml:mi><mml:mi>n</mml:mi><mml:mrow><mml:msup><mml:mi>Y</mml:mi><mml:mo>*</mml:mo></mml:msup></mml:mrow></mml:msubsup><mml:mo>(</mml:mo><mml:mi>s</mml:mi><mml:mo>)</mml:mo><mml:mo>,</mml:mo></mml:mrow></mml:math></disp-formula>
            where the asterisk denotes the complex conjugate. The cross-wavelet power is
defined as <inline-formula><mml:math id="M32" display="inline"><mml:mrow><mml:mo>|</mml:mo><mml:msubsup><mml:mi>W</mml:mi><mml:mi>n</mml:mi><mml:mrow><mml:mi>X</mml:mi><mml:mi>Y</mml:mi></mml:mrow></mml:msubsup><mml:mo>(</mml:mo><mml:mi>s</mml:mi><mml:mo>)</mml:mo><mml:mo>|</mml:mo></mml:mrow></mml:math></inline-formula> and signifies the joint power of the two time series. The XWT between the Onion Creek observations and the synthetic 5 h offset time series is shown in Fig. 3b, with power represented by the color scale.</p>
      <p id="d1e1219">Similar to step 1b of the WT, we can also calculate areas of significance for the XWT power as shown by the black contour in Fig. 3b. For the XWT, significance is calculated with respect to the theoretical background wavelet spectra of each time series (Torrence and Compo, 1998). We define XWT events as points of significant XWT power outside the COI. XWT events indicate significant joint variability between the observed and modeled time series. Below, in step 2d, we employ XWT events as a basis for identifying hits and misses on observed events for which the timing errors are calculated. Figure 3c shows the observed events (colors) and the intersection between the observed and XWT events (dashed contour). As described later, this intersection (inside dashed contour) is a region of hits where timing errors are considered valid. Note that the early part of the observed events at shorter timescales is not in the XWT events. This is because the timing offset in the modeled time series misses the early part of the observed event for some timescales.</p>
</sec>
<sec id="Ch1.S3.SS2.SSS2">
  <label>3.2.2</label><title>Step 2b: calculate the cross-wavelet timing errors</title>
      <p id="d1e1230">For complex wavelets, such as the Morlet used in this paper, the individual WTs include an imaginary component of the convolution. Together, the real and imaginary parts of the convolution describe the phase of each time series with respect to the wavelet. The cross-wavelet transform combines the WTs in conjugate, allowing the calculation of a phase difference or angle
(radians), which can be computed as follows:
              <disp-formula id="Ch1.E4" content-type="numbered"><label>4</label><mml:math id="M33" display="block"><mml:mrow><mml:msubsup><mml:mi mathvariant="italic">ϕ</mml:mi><mml:mi>n</mml:mi><mml:mrow><mml:mi>X</mml:mi><mml:mi>Y</mml:mi></mml:mrow></mml:msubsup><mml:mo>(</mml:mo><mml:mi>s</mml:mi><mml:mo>)</mml:mo><mml:mo>=</mml:mo><mml:msup><mml:mi>tan⁡</mml:mi><mml:mrow><mml:mo>-</mml:mo><mml:mn mathvariant="normal">1</mml:mn></mml:mrow></mml:msup><mml:mfenced close="]" open="["><mml:mstyle displaystyle="true"><mml:mfrac style="display"><mml:mrow><mml:mi>I</mml:mi><mml:mfenced close=")" open="("><mml:mrow><mml:mi mathvariant="script">I</mml:mi><mml:mo>〈</mml:mo><mml:msup><mml:mi>s</mml:mi><mml:mrow><mml:mo>-</mml:mo><mml:mn mathvariant="normal">1</mml:mn></mml:mrow></mml:msup><mml:msubsup><mml:mi>W</mml:mi><mml:mi>n</mml:mi><mml:mrow><mml:mi>X</mml:mi><mml:mi>Y</mml:mi></mml:mrow></mml:msubsup><mml:mo>(</mml:mo><mml:mi>s</mml:mi><mml:mo>)</mml:mo><mml:mo>〉</mml:mo></mml:mrow></mml:mfenced></mml:mrow><mml:mrow><mml:mi mathvariant="script">R</mml:mi><mml:mfenced close=")" open="("><mml:mrow><mml:mi mathvariant="script">I</mml:mi><mml:mo>〈</mml:mo><mml:msup><mml:mi>s</mml:mi><mml:mrow><mml:mo>-</mml:mo><mml:mn mathvariant="normal">1</mml:mn></mml:mrow></mml:msup><mml:msubsup><mml:mi>W</mml:mi><mml:mi>n</mml:mi><mml:mrow><mml:mi>X</mml:mi><mml:mi>Y</mml:mi></mml:mrow></mml:msubsup><mml:mo>(</mml:mo><mml:mi>s</mml:mi><mml:mo>)</mml:mo><mml:mo>〉</mml:mo></mml:mrow></mml:mfenced></mml:mrow></mml:mfrac></mml:mstyle></mml:mfenced><mml:mo>,</mml:mo></mml:mrow></mml:math></disp-formula>
            where <inline-formula><mml:math id="M34" display="inline"><mml:mi mathvariant="script">I</mml:mi></mml:math></inline-formula> is the imaginary and <inline-formula><mml:math id="M35" display="inline"><mml:mi mathvariant="script">R</mml:mi></mml:math></inline-formula> is the real component of <inline-formula><mml:math id="M36" display="inline"><mml:mrow><mml:msubsup><mml:mi>W</mml:mi><mml:mi>n</mml:mi><mml:mrow><mml:mi>X</mml:mi><mml:mi>Y</mml:mi></mml:mrow></mml:msubsup><mml:mo>(</mml:mo><mml:mi>s</mml:mi><mml:mo>)</mml:mo></mml:mrow></mml:math></inline-formula>. The arrows in Fig. 3b indicate the phase difference for our example case, which is used to calculate the timing errors. Note that these are calculated at all points in the wavelet domain.</p>
      <?pagebreak page2606?><p id="d1e1376">The distance around the phase circle at each timescale is the Fourier period (hours). We convert the phase angle into the timing errors (hours) as in Liu et al. (2011) as follows:
<?xmltex \hack{\newpage}?><?xmltex \hack{\vspace*{-6mm}}?>
              <disp-formula id="Ch1.E5" content-type="numbered"><label>5</label><mml:math id="M37" display="block"><mml:mrow><mml:mi mathvariant="normal">Δ</mml:mi><mml:msubsup><mml:mi>t</mml:mi><mml:mi>n</mml:mi><mml:mrow><mml:mi>X</mml:mi><mml:mi>Y</mml:mi></mml:mrow></mml:msubsup><mml:mo>(</mml:mo><mml:mi>s</mml:mi><mml:mo>)</mml:mo><mml:mo>=</mml:mo><mml:msubsup><mml:mi mathvariant="italic">ϕ</mml:mi><mml:mi>n</mml:mi><mml:mrow><mml:mi>X</mml:mi><mml:mi>Y</mml:mi></mml:mrow></mml:msubsup><mml:mo>(</mml:mo><mml:mi>s</mml:mi><mml:mo>)</mml:mo><mml:mo>⋅</mml:mo><mml:mi>T</mml:mi><mml:mo>/</mml:mo><mml:mn mathvariant="normal">2</mml:mn><mml:mi mathvariant="italic">π</mml:mi><mml:mo>,</mml:mo></mml:mrow></mml:math></disp-formula>
            where <inline-formula><mml:math id="M38" display="inline"><mml:mi>T</mml:mi></mml:math></inline-formula> is the equivalent Fourier period of the wavelet. Note that the
maximum timing error which can be represented at each timescale is half the
Fourier period because the phase angle is in the interval (<inline-formula><mml:math id="M39" display="inline"><mml:mrow><mml:mo>-</mml:mo><mml:mi mathvariant="italic">π</mml:mi></mml:mrow></mml:math></inline-formula>, <inline-formula><mml:math id="M40" display="inline"><mml:mi mathvariant="italic">π</mml:mi></mml:math></inline-formula>). In
other words, only timescales greater than <inline-formula><mml:math id="M41" display="inline"><mml:mrow><mml:mn mathvariant="normal">2</mml:mn><mml:mi>E</mml:mi></mml:mrow></mml:math></inline-formula> can accurately represent a
timing error <inline-formula><mml:math id="M42" display="inline"><mml:mi>E</mml:mi></mml:math></inline-formula>. Because the range of the arctan function is limited by <inline-formula><mml:math id="M43" display="inline"><mml:mrow><mml:mo>±</mml:mo><mml:mi mathvariant="italic">π</mml:mi></mml:mrow></mml:math></inline-formula>, true phase angles outside this range alias to angles inside this range. (For example, the phase angles <inline-formula><mml:math id="M44" display="inline"><mml:mrow><mml:mn mathvariant="normal">1.05</mml:mn><mml:mo>⋅</mml:mo><mml:mi mathvariant="italic">π</mml:mi></mml:mrow></mml:math></inline-formula> and <inline-formula><mml:math id="M45" display="inline"><mml:mrow><mml:mo>-</mml:mo><mml:mn mathvariant="normal">0.95</mml:mn><mml:mo>⋅</mml:mo><mml:mi mathvariant="italic">π</mml:mi></mml:mrow></mml:math></inline-formula> are both assigned to <inline-formula><mml:math id="M46" display="inline"><mml:mrow><mml:mo>-</mml:mo><mml:mn mathvariant="normal">0.95</mml:mn><mml:mo>⋅</mml:mo><mml:mi mathvariant="italic">π</mml:mi></mml:mrow></mml:math></inline-formula>). Also note that, when the wavelet transforms are approximately antiphase, the computed phase differences and timing errors produce corresponding bimodal distributions given the noise in the data. Figure 3c shows phase aliasing in the negative timing errors at timescales less than 10 h, which is double the 5 h synthetic timing error we introduced. The bimodality of the phase and timing are also seen at the 10 h timescale when the timing errors abruptly change sign (or phase by <inline-formula><mml:math id="M47" display="inline"><mml:mrow><mml:mn mathvariant="normal">2</mml:mn><mml:mi mathvariant="italic">π</mml:mi></mml:mrow></mml:math></inline-formula>). We note the convention used is that the XWT produces timing errors that are interpreted as modeled minus observed, i.e., positive values mean the model occurs after the observed. Positive 5 h timing errors in Fig. 3c describe that the model is late compared to the observations as seen in the hydrographs in the top panel (Fig. 3a).</p>
</sec>
<sec id="Ch1.S3.SS2.SSS3">
  <label>3.2.3</label><title>Step 2c – subset cross-wavelet timing errors to sampled observed events</title>
      <p id="d1e1549">Step 2b results in an estimate of timing errors for all times and timescales
in the cross-wavelet transform space. In our application, we are interested
in the timing errors that correspond to the identified sample of observed events, especially for the maximum power events in each cluster for each characteristic timescale. In the synthetic Onion Creek example, the point of interest in the wavelet transform of the observed time series, used to sample the timing errors produced by the XWT, is shown by the gray asterisk in Fig. 3c.</p>
      <p id="d1e1552">The results for the synthetic Onion Creek example are summarized in Table 2.
For the identified characteristic timescale of 22 h in the observed wavelet power (which had an average WT power of 555 700 m<inline-formula><mml:math id="M48" display="inline"><mml:msup><mml:mi/><mml:mn mathvariant="normal">6</mml:mn></mml:msup></mml:math></inline-formula> s<inline-formula><mml:math id="M49" display="inline"><mml:msup><mml:mi/><mml:mrow><mml:mo>-</mml:mo><mml:mn mathvariant="normal">2</mml:mn></mml:mrow></mml:msup></mml:math></inline-formula>; see Fig. 2c on the right), there was one event cluster, and the timing error at the cluster maximum was 5 h, and it occurred at hour 37 of the time series.</p>

<?xmltex \floatpos{t}?><table-wrap id="Ch1.T2"><?xmltex \currentcnt{2}?><label>Table 2</label><caption><p id="d1e1579">Summary of timing error results for cluster maxima for the isolated peak and prescribed 5 h offset from Onion Creek, TX.</p></caption><oasis:table frame="topbot"><?xmltex \begin{scaleboxenv}{.90}[.90]?><oasis:tgroup cols="6">
     <oasis:colspec colnum="1" colname="col1" align="left"/>
     <oasis:colspec colnum="2" colname="col2" align="center"/>
     <oasis:colspec colnum="3" colname="col3" align="center"/>
     <oasis:colspec colnum="4" colname="col4" align="center"/>
     <oasis:colspec colnum="5" colname="col5" align="center"/>
     <oasis:colspec colnum="6" colname="col6" align="center"/>
     <oasis:thead>
       <oasis:row>
         <oasis:entry colname="col1">Characteristic</oasis:entry>
         <oasis:entry colname="col2">Average WT</oasis:entry>
         <oasis:entry colname="col3">Number of</oasis:entry>
         <oasis:entry rowsep="1" namest="col4" nameend="col6">Cluster maxima </oasis:entry>
       </oasis:row>
       <oasis:row>
         <oasis:entry colname="col1">timescale (h)</oasis:entry>
         <oasis:entry colname="col2">power</oasis:entry>
         <oasis:entry colname="col3">clusters</oasis:entry>
         <oasis:entry colname="col4">Timing</oasis:entry>
         <oasis:entry colname="col5">Time</oasis:entry>
         <oasis:entry colname="col6">Hit?</oasis:entry>
       </oasis:row>
       <oasis:row rowsep="1">
         <oasis:entry colname="col1"/>
         <oasis:entry colname="col2"/>
         <oasis:entry colname="col3"/>
         <oasis:entry colname="col4">error (h)</oasis:entry>
         <oasis:entry colname="col5">(h)</oasis:entry>
         <oasis:entry colname="col6"/>
       </oasis:row>
     </oasis:thead>
     <oasis:tbody>
       <oasis:row>
         <oasis:entry colname="col1">22</oasis:entry>
         <oasis:entry colname="col2">555 700</oasis:entry>
         <oasis:entry colname="col3">1</oasis:entry>
         <oasis:entry colname="col4">5</oasis:entry>
         <oasis:entry colname="col5">37</oasis:entry>
         <oasis:entry colname="col6">True</oasis:entry>
       </oasis:row>
     </oasis:tbody>
   </oasis:tgroup><?xmltex \end{scaleboxenv}?></oasis:table></table-wrap>

</sec>
<sec id="Ch1.S3.SS2.SSS4">
  <label>3.2.4</label><title>Step 2d – filter misses</title>
      <p id="d1e1691">The premise of computing a timing error between the observed and modeled time series is that they share common events which can be meaningfully compared. In a two-way contingency analysis of events, a hit refers to when the modeled time series reproduces an observed event. When the modeled time series fails to reproduce an observed event, it is termed a miss. In the case of a miss, it does not make sense to include the timing error in the overall assessment. Once the characteristic timescales of the observed event spectrum are identified and event cluster maxima are located, timing errors are obtained at these locations in the XWT. In this step, the significance of the XWT on these event cluster maxima is used to decide if the model produced a hit or a miss for each point and to determine if the timing error is valid. As previewed above, Fig. 3c shows the observed events (colors), and the dashed contour shows the intersection between the observed and XWT events. Regions of intersection between observed events and XWT events are considered model hits, and observed events falling outside the XWT events are considered misses. Because we constrain our analysis to observed events in the wavelet power spectrum, we do not consider either of the remaining categories in a two-way analysis (false alarms and correct negatives). We note that a complete two-way event analysis could, alternatively, be constructed in the wavelet domain based on the Venn diagram of the observed and modeled events without necessarily using the XWT. We choose to use the XWT events because the XWT is the basis of the timing errors.</p>
      <p id="d1e1694">In the synthetic example of Onion Creek, a single characteristic timescale
and event cluster yields a single cluster maximum, as shown by the asterisk in
Fig. 3c. Because this asterisk falls both within the observed and XWT events,
it is a hit, and the timing error at that point is valid (Table 2). For a
longer time series, as seen in subsequent examples, a useful diagnostic and
complement to the timing error statistics at each characteristic timescale is
the percent hits. When summarizing timing error statistics for a timescale,
we drop misses from the calculation and the percent hits indicates what portion
of the time series was dropped (percent misses is equal to <inline-formula><mml:math id="M50" display="inline"><mml:mrow><mml:mn mathvariant="normal">100</mml:mn><mml:mspace linebreak="nobreak" width="0.25em"/><mml:mo>-</mml:mo></mml:mrow></mml:math></inline-formula> percent hits). In our tables, we provided timing error statistics for hits only.</p>
</sec>
</sec>
</sec>
<sec id="Ch1.S4">
  <label>4</label><title>Results</title>
      <p id="d1e1718">In the previous section, we illustrate the method using an isolated peak and
a prescribed timing error. In this section, we demonstrate the method using
NWM model simulations which introduce greater complexity and longer time
series. Finally, we show version-over-version comparisons for 5-year simulations to illustrate the utility for evaluation.</p>

      <?xmltex \floatpos{t}?><fig id="Ch1.F4" specific-use="star"><?xmltex \currentcnt{4}?><?xmltex \def\figurename{Figure}?><label>Figure 4</label><caption><p id="d1e1723">For the 3-month time series from the Pemigewasset River, NH, panel <bold>(a)</bold> shows the observed time series, and <bold>(b)</bold> shows the observed wavelet power spectrum (left) and average power by timescale for all points (right). Panel <bold>(c)</bold> shows the statistically significant wavelet power spectrum of events (left) and average power by timescale for all events, with maxima shown by gray dots (right). Panel <bold>(d)</bold> shows the characteristic scale event clusters (horizontal lines) and cluster maxima (gray asterisks).</p></caption>
        <?xmltex \igopts{width=398.338583pt}?><graphic xlink:href="https://hess.copernicus.org/articles/25/2599/2021/hess-25-2599-2021-f04.png"/>

      </fig>

<?xmltex \hack{\newpage}?>
<?pagebreak page2607?><sec id="Ch1.S4.SS1">
  <label>4.1</label><title>Demonstration using NWM data</title>
<sec id="Ch1.S4.SS1.SSS1">
  <label>4.1.1</label><title>Pemigewasset River, NH</title>
      <p id="d1e1761">This example uses a 3-month time series from the Pemigewasset River, NH,
to examine multiple peaks in the hydrograph (Fig. 4a). It is fairly straightforward to pick out three main peaks with the naked eye. From step 1 of our method, the wavelet transform is applied to the observations (Fig. 4b, left panel; Fig. 4c, left panel), revealing up to three event clusters, depending on the characteristic timescale examined (Fig. 4d). When we plot the average event power by timescale (Fig. 4c, right panel), we see that there are nine relative maxima (small gray dots); hence, there are nine characteristic scales for this example. The cluster maxima (gray asterisks) for each observed event cluster are shown in Fig. 4d.</p>

      <?xmltex \floatpos{t}?><fig id="Ch1.F5" specific-use="star"><?xmltex \currentcnt{5}?><?xmltex \def\figurename{Figure}?><label>Figure 5</label><caption><p id="d1e1766">For 3-month time series from Pemigewasset River, NH, panel <bold>(a)</bold> shows the observed and simulated NWM time series (note the logged <inline-formula><mml:math id="M51" display="inline"><mml:mi>y</mml:mi></mml:math></inline-formula> axis), <bold>(b)</bold>  shows the cross-wavelet (XWT) power spectrum (colors), phase angles (arrows), and statistically significant XWT events (solid contours), and <bold>(c)</bold> shows the sampled timing errors for observed events (inside dashed contour indicates intersection of XWT events with observed events) and cluster maxima (gray asterisks).</p></caption>
            <?xmltex \igopts{width=398.338583pt}?><graphic xlink:href="https://hess.copernicus.org/articles/25/2599/2021/hess-25-2599-2021-f05.png"/>

          </fig>

      <?pagebreak page2608?><p id="d1e1791">Next, we compare the observed time series with the simulation from the NWM V1.2 (Fig. 5a) and follow step 2 of our method: (a) apply the cross-wavelet transform (Fig. 5b colors), (b) calculate the timing error for all observed events from the phase difference (Fig. 5b arrows), (c) subset the timing errors to the observed cluster maxima (Fig. 5c asterisks), and (d) retain only modeled hits (Fig. 5c asterisks within the dashed contours). Table 3 is ordered, by characteristic timescales, from highest to lowest average power; we only show the top five characteristic scales. The absolute maximum of the time average event spectrum has a timescale equal to 24.8 h; for cluster one, the model is nearly 11 h late, and cluster two is early (<inline-formula><mml:math id="M52" display="inline"><mml:mrow><mml:mo>-</mml:mo><mml:mn mathvariant="normal">3.5</mml:mn></mml:mrow></mml:math></inline-formula> h). Both are hits, and the average timing error is 3.5 h late. However, for the next timescale (<inline-formula><mml:math id="M53" display="inline"><mml:mrow><mml:mo>=</mml:mo><mml:mn mathvariant="normal">27.8</mml:mn></mml:mrow></mml:math></inline-formula> h), the third cluster maximum is a miss, so its timing error is reported as n/a (not applicable) and is not included in the average. This miss can be seen in Fig. 5c where the cluster 3 asterisk falls just outside the XWT events for the 27.8 h, timescale. Moreover, this miss can also be interpreted from the comparison of the hydrographs in Fig. 5a where the modeled third peak does not reasonably approximate the magnitude of the observed peak. Interestingly, while it is a narrow miss at the shorter timescale of 27.8 h, the associated (third) cluster maxima at the next most powerful characteristic timescale (33.1 h) is a hit. This reflects that the hydrograph is insufficiently peaked for this event but does have some of the observed, lower-frequency variability. Overall, the characteristic timescale of 33.1 h has timing results similar to the 27.8 h timescale, with the exception of the third cluster maximum. This raises the question of whether these are distinct characteristic timescales. In Sect. 5, we discuss smoothing the time average event power by timescale to address this issue.</p>
      <p id="d1e1815">The characteristic timescale with the fourth-highest time-averaged power occurs at 111 h, which is a different order of magnitude, suggesting that this may have a different physical process driving it. At this timescale, the model is late in both event clusters (10 and 16 h). Results are similar for the next timescale of 148 h. We do not show results for the remaining four characteristic timescales with lower average power, since they have similar characteristic timescale values and associated timing errors to what has already been shown.</p>

      <?xmltex \floatpos{t}?><fig id="Ch1.F6" specific-use="star"><?xmltex \currentcnt{6}?><?xmltex \def\figurename{Figure}?><label>Figure 6</label><caption><p id="d1e1820">For a 1-year time series from Taylor River, CO, panel <bold>(a)</bold> shows the observed time series, and <bold>(b)</bold> shows observed wavelet power spectrum (left) and average power by timescale for all points (right). Panel <bold>(c)</bold> shows the statistically significant wavelet power spectrum of events (left) and average power by timescale for all events, with maxima shown by gray dots (right). Panel <bold>(d)</bold> shows the characteristic scale event clusters (horizontal lines).</p></caption>
            <?xmltex \igopts{width=398.338583pt}?><graphic xlink:href="https://hess.copernicus.org/articles/25/2599/2021/hess-25-2599-2021-f06.png"/>

          </fig>

      <?xmltex \floatpos{t}?><fig id="Ch1.F7" specific-use="star"><?xmltex \currentcnt{7}?><?xmltex \def\figurename{Figure}?><label>Figure 7</label><caption><p id="d1e1843">For a 1-year time series from Taylor River, CO, panel <bold>(a)</bold> shows the observed and simulated NWM time series (note the logged <inline-formula><mml:math id="M54" display="inline"><mml:mi>y</mml:mi></mml:math></inline-formula> axis), <bold>(b)</bold> shows the cross-wavelet (XWT) power spectrum (colors), phase angles (arrows), and statistically significant XWT events (solid contours). Panel <bold>(c)</bold> shows the sampled timing errors for observed events (inside dashed contour indicates intersection of XWT events with observed events).</p></caption>
            <?xmltex \igopts{width=398.338583pt}?><graphic xlink:href="https://hess.copernicus.org/articles/25/2599/2021/hess-25-2599-2021-f07.png"/>

          </fig>

      <?xmltex \floatpos{t}?><fig id="Ch1.F8"><?xmltex \currentcnt{8}?><?xmltex \def\figurename{Figure}?><label>Figure 8</label><caption><p id="d1e1870">Magnified view of the spring runoff of a 1-year time series for Taylor Park, CO, showing the observed and simulated NWM time series.</p></caption>
            <?xmltex \igopts{width=236.157874pt}?><graphic xlink:href="https://hess.copernicus.org/articles/25/2599/2021/hess-25-2599-2021-f08.png"/>

          </fig>

</sec>
<?pagebreak page2609?><sec id="Ch1.S4.SS1.SSS2">
  <label>4.1.2</label><title>Taylor River, CO</title>
      <p id="d1e1887">In this example, we examine a 1-year time series from Taylor River, CO,
that illustrates hydrograph peaks driven by different processes. The Taylor
River is in a mountainous area where the spring hydrology is dominated by
snowmelt runoff. Figure 6a shows the time series from Taylor River, CO,
where we can see the snowmelt runoff in spring and also several peaks in
summer, likely driven by summer rains. Figure 6b shows the WT and
illustrates how missing data is handled. This results in additional COIs (muted colors) to account for the edge effects, and areas of the COI are
ignored in our analyses.</p>
      <p id="d1e1890"><?xmltex \hack{\newpage}?>From the statistically significant events in the WT, we see the peak in the
characteristic timescales at 23.4 h (Fig. 6c, right), and there is another maxima at the 99 and 118 h timescales. The process-based shift in
dominant timescales is evident in the wavelet power (Fig. 6b and c). The
23.4 h timescale is dominant before 1 July, during snowmelt runoff, and
then shifts to the 99 and 118 h timescales, relating to flows from summer
rains. In step 2, we compare the observed time series with the simulation from the NWM V1.2 (Fig. 7a); here, it is useful to magnify the spring melt season time series (Fig. 8), where we see that the amplitude of the diurnal signal is too high, but it is hard to visually tell much about the timing error. Next, the cross-wavelet transform (Fig. 7b) and timing errors are calculated<?pagebreak page2610?> (Fig. 7c). The results are summarized in Table 4. Starting with the dominant 23.4 h timescale, we see that there are 11 clusters, that 73 % (<inline-formula><mml:math id="M55" display="inline"><mml:mrow><mml:mo>=</mml:mo><mml:mn mathvariant="normal">8</mml:mn><mml:mo>/</mml:mo><mml:mn mathvariant="normal">11</mml:mn></mml:mrow></mml:math></inline-formula> cluster maxima) are hits, and that the model is generally early (the mean is 6 h early). For the 118 and 99 h timescales, there are no hits. This suggests that we are confident in the timing errors of the model for the diurnal snowmelt cycle, and these timing errors can be used as guidance for model performance and model improvements. However, the model does not successfully reproduce key variability during the summer, and timing errors are not valid at this timescale. This underscores the key point that timing errors are timescale dependent and can help diagnose which processes to target for improvements.</p>

<?xmltex \floatpos{t}?><table-wrap id="Ch1.T3" specific-use="star"><?xmltex \currentcnt{3}?><label>Table 3</label><caption><p id="d1e1911">For a 3-month time series from Pemigewasset River, NH, by
characteristic timescale, this is a summary of the timing error results for cluster maxima that were hits when using NWM v1.2.</p></caption><oasis:table frame="topbot"><oasis:tgroup cols="8">
     <oasis:colspec colnum="1" colname="col1" align="left"/>
     <oasis:colspec colnum="2" colname="col2" align="center"/>
     <oasis:colspec colnum="3" colname="col3" align="center"/>
     <oasis:colspec colnum="4" colname="col4" align="right"/>
     <oasis:colspec colnum="5" colname="col5" align="left"/>
     <oasis:colspec colnum="6" colname="col6" align="center"/>
     <oasis:colspec colnum="7" colname="col7" align="right"/>
     <oasis:colspec colnum="8" colname="col8" align="right"/>
     <oasis:thead>
       <oasis:row>

         <oasis:entry colname="col1">Characteristic</oasis:entry>

         <oasis:entry colname="col2">Avg WT</oasis:entry>

         <oasis:entry colname="col3">Cluster</oasis:entry>

         <oasis:entry colname="col4">Timing</oasis:entry>

         <oasis:entry colname="col5">Hit?</oasis:entry>

         <oasis:entry colname="col6">Total</oasis:entry>

         <oasis:entry colname="col7">Percent of</oasis:entry>

         <oasis:entry colname="col8">Avg</oasis:entry>

       </oasis:row>
       <oasis:row>

         <oasis:entry colname="col1">timescale (h)</oasis:entry>

         <oasis:entry colname="col2">power</oasis:entry>

         <oasis:entry colname="col3"/>

         <oasis:entry colname="col4">error (h)</oasis:entry>

         <oasis:entry colname="col5"/>

         <oasis:entry colname="col6">number of</oasis:entry>

         <oasis:entry colname="col7">hits</oasis:entry>

         <oasis:entry colname="col8">timing</oasis:entry>

       </oasis:row>
       <oasis:row rowsep="1">

         <oasis:entry colname="col1"/>

         <oasis:entry colname="col2"/>

         <oasis:entry colname="col3"/>

         <oasis:entry colname="col4"/>

         <oasis:entry colname="col5"/>

         <oasis:entry colname="col6">clusters</oasis:entry>

         <oasis:entry colname="col7"/>

         <oasis:entry colname="col8">error (h)</oasis:entry>

       </oasis:row>
     </oasis:thead>
     <oasis:tbody>
       <oasis:row>

         <oasis:entry rowsep="1" colname="col1" morerows="1">24.8</oasis:entry>

         <oasis:entry rowsep="1" colname="col2" morerows="1">82 800</oasis:entry>

         <oasis:entry colname="col3">1</oasis:entry>

         <oasis:entry colname="col4">10.7</oasis:entry>

         <oasis:entry colname="col5">True</oasis:entry>

         <oasis:entry rowsep="1" colname="col6" morerows="1">2</oasis:entry>

         <oasis:entry rowsep="1" colname="col7" morerows="1">100</oasis:entry>

         <oasis:entry rowsep="1" colname="col8" morerows="1">3.5</oasis:entry>

       </oasis:row>
       <oasis:row rowsep="1">

         <oasis:entry colname="col3">2</oasis:entry>

         <oasis:entry colname="col4"><inline-formula><mml:math id="M56" display="inline"><mml:mrow><mml:mo>-</mml:mo><mml:mn mathvariant="normal">3.64</mml:mn></mml:mrow></mml:math></inline-formula></oasis:entry>

         <oasis:entry colname="col5">True</oasis:entry>

       </oasis:row>
       <oasis:row>

         <oasis:entry rowsep="1" colname="col1" morerows="2">27.8</oasis:entry>

         <oasis:entry rowsep="1" colname="col2" morerows="2">74 400</oasis:entry>

         <oasis:entry colname="col3">1</oasis:entry>

         <oasis:entry colname="col4">9.54</oasis:entry>

         <oasis:entry colname="col5">True</oasis:entry>

         <oasis:entry rowsep="1" colname="col6" morerows="2">3</oasis:entry>

         <oasis:entry rowsep="1" colname="col7" morerows="2">67</oasis:entry>

         <oasis:entry rowsep="1" colname="col8" morerows="2">2.8</oasis:entry>

       </oasis:row>
       <oasis:row>

         <oasis:entry colname="col3">2</oasis:entry>

         <oasis:entry colname="col4"><inline-formula><mml:math id="M57" display="inline"><mml:mrow><mml:mo>-</mml:mo><mml:mn mathvariant="normal">3.99</mml:mn></mml:mrow></mml:math></inline-formula></oasis:entry>

         <oasis:entry colname="col5">True</oasis:entry>

       </oasis:row>
       <oasis:row rowsep="1">

         <oasis:entry colname="col3">3</oasis:entry>

         <oasis:entry colname="col4">n/a</oasis:entry>

         <oasis:entry colname="col5">False</oasis:entry>

       </oasis:row>
       <oasis:row>

         <oasis:entry rowsep="1" colname="col1" morerows="2">33.1</oasis:entry>

         <oasis:entry rowsep="1" colname="col2" morerows="2">73 100</oasis:entry>

         <oasis:entry colname="col3">1</oasis:entry>

         <oasis:entry colname="col4">8.41</oasis:entry>

         <oasis:entry colname="col5">True</oasis:entry>

         <oasis:entry rowsep="1" colname="col6" morerows="2">3</oasis:entry>

         <oasis:entry rowsep="1" colname="col7" morerows="2">100</oasis:entry>

         <oasis:entry rowsep="1" colname="col8" morerows="2">1.2</oasis:entry>

       </oasis:row>
       <oasis:row>

         <oasis:entry colname="col3">2</oasis:entry>

         <oasis:entry colname="col4"><inline-formula><mml:math id="M58" display="inline"><mml:mrow><mml:mo>-</mml:mo><mml:mn mathvariant="normal">2.12</mml:mn></mml:mrow></mml:math></inline-formula></oasis:entry>

         <oasis:entry colname="col5">True</oasis:entry>

       </oasis:row>
       <oasis:row rowsep="1">

         <oasis:entry colname="col3">3</oasis:entry>

         <oasis:entry colname="col4"><inline-formula><mml:math id="M59" display="inline"><mml:mrow><mml:mo>-</mml:mo><mml:mn mathvariant="normal">2.71</mml:mn></mml:mrow></mml:math></inline-formula></oasis:entry>

         <oasis:entry colname="col5">True</oasis:entry>

       </oasis:row>
       <oasis:row>

         <oasis:entry rowsep="1" colname="col1" morerows="1">111</oasis:entry>

         <oasis:entry rowsep="1" colname="col2" morerows="1">72 000</oasis:entry>

         <oasis:entry colname="col3">1</oasis:entry>

         <oasis:entry colname="col4">10.0</oasis:entry>

         <oasis:entry colname="col5">True</oasis:entry>

         <oasis:entry rowsep="1" colname="col6" morerows="1">2</oasis:entry>

         <oasis:entry rowsep="1" colname="col7" morerows="1">100</oasis:entry>

         <oasis:entry rowsep="1" colname="col8" morerows="1">13</oasis:entry>

       </oasis:row>
       <oasis:row rowsep="1">

         <oasis:entry colname="col3">2</oasis:entry>

         <oasis:entry colname="col4">16.5</oasis:entry>

         <oasis:entry colname="col5">True</oasis:entry>

       </oasis:row>
       <oasis:row>

         <oasis:entry colname="col1" morerows="1">148</oasis:entry>

         <oasis:entry colname="col2" morerows="1">58 200</oasis:entry>

         <oasis:entry colname="col3">1</oasis:entry>

         <oasis:entry colname="col4">12.0</oasis:entry>

         <oasis:entry colname="col5">True</oasis:entry>

         <oasis:entry colname="col6" morerows="1">2</oasis:entry>

         <oasis:entry colname="col7" morerows="1">100</oasis:entry>

         <oasis:entry colname="col8" morerows="1">14</oasis:entry>

       </oasis:row>
       <oasis:row>

         <oasis:entry colname="col3">2</oasis:entry>

         <oasis:entry colname="col4">15.0</oasis:entry>

         <oasis:entry colname="col5">True</oasis:entry>

       </oasis:row>
     </oasis:tbody>
   </oasis:tgroup></oasis:table><table-wrap-foot><p id="d1e1914">The term n/a stands for not applicable.</p></table-wrap-foot></table-wrap>

<?xmltex \floatpos{t}?><table-wrap id="Ch1.T4" specific-use="star"><?xmltex \currentcnt{4}?><label>Table 4</label><caption><p id="d1e2283">For a 1-year time series from Taylor River, CO, by characteristic
timescale, this is a summary of the timing error results for the cluster maxima that were hits when using NWM v1.2.</p></caption><oasis:table frame="topbot"><oasis:tgroup cols="7">
     <oasis:colspec colnum="1" colname="col1" align="left"/>
     <oasis:colspec colnum="2" colname="col2" align="right"/>
     <oasis:colspec colnum="3" colname="col3" align="right"/>
     <oasis:colspec colnum="4" colname="col4" align="right"/>
     <oasis:colspec colnum="5" colname="col5" align="right"/>
     <oasis:colspec colnum="6" colname="col6" align="right"/>
     <oasis:colspec colnum="7" colname="col7" align="right"/>
     <oasis:thead>
       <oasis:row>
         <oasis:entry colname="col1">Characteristic</oasis:entry>
         <oasis:entry colname="col2">Avg WT</oasis:entry>
         <oasis:entry colname="col3">Number of</oasis:entry>
         <oasis:entry colname="col4">Percent</oasis:entry>
         <oasis:entry rowsep="1" namest="col5" nameend="col7" align="center">Timing error (h) </oasis:entry>
       </oasis:row>
       <oasis:row rowsep="1">
         <oasis:entry colname="col1">timescale (h)</oasis:entry>
         <oasis:entry colname="col2">power</oasis:entry>
         <oasis:entry colname="col3">clusters</oasis:entry>
         <oasis:entry colname="col4">of hits</oasis:entry>
         <oasis:entry colname="col5">Min</oasis:entry>
         <oasis:entry colname="col6">Mean</oasis:entry>
         <oasis:entry colname="col7">Max</oasis:entry>
       </oasis:row>
     </oasis:thead>
     <oasis:tbody>
       <oasis:row>
         <oasis:entry colname="col1">23.4</oasis:entry>
         <oasis:entry colname="col2">316</oasis:entry>
         <oasis:entry colname="col3">11</oasis:entry>
         <oasis:entry colname="col4">73</oasis:entry>
         <oasis:entry colname="col5"><inline-formula><mml:math id="M60" display="inline"><mml:mrow><mml:mo>-</mml:mo><mml:mn mathvariant="normal">8.2</mml:mn></mml:mrow></mml:math></inline-formula></oasis:entry>
         <oasis:entry colname="col6"><inline-formula><mml:math id="M61" display="inline"><mml:mrow><mml:mo>-</mml:mo><mml:mn mathvariant="normal">6.0</mml:mn></mml:mrow></mml:math></inline-formula></oasis:entry>
         <oasis:entry colname="col7"><inline-formula><mml:math id="M62" display="inline"><mml:mrow><mml:mo>-</mml:mo><mml:mn mathvariant="normal">3.6</mml:mn></mml:mrow></mml:math></inline-formula></oasis:entry>
       </oasis:row>
       <oasis:row>
         <oasis:entry colname="col1">118</oasis:entry>
         <oasis:entry colname="col2">93.1</oasis:entry>
         <oasis:entry colname="col3">2</oasis:entry>
         <oasis:entry colname="col4">0</oasis:entry>
         <oasis:entry colname="col5">n/a</oasis:entry>
         <oasis:entry colname="col6">n/a</oasis:entry>
         <oasis:entry colname="col7">n/a</oasis:entry>
       </oasis:row>
       <oasis:row>
         <oasis:entry colname="col1">99.1</oasis:entry>
         <oasis:entry colname="col2">90.5</oasis:entry>
         <oasis:entry colname="col3">2</oasis:entry>
         <oasis:entry colname="col4">0</oasis:entry>
         <oasis:entry colname="col5">n/a</oasis:entry>
         <oasis:entry colname="col6">n/a</oasis:entry>
         <oasis:entry colname="col7">n/a</oasis:entry>
       </oasis:row>
     </oasis:tbody>
   </oasis:tgroup></oasis:table><table-wrap-foot><p id="d1e2286">The term n/a stands for not applicable.</p></table-wrap-foot></table-wrap>

</sec>
</sec>
<sec id="Ch1.S4.SS2">
  <label>4.2</label><title>Evaluating model performance</title>
      <p id="d1e2466">Finally, we show how the methodology can be used for evaluating performance
changes across NWM versions. We point out that none of the NWM version upgrades were targeting timing errors, so these results just provide a
demonstration. We use 5-year observed and modeled time series at the three
locations, namely Onion Creek, TX, Pemigewasset River, NH, and Taylor River, CO.</p>
      <p id="d1e2469">For Onion Creek, Table 5 summarizes the results for the three most important
timescales, and Fig. 9 provides a graphical representation of these timing
errors (hits only). For the dominant 29.5 h timescale and for all model
versions, there were 19 cluster maxima, 89.5 % of which were hits, with a
median timing error of 1.4 h early. However, the model shows<?pagebreak page2611?> progressively earlier timing errors with increasing version (Fig. 9). The results are similar for the other two characteristic timescales.</p>

      <?xmltex \floatpos{t}?><fig id="Ch1.F9"><?xmltex \currentcnt{9}?><?xmltex \def\figurename{Figure}?><label>Figure 9</label><caption><p id="d1e2474">A 5-year time series from Onion Creek, TX, which compares cluster maxima timing error distributions for the top three characteristic timescales (see panel title) across NWM versions.</p></caption>
          <?xmltex \igopts{width=236.157874pt}?><graphic xlink:href="https://hess.copernicus.org/articles/25/2599/2021/hess-25-2599-2021-f09.png"/>

        </fig>

<?xmltex \floatpos{t}?><table-wrap id="Ch1.T5"><?xmltex \currentcnt{5}?><label>Table 5</label><caption><p id="d1e2487">Summary of timing errors from cluster maxima that were hits for 5-year time series from Onion Creek, TX.</p></caption><oasis:table frame="topbot"><?xmltex \begin{scaleboxenv}{.80}[.80]?><oasis:tgroup cols="6">
     <oasis:colspec colnum="1" colname="col1" align="left"/>
     <oasis:colspec colnum="2" colname="col2" align="center"/>
     <oasis:colspec colnum="3" colname="col3" align="center"/>
     <oasis:colspec colnum="4" colname="col4" align="center"/>
     <oasis:colspec colnum="5" colname="col5" align="center"/>
     <oasis:colspec colnum="6" colname="col6" align="center"/>
     <oasis:thead>
       <oasis:row>
         <oasis:entry colname="col1">NWM</oasis:entry>
         <oasis:entry colname="col2">Characteristic</oasis:entry>
         <oasis:entry colname="col3">Avg WT</oasis:entry>
         <oasis:entry colname="col4">Number of</oasis:entry>
         <oasis:entry colname="col5">Percent</oasis:entry>
         <oasis:entry colname="col6">Median</oasis:entry>
       </oasis:row>
       <oasis:row>
         <oasis:entry colname="col1">version</oasis:entry>
         <oasis:entry colname="col2">power</oasis:entry>
         <oasis:entry colname="col3">timescale (h)</oasis:entry>
         <oasis:entry colname="col4">clusters</oasis:entry>
         <oasis:entry colname="col5">of hits</oasis:entry>
         <oasis:entry colname="col6">timing</oasis:entry>
       </oasis:row>
       <oasis:row rowsep="1">
         <oasis:entry colname="col1"/>
         <oasis:entry colname="col2"/>
         <oasis:entry colname="col3"/>
         <oasis:entry colname="col4"/>
         <oasis:entry colname="col5"/>
         <oasis:entry colname="col6">error (h)</oasis:entry>
       </oasis:row>
     </oasis:thead>
     <oasis:tbody>
       <oasis:row>
         <oasis:entry colname="col1">v1.0</oasis:entry>
         <oasis:entry colname="col2">29.5</oasis:entry>
         <oasis:entry colname="col3">2 843 000</oasis:entry>
         <oasis:entry colname="col4">19</oasis:entry>
         <oasis:entry colname="col5">89</oasis:entry>
         <oasis:entry colname="col6"><inline-formula><mml:math id="M63" display="inline"><mml:mrow><mml:mo>-</mml:mo><mml:mn mathvariant="normal">1.4</mml:mn></mml:mrow></mml:math></inline-formula></oasis:entry>
       </oasis:row>
       <oasis:row>
         <oasis:entry colname="col1">v1.1</oasis:entry>
         <oasis:entry colname="col2">29.5</oasis:entry>
         <oasis:entry colname="col3">2 843 000</oasis:entry>
         <oasis:entry colname="col4">19</oasis:entry>
         <oasis:entry colname="col5">89</oasis:entry>
         <oasis:entry colname="col6"><inline-formula><mml:math id="M64" display="inline"><mml:mrow><mml:mo>-</mml:mo><mml:mn mathvariant="normal">2.8</mml:mn></mml:mrow></mml:math></inline-formula></oasis:entry>
       </oasis:row>
       <oasis:row rowsep="1">
         <oasis:entry colname="col1">v1.2</oasis:entry>
         <oasis:entry colname="col2">29.5</oasis:entry>
         <oasis:entry colname="col3">2 843 000</oasis:entry>
         <oasis:entry colname="col4">19</oasis:entry>
         <oasis:entry colname="col5">89</oasis:entry>
         <oasis:entry colname="col6"><inline-formula><mml:math id="M65" display="inline"><mml:mrow><mml:mo>-</mml:mo><mml:mn mathvariant="normal">3.2</mml:mn></mml:mrow></mml:math></inline-formula></oasis:entry>
       </oasis:row>
       <oasis:row>
         <oasis:entry colname="col1">v1.0</oasis:entry>
         <oasis:entry colname="col2">17.5</oasis:entry>
         <oasis:entry colname="col3">2 672 000</oasis:entry>
         <oasis:entry colname="col4">26</oasis:entry>
         <oasis:entry colname="col5">92</oasis:entry>
         <oasis:entry colname="col6"><inline-formula><mml:math id="M66" display="inline"><mml:mrow><mml:mo>-</mml:mo><mml:mn mathvariant="normal">1.1</mml:mn></mml:mrow></mml:math></inline-formula></oasis:entry>
       </oasis:row>
       <oasis:row>
         <oasis:entry colname="col1">v1.1</oasis:entry>
         <oasis:entry colname="col2">17.5</oasis:entry>
         <oasis:entry colname="col3">2 672 000</oasis:entry>
         <oasis:entry colname="col4">26</oasis:entry>
         <oasis:entry colname="col5">88</oasis:entry>
         <oasis:entry colname="col6"><inline-formula><mml:math id="M67" display="inline"><mml:mrow><mml:mo>-</mml:mo><mml:mn mathvariant="normal">1.9</mml:mn></mml:mrow></mml:math></inline-formula></oasis:entry>
       </oasis:row>
       <oasis:row rowsep="1">
         <oasis:entry colname="col1">v1.2</oasis:entry>
         <oasis:entry colname="col2">17.5</oasis:entry>
         <oasis:entry colname="col3">2 672 000</oasis:entry>
         <oasis:entry colname="col4">26</oasis:entry>
         <oasis:entry colname="col5">92</oasis:entry>
         <oasis:entry colname="col6"><inline-formula><mml:math id="M68" display="inline"><mml:mrow><mml:mo>-</mml:mo><mml:mn mathvariant="normal">2.4</mml:mn></mml:mrow></mml:math></inline-formula></oasis:entry>
       </oasis:row>
       <oasis:row>
         <oasis:entry colname="col1">v1.0</oasis:entry>
         <oasis:entry colname="col2">58.9</oasis:entry>
         <oasis:entry colname="col3">1 578 000</oasis:entry>
         <oasis:entry colname="col4">14</oasis:entry>
         <oasis:entry colname="col5">79</oasis:entry>
         <oasis:entry colname="col6"><inline-formula><mml:math id="M69" display="inline"><mml:mrow><mml:mo>-</mml:mo><mml:mn mathvariant="normal">1.4</mml:mn></mml:mrow></mml:math></inline-formula></oasis:entry>
       </oasis:row>
       <oasis:row>
         <oasis:entry colname="col1">v1.1</oasis:entry>
         <oasis:entry colname="col2">58.9</oasis:entry>
         <oasis:entry colname="col3">1 578 000</oasis:entry>
         <oasis:entry colname="col4">14</oasis:entry>
         <oasis:entry colname="col5">79</oasis:entry>
         <oasis:entry colname="col6"><inline-formula><mml:math id="M70" display="inline"><mml:mrow><mml:mo>-</mml:mo><mml:mn mathvariant="normal">3.0</mml:mn></mml:mrow></mml:math></inline-formula></oasis:entry>
       </oasis:row>
       <oasis:row>
         <oasis:entry colname="col1">v1.2</oasis:entry>
         <oasis:entry colname="col2">58.9</oasis:entry>
         <oasis:entry colname="col3">1 578 000</oasis:entry>
         <oasis:entry colname="col4">14</oasis:entry>
         <oasis:entry colname="col5">79</oasis:entry>
         <oasis:entry colname="col6"><inline-formula><mml:math id="M71" display="inline"><mml:mrow><mml:mo>-</mml:mo><mml:mn mathvariant="normal">3.0</mml:mn></mml:mrow></mml:math></inline-formula></oasis:entry>
       </oasis:row>
     </oasis:tbody>
   </oasis:tgroup><?xmltex \end{scaleboxenv}?></oasis:table></table-wrap>

      <p id="d1e2846">For Pemigewasset River, Table 6 summarizes the results for the three most important timescales, and Fig. 10 provides a graphical representation of the timing errors (hits only). At this location, the median timing error improved with NWM V1.2, moving closer to zero. While the distribution of the timing errors became less biased than the previous versions, it also became wider (Fig. 10). Over the time series, there were between 59 and 76 event clusters. Interestingly, the hit rate for all timescales was best for NWM V1.1, though its timing errors are broadly the worst. From NWM V1.0 to NWM V1.2, improvements to both hit rate and median timing errors were obtained at all timescales.</p>

      <?xmltex \floatpos{t}?><fig id="Ch1.F10"><?xmltex \currentcnt{10}?><?xmltex \def\figurename{Figure}?><label>Figure 10</label><caption><p id="d1e2851">A 5-year time series from Pemigewasset River, NH, which compares cluster maxima timing error distributions for the top three characteristic timescales (see panel title) across NWM versions.</p></caption>
          <?xmltex \igopts{width=236.157874pt}?><graphic xlink:href="https://hess.copernicus.org/articles/25/2599/2021/hess-25-2599-2021-f10.png"/>

        </fig>

<?xmltex \floatpos{t}?><table-wrap id="Ch1.T6"><?xmltex \currentcnt{6}?><label>Table 6</label><caption><p id="d1e2863">Summary of timing errors from cluster maxima that were hits for 5-year time series from Pemigewasset River, NH.</p></caption><oasis:table frame="topbot"><?xmltex \begin{scaleboxenv}{.80}[.80]?><oasis:tgroup cols="6">
     <oasis:colspec colnum="1" colname="col1" align="left"/>
     <oasis:colspec colnum="2" colname="col2" align="center"/>
     <oasis:colspec colnum="3" colname="col3" align="center"/>
     <oasis:colspec colnum="4" colname="col4" align="center"/>
     <oasis:colspec colnum="5" colname="col5" align="center"/>
     <oasis:colspec colnum="6" colname="col6" align="right"/>
     <oasis:thead>
       <oasis:row>
         <oasis:entry colname="col1">NWM</oasis:entry>
         <oasis:entry colname="col2">Characteristic</oasis:entry>
         <oasis:entry colname="col3">Avg WT</oasis:entry>
         <oasis:entry colname="col4">Number of</oasis:entry>
         <oasis:entry colname="col5">Percent</oasis:entry>
         <oasis:entry colname="col6">Median</oasis:entry>
       </oasis:row>
       <oasis:row>
         <oasis:entry colname="col1">version</oasis:entry>
         <oasis:entry colname="col2">timescale (h)</oasis:entry>
         <oasis:entry colname="col3">power</oasis:entry>
         <oasis:entry colname="col4">clusters</oasis:entry>
         <oasis:entry colname="col5">of hits</oasis:entry>
         <oasis:entry colname="col6">timing</oasis:entry>
       </oasis:row>
       <oasis:row rowsep="1">
         <oasis:entry colname="col1"/>
         <oasis:entry colname="col2"/>
         <oasis:entry colname="col3"/>
         <oasis:entry colname="col4"/>
         <oasis:entry colname="col5"/>
         <oasis:entry colname="col6">error (h)</oasis:entry>
       </oasis:row>
     </oasis:thead>
     <oasis:tbody>
       <oasis:row>
         <oasis:entry colname="col1">v1.0</oasis:entry>
         <oasis:entry colname="col2">17.5</oasis:entry>
         <oasis:entry colname="col3">172 900</oasis:entry>
         <oasis:entry colname="col4">67</oasis:entry>
         <oasis:entry colname="col5">84</oasis:entry>
         <oasis:entry colname="col6"><inline-formula><mml:math id="M72" display="inline"><mml:mrow><mml:mo>-</mml:mo><mml:mn mathvariant="normal">2.7</mml:mn></mml:mrow></mml:math></inline-formula></oasis:entry>
       </oasis:row>
       <oasis:row>
         <oasis:entry colname="col1">v1.1</oasis:entry>
         <oasis:entry colname="col2">17.5</oasis:entry>
         <oasis:entry colname="col3">172 900</oasis:entry>
         <oasis:entry colname="col4">67</oasis:entry>
         <oasis:entry colname="col5">91</oasis:entry>
         <oasis:entry colname="col6"><inline-formula><mml:math id="M73" display="inline"><mml:mrow><mml:mo>-</mml:mo><mml:mn mathvariant="normal">2.8</mml:mn></mml:mrow></mml:math></inline-formula></oasis:entry>
       </oasis:row>
       <oasis:row rowsep="1">
         <oasis:entry colname="col1">v1.2</oasis:entry>
         <oasis:entry colname="col2">17.5</oasis:entry>
         <oasis:entry colname="col3">172 900</oasis:entry>
         <oasis:entry colname="col4">67</oasis:entry>
         <oasis:entry colname="col5">85</oasis:entry>
         <oasis:entry colname="col6"><inline-formula><mml:math id="M74" display="inline"><mml:mrow><mml:mo>-</mml:mo><mml:mn mathvariant="normal">0.2</mml:mn></mml:mrow></mml:math></inline-formula></oasis:entry>
       </oasis:row>
       <oasis:row>
         <oasis:entry colname="col1">v1.0</oasis:entry>
         <oasis:entry colname="col2">27.8</oasis:entry>
         <oasis:entry colname="col3">169 600</oasis:entry>
         <oasis:entry colname="col4">61</oasis:entry>
         <oasis:entry colname="col5">82</oasis:entry>
         <oasis:entry colname="col6"><inline-formula><mml:math id="M75" display="inline"><mml:mrow><mml:mo>-</mml:mo><mml:mn mathvariant="normal">3.9</mml:mn></mml:mrow></mml:math></inline-formula></oasis:entry>
       </oasis:row>
       <oasis:row>
         <oasis:entry colname="col1">v1.1</oasis:entry>
         <oasis:entry colname="col2">27.8</oasis:entry>
         <oasis:entry colname="col3">169 600</oasis:entry>
         <oasis:entry colname="col4">61</oasis:entry>
         <oasis:entry colname="col5">97</oasis:entry>
         <oasis:entry colname="col6"><inline-formula><mml:math id="M76" display="inline"><mml:mrow><mml:mo>-</mml:mo><mml:mn mathvariant="normal">4.2</mml:mn></mml:mrow></mml:math></inline-formula></oasis:entry>
       </oasis:row>
       <oasis:row rowsep="1">
         <oasis:entry colname="col1">v1.2</oasis:entry>
         <oasis:entry colname="col2">27.8</oasis:entry>
         <oasis:entry colname="col3">169 600</oasis:entry>
         <oasis:entry colname="col4">61</oasis:entry>
         <oasis:entry colname="col5">90</oasis:entry>
         <oasis:entry colname="col6">1.1</oasis:entry>
       </oasis:row>
       <oasis:row>
         <oasis:entry colname="col1">v1.0</oasis:entry>
         <oasis:entry colname="col2">31.2</oasis:entry>
         <oasis:entry colname="col3">169 500</oasis:entry>
         <oasis:entry colname="col4">59</oasis:entry>
         <oasis:entry colname="col5">86</oasis:entry>
         <oasis:entry colname="col6"><inline-formula><mml:math id="M77" display="inline"><mml:mrow><mml:mo>-</mml:mo><mml:mn mathvariant="normal">4.2</mml:mn></mml:mrow></mml:math></inline-formula></oasis:entry>
       </oasis:row>
       <oasis:row>
         <oasis:entry colname="col1">v1.1</oasis:entry>
         <oasis:entry colname="col2">31.2</oasis:entry>
         <oasis:entry colname="col3">169 500</oasis:entry>
         <oasis:entry colname="col4">59</oasis:entry>
         <oasis:entry colname="col5">95</oasis:entry>
         <oasis:entry colname="col6"><inline-formula><mml:math id="M78" display="inline"><mml:mrow><mml:mo>-</mml:mo><mml:mn mathvariant="normal">4.6</mml:mn></mml:mrow></mml:math></inline-formula></oasis:entry>
       </oasis:row>
       <oasis:row>
         <oasis:entry colname="col1">v1.2</oasis:entry>
         <oasis:entry colname="col2">31.2</oasis:entry>
         <oasis:entry colname="col3">169 500</oasis:entry>
         <oasis:entry colname="col4">59</oasis:entry>
         <oasis:entry colname="col5">93</oasis:entry>
         <oasis:entry colname="col6">1.6</oasis:entry>
       </oasis:row>
     </oasis:tbody>
   </oasis:tgroup><?xmltex \end{scaleboxenv}?></oasis:table></table-wrap>

      <p id="d1e3206">For Taylor River, Table 7 summarizes the results for the two most important
timescales. For the characteristic timescale of 235 h (<inline-formula><mml:math id="M79" display="inline"><mml:mrow><mml:mo>∼</mml:mo><mml:mn mathvariant="normal">10</mml:mn></mml:mrow></mml:math></inline-formula> d), there are only four event clusters, and each model version has only one hit. The timing of this hit improves by roughly half its error from NWM V1.0 to NWM V1.2 in going from 16 to 9 h. The 23.4 h timescale has 41 event clusters, with a hit rate varying considerably by version. The median timing error is fairly consistent with version, however, ranging from 6 to 7 h early.</p>

<?xmltex \floatpos{t}?><table-wrap id="Ch1.T7"><?xmltex \currentcnt{7}?><label>Table 7</label><caption><p id="d1e3223">Summary of timing errors from cluster maxima that were hits for 5-year time series of Taylor River, CO.</p></caption><oasis:table frame="topbot"><?xmltex \begin{scaleboxenv}{.80}[.80]?><oasis:tgroup cols="6">
     <oasis:colspec colnum="1" colname="col1" align="left"/>
     <oasis:colspec colnum="2" colname="col2" align="right"/>
     <oasis:colspec colnum="3" colname="col3" align="center"/>
     <oasis:colspec colnum="4" colname="col4" align="right"/>
     <oasis:colspec colnum="5" colname="col5" align="center"/>
     <oasis:colspec colnum="6" colname="col6" align="right"/>
     <oasis:thead>
       <oasis:row>
         <oasis:entry colname="col1">NWM</oasis:entry>
         <oasis:entry colname="col2">Characteristic</oasis:entry>
         <oasis:entry colname="col3">Avg WT</oasis:entry>
         <oasis:entry colname="col4">Number of</oasis:entry>
         <oasis:entry colname="col5">Percent</oasis:entry>
         <oasis:entry colname="col6">Median</oasis:entry>
       </oasis:row>
       <oasis:row>
         <oasis:entry colname="col1">version</oasis:entry>
         <oasis:entry colname="col2">timescale (h)</oasis:entry>
         <oasis:entry colname="col3">power</oasis:entry>
         <oasis:entry colname="col4">clusters</oasis:entry>
         <oasis:entry colname="col5">of hits</oasis:entry>
         <oasis:entry colname="col6">timing</oasis:entry>
       </oasis:row>
       <oasis:row rowsep="1">
         <oasis:entry colname="col1"/>
         <oasis:entry colname="col2"/>
         <oasis:entry colname="col3"/>
         <oasis:entry colname="col4"/>
         <oasis:entry colname="col5"/>
         <oasis:entry colname="col6">error (h)</oasis:entry>
       </oasis:row>
     </oasis:thead>
     <oasis:tbody>
       <oasis:row>
         <oasis:entry colname="col1">v1.0</oasis:entry>
         <oasis:entry colname="col2">236</oasis:entry>
         <oasis:entry colname="col3">263</oasis:entry>
         <oasis:entry colname="col4">4</oasis:entry>
         <oasis:entry colname="col5">25</oasis:entry>
         <oasis:entry colname="col6"><inline-formula><mml:math id="M80" display="inline"><mml:mrow><mml:mo>-</mml:mo><mml:mn mathvariant="normal">16</mml:mn></mml:mrow></mml:math></inline-formula></oasis:entry>
       </oasis:row>
       <oasis:row>
         <oasis:entry colname="col1">v1.1</oasis:entry>
         <oasis:entry colname="col2">236</oasis:entry>
         <oasis:entry colname="col3">263</oasis:entry>
         <oasis:entry colname="col4">4</oasis:entry>
         <oasis:entry colname="col5">25</oasis:entry>
         <oasis:entry colname="col6"><inline-formula><mml:math id="M81" display="inline"><mml:mrow><mml:mo>-</mml:mo><mml:mn mathvariant="normal">10</mml:mn></mml:mrow></mml:math></inline-formula></oasis:entry>
       </oasis:row>
       <oasis:row rowsep="1">
         <oasis:entry colname="col1">v1.2</oasis:entry>
         <oasis:entry colname="col2">236</oasis:entry>
         <oasis:entry colname="col3">263</oasis:entry>
         <oasis:entry colname="col4">4</oasis:entry>
         <oasis:entry colname="col5">25</oasis:entry>
         <oasis:entry colname="col6"><inline-formula><mml:math id="M82" display="inline"><mml:mrow><mml:mo>-</mml:mo><mml:mn mathvariant="normal">9.0</mml:mn></mml:mrow></mml:math></inline-formula></oasis:entry>
       </oasis:row>
       <oasis:row>
         <oasis:entry colname="col1">v1.0</oasis:entry>
         <oasis:entry colname="col2">23.4</oasis:entry>
         <oasis:entry colname="col3">250</oasis:entry>
         <oasis:entry colname="col4">41</oasis:entry>
         <oasis:entry colname="col5">68</oasis:entry>
         <oasis:entry colname="col6"><inline-formula><mml:math id="M83" display="inline"><mml:mrow><mml:mo>-</mml:mo><mml:mn mathvariant="normal">6.1</mml:mn></mml:mrow></mml:math></inline-formula></oasis:entry>
       </oasis:row>
       <oasis:row>
         <oasis:entry colname="col1">v1.1</oasis:entry>
         <oasis:entry colname="col2">23.4</oasis:entry>
         <oasis:entry colname="col3">250</oasis:entry>
         <oasis:entry colname="col4">41</oasis:entry>
         <oasis:entry colname="col5">44</oasis:entry>
         <oasis:entry colname="col6"><inline-formula><mml:math id="M84" display="inline"><mml:mrow><mml:mo>-</mml:mo><mml:mn mathvariant="normal">6.9</mml:mn></mml:mrow></mml:math></inline-formula></oasis:entry>
       </oasis:row>
       <oasis:row>
         <oasis:entry colname="col1">v1.2</oasis:entry>
         <oasis:entry colname="col2">23.4</oasis:entry>
         <oasis:entry colname="col3">250</oasis:entry>
         <oasis:entry colname="col4">41</oasis:entry>
         <oasis:entry colname="col5">56</oasis:entry>
         <oasis:entry colname="col6"><inline-formula><mml:math id="M85" display="inline"><mml:mrow><mml:mo>-</mml:mo><mml:mn mathvariant="normal">6.5</mml:mn></mml:mrow></mml:math></inline-formula></oasis:entry>
       </oasis:row>
     </oasis:tbody>
   </oasis:tgroup><?xmltex \end{scaleboxenv}?></oasis:table></table-wrap>

</sec>
</sec>
<?pagebreak page2612?><sec id="Ch1.S5" sec-type="conclusions">
  <label>5</label><title>Discussion and conclusions</title>
      <p id="d1e3502">In this paper, we develop a systematic, data-driven methodology to objectively identify time series (hydrograph) events and estimate timing
errors in large-sample, high-resolution hydrologic models. The method was
developed towards several intended uses. First, it was primarily developed for
model evaluation, so that model performance can be documented in terms of
defined standards. We illustrate this with the version-over-version NWM
comparisons. Second, it can be used for model development, whereby potential
timing error sources can be diagnosed (by timescale) and targeted for
improvement. Related to this point, and given the advantages of calibrating
using multiple criteria (e.g., Gupta et al., 1998), timing errors could be
used as part of a larger calibration strategy. However, minimizing timing
errors at one timescale may not translate to improvements in timing errors
(or other metrics) at other timescales. Wavelet analysis has also been used
directly as an objective function for<?pagebreak page2613?> calibration, although a difficulty arises in determining which similarity measure to use (e.g., Schaefli and Zehe, 2009;
Rathinasamy et al., 2014). Future research will investigate the application
of the timing errors presented here for calibration purposes. Finally, the
approach can be used for model interpretation and forecast guidance, as estimating timing errors provides characterization of the timing uncertainty
(i.e., for a given timescale, the model is generally late or early) or
confidence.</p>
      <p id="d1e3505">Given the fact that several subjective choices were made specific to our
application and goals, it is important to highlight that we have made the
analysis framework openly available (detailed in the code availability
section below), so the method can be adapted, extended, or refined by the
community right away. We look at timing errors from an observed event set
relevant to our analysis, but there are other ways to subset the events that
might be more suitable to other applications. For example, we focus on the
event cluster maxima, but one could also examine the event cluster means or
the local maxima along time. Another alternative to finding the event
cluster maxima (i.e., for a given timescale) would be to identify the event
with maximum power in islands of significance across timescales, i.e.,
contiguous regions of contiguous significance across both time and timescale. This approach would ignore that multiple frequencies can be important at once. Moreover, defining such islands is not straightforward. A different approach could be desirable if one suspected nonstationarity in the characteristic timescales over the time series. Then perhaps a moving average in timescale could be employed to identify characteristic timescales. In our approach, we define the event set broadly. However, it could be subset using streamflow thresholds (e.g., for flooding events) to compare events in the wavelet domain with traditional peak-over-threshold events. For example, Fig. 11 shows the maximum streamflows for the event set from the 5 year time series at Taylor River. This figure shows that all events identified by the algorithm are not necessarily high-flow events (i.e., the maximum streamflow peaks are lower for the 23.4 h timescale compared to the 235.6 h timescale). To compare with traditional peak-over-threshold approaches, this event set could be filtered to include only events above a given threshold (i.e., events in both the wavelet and time domains).</p>

      <?xmltex \floatpos{t}?><fig id="Ch1.F11"><?xmltex \currentcnt{11}?><?xmltex \def\figurename{Figure}?><label>Figure 11</label><caption><p id="d1e3510">A 5-year time series from Taylor River, CO, showing the top two characteristic timescales and maximum streamflow peak distributions for each
event (using cluster maxima) in cubic meters per second (m<inline-formula><mml:math id="M86" display="inline"><mml:msup><mml:mi/><mml:mn mathvariant="normal">3</mml:mn></mml:msup></mml:math></inline-formula> s<inline-formula><mml:math id="M87" display="inline"><mml:msup><mml:mi/><mml:mrow><mml:mo>-</mml:mo><mml:mn mathvariant="normal">1</mml:mn></mml:mrow></mml:msup></mml:math></inline-formula>).</p></caption>
        <?xmltex \igopts{width=236.157874pt}?><graphic xlink:href="https://hess.copernicus.org/articles/25/2599/2021/hess-25-2599-2021-f11.png"/>

      </fig>

      <p id="d1e3541">Another point that arises is how many characteristic timescales should be
examined and the similarity of adjacent characteristic timescales. In our
method, we average the power in timescales and identify characteristic scales at every absolute and relative maxima. As seen in the illustrative examples, this can result in multiple characteristic scales, some of which can be quite similar, suggesting that events at those scales are from similar or related processes. A solution could be to smooth the average power by timescale, which would reduce the number of local maxima, or to look at timing errors within a band of timescales. It is also important to note that the characteristic scales are data driven, so they will change with different lengths of observed time series. Longer runs capture more events and should converge on the more dominant timescales and events for a location. However, for performance evaluation, overlapping time periods for observed and modeled time series are needed.</p>
      <p id="d1e3544">In our application of the WT, we follow Liu et al. (2011) and select the
Morlet as the mother wavelet. However, results are sensitive to the mother
wavelet selected. Further discussion of mother wavelet choices can be found
in Torrence and Compo (1998) and in ElSaadani and Krajewski (2017).</p>
      <p id="d1e3547">In summary, this paper provides a systematic, flexible, and computationally
efficient methodology for calculating model timing errors that is appropriate for model evaluation and comparison and is useful for model development and<?pagebreak page2614?> guidance. Based on the wavelet transform, the method introduces timescale as a property of timing errors. The approach also identifies streamflow events in the observed and modeled time series and only evaluates timing errors for modeled events which are hits in a two-way contingency analysis. Future work will apply the approach to identify characteristic timescales across the United States and to assess the associated timing errors in the NWM.</p>
</sec>

      
      </body>
    <back><notes notes-type="codedataavailability"><title>Code and data availability</title>

      <p id="d1e3554">The code for reproducing the figures and tables in this paper is provided in the GitHub repository at <ext-link xlink:href="https://doi.org/10.5281/zenodo.4746587" ext-link-type="DOI">10.5281/zenodo.4746587</ext-link> (McCreight 2021), with instructions for installing dependencies. The core code used in the above repository is provided in the “rwrfhydro” R package (<ext-link xlink:href="https://doi.org/10.5281/zenodo.4746607" ext-link-type="DOI">10.5281/zenodo.4746607</ext-link>; McCreight et al., 2021). The code is written in the open-source R language (R Core Team, 2019) and builds on multiple, existing R packages. Most notably, the wavelet and cross-wavelet analyses are performed using the “biwavelet” package (Gouhier et al., 2018).</p>

      <p id="d1e3563">We emphasize that the analysis framework is meant to be flexible and adapted
to similar applications where different statistics may be desired. The
figures created are specific to the applications in this paper but provide a
starting point for other work.</p>
  </notes><notes notes-type="authorcontribution"><title>Author contributions</title>

      <p id="d1e3569">ET and JLM collaborated to develop the methodology. ET led the results analysis, prepared the paper, and did the revisions. JLM led the initial idea for the work and developed the open-source software and visualizations.</p>
  </notes><notes notes-type="competinginterests"><title>Competing interests</title>

      <p id="d1e3575">The authors declare that they have no conflict of interest.</p>
  </notes><ack><title>Acknowledgements</title><p id="d1e3581">The authors would like to thank Dave Gochis, for the useful discussions, and
Aubrey Dugger, for providing the NWM data. We thank the NOAA/OWP and NCAR NWM
team for their support of this research.</p></ack><notes notes-type="financialsupport"><title>Financial support</title>

      <p id="d1e3586">This research has been supported by the Joint Technology Transfer Initiative grant (grant no. 2018-0303-1556911) and the National Oceanic and Atmospheric Administration R &amp; D (contract no. 1305M219FNWWY0382). This material is based upon work supported by the National Center for Atmospheric Research (NCAR), which is a major facility sponsored by the National Science Foundation (NSF; grant no. 1852977).</p>
  </notes><notes notes-type="reviewstatement"><title>Review statement</title>

      <p id="d1e3592">This paper was edited by Matthew Hipsey and reviewed by Cedric David and Uwe Ehret.</p>
  </notes><ref-list>
    <title>References</title>

      <ref id="bib1.bib1"><label>1</label><?label 1?><mixed-citation>Bogner, K. and Kalas, M.: Error-correction methods and evaluation of an ensemble based hydrological forecasting system for the Upper Danube catchment, Atmos. Sci. Lett., 9, 95–102, <ext-link xlink:href="https://doi.org/10.1002/asl.180" ext-link-type="DOI">10.1002/asl.180</ext-link>, 2008.</mixed-citation></ref>
      <ref id="bib1.bib2"><label>2</label><?label 1?><mixed-citation>Bogner, K. and Pappenberger, F.: Multiscale error analysis, correction, and predictive uncertainty estimation in a flood forecasting system, Water Resour. Res., 47, W07524, <ext-link xlink:href="https://doi.org/10.1029/2010WR009137" ext-link-type="DOI">10.1029/2010WR009137</ext-link>, 2011.</mixed-citation></ref>
      <ref id="bib1.bib3"><label>3</label><?label 1?><mixed-citation>
Coles, S.: An Introduction to Statistical Modeling of Extreme Values, in:
Springer Ser. Stat., Springer, London, 2001.</mixed-citation></ref>
      <ref id="bib1.bib4"><label>4</label><?label 1?><mixed-citation>
Daubechies, I.: The wavelet transform time-frequency localization and signal analysis, IEEE Trans. Inform. Theory, 36, 961–1004, 1990.</mixed-citation></ref>
      <ref id="bib1.bib5"><label>5</label><?label 1?><mixed-citation>Ehret, U. and Zehe, E.: Series distance-an intuitive metric to quantify
hydrograph similarity in terms of occurrence, amplitude and timing of hydrological events, Hydrol. Earth Syst. Sci., 15, 877–896,
<ext-link xlink:href="https://doi.org/10.5194/hess-15-877-2011" ext-link-type="DOI">10.5194/hess-15-877-2011</ext-link>, 2011.</mixed-citation></ref>
      <ref id="bib1.bib6"><label>6</label><?label 1?><mixed-citation>ElSaadani, M. and Krajewski, W. F.: A time-based framework for evaluating
hydrologic routing methodologies using wavelet transform, J. Water Resour. Protect., 9, 723–744, <ext-link xlink:href="https://doi.org/10.4236/jwarp.2017.97048" ext-link-type="DOI">10.4236/jwarp.2017.97048</ext-link>, 2017.</mixed-citation></ref>
      <ref id="bib1.bib7"><label>7</label><?label 1?><mixed-citation>Gochis, D., Barlage, M., Cabell, R., Dugger, A., Fanfarillo, A., FitzGerald, K., McAllister, M., McCreight, J., RafieeiNasab, A., Read, L., Frazier, N., Johnson, D., Mattern, J. D., Karsten, L., Mills, T. J., and Fersch, B.: WRF-Hydro<sup>®</sup> v5.1.1, Zenodo [data set], <ext-link xlink:href="https://doi.org/10.5281/zenodo.3625238" ext-link-type="DOI">10.5281/zenodo.3625238</ext-link>, 2020.</mixed-citation></ref>
      <ref id="bib1.bib8"><label>8</label><?label 1?><mixed-citation>Gouhier, T. C., Grinsted, A., and Simko, V.: R package biwavelet: Conduct
Univariate and Bivariate Wavelet Analyses (Version 0.20.17), Git Hub, available at: <uri>https://github.com/tgouhier/biwavelet</uri> (last access: 12 April 2021), 2018.</mixed-citation></ref>
      <ref id="bib1.bib9"><label>9</label><?label 1?><mixed-citation>
Gupta, H. V., Sorooshian, S., and Yapo, P. O.: Towards improved calibration of hydrologic models: multiple and non-commensurable measures of information,
Water Resour. Res., 34, 751–763, 1998.</mixed-citation></ref>
      <ref id="bib1.bib10"><label>10</label><?label 1?><mixed-citation>Gupta, H. V., Wagener, T., and Liu, Y.: Reconciling theory with observations:
elements of a diagnostic approach to model evaluation, Hydrol. Process., 22, 3802–3813, <ext-link xlink:href="https://doi.org/10.1002/hyp.6989" ext-link-type="DOI">10.1002/hyp.6989</ext-link>, 2008.</mixed-citation></ref>
      <ref id="bib1.bib11"><label>11</label><?label 1?><mixed-citation>Gupta, H. V., Perrin, C., Blöschl, G., Montanari, A., Kumar, R., Clark, M., and Andréassian, V.: Large-sample hydrology: a need to balance depth
with breadth, Hydrol. Earth Syst. Sci., 18, 463–477, <ext-link xlink:href="https://doi.org/10.5194/hess-18-463-2014" ext-link-type="DOI">10.5194/hess-18-463-2014</ext-link>, 2014.</mixed-citation></ref>
      <ref id="bib1.bib12"><label>12</label><?label 1?><mixed-citation>Koskelo, A. I., Fisher, T. R., Utz, R. M., and Jordan, T. E.: A new
precipitation-based method of baseflow separation and event identification for small watersheds (<inline-formula><mml:math id="M88" display="inline"><mml:mrow><mml:mo>&lt;</mml:mo><mml:mn mathvariant="normal">50</mml:mn></mml:mrow></mml:math></inline-formula> km<inline-formula><mml:math id="M89" display="inline"><mml:msup><mml:mi/><mml:mn mathvariant="normal">2</mml:mn></mml:msup></mml:math></inline-formula>), J. Hydrol., 450–451, 267–278,
<ext-link xlink:href="https://doi.org/10.1016/j.jhydrol.2012.04.055" ext-link-type="DOI">10.1016/j.jhydrol.2012.04.055</ext-link>, 2012.</mixed-citation></ref>
      <ref id="bib1.bib13"><label>13</label><?label 1?><mixed-citation>Lane, S. N.: Assessment of rainfall–runoff models based upon wavelet analysis, Hydrol. Process., 21, 586–607, <ext-link xlink:href="https://doi.org/10.1002/hyp.6249" ext-link-type="DOI">10.1002/hyp.6249</ext-link>, 2007.</mixed-citation></ref>
      <ref id="bib1.bib14"><label>14</label><?label 1?><mixed-citation>
Liu, Y., Liang, X. S., and Weisberg, R. H.: Rectification of the bias in the
wavelet power spectrum, J. Atmos. Ocean. Tech., 24, 2093–2102, 2007.</mixed-citation></ref>
      <ref id="bib1.bib15"><label>15</label><?label 1?><mixed-citation>Liu, Y., Brown, J., Demargne, J., and Seo, D. J.: A wavelet-based approach
to assessing timing errors in hydrologic predictions, J. Hydrol., 397, 210–224, <ext-link xlink:href="https://doi.org/10.1016/j.jhydrol.2010.11.040" ext-link-type="DOI">10.1016/j.jhydrol.2010.11.040</ext-link>, 2011.</mixed-citation></ref>
      <?pagebreak page2615?><ref id="bib1.bib16"><label>16</label><?label 1?><mixed-citation>Luo, Y. Q., Randerson, J. T., Abramowitz, G., Bacour, C., Blyth, E., Carvalhais, N., Ciais, P., Dalmonech, D., Fisher, J. B., Fisher, R., Friedlingstein, P., Hibbard, K., Hoffman, F., Huntzinger, D., Jones, C. D., Koven, C., Lawrence, D., Li, D. J., Mahecha, M., Niu, S. L., Norby, R., Piao, S. L., Qi, X., Peylin, P., Prentice, I. C., Riley, W., Reichstein, M., Schwalm, C., Wang, Y. P., Xia, J. Y., Zaehle, S., and Zhou, X. H.: A framework for benchmarking land models, Biogeosciences, 9, 3857–3874, <ext-link xlink:href="https://doi.org/10.5194/bg-9-3857-2012" ext-link-type="DOI">10.5194/bg-9-3857-2012</ext-link>, 2012.</mixed-citation></ref>
      <ref id="bib1.bib17"><label>17</label><?label 1?><mixed-citation>McCreight, J. L.: NCAR/wavelet_timing: Publication (Version v0.0.1), Zenodo, <ext-link xlink:href="https://doi.org/10.5281/zenodo.4746587" ext-link-type="DOI">10.5281/zenodo.4746587</ext-link>, 2021.</mixed-citation></ref>
      <ref id="bib1.bib18"><label>18</label><?label 1?><mixed-citation>McCreight, J. L., Mills, T. J., Rafieeinasab, A., FitzGerald, K., Reads, L., Hoover, C., Johnson, D. W., Towler, E., Huang, Y.-F., Dugger, A., and Nowosad, J.: NCAR/rwrfhydro: wavelet timing tag (Version v1.0.1), Zenodo, <ext-link xlink:href="https://doi.org/10.5281/zenodo.4746607" ext-link-type="DOI">10.5281/zenodo.4746607</ext-link>, 2021.</mixed-citation></ref>
      <ref id="bib1.bib19"><label>19</label><?label 1?><mixed-citation>
McKay, L., Bondelid, T., Dewald, T., Johnston, J., Moore, R., and Rea, A.:
NHDPlus Version 2: user guide, National Operational Hydrologic Remote Sensing Center, Washington, DC, 2012.</mixed-citation></ref>
      <ref id="bib1.bib20"><label>20</label><?label 1?><mixed-citation>Mei, Y. and Anagnostou, E. N.: A hydrograph separation method based on
information from rainfall and runoff records, J. Hydrol., 523, 636–649,
<ext-link xlink:href="https://doi.org/10.1016/j.jhydrol.2015.01.083" ext-link-type="DOI">10.1016/j.jhydrol.2015.01.083</ext-link>, 2015.</mixed-citation></ref>
      <ref id="bib1.bib21"><label>21</label><?label 1?><mixed-citation>Merz, R., Blöschl, G., and Parajka, J.: Spatio-temporal variability of
event runoff coefficients, J. Hydrol., 331, 591–604, <ext-link xlink:href="https://doi.org/10.1016/j.jhydrol.2006.06.008" ext-link-type="DOI">10.1016/j.jhydrol.2006.06.008</ext-link>, 2006.</mixed-citation></ref>
      <ref id="bib1.bib22"><label>22</label><?label 1?><mixed-citation>Newman, A. J., Mizukami, N., Clark, M. P., Wood, A. W., Nijssen, B., and
Nearing, G.: Benchmarking of a physically based hydrologic model, J.
Hydrometeorol., 18, 2215–2225, <ext-link xlink:href="https://doi.org/10.1175/JHM-D-16-0284.1" ext-link-type="DOI">10.1175/JHM-D-16-0284.1</ext-link>, 2017.</mixed-citation></ref>
      <ref id="bib1.bib23"><label>23</label><?label 1?><mixed-citation>Niu, G.-Y., Yang, Z.-L., Mitchell, K. E., Chen, F., Ek, M. B., Barlage, M.,
Kumar, A., Manning, K., Niyogi, D., Rosero, E., Tewari, M., and Xia, Y.: The
community Noah land surface model with multiparameterization options (Noah-MP): 1. Model description and evaluation with local-scale
measurements, J. Geophys. Res., 116, D12109, <ext-link xlink:href="https://doi.org/10.1029/2010JD015139" ext-link-type="DOI">10.1029/2010JD015139</ext-link>, 2011.
</mixed-citation></ref><?xmltex \hack{\newpage}?>
      <ref id="bib1.bib24"><label>24</label><?label 1?><mixed-citation>NOAA National Weather Service: NWS Manual 10-950, Definitions and General
Terminology, Hydrological Services Program, NWSPD 10-9, available at:
<uri>http://www.nws.noaa.gov/directives/sym/pd01009050curr.pdf</uri> (last access: 8 May 2021), 2012.</mixed-citation></ref>
      <ref id="bib1.bib25"><label>25</label><?label 1?><mixed-citation>
Rathinasamy, M., Khosa, R., Adamowski, J., Ch, S., Partheepan, G., Anand,
J., and Narsimlu, B.: Wavelet-based multiscale performance analysis: An
approach to assess and improve hydrological models, Water Resour. Res., 50, 9721–9737, 2014.</mixed-citation></ref>
      <ref id="bib1.bib26"><label>26</label><?label 1?><mixed-citation>R Core Team: R: A language and environment for statistical computing, R Foundation for Statistical Computing, Vienna, Austria, available at: <uri>https://www.R-project.org/</uri> (last access: 7 April 2021), 2019.</mixed-citation></ref>
      <ref id="bib1.bib27"><label>27</label><?label 1?><mixed-citation>Schaefli, B. and Zehe, E.: Hydrological model performance and parameter
estimation in the wavelet-domain, Hydrol. Earth Syst. Sci., 13, 1921–1936,
<ext-link xlink:href="https://doi.org/10.5194/hess-13-1921-2009" ext-link-type="DOI">10.5194/hess-13-1921-2009</ext-link>, 2009.</mixed-citation></ref>
      <ref id="bib1.bib28"><label>28</label><?label 1?><mixed-citation>Seibert, S. P., Ehret, U., and Zehe, E.: Disentangling timing and amplitude
errors in streamflow simulations, Hydrol. Earth Syst. Sci., 20, 3745–3763,
<ext-link xlink:href="https://doi.org/10.5194/hess-20-3745-2016" ext-link-type="DOI">10.5194/hess-20-3745-2016</ext-link>, 2016.</mixed-citation></ref>
      <ref id="bib1.bib29"><label>29</label><?label 1?><mixed-citation>
Torrence, C. and Compo, G. P.: A practical guide to wavelet analysis, B. Am. Meteorol. Soc., 79, 61–78, 1998.</mixed-citation></ref>
      <ref id="bib1.bib30"><label>30</label><?label 1?><mixed-citation>
Veleda, D., Montagne, R., and Araujo, M.: Cross-wavelet bias corrected by
normalizing scales, J. Atmos. Ocean. Tech., 29, 1401–1408, 2012.</mixed-citation></ref>
      <ref id="bib1.bib31"><label>31</label><?label 1?><mixed-citation>Weedon, G. P., Prudhomme, C., Crooks, S., Ellis, R. J., Folwell, S. S., and
Best, M. J.: Evaluating the performance of hydrological models via
cross-spectral analysis: case study of the Thames Basin, United Kingdom, J.
Hydrometeorol., 16, 214–231, <ext-link xlink:href="https://doi.org/10.1175/JHM-D-14-0021.1" ext-link-type="DOI">10.1175/JHM-D-14-0021.1</ext-link>, 2015.</mixed-citation></ref>

  </ref-list></back>
    <!--<article-title-html>A wavelet-based approach to streamflow event identification  and modeled timing error evaluation</article-title-html>
<abstract-html><p>Streamflow timing errors (in the units of time) are rarely explicitly
evaluated but are useful for model evaluation and development. Wavelet-based approaches have been shown to reliably quantify timing errors
in streamflow simulations but have not been applied in a systematic way
that is suitable for model evaluation. This paper provides a step-by-step
methodology that objectively identifies events, and then estimates timing
errors for those events, in a way that can be applied to large-sample,
high-resolution predictions. Step 1 applies the wavelet transform to the
observations and uses statistical significance to identify observed events. Step 2 utilizes the cross-wavelet transform to calculate the timing errors for the events identified in step 1; this includes the diagnostic of model event hits, and timing errors are only assessed for hits. The
methodology is illustrated using real and simulated stream discharge data
from several locations to highlight key method features. The method groups
event timing errors by dominant timescales, which can be used to identify
the potential processes contributing to the timing errors and the associated model development needs. For instance, timing errors that are associated with the diurnal melt cycle are identified. The method is also useful for documenting and evaluating model performance in terms of defined standards. This is illustrated by showing the version-over-version performance of the National Water Model (NWM) in terms of timing errors.</p></abstract-html>
<ref-html id="bib1.bib1"><label>1</label><mixed-citation>
Bogner, K. and Kalas, M.: Error-correction methods and evaluation of an ensemble based hydrological forecasting system for the Upper Danube catchment, Atmos. Sci. Lett., 9, 95–102, <a href="https://doi.org/10.1002/asl.180" target="_blank">https://doi.org/10.1002/asl.180</a>, 2008.
</mixed-citation></ref-html>
<ref-html id="bib1.bib2"><label>2</label><mixed-citation>
Bogner, K. and Pappenberger, F.: Multiscale error analysis, correction, and predictive uncertainty estimation in a flood forecasting system, Water Resour. Res., 47, W07524, <a href="https://doi.org/10.1029/2010WR009137" target="_blank">https://doi.org/10.1029/2010WR009137</a>, 2011.
</mixed-citation></ref-html>
<ref-html id="bib1.bib3"><label>3</label><mixed-citation>
Coles, S.: An Introduction to Statistical Modeling of Extreme Values, in:
Springer Ser. Stat., Springer, London, 2001.
</mixed-citation></ref-html>
<ref-html id="bib1.bib4"><label>4</label><mixed-citation>
Daubechies, I.: The wavelet transform time-frequency localization and signal analysis, IEEE Trans. Inform. Theory, 36, 961–1004, 1990.
</mixed-citation></ref-html>
<ref-html id="bib1.bib5"><label>5</label><mixed-citation>
Ehret, U. and Zehe, E.: Series distance-an intuitive metric to quantify
hydrograph similarity in terms of occurrence, amplitude and timing of hydrological events, Hydrol. Earth Syst. Sci., 15, 877–896,
<a href="https://doi.org/10.5194/hess-15-877-2011" target="_blank">https://doi.org/10.5194/hess-15-877-2011</a>, 2011.
</mixed-citation></ref-html>
<ref-html id="bib1.bib6"><label>6</label><mixed-citation>
ElSaadani, M. and Krajewski, W. F.: A time-based framework for evaluating
hydrologic routing methodologies using wavelet transform, J. Water Resour. Protect., 9, 723–744, <a href="https://doi.org/10.4236/jwarp.2017.97048" target="_blank">https://doi.org/10.4236/jwarp.2017.97048</a>, 2017.
</mixed-citation></ref-html>
<ref-html id="bib1.bib7"><label>7</label><mixed-citation>
Gochis, D., Barlage, M., Cabell, R., Dugger, A., Fanfarillo, A., FitzGerald, K., McAllister, M., McCreight, J., RafieeiNasab, A., Read, L., Frazier, N., Johnson, D., Mattern, J. D., Karsten, L., Mills, T. J., and Fersch, B.: WRF-Hydro<span style="position:relative; bottom:0.5em; " class="text">®</span> v5.1.1, Zenodo [data set], <a href="https://doi.org/10.5281/zenodo.3625238" target="_blank">https://doi.org/10.5281/zenodo.3625238</a>, 2020.
</mixed-citation></ref-html>
<ref-html id="bib1.bib8"><label>8</label><mixed-citation>
Gouhier, T. C., Grinsted, A., and Simko, V.: R package biwavelet: Conduct
Univariate and Bivariate Wavelet Analyses (Version 0.20.17), Git Hub, available at: <a href="https://github.com/tgouhier/biwavelet" target="_blank"/> (last access: 12 April 2021), 2018.
</mixed-citation></ref-html>
<ref-html id="bib1.bib9"><label>9</label><mixed-citation>
Gupta, H. V., Sorooshian, S., and Yapo, P. O.: Towards improved calibration of hydrologic models: multiple and non-commensurable measures of information,
Water Resour. Res., 34, 751–763, 1998.
</mixed-citation></ref-html>
<ref-html id="bib1.bib10"><label>10</label><mixed-citation>
Gupta, H. V., Wagener, T., and Liu, Y.: Reconciling theory with observations:
elements of a diagnostic approach to model evaluation, Hydrol. Process., 22, 3802–3813, <a href="https://doi.org/10.1002/hyp.6989" target="_blank">https://doi.org/10.1002/hyp.6989</a>, 2008.
</mixed-citation></ref-html>
<ref-html id="bib1.bib11"><label>11</label><mixed-citation>
Gupta, H. V., Perrin, C., Blöschl, G., Montanari, A., Kumar, R., Clark, M., and Andréassian, V.: Large-sample hydrology: a need to balance depth
with breadth, Hydrol. Earth Syst. Sci., 18, 463–477, <a href="https://doi.org/10.5194/hess-18-463-2014" target="_blank">https://doi.org/10.5194/hess-18-463-2014</a>, 2014.
</mixed-citation></ref-html>
<ref-html id="bib1.bib12"><label>12</label><mixed-citation>
Koskelo, A. I., Fisher, T. R., Utz, R. M., and Jordan, T. E.: A new
precipitation-based method of baseflow separation and event identification for small watersheds ( &lt; 50&thinsp;km<sup>2</sup>), J. Hydrol., 450–451, 267–278,
<a href="https://doi.org/10.1016/j.jhydrol.2012.04.055" target="_blank">https://doi.org/10.1016/j.jhydrol.2012.04.055</a>, 2012.
</mixed-citation></ref-html>
<ref-html id="bib1.bib13"><label>13</label><mixed-citation>
Lane, S. N.: Assessment of rainfall–runoff models based upon wavelet analysis, Hydrol. Process., 21, 586–607, <a href="https://doi.org/10.1002/hyp.6249" target="_blank">https://doi.org/10.1002/hyp.6249</a>, 2007.
</mixed-citation></ref-html>
<ref-html id="bib1.bib14"><label>14</label><mixed-citation>
Liu, Y., Liang, X. S., and Weisberg, R. H.: Rectification of the bias in the
wavelet power spectrum, J. Atmos. Ocean. Tech., 24, 2093–2102, 2007.
</mixed-citation></ref-html>
<ref-html id="bib1.bib15"><label>15</label><mixed-citation>
Liu, Y., Brown, J., Demargne, J., and Seo, D. J.: A wavelet-based approach
to assessing timing errors in hydrologic predictions, J. Hydrol., 397, 210–224, <a href="https://doi.org/10.1016/j.jhydrol.2010.11.040" target="_blank">https://doi.org/10.1016/j.jhydrol.2010.11.040</a>, 2011.
</mixed-citation></ref-html>
<ref-html id="bib1.bib16"><label>16</label><mixed-citation>
Luo, Y. Q., Randerson, J. T., Abramowitz, G., Bacour, C., Blyth, E., Carvalhais, N., Ciais, P., Dalmonech, D., Fisher, J. B., Fisher, R., Friedlingstein, P., Hibbard, K., Hoffman, F., Huntzinger, D., Jones, C. D., Koven, C., Lawrence, D., Li, D. J., Mahecha, M., Niu, S. L., Norby, R., Piao, S. L., Qi, X., Peylin, P., Prentice, I. C., Riley, W., Reichstein, M., Schwalm, C., Wang, Y. P., Xia, J. Y., Zaehle, S., and Zhou, X. H.: A framework for benchmarking land models, Biogeosciences, 9, 3857–3874, <a href="https://doi.org/10.5194/bg-9-3857-2012" target="_blank">https://doi.org/10.5194/bg-9-3857-2012</a>, 2012.
</mixed-citation></ref-html>
<ref-html id="bib1.bib17"><label>17</label><mixed-citation>
McCreight, J. L.: NCAR/wavelet_timing: Publication (Version v0.0.1), Zenodo, <a href="https://doi.org/10.5281/zenodo.4746587" target="_blank">https://doi.org/10.5281/zenodo.4746587</a>, 2021.
</mixed-citation></ref-html>
<ref-html id="bib1.bib18"><label>18</label><mixed-citation>
McCreight, J. L., Mills, T. J., Rafieeinasab, A., FitzGerald, K., Reads, L., Hoover, C., Johnson, D. W., Towler, E., Huang, Y.-F., Dugger, A., and Nowosad, J.: NCAR/rwrfhydro: wavelet timing tag (Version v1.0.1), Zenodo, <a href="https://doi.org/10.5281/zenodo.4746607" target="_blank">https://doi.org/10.5281/zenodo.4746607</a>, 2021.
</mixed-citation></ref-html>
<ref-html id="bib1.bib19"><label>19</label><mixed-citation>
McKay, L., Bondelid, T., Dewald, T., Johnston, J., Moore, R., and Rea, A.:
NHDPlus Version 2: user guide, National Operational Hydrologic Remote Sensing Center, Washington, DC, 2012.
</mixed-citation></ref-html>
<ref-html id="bib1.bib20"><label>20</label><mixed-citation>
Mei, Y. and Anagnostou, E. N.: A hydrograph separation method based on
information from rainfall and runoff records, J. Hydrol., 523, 636–649,
<a href="https://doi.org/10.1016/j.jhydrol.2015.01.083" target="_blank">https://doi.org/10.1016/j.jhydrol.2015.01.083</a>, 2015.
</mixed-citation></ref-html>
<ref-html id="bib1.bib21"><label>21</label><mixed-citation>
Merz, R., Blöschl, G., and Parajka, J.: Spatio-temporal variability of
event runoff coefficients, J. Hydrol., 331, 591–604, <a href="https://doi.org/10.1016/j.jhydrol.2006.06.008" target="_blank">https://doi.org/10.1016/j.jhydrol.2006.06.008</a>, 2006.
</mixed-citation></ref-html>
<ref-html id="bib1.bib22"><label>22</label><mixed-citation>
Newman, A. J., Mizukami, N., Clark, M. P., Wood, A. W., Nijssen, B., and
Nearing, G.: Benchmarking of a physically based hydrologic model, J.
Hydrometeorol., 18, 2215–2225, <a href="https://doi.org/10.1175/JHM-D-16-0284.1" target="_blank">https://doi.org/10.1175/JHM-D-16-0284.1</a>, 2017.
</mixed-citation></ref-html>
<ref-html id="bib1.bib23"><label>23</label><mixed-citation>
Niu, G.-Y., Yang, Z.-L., Mitchell, K. E., Chen, F., Ek, M. B., Barlage, M.,
Kumar, A., Manning, K., Niyogi, D., Rosero, E., Tewari, M., and Xia, Y.: The
community Noah land surface model with multiparameterization options (Noah-MP): 1. Model description and evaluation with local-scale
measurements, J. Geophys. Res., 116, D12109, <a href="https://doi.org/10.1029/2010JD015139" target="_blank">https://doi.org/10.1029/2010JD015139</a>, 2011.

</mixed-citation></ref-html>
<ref-html id="bib1.bib24"><label>24</label><mixed-citation>
NOAA National Weather Service: NWS Manual 10-950, Definitions and General
Terminology, Hydrological Services Program, NWSPD 10-9, available at:
<a href="http://www.nws.noaa.gov/directives/sym/pd01009050curr.pdf" target="_blank"/> (last access: 8 May 2021), 2012.
</mixed-citation></ref-html>
<ref-html id="bib1.bib25"><label>25</label><mixed-citation>
Rathinasamy, M., Khosa, R., Adamowski, J., Ch, S., Partheepan, G., Anand,
J., and Narsimlu, B.: Wavelet-based multiscale performance analysis: An
approach to assess and improve hydrological models, Water Resour. Res., 50, 9721–9737, 2014.
</mixed-citation></ref-html>
<ref-html id="bib1.bib26"><label>26</label><mixed-citation>
R Core Team: R: A language and environment for statistical computing, R Foundation for Statistical Computing, Vienna, Austria, available at: <a href="https://www.R-project.org/" target="_blank"/> (last access: 7 April 2021), 2019.
</mixed-citation></ref-html>
<ref-html id="bib1.bib27"><label>27</label><mixed-citation>
Schaefli, B. and Zehe, E.: Hydrological model performance and parameter
estimation in the wavelet-domain, Hydrol. Earth Syst. Sci., 13, 1921–1936,
<a href="https://doi.org/10.5194/hess-13-1921-2009" target="_blank">https://doi.org/10.5194/hess-13-1921-2009</a>, 2009.
</mixed-citation></ref-html>
<ref-html id="bib1.bib28"><label>28</label><mixed-citation>
Seibert, S. P., Ehret, U., and Zehe, E.: Disentangling timing and amplitude
errors in streamflow simulations, Hydrol. Earth Syst. Sci., 20, 3745–3763,
<a href="https://doi.org/10.5194/hess-20-3745-2016" target="_blank">https://doi.org/10.5194/hess-20-3745-2016</a>, 2016.
</mixed-citation></ref-html>
<ref-html id="bib1.bib29"><label>29</label><mixed-citation>
Torrence, C. and Compo, G. P.: A practical guide to wavelet analysis, B. Am. Meteorol. Soc., 79, 61–78, 1998.
</mixed-citation></ref-html>
<ref-html id="bib1.bib30"><label>30</label><mixed-citation>
Veleda, D., Montagne, R., and Araujo, M.: Cross-wavelet bias corrected by
normalizing scales, J. Atmos. Ocean. Tech., 29, 1401–1408, 2012.
</mixed-citation></ref-html>
<ref-html id="bib1.bib31"><label>31</label><mixed-citation>
Weedon, G. P., Prudhomme, C., Crooks, S., Ellis, R. J., Folwell, S. S., and
Best, M. J.: Evaluating the performance of hydrological models via
cross-spectral analysis: case study of the Thames Basin, United Kingdom, J.
Hydrometeorol., 16, 214–231, <a href="https://doi.org/10.1175/JHM-D-14-0021.1" target="_blank">https://doi.org/10.1175/JHM-D-14-0021.1</a>, 2015.
</mixed-citation></ref-html>--></article>
