Draft User Workflow

[clizbe]

Prereqs:

• Download Julia
• Add Tulipa
• Get an ESDL MapEditor account
• Download VSCode (optional)
• Add Pluto (optional)

Create 3 Core files:

1. Graph file

   • What are the requirements?
   • Where should this be explained?
   • Use ESDL MapEditor
   • Include assigning profiles?
     Export ESDL to analysis folder

2. Scenario file

   • How?
   • How is this related to editing data in TIO?

3. Partitions file

   • How?

Follow Pipeline
Create a Julia script or Pluto notebook (recommended) to follow:
https://github.com/TulipaEnergy/pipeline-example

Summary of pipeline:

1. Use TIO to read files
   1a) Edit data for alternatives?
   Define scenario specification workflow #414
2. Send data to TC
3. Send data to TEM
   • Future: With feature specifications (see Implement data validation & default assumptions #461 (comment))
4. Graph results
   • Currently: Hand-craft as needed (in Julia!)
   • Future: Import data into Pluto graph template

Related:

• Create a diagram of the workflow #415
• Define scenario specification workflow #414
• Build the input workflow #289
• How should we handle data duplication, provenance, metadata? #499
• Maybe some ideas in here while we were talking ESDL: Input and output data files in the model #56

[clizbe]

Just wanted to write this down for my own sanity. Also to see if it makes sense and/or can be simplified.

[clizbe]

Random thought: Another model I know has a files that explicitly state whether a specific technology is allowed (or prohibited) in an area. This is specified in addition to their normal method of allowing tech in areas, as an override switch to be sure those specific techs are allowed/prohibited.
Long story short this shows that model does not have oversight of all the data going into the model for a given scenario. So some kind of "overview" and/or sanity checks of a scenario would be nice.

[datejada]

@IsaiMaganTNO, we can help to add more things to this workflow from our experience in the OBZ case study. So, let's keep this discussion on our radar and update it with the main findings.

[clizbe]

Yes and feel free to update the main block of the discussion above with the new workflow. Delete what's there and put what you actually have. :)

[clizbe]

Closing this discussion as we've moved on. It's linked in #974 for background info.