restructure files

[claytonpbarrows]

I plan to improve the file structure of this repo. A proposal for the new structure follows:

• src # scripts for tool specific data conversion
• data # the source data
• dist # tool specific formatted versions
  • unsupported # formatted versions without programmatic conversions and CI
  • PandaPower
  • Plexos
  • Prescient
  • MATPOWER
  • ...
• test # CI tests for tool formatters

[GordStephen]

In the spirit of brainstorming, could I suggest splitting the "canonical" data and the tool-specific formats into separate repositories? Or better yet, canonical data + one repository per tool? That would make the respective commit histories a lot more informative, and also decentralize the process of adding new formats (stewarding the system specification and maintaining a dozen different implementations of that specification are fairly distinct tasks and you/NREL/the IEEE TF doesn't necessarily need to be involved in the latter).

[claytonpbarrows]

Makes sense.

[GordStephen]

Cool. You should still be able to pull in a whitelisted set of format generators as part of a CI workflow, if you want to automatically generate new formatted data whenever the spec changes. If you want help just let me know!