Skip to content
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

Add test how it should be #842

Merged
merged 1 commit into from Dec 12, 2018
Merged

Conversation

maxnoe
Copy link
Member

@maxnoe maxnoe commented Nov 29, 2018

This test shows how one should use our coordinate frames using skycoord

@thomasgas
Copy link

thomasgas commented Nov 29, 2018

Just to add a comment: this PR goes in the way of having the coordinate frames behaving correctly (and being used correctly, see #727) with the astropy SkyCoord class.
Solutions are:

  1. use SkyCoord from astropy with small fixes with respect to the present implementation.
  2. refactor coordinates in order to make them fast (a first implementation came from Dan: Coordinates improvements #753)

Both approaches needs to be consistent across the whole ctapipe (which is not the case right now). Tests, notebooks and classes using coordinates have to be updated accordingly.
It would be nice if also @kosack and @ParsonsRD could comment on this.

PLAN: The plan might be to make a small fix now and use astropy and then compare it with @ParsonsRD implementation.

@codecov
Copy link

codecov bot commented Nov 30, 2018

Codecov Report

Merging #842 into master will increase coverage by 0.01%.
The diff coverage is 100%.

Impacted file tree graph

@@            Coverage Diff             @@
##           master     #842      +/-   ##
==========================================
+ Coverage   73.52%   73.54%   +0.01%     
==========================================
  Files         211      211              
  Lines       12066    12075       +9     
==========================================
+ Hits         8871     8880       +9     
  Misses       3195     3195
Impacted Files Coverage Δ
ctapipe/coordinates/tests/test_coordinates.py 100% <100%> (ø) ⬆️

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update e715248...a4c5cc4. Read the comment docs.

@kbruegge kbruegge merged commit d30d4d8 into cta-observatory:master Dec 12, 2018
@kbruegge kbruegge deleted the fix_coordinates branch December 12, 2018 09:09
watsonjj added a commit to watsonjj/ctapipe that referenced this pull request Jan 7, 2019
* master: (22 commits)
  Remove all hillas_paramters but version 5, fixes cta-observatory#866  (cta-observatory#904)
  Fix docstring of EventSeeker, fixes cta-observatory#768 (cta-observatory#914)
  Do not set autodownload, fixes doc build (cta-observatory#910)
  Import bokeh.palletes correctly, fixes cta-observatory#911 (cta-observatory#912)
  Fix SST-1M to be DC and not SC. Solves cta-observatory#905 (cta-observatory#908)
  Fix a few test warnings (cta-observatory#902)
  Updates of NectarCam and LSTCam real data eventsource class (cta-observatory#812)
  Implemented FACT image cleaning (cta-observatory#862)
  remove `config=None, tool=None` in some tests (cta-observatory#897)
  Remove flow submodule (got moved to its own package) (cta-observatory#893)
  Cleaning the ctapipe folder. this has been empty for 3 years. (cta-observatory#892)
  Additional metadata from pyhessio, similar to cta-observatory#655 (cta-observatory#895)
  add scikit-learn to install_requires (cta-observatory#877)
  Add .mailmap (cta-observatory#894)
  Fix subarray peek. No more warnings. (cta-observatory#841)
  SimTelEventSource using pyeventio (cta-observatory#864)
  Use sparse neighbor matrix (cta-observatory#826)
  Add test how it should be (cta-observatory#842)
  fix errordef > 0. (cta-observatory#839)
  Fix warning about already closed hessio file (cta-observatory#834)
  ...

# Conflicts:
#	ctapipe/analysis/camera/chargeresolution.py
#	ctapipe/tools/extract_charge_resolution.py
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants