You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm thinking about using Pluto for report generation. Basically, there would be a template notebook. For each new report (say each day), we'd load the template notebook, update a few variables, let PlutoRESTClient take care of updating things, store some outputs, and then export jl and/or html versions of the resulting Pluto notebook. On "good days", people would quickly view the html version including visualizations of the outputs and verify that everything went ok. But if they ever wanted to dig into what happened, then they could open the Pluto notebook from the html and jump right into data analysis.
nb =PlutoNotebook("MyTemplateNotebook.jl") # Open template notebook with PlutoRESTClient# Set some variables specific to this report
input_file =joinpath(data_path,string(today()),"inputs.csv")
output_file =joinpath(data_path,string(today()),"outputs.csv")
output_notebook_html =joinpath(data_path,string(today()),"report.jl")
output_notebook_html =joinpath(data_path,string(today()),"report.html")
# Set variables in notebook, update notebook, and get results (assumed to be in df_output)
results =nb(; report_date=today(), input_file=input_file ).df_output
# Write output data to table
CSV.write(output_file, results)
# Export resulting Pluto notebook
PlutoRESTClient.save(output_notebook_jl,nb)
# Export html version of notebook using PlutoSliderServer # Would provide both pretty report and ability to dive into notebook when needed using PlutoSliderServer
PlutoSliderServer.export_notebook(output_notebook_jl)
# or maybe the previous two steps could be merged likeexport_notebook(output_notebook_html, nb)
The text was updated successfully, but these errors were encountered:
I'm thinking about using Pluto for report generation. Basically, there would be a template notebook. For each new report (say each day), we'd load the template notebook, update a few variables, let PlutoRESTClient take care of updating things, store some outputs, and then export jl and/or html versions of the resulting Pluto notebook. On "good days", people would quickly view the html version including visualizations of the outputs and verify that everything went ok. But if they ever wanted to dig into what happened, then they could open the Pluto notebook from the html and jump right into data analysis.
The text was updated successfully, but these errors were encountered: