Separate filenames for parametrised notebooks

[shaenzi]

Hi,
I am using the Parameters feature described here to generate two identical-looking reports but starting with different input data. I would like to run this in my data pipeline (currently implemented in kedro) and was wondering whether it is possible to specify a different output filename for each parametrised rendering? Otherwise I would try and write the same file twice (I could of course rename in the mean time, but thought there might be an option to specify the output filename).
I am working in a jupyter notebook, and trying to turn a ipynb file to a html.
thanks!

[cderv]

How are you calling quarto render within your pipeline ?

Using -o or --output flag in quarto render allows you to specify the output filename.

quarto render test.qmd -o custom.html

Details of `quarto render help`

❯ quarto render help

  Usage:   quarto render [input:string] [...args]
  Version: 99.9.9

  Description:

    Render input file(s) to various document types.

  Options:

    -h, --help                          - Show this help.
    -t, --to                            - Specify output format(s).
    -o, --output                        - Write output to FILE (use '--output -' for stdout).
    --output-dir                        - Write project output to DIR (path is project relative)
    --execute                           - Execute code (--no-execute to skip execution).
    -P, --execute-param                 - Execution parameter (KEY:VALUE).
    --execute-params                    - YAML file with execution parameters.
    --execute-dir                       - Working directory for code execution.
    --execute-daemon                    - Keep Jupyter kernel alive (defaults to 300 seconds).
    --execute-daemon-restart            - Restart keepalive Jupyter kernel before render.
    --execute-debug                     - Show debug output for Jupyter kernel.
    --use-freezer                       - Force use of frozen computations for an incremental file render.
    --cache                             - Cache execution output (--no-cache to prevent cache).
    --cache-refresh                     - Force refresh of execution cache.
    --no-clean                          - Do not clean project output-dir prior to render
    --debug                             - Leave intermediate files in place after render.
    pandoc-args...                      - Additional pandoc command line arguments.
    --log                     <level>   - Path to log file
    --log-level               <level>   - Log level (info, warning, error, critical)
    --log-format              <format>  - Log format (plain, json-stream)
    --quiet                             - Suppress console output.

  Commands:

    help  [command]  - Show this help or the help of a sub-command.

  Examples:

    Render Markdown (w/ Knitr engine):   quarto render notebook.Rmd
                                         quarto render notebook.Rmd --to html
                                         quarto render notebook.Rmd --to pdf --toc
    Render Markdown (w/ Jupyter engine): quarto render notebook.qmd
                                         quarto render notebook.qmd --to docx --highlight-style=espresso
    Render Jupyter Notebook:             quarto render notebook.ipynb --to docx
                                         quarto render notebook.ipynb --to pdf --toc
    Render to Standard Output:           quarto render notebook.Rmd --output -

[shaenzi]

ah, thought it had to be easy. Thanks!
Should the output look exactly the same? the HTML looks quite different in terms of styling when I -o

[shaenzi]

never mind. It does look exactly the same when I specify the same folder, good enough for me. Thanks again!