Christoph Gohlke

> because we need to apply lstsq for each (real, imag) pair in the image. I understand that the inputs for `lstsq` need to be in a certain way. But...

> (0.9999999999999994, 3.9099874730191774e-16) Those numbers are 1.0 and 0.0 within expected precision. Not a good example for docstrings. Maybe better to use `(1.0, 0.0)` with `# doctest: +SKIP` The codecov...

I think we need @bruno-pannunzio on this. In general, please: - provide a PR description. Follow the checklist. - run `pre-commit` on your system before committing. - verify that the...

That makes sense. In that case, mention the use case in the documentation/tutorial and provide a separate function that assembles the coefficient matrix from any number of component phasor coordinates....

Superseded by #238

FWIW, I get ~18 ms with numpy+MKL 1.6.4 and 2.0.0 on i7-14700K.

> I've been following a manual approach with tifffile following [this tutorial](https://github.com/cgohlke/tifffile/blob/v2021.10.10/examples/earthbigdata.py) and the lessons from this issue https://github.com/fsspec/kerchunk/issues/78, but the lack of access to intra-file chunks makes it a...

> Another complication arises when two cursors overlap in the same region causing images to loose colour. For instance, if a blue and a red cursor are present, the expected...

Closed by #201

Hi @Mariochem92 thanks for contributing to this project. Since this is the first contributor pull request, it may be a good time to review the [contributor guide](https://www.phasorpy.org/stable/contributing.html#contribute-code-or-documentation) and get feedback...