reproject
reproject copied to clipboard
Python-based Astronomical image reprojection :milky_way: - maintainer @astrofrog
updates: - [github.com/psf/black-pre-commit-mirror: 24.4.0 → 24.4.2](https://github.com/psf/black-pre-commit-mirror/compare/24.4.0...24.4.2) - [github.com/scientific-python/cookie: 2024.03.10 → 2024.04.23](https://github.com/scientific-python/cookie/compare/2024.03.10...2024.04.23) - [github.com/astral-sh/ruff-pre-commit: v0.4.1 → v0.4.3](https://github.com/astral-sh/ruff-pre-commit/compare/v0.4.1...v0.4.3)
I am seeing a very strange issue. The following example tries to reproject a dataset with a GWCS to a slightly different GWCS: ```python import os import asdf from copy...
The main functions in reproject, such as ``reproject_interp``, accept ``parallel=`` and ``block_size=`` arguments which, if used, will leverage dask behind the scenes to split up the data into chunks and...
At the moment, we force cdelt[0] to be negative but this isn't true for e.g. solar data. We should avoid this!
This is an experiment for now but it allows: * N-dimensional reprojection/co-addition * ``combine_function='median'`` (not implemented here but trivial to do) * ``reproject_and_coadd`` to optionally return a dask array (``return_type='dask'``)...
Dear all, I have an issue with the reproject_exact() function, which doesn't properly conserve the flux. To demonstrate the issue, I prepared an example which you can download from my...
This adds a `blank_pixel_value` keyword that defaults to `nan` and applies to all combination modes in the coadd/mosaicking step.
Before #413, pixels that were not covered by the footprint were set to nan, and they are now set to zero. https://github.com/astropy/reproject/commit/31c420533e4c86b0e44b988485f1f87dd7bf8ac5 I have a lot of code that relied...
This enables memmap'd output, which will be needed for very large (greater-than-memory) output cubes EDIT: it also extends `reproject_and_coadd` into three dimensions