Skip to content

Conversation

IsaiMaganTNO
Copy link
Contributor

@IsaiMaganTNO IsaiMaganTNO commented Oct 14, 2025

Related issues

This pull request is related to several issues, namely reconstructing a Workflow tutorial for the TLC, showing a case where multiple runs of TEM are done through one connection and working with explicit DuckDB files to store results, read in data etc.
This is just an outline and needs major changes before it can be implemented, I am creating this pull request mainly for upcoming review meetings

Outside of these major changes there is currently 1 'bug'(?) that will prevent you from running all code in sequence when attempting to close the connection in order to create a backup .db file

"
connection = nothing
GC.gc()
"

will not work until running AGAIN (perhaps memory should be flushed before redefining 'connection'?)

Checklist

  • I am following the contributing guidelines
  • Tests are passing
  • Lint workflow is passing
  • Docs were updated and workflow is passing

@gnawin
Copy link
Member

gnawin commented Oct 14, 2025

Hi @IsaiMaganTNO great work! Just a heads-up after a quick browse.

I saw at various places the path is "docs/src/10-tutorials/my-awesome-energy-system/tutorial-7/results", you should change it starting from "my-awesome-energy-system".

And be sure to add the warning that the user has to create the "results" folder manually. See the warning message in other tutorials. An alternative is to add something like "mkdir(output_dir)", but that sometimes requires admin rights, which also gives headaches, so I did not do that.

@IsaiMaganTNO
Copy link
Contributor Author

Hi @IsaiMaganTNO great work! Just a heads-up after a quick browse.

I saw at various places the path is "docs/src/10-tutorials/my-awesome-energy-system/tutorial-7/results", you should change it starting from "my-awesome-energy-system".

And be sure to add the warning that the user has to create the "results" folder manually. See the warning message in other tutorials. An alternative is to add something like "mkdir(output_dir)", but that sometimes requires admin rights, which also gives headaches, so I did not do that.

Thanks a lot @gnawin ! Indeed I need to change that to make it consistent with other tutorials, good point! I am planning on making major changes, especially considering the tutorial is not finished yet. I will make sure to incorporate all these important details then as well.

@IsaiMaganTNO IsaiMaganTNO requested a review from clizbe October 14, 2025 09:26
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants