Choose what naming we want to use for recurring concepts

[EllieKallmier]

Recurring concepts:

• Things that have ISP versions
  • Sub-regions
  • Regions
  • ?
  • Area, project, etc for trace naming
• REZ names vs. IDs (where do each get used?)
  • we did discuss this a little last year - using REZ IDs from the templater step onwards. I.e. templater replaces instances of full text names with IDs
  • But maybe we want to keep the names around somewhere (?) for plotting or results formatting later
• Technology/resource/generator type/carrier-esque concepts
  • "Name"-adjacent columns in generator summaries, for example (ID?)
• Convention for naming columns not used in pypsa model but still useful for results/plotting/saving/validation etc?

Probably a few more!

More broadly - at what point do we change variable names when there's a mapping from ISP -> PyPSA? How do we log/document that change to be super clear?

[nick-gorman]

From discussion

node naming decisions:

• always use "subregion"
• dont use "isp_" preffix for "subregion"
• always use "rez" in ispypsa (trace parser might be differently)
• always use "region"
• always use "_id" as suffix to indicate a data column contain IDs

TODO:

• Document in dev-practices repo
• raise issue to refactor