Update with new tests

doc/NextGen_ON_CONUS.md

@@ -195,7 +195,7 @@ The abbreviation used for submodule names in the table:
 
 # Run Computation with Topmodel
 
-Running Topmodel is similar to running CFE model. The build process is the same as described above in the [Build the Executable](#build-the-executable) using the same build script. In the realization configuration file, you will just need to replace the part for CFE submodule with the one for Topmodel submodule. Note that Topmodel uses different initial configuration data and parameters that need to be generated. For this we refer the users to githup home page for [Topmodel](https://github.com/NOAA-OWP/topmodel) for more in depth discussion. In the following, we provide two examples for illustration. Note that in the examples we tested with the realization configuration files that used the so called `synthetic TWI (Topographic Wetness Index)`, i.e., the same initial configuration file for all catchments to make the computation simple. Also, for Topmodel, some of the realization configurations do not need `sloth` submodule for initialization.
+Running Topmodel is similar to running CFE model. The build process is the same as described above in the [Build the Executable](#build-the-executable) using the same build script. In the realization configuration file, you will just need to replace the part for CFE submodule with the one for Topmodel submodule. Note that Topmodel uses different initial configuration data and parameters that need to be generated. For this we refer the users to githup home page for [Topmodel](https://github.com/NOAA-OWP/topmodel) for more in depth discussion. In the following, we provide two examples for illustration. Note that in the examples we tested with the realization configuration files provided, the so called `synthetic TWI (Topographic Wetness Index)`, i.e., the same initial configuration file for all catchments is used to make the computation simple. In addition, when running Topmodel with SoilMoistureProfiles submodule, a different initial config (config_topmodel.txt) for SMP than for CFE is needed. For simplicity, we also used the same initial config on entire CONUS. Note also that, for Topmodel, some of the realization configurations do not need `sloth` submodule for initialization.
 
 For a relatively simple example involving just two submodules, you can run the following command:
 
@@ -225,7 +225,7 @@ The wall clock timing in our tests for various realization configurations runnin
 
 # Run Computation with LASAM
 
-Running Lumped Arid/Semi-arid Model (LASAM) is similar to running CFE and Topmodel model. The build process is the same as described above in the [Build the Executable](#build-the-executable) using the same build script. In the realization configuration file, you will need to replace the part for CFE or Topmodel submodule with the one for [LASAM](https://github.com/NOAA-OWP/LGAR-C) submodule. For the initial configuration and parameters, for the computation results reported here, we have used the same one for all catchments on CONUS for testing purpose. The initial configuration is a work in progress and when the more realstic initial configuration becomes available, we will repeat the calculations and update the results. It is noted that different initial condition file for LASAM, `config_layered.txt`, is used for SMP from CFE, where an equivalent of `config_conceptual.txt (SoilMoistureProfile_{{id}}.ini` is used. This is reflected in the realization configuration files.
+Running Lumped Arid/Semi-arid Model (LASAM) is similar to running CFE and Topmodel model. The build process is the same as described above in the [Build the Executable](#build-the-executable) using the same build script. In the realization configuration file, you will need to replace the part for CFE or Topmodel submodule with the one for [LASAM](https://github.com/NOAA-OWP/LGAR-C) submodule. For the initial configuration and parameters, for the computation results reported here, we have used the same one for all catchments on CONUS for testing purpose. The initial configuration is a work in progress and when the more realstic initial configuration becomes available, we will repeat the calculations and update the results. It is noted that different initial condition file for LASAM, `config_layered.txt`, is needed for SMP from CFE, where an equivalent of `config_conceptual.txt (SoilMoistureProfile_{{id}}.ini` is used. This is similar as in the case for Topmodel.
 
 To run one of the example realization configs, you can execute the following command:
 
@@ -298,7 +298,11 @@ FC=mpif90 ./compiler.sh no-e
 
 Users are referred to [t-route](https://github.com/NOAA-OWP/t-route) github repo `readme.md` for details.
 
-After successfully building `t-route`, you can run `ngen` with routing. Note that we have several realization configuration files and the `routing_config_CONUS.yaml` file for running `ngen` with routing. The realization configuration file and `routing_config_CONUS.yaml` specify where the input and output files are. For routing, we assume the existence of a `stream_output_dir` directory in the project directory for writing output files. You need to do `mkdir stream_output_dir` before running `ngen`. With that, we can run an example with the command:
+After successfully building `t-route`, you can run `ngen` with routing. Note that we have several realization configuration files and the `routing_config_CONUS.yaml` file for running `ngen` with routing. The realization configuration file and `routing_config_CONUS.yaml` specify where the input and output files are. For routing, we assume the existence of a `stream_output_dir` directory in the project directory for writing output files. You need to do `mkdir stream_output_dir` before running `ngen`.
+
+Note that t-route is a continuously evolving software package. In the process of writing this documentation, we find that we also need to create a directory named `usgs_TimeSlice` in the project directory. An alternative is to comment out or remove the part after colon in the line `usgs_timeslices_folder : ./usgs_TimeSlice/` in the `routing_config_CONUS.yaml`, although the directory will not contain any data for the test computations described here.
+
+With that, we can run an example with the command:
 
 ```
 mpirun -n 32 ./cmake_build_mpi/ngen ./hydrofabric/conus.gpkg '' ./hydrofabric/conus.gpkg '' data/baseline/conus_bmi_multi_realization_config_w_sloth_noah_pet_cfe_trt.json conus_partition_32.json