UX Leo - Table description

[LeoEble]

Why are there three asset tables? Could be useful to include a small description per table in the "Model Parameters" section of the docs. Diving into the column descriptions is challenging when you don't understand the general purpose of the table.

[clizbe]

Thanks for the feedback!

The three tables have different unique indices or "keys":

• asset_commission: asset name + commission_year
• asset_milestone: asset name + milestone_year
• asset_both: asset name + commission_year + milestone_year
  (We know asset_both is a bad name... any ideas on what we should rename it?)

We split the data into tables based on these indices to avoid empty or repeated data.

We'll add some descriptions like you suggested, but understanding the tables and how the parameters relate to assets is something we need to explain better. What else do you think would help?
I think a mock network diagram of assets and flows with associated constraints and parameters would help - but it might be crowded or get outdated quickly...