-
Notifications
You must be signed in to change notification settings - Fork 656
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
Suport for parametrized books/pages #424
Comments
I’d be fine depending on papermill...it’s a community-supported project and I agree gives us a better ceiling for expanding functionality if we like. |
I just want to add that it would be nice to have dynamic parameters. I am making a report that the parameters could change year to year depending on the output of a calculation. So the calculation will be run in one notebook, the output will serve as the parameters for the parameterized one. I am struggling on how I will implement this currently. I am just starting out with jupyter-book and love it so far so thank you! I look forward to parameterized notebook support. |
Just throwing in an idea/use case. I have a notebook that does a query to fetch the same parameter from two different datasets and then compares the distributions. In my database I have many parameters and am currently using papermill to render a notebook per parameter. It would be cool to be able to declare something like this in the toc format: jb-book
root: index
parts:
- caption: Name of Numbered Part 1
numbered: True # Only applies to chapters in Part 1.
chapters:
- template_file: path/to/part1/chapter1
parameters:
- param_a: 1
param_b: 2
- param_a: 4
param_a: 5 and have a page rendered for each item in the parameters array |
As discussed in #113, I suggest adding support for parametrized books or single-pages.
Rationale
Design choices and open questions
parameters
at the beginning of the notebook. That sounds like a decent approach.--execute
.Papermill also supports reading parameters from a yaml file, which is nice:
parameters
cell.Let me know what you think!
The text was updated successfully, but these errors were encountered: