Repository navigation
Fixing missing coordinate unit in aperture_photometry return for single ... - #213
Conversation
|
@bsipocz - Thanks! Do you have a self-contained code snippet for your question if there's an issue to be filed for |
|
Is this ready to merge? |
|
@cdeil - yes, I'll make a self contained version of it for the core, just wondered first whether you think this is a problem or not. I think it could be more like Quantity for single elements, like the example below, but I may well miss a trivial point with it: |
|
@bsipocz - I don't understand what the issue was / is here. If you want me to check this out before you ask somewhere else, can you post some code I can execute and mention what you think is not nice about how |
|
Restarted travis-ci ... this was an unrelated issue I just now fixed in master. |
|
@bsipocz Are you still working on this? |
|
@larrybradley - No, this should be fine as is. |
|
OK, great. Can you please rebase this? It looks like |
f7c6a1d to
7146c4d
Compare
Fixing missing coordinate unit in aperture_photometry return table
...positions
Sadly
hubis not working out of the box, thus I couldn't attached this directly to #212.Part of the problem causing this bug was that the inner container of
SkyCoordis not as consistent asQuantity's for single and multiple elements. I'm not sure whether this is a feature or just accidental, if the latter I'll open an issue for it in core.fixes #212