Open jduckerOWP opened 5 months ago
Thx @jduckerOWP ! @feiye-vims I reviewed the changes, which are mostly enhancement but I don't know pySCHISM enough. Can u plz review? Thx
Thx @jduckerOWP ! @feiye-vims I reviewed the changes, which are mostly enhancement but I don't know pySCHISM enough. Can u plz review? Thx
I don't think the new code interferes with any existing functions. In fact, it is the original element paring function that has minor problems.
Thanks @jduckerOWP
@feiye-vims is there an issue created on the PySCHISM page to describe the problem with the original element pairing problem? I'll be happy to take a look at it and see if our team can help fix the issues in the future. The idea here for the NextGen module was to at least mimic the process for creating the source.nc file with the original NWM vector-based routing network. However, we want to certainly fix the code if issues are introduced as well with linking the NextGen hydrofabric flow path network with the hgrid.gr3 file elements. Thanks again @josephzhang8 and @feiye-vims for both looking at this pull request quickly!
@jduckerOWP Some other users and I identified the issue, and I briefly summarized it in issue #113. Everybody in our group is tied up with other more urgent tasks, so we haven't fixed it.
The Office of Water Prediction is currently developing the Next Generation Water Resources Modeling Framework (NextGen) project using SCHISM as a coastal model. We are constructing a common hydrofabric to apply a new routing network model called T-Route, which is constrained to the NextGen hydrofabric itself. The NextGen hydrofabric encapsulates the flow path geometry information within a geopackage file. This pull request aims to accomplish the following:
I'll be happy to answer any questions or work with developers to merge this PySCHISM branch into the main branch of the repository.