-
Notifications
You must be signed in to change notification settings - Fork 17
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
possible bug in demand function #21
Comments
PaulDudaRESPEC
added a commit
that referenced
this issue
Apr 9, 2021
PaulDudaRESPEC
pushed a commit
that referenced
this issue
Apr 30, 2021
From @PaulDudaRESPEC, added to new `docs` directory that we'll want to build out over time. Connects to #20 & #21.
PaulDudaRESPEC
pushed a commit
that referenced
this issue
Apr 30, 2021
.exp & .OUT files from @@jlkittle using WDMRX debugger: https://github.com/respec/FORTRAN/blob/master/lib3.0/BIN/WDMRX.EXE CSV file from @htaolimno using https://github.com/respec/BASINS/tree/master/atcWdmVb Connects to #21 & #22.
PaulDudaRESPEC
pushed a commit
that referenced
this issue
Apr 30, 2021
@ptomasula, try running either of these notebooks. Connects to issue #21 & PR #35
PaulDudaRESPEC
pushed a commit
that referenced
this issue
Apr 30, 2021
This commit addresses a mismatch in the 'Stop' parameter of the '/TIMESERIES/SUMMARY' table. The updated WDMreader wrote a value 1 timestep less than the end of the last group in the timeseries. See Issue #21.
I think this was fully fixed with #40. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
There is a possible bug in 'demand' function in hrchhyd.py. Try running 'demand' function without jit with following input
and it will throw the error
The problem with numba is that when we try to access a non-existent value in an array, it just gives a junk value like 1e-313 etc.
The text was updated successfully, but these errors were encountered: