Alternate #21
Open
Alternate #21
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
* now that we have an open channel of communication with the codecov team and GitHub app has been activated (scipygh-12240), try turning on pull request patch diffs again, similar to NumPy PR 16409
Co-authored-by: Thomas Hu <[email protected]>
* fix the two CI `pycodestyle` failures observable in latest `master` branch merge: https://travis-ci.org/github/scipy/scipy/jobs/741128508
…ixes MAINT: fix CI pycodestyle fails
MAINT: forward port 1.5.4 release notes
… method is 'lm'. (scipy#13046)
* BUG: forward port lint_diff shims * forward port the Travis CI shallow clone-related fixes required for `lint_diff.py` to run properly on backport PRs from scipygh-13028 * a better fix might happen with the Python module itself so that the module may be used within any CI service (or at least provide some kind of warning in the presence of a shallow clone); that said, if such a fix is pursued, please do test with a "dummy PR" against a maintenance branch as well * MAINT: PR 13036 revisions * reduce the amount of data fetched in Travis CI for the purposes of the `lint_diff.py` script in backport PRs, as requested by reviewer
DOC: typo fix for cluster documentation
…#11346) The new function `scipy.linalg.matmul_toeplitz` uses the FFT to compute the product of a Toeplitz matrix with another matrix. Co-authored-by: Matt Haberland <[email protected]> Co-authored-by: Warren Weckesser <[email protected]>
Add calculation of the standard error of the intercept to `linregress`. - Add estimation of standard error on intercept - Updated all code which uses linregress - Add test comparing linregress to polyfit - Added confidence interval estimation to the docstring
…ndices instead of Bj
…scipy#12767) * ENH: add mode NI_EXTEND_WRAP_GRID to map_coordinates * MAINT: remove duplicated code for the mirror extension case The next step is to use other modes here in addition to the existing map_coordinates call above * pass the mode argument to spline_filter1d calls in interpolation.py * BUG: use wrap and reflect spline boundary conditions appropriately * use grid-wrap instead of wrap-grid as suggested in scipygh-206 add alias grid-mirror for reflect TST: test_splines.py now needs to use 'grid-wrap' rather than 'wrap' * ENH: modify NI_ZoomShift to support all spline boundary modes as well the same approach for spline_mode as used in NI_GeometricTransform is repeated * BUG: For line buffer functions set grid-wrap equivalent to wrap * TST: add map_coordinates boundary tests for new modes TST: add new zoom and shift tests TST: add reflect via affine shift test * DOC: update ndimage.interpolation docstrings * DOC: add boundary and interpolation grid figures ndimage tutorial * DOC: pep8 in tutorial examples * DOC: update plot_interp_grid.py tickmarks for matplotlib 3.3 compatibility * DOC: update tutorial on reviewer feedback * DOC: link to boundary mode illustrations from interpolation docstrings DOC: mention grid-mirror and grid-wrap synonyms in ndimage filter docstrings DOC: update mode descripts in the ndimage filter tutorial text
For instance, scipy.signal.hann is deprecated in favor of scipy.signal.windows.hann, so I changed many similar examples to the updated namespace.
MAINT:optimize: clip_x_for_func should be private
This warning was being generated when the pocketfft code was compiled:
g++: scipy/fft/_pocketfft/pypocketfft.cxx
scipy/fft/_pocketfft/pypocketfft.cxx: In function ‘PyObject* {anonymous}::good_size(PyObject*, PyObject*, PyObject*)’:
scipy/fft/_pocketfft/pypocketfft.cxx:381:24: warning: ISO C++ forbids converting a string constant to ‘char*’ [-Wwrite-strings]
381 | char * keywords[] = {"target", "real", nullptr};
| ^~~~~~~~
scipy/fft/_pocketfft/pypocketfft.cxx:381:34: warning: ISO C++ forbids converting a string constant to ‘char*’ [-Wwrite-strings]
381 | char * keywords[] = {"target", "real", nullptr};
| ^~~~~~
In ISO C++, the type of a string literal is `const char *`. This commit
fixes the warnings by making the `keywords` array `const`, and then casting
away the constness when it is passed to PyArg_ParseTupleAndKeywords.
* For values of df > 344 the stats method of nct would raise runtime warnings and become nan unnecessarily. * add fix for df < 2 cases to nan Co-authored-by: Warren Weckesser <[email protected]>
TST, CI: turn on codecov patch diffs
Minor fixes on doc of function csr_tocsc
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Reference issue
What does this implement/fix?
Additional information