TLC Workflow tutorial draft outline #1390
Draft
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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