-
Notifications
You must be signed in to change notification settings - Fork 65
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
Cube mosaicing: Expand capabilities substantially #868
base: master
Are you sure you want to change the base?
Conversation
e8083b7
to
12ac463
Compare
Now branched off of #854 |
12ac463
to
3719766
Compare
11ccf6b
to
85a8999
Compare
This is largely reimplementing |
Some of the functionality I want here needs to be pushed into |
Dang, I thought I was getting somewhere.
|
2f4371f
to
944bd2e
Compare
I've been using this in production for a while. @e-koch, want to give it a once-over? Looks like I have some failing tests to fix, but I'm not sure if they're also failing on master |
Codecov ReportPatch has no changes to coverable lines.
📢 Thoughts on this report? Let us know!. |
WIP / stash
…(but it doesn't work right yet)
… add a lot of verbosity
…should be semiautomatically excluded
0cfcd02
to
10e3ed3
Compare
I added some tests in, and they revealed that something is going very weird with weighted mosaicking in at least one case (weights are going to nan when the data are fine). cube-based reprojection (i.e., fully relying on reproject) is extrapolating in a region where it shouldn't, but that's literally an edge case, so I'm not so worried about it. |
I'm now pretty confident there's a bug in reproject, or at least in how it's interacting with cube reprojection. For one channel in the test case, I get:
while for the exact same input parameters (same WCS, same everything except it's "array" instead of "weights":
Why are weights going to NaN? |
this raises a different issue, which is that weights are implicitly on the same grid as the data, but they're not actually required to be |
I fixed the bad weights issue in reproject/5cfa233 / astropy/reproject#474. However, I still don't understand how I encountered the error in the first place - the weight & cube headers are identical. |
Checking through errors... there are some horrendous ones.
I think this indicates that an This could be associated with memmap; I can't tell yet (waiting on tests to finish). |
following up - it's not exclusive to memmap or mode:
|
Test failures are down to
|
those configurations are impossible to read.
means
means
means
so the error is just all |
the cube utils mosaic header maker wasn't checking the spectral dimension before