-
Notifications
You must be signed in to change notification settings - Fork 33
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
[WIP] Add GZ3D vac code #733
Conversation
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 this still a WIP? I would add docstrings everywhere there isn't it. Complete ones for exposed methods, single line ones for hidden methods. Overall there's a lot going on here. Which are the key methods that you want exposed to the user? I'm guessing the plot
methods. Are there methods that return useful data to the user? I would recommend making everything that is really unnecessary to the user hidden.
VAC name: <look this up> | ||
|
||
URL: <look this up> | ||
|
||
Description: <look this up> | ||
|
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.
Needs text.
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.
What URL should go here?
The WIP is exactly there because of the lack of doc string. I will try to get to this soon, but other projects are eating my time at the moment. Also how important are unit tests for VAC code? |
I just added doc strings to the private function, just need to add them to the plotting functions. While working on this code I created an example notebook that shows how to use it. Is this something that can be used in marvin's docs? If so where should it go and what format should it be? https://gist.github.com/CKrawczyk/191897d179464a8270cda2d055a9f2a0 |
Thanks for adding the docstrings! Regarding tests, it's not super important. Our test suite is a bit clunky, out-of-date, and broken at the moment. That being said, if there were some tests you wanted to include as a sanity check, they could go in The notebook looks great! We can definitely put it in place. It should go in the Let me know when you think this is ready to be merged. I'm aiming to have all the VAC PRs merged in the next few weeks so I can begin testing and finalization for DR17. |
@CKrawczyk Are you ready for this to be merged? I need to merge this as soon as possible so I can start finalizing the release of Marvin for DR17 in less than a month. |
This PR adds the custom class needed to read in GZ3D data mask fits files.
When reading in a fits table astropy adds blank spaces to the end of short stirngs in a column. For the mangaid search to work these spaces need to be `.strip`ed frist.
This uses the approximation from Westfall 2019 to account for covariance in the spectra when taking averages.
This is a first pass on documenting all the class attributes and methods along with some funcions for plotting the image and masks.
And also with less memory. `_stack_spectra` now uses a running sum for the variance calculation rather than building a full covariance matrix. It also assumes no cov for spaxels with distances more than 6.4 as suggested in Westfall 2019.
Also add abilit to make mask plots in spaxel space.
This is the last of the plotting functions.
Defualt to the correct IFU hexagon and make the `correct_hex=False` give the hexagon shown to the GZ3D volunteers (same as what is baked into the iamge).
All private funcions now have 1-line doc strings.
Finished adding doc strings to all helper functions defined before the main class.
Add the last of the doc strings for the plotting methods of the mian class.
This notebook shows how to use the GZ3D custom class to make various plots.
One of the class methods was a hold over from old code and is no longer needed.
4b7e2fa
to
54b96cc
Compare
@havok2063 I think this is ready to go, I just need to know what URL you want to be included in the docstring for the I have done a test build of the docs locally to make sure the example notebook shows up as expected. For good measure, I also rebased against the latest |
@CKrawczyk Ok, cool. The URL can be whatever URL you want. Most people put a link to the VAC description on the SDSS Wordpress site, but if you have another site to point instead that's fine too. Ok, great. I'll wait until later in the day to merge this PR in case you want to make any final edits. In the past we've done only |
The rebase basically just replayed my commits on top of any there were made to the base branch, any time a conflict was found I resolved it (just in the This will merge into the base branch as if all my commits were made from a fresh branch made today rather than one made several months ago. All in all the git history will look "cleaner" than if I merged the base branch into this branch only for it to be merged back into the base branch. I will double-check with Karen if we have a VAC URL yet. |
Sounds good to me. |
Adds code for GZ3D VAC integration.
Things left to do:
This pull request: