Conversation
|
Check results are now reported in the status checks at the bottom of this page. |
Codecov Report
@@ Coverage Diff @@
## master #1163 +/- ##
==========================================
- Coverage 62.61% 62.47% -0.15%
==========================================
Files 174 176 +2
Lines 14413 14612 +199
==========================================
+ Hits 9025 9129 +104
- Misses 5388 5483 +95
Continue to review full report at Codecov.
|
keflavich
left a comment
There was a problem hiding this comment.
Initial review. Only minor comments so far.
ab0c591 to
712c326
Compare
|
@mwcraig - just ping us when this is ready for further review |
|
(still working on this but wanted to push some updates) |
|
I could use some feedback on how to structure the arguments for the two methods here. The challenge is that each method ( Two approaches I can see:
I just pushed a version which sort of does the second but I'm not sure I like the approach I took of adding a |
|
I prefer two methods with common settings factored out. Will look at the code too... |
keflavich
left a comment
There was a problem hiding this comment.
The approach you've taken seems fine for now, but I haven't seen it in action
|
Still working on the documentation, but the code is just about done... |
229e5a9 to
83b5fc7
Compare
|
@keflavich @bsipocz -- this is ready for review, though there are still a few things to be fixed before merging:
|
|
@dstndstn -- this PR adds a Python interface to astrometry.net. I have a question -- what is the appropriate rate at which to query the server to see if it is done with a solution? Right now it simply checks every second (see https://github.com/astropy/astroquery/pull/1163/files#diff-93fb4c4b0964e0725414e59df9f4150dR229 ) but I could make it less aggressive. (and thanks again for the service!) |
|
Question about coverage -- many the bits being reported by codecov as uncovered are actually covered by the remote data tests. Should I be mocking up the remote or something and writing non-remote tests for those things (the methods Will, of course, write additional tests for everything that clearly does not require remote. |
|
@mwcraig - I will review this if I can find time, but it's a big one and I'm pretty preoccupied. I hope I'll find time this week.... On coverage, we just don't measure the coverage of remote tests, unfortunately. |
|
No big rush; I'll check the coverage locally with the remote tests running. Let me know if you want me to try mocking up some tests. |
|
@mwcraig - I'm also snowed it quite badly, but will try to find time to do a review. As for coverage, don't worry that much about mocking for things where local testing is not sensible. |
29b0ef4 to
ebcd9b6
Compare
| def api_key(self): | ||
| """ Return the Astrometry.net API key. """ | ||
| if not conf.api_key: | ||
| log.error("Astrometry.net API key not in configuration file") |
There was a problem hiding this comment.
is the api key required? if so, raise instead of log this error?
There was a problem hiding this comment.
An error is raised if you do any operation that requires the api key (all communication with astrometry.net goes through _login, which raises an error). Here the user gets a warning if they try accessing the attribute.
There was a problem hiding this comment.
would that be possible to get an API key for testing? We ideally need something for CI cron tests.
There was a problem hiding this comment.
Yes; we'd need to set up an account on astrometry.net. I'll do that this morning and pass the credentials off to @bsipocz for CI encryption.
| The contents of the returned object depend on whether the solve | ||
| succeeds or fails. If the solve succeeds the header with | ||
| the WCS solution generated by astrometry.net is returned. If the solve | ||
| fails then an empty dictionary is returned. See below for the outcome |
There was a problem hiding this comment.
I don't remember why I did an empty dict instead of None; happy to change.
|
@mwcraig - Could you rebase one more time to clear up the unrelated test failures? |
ce209a5 to
15547d5
Compare
|
@bsipocz -- rebased |
These apply to one type of source input (a list) and are not general settings like the rest
8d60cce to
378360e
Compare
This PR replaces #521 (but does include all of the commits from that PR with proper attribution). I'll add a test that checks the solution for the small data file I've added later tonight.
The intent is that there also be a
solve_from_imagemethod or something that uploads an image for astrometry.net to do the source detection.I'd like a better way of managing all of the options, but this is a start....
To do