-
-
Notifications
You must be signed in to change notification settings - Fork 52
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 a support to write NDCube data into FITS file #179
Conversation
1. Used mixin class to implement the write method 2. This would ensure that we can add further read and write functions for different formats 3. Only three types of uncertainty have been added.
1. Added the NDCubeIOMixin as a mixin class for ndcube 2. Added a writer function 3. Registered the writer function 4. Added a cross-check for ensuring the fits convention is followed
1. Changed the uncertainty defaults 2. Now any uncertainty along with any uncertainty data type would be accepted.
1. Changed the mixin class design 2. Removed the constructor
1. Changed the comments of the flattened dictionary 2. Corrected some typo for fits_checker 3. Changed the name of the `to_hdu` to `to_hdulist` 4. Changed the name of the ImageHDU list 5. Used `isinstance` to conform to numpy mask 6. Changed the LABEL for extra coords 7. Shifted the `fits_ndcube_writer`
1. Moved the label for missing and extra_coords inside the function 2. Corrected the `self._mask` parameter
1. Changed to the correct import order 2. Added the function name to the list of public objects
Thanks for the pull request @yashrsharma44! I am a bot that checks pull requests for milestones and changelog entries. If you have any questions about what I am saying, please ask!
If there are any issues with this message, please report them here. |
Hello @yashrsharma44! Thanks for updating this PR. We checked the lines you've touched for PEP 8 issues, and found:
Comment last updated at 2020-04-09 16:03:55 UTC |
] | ||
) | ||
def test_meta_from_hdulist(header_obj, header_values1, header_values2, header_values3, header_values4, header_values5, missing_axes): | ||
wcs_axes, crpix1, crpix2, crpix3 = header_values1 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Here I haven't found a way to test meta values, so maybe we need to decide on the way we store meta values? So that we have only one way to access them.
|
||
""" | ||
|
||
if len(key) > 8 and len(value) > 72: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is it necessary that both these conditions are met? What if len(value) < 72
but len(key) > 8
? Is this still correct?
This pull request has been automatically marked as stale because it has not had any activity for the past five months. It will be closed if no further activity occurs. If the ideas in this pull request are still worth implementing, please make sure you open an issue to keep track of that idea! |
This pull request has been automatically closed since there was no activity for a month since it was marked as stale. If the ideas in this pull request are still worth implementing, please make sure you open an issue to keep track of that idea! |
This PR addresses issue #111.
This is a continuation of the PR #154.
All the relevant discussions have taken place there.
Tasks before this is merged -
Tests for the new method inndcube.py
ndcubeio.py
Ping @DanRyanIrish