-
Notifications
You must be signed in to change notification settings - Fork 68
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
Fix how we structure the run notebook rules. #1384
Conversation
Codecov Report
@@ Coverage Diff @@
## master #1384 +/- ##
=======================================
Coverage 89.49% 89.49%
=======================================
Files 151 151
Lines 5482 5482
=======================================
Hits 4906 4906
Misses 576 576 Continue to review full report at Codecov.
|
85045a8
to
37176b6
Compare
With this change, one can just run `make notebooks/py/smFISH.py` or `make smFISH.py`. For the examples in `docs/source/_static/data_processing_examples/`, we can also directly invoke them, i.e., `make 3d_smFISH.py`. Also, we run all notebooks with ipython instead of python now.
37176b6
to
8e5a64d
Compare
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.
Great. 👍
This should unbreak the cronjob. I think I broke this in #1384. Whoops!
This should unbreak the cronjob. I think I broke this in #1384. Whoops!
In #1384, I made it such that someone could run `make notebooks/py/xxxx.py` and run the notebook. Unfortunately, that created a dependency between the rule that regenerated the .ipynb file and the notebook running rule. This is not desirable, as regenerating the .ipynb files take forever now. This PR breaks that dependency. The idea is that the notebook regeneration process is so lightweight that we don't really need to examine the mtimes, and just do it blindly. Test: make -j validate-ipynb does not run the notebooks
In #1384, I made it such that someone could run `make notebooks/py/xxxx.py` and run the notebook. Unfortunately, that created a dependency between the rule that regenerated the .ipynb file and the notebook running rule. This is not desirable, as regenerating the .ipynb files take forever now. This PR breaks that dependency. The idea is that the notebook regeneration process is so lightweight that we don't really need to examine the mtimes, and just do it blindly. Test: make -j validate-ipynb does not run the notebooks
In #1384, I made it such that someone could run `make notebooks/py/xxxx.py` and run the notebook. Unfortunately, that created a dependency between the rule that regenerated the .ipynb file and the notebook running rule. This is not desirable, as regenerating the .ipynb files take forever now. This PR breaks that dependency. The idea is that the notebook regeneration process is so lightweight that we don't really need to examine the mtimes, and just do it blindly. Test: make -j validate-ipynb does not run the notebooks
With this change, one can just run
make notebooks/py/smFISH.py
Also, we run all notebooks with ipython instead of python now.