Improve the OUTPUT workflow

[clizbe]

The output workflow (solution -> graphs) needs improvements. This will take many iterations, but an initial effort should improve the user experience in the short term as our community grows.

Post-Processing

How should we make the output easier for the analyst to use?

• Create export format - is this something standard or should be flexible / user-choice?
• Add explanation of model output to documentation #352

See the OBZ repo for the processing @datejada and @IsaiMaganTNO have created, specifically pipeline.jl using functions.jl. Keep in mind this is using a TEM version before the refactor.

Export

Document multiple options so user can choose.

• Return tables (a.k.a. DuckDB) or dataframes as the output format #115
• Document how to interact with result in DuckDB
• Document export to Excel/CSV
• What other export formats are useful to document?

Graphing

Should we only provide suggestions & examples of tools, or also set up a sharing library for the TLC?

• Hide TulipaPlots repo TulipaPlots.jl#39
  • Salvage anything useful.
• Documentation for using pygwalker (decide what documentation is most appropriate)
• Other tools?
• Consider setting up (how?) graph/script-sharing library for TLC

Related Issues/Discussions

• Improve the INPUT workflow #974
• Create a diagram of the workflow #415
• Handle management of existing tables TulipaIO.jl#35