-
Notifications
You must be signed in to change notification settings - Fork 35
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
Graphics for file flow #684
Conversation
I'll check on the codestyle things. But in the meantime, @karllark do you happen know what's going on with docs error about not being able to read the image file? |
This pull request introduces 1 alert when merging a5629c3 into b1950c6 - view on LGTM.com new alerts:
|
You need to add the png file to the |
Oh right! I'm pretty sure you've had to explain that to me a few times now 😆 |
Hmm, that seems to not be the problem. I think that line in setup.cfg is for things in the |
Humm....do the docs build on your computer? Another thought, are the permissions on those files ok? |
Ok, the issue is the filename is wrong in the rst file. In the docs it is |
Thanks for catching that!! Hopefully things are good to go now... |
It looks like the coverage test is failing because it's having download problems. I noticed that yesterday too, but with a different file. |
I agree the coverage tests are an unrelated download issue. Can you fix the minor codacy issue? |
I just checked on the Codacy issue. I'm a little confused - it says "No blank lines allowed after function docstring", but only finds one instance of it, when there are actually three functions with what I assume are blank lines after the function docstring. Is this something you're familiar with? |
Nope. If black is ok with the file, then say the word and I'll ignore the codacy check. |
Yeah, I re-blackened and nothing was changed. I did some googling, and from discussion here, it seems like it might be varying interpretations of one of the PEPs: (and apparently I inadvertently linked that issue and this PR... woops 😬) |
One last minor change. Can you change the title of the rst page to |
Done! |
Codecov Report
@@ Coverage Diff @@
## master #684 +/- ##
==========================================
- Coverage 44.91% 44.24% -0.68%
==========================================
Files 98 99 +1
Lines 9477 9638 +161
==========================================
+ Hits 4257 4264 +7
- Misses 5220 5374 +154
Continue to review full report at Codecov.
|
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.
Looks great.
This adds visualizations of what files are created when a BEAST run is split by either subgrids or source density. These are added to the docs and the code is in
plotting
. To help untangle the mess of lines, some of them are color-coded to separately follow the SED grid, noise model, and photometry.plot_graphic_file_flow.py
has options to change the numbers of subgrids, SD bins/sub-bins, etc. I settled on the current numbers because sometimes the graphs get rearranged in unhelpful ways.Partially addresses #680
Subgrid splitting
Source Density splitting