Eric Firing

@jni I'm getting a better picture of what you mean now; yes, I see the logic in having imsave/imread be inverses (provided a lossless format is used for both) in...

@weathergod, I don't understand; would you elaborate, please?

On 2014/10/19, 4:25 AM, Benjamin Root wrote: > Maybe a more apt analogy would be "figimage(); savefig()"? That's basically how it is implemented.

We would be happy to see two PRs, one simple one to improve the documentation as you suggest immediately above, and a second to add the ability to write grayscale...

The problem also appears in simple comparisons: ``` In [2]: np.ma.masked_invalid([1.1, np.nan]) > 1 /Users/efiring/anaconda/envs/test/bin/ipython:1: RuntimeWarning: invalid value encountered in greater #!/Users/efiring/anaconda/envs/test/bin/python masked_array(data = [True --], mask = [False True],...

It's not clear to me that this is worth the added CI load and complexity.

I don't see any reason it shouldn't work. A quick test with a modification of https://github.com/wesleybowman/UTide/blob/master/notebooks/utide_uv_example.ipynb shows that one can call `reconstruct` with a much longer time series than was...

Given that #2972 has been merged, this PR should be closed, shouldn't it? (With thanks to @wbadart for initiating it, and to @CoolCat467 for pushing it forward.)

The present code is heavily based on working with a single series at a time, and it is doing all sorts of things that you would not actually want for...

Not sure what you mean by "astronomical adjustments". What I have in mind is factoring out the calculation of the model matrix, "B", which is roughly lines 229-277 in _solve.py....