Move in bpz notebooks, update paths; copy over cmnn nb changes

OliviaLynn commented 8 months ago

Problem & Solution Description (including issue #)

Moving in bpz notebooks for #48
Paths have been adjusted as needed
I wasn't 100% sure on the other two data files that were stored next to the notebooks (are they also meant to be kept separate like the tar?), so I added them to the rail get-data --bpz-demo-data script in rail_base#76.

Also copies over updates to CMNN notebook made in CMNN repo to the notebook here

That was on me, should have deleted it sooner. PR is out to remove it at LSSTDESC/rail_cmnn#13

Code Quality

[x] My code follows the code style of this project
[x] I have written unit tests or justified all instances of #pragma: no cover; in the case of a bugfix, a new test that breaks as a result of the bug has been added
[x] My code contains relevant comments and necessary documentation for future maintainers; the change is reflected in applicable demos/tutorials (with output cleared!) and added/updated docstrings use the NumPy docstring format
[x] Any breaking changes, described above, are accompanied by backwards compatibility and deprecation warnings

codecov[bot] commented 8 months ago

Codecov Report

All modified and coverable lines are covered by tests :white_check_mark:

Comparison is base (1de4475) 100.00% compared to head (453792d) 100.00%.

Additional details and impacted files

```diff @@ Coverage Diff @@ ## main #109 +/- ## ========================================= Coverage 100.00% 100.00% ========================================= Files 1 1 Lines 1 1 ========================================= Hits 1 1 ```

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.

OliviaLynn commented 7 months ago

Ok, I changed some text and added a commented rail get-data command, so now I think it looks good, I'll approve, if my changes look good go ahead and merge.

Nice catch! That looks great, thank you

LSSTDESC / rail