Skip to content

Commit

Permalink
Apply typographical suggestions from code review
Browse files Browse the repository at this point in the history
Co-authored-by: Phil Miller - NOAA <[email protected]>
  • Loading branch information
mattw-nws and PhilMiller authored Aug 28, 2023
1 parent 7d48fdd commit 110de1d
Show file tree
Hide file tree
Showing 2 changed files with 4 additions and 4 deletions.
2 changes: 1 addition & 1 deletion include/core/HY_Features.hpp
Original file line number Diff line number Diff line change
Expand Up @@ -60,7 +60,7 @@ namespace hy_features {
/**
* @brief Construct a new HY_Features object from a Network and a set of formulations.
*
* Constructs the HY_Catchment objects for each catchment connecting them with the provided link_key attaches tha formaulation
* Constructs the HY_Catchment objects for each catchment connecting them with the provided link_key attaches the formulation
* associated with the catchment found in the Formulation_Manager. Also constucts each nexus as a HY_PointHydroNexus.
*
* @param catchments
Expand Down
6 changes: 3 additions & 3 deletions include/core/Layer.hpp
Original file line number Diff line number Diff line change
Expand Up @@ -43,13 +43,13 @@ namespace ngen
virtual ~Layer() {}

/***
* @brief Return the next timestep that will be processed by this layer in epoc time units
* @brief Return the next timestep that will be processed by this layer in epoch time units
*/
time_t next_timestep_epoch_time() { return simulation_time.next_timestep_epoch_time(); }


/***
* @brief Return the last timesteo that was processed by this layer in epoc time units
* @brief Return the last timestep that was processed by this layer in epoch time units
*/
time_t current_timestep_epoch_time() { return simulation_time.get_current_epoch_time(); }

Expand Down Expand Up @@ -113,7 +113,7 @@ namespace ngen
double response_m_h = response_m_s / 3600.0;
//update the nexus with this flow
for(auto& nexus : features.destination_nexuses(id)) {
//TODO in a DENDRIDIC network, only one destination nexus per catchment
//TODO in a DENDRITIC network, only one destination nexus per catchment
//If there is more than one, some form of catchment partitioning will be required.
//for now, only contribute to the first one in the list
nexus->add_upstream_flow(response_m_h, id, output_time_index);
Expand Down

0 comments on commit 110de1d

Please sign in to comment.