Make catalog.py, config.py and io.py their own package

[RondeauG]

Addressing a Problem?

These 3 scripts do a lot of useful things that go beyong xscen. They ould be moved to their own repo/package, and simply be imported by xscen.

Potential Solution

No response

Additional context

No response

Contribution

• I would be willing/able to open a Pull Request to contribute this feature.

[RondeauG]

Or not... Compare to functions in miranda and assess who copies who and which ones should be merged.

[Zeitsperre]

I still don't think it's a terrible idea to make these into a helper package. This is a pretty standard approach for libraries that produced by the same organization (e.g. https://github.com/roocs/roocs-utils).

We wouldn't be the first to consider doing this either...

[RondeauG]

Following our discussions last week and here, this issue can be closed.

• miranda keeps:

  • Downloads and APIs
  • convert
  • validation (CV, facets)
  • frequency & xrfreq dictionnaries

• xscen keeps:

  • IO, config, scripting
  • frequency & xrfreq dictionnaries

• xscen gains those from miranda:

  • structure: Building the Ouranos folder structure based on facets
  • decode: To be replaced by a ‘parse_directory’ workflow

The specific workflows (e.g. download ERA5, convert and validate, then move the files to the correct folder structure) will move to a private repo.

[Zeitsperre]

It might be worthwhile to create a "project" under xscen and open issues in the affected repositories, associating them to the project.

[Zeitsperre]

Issues are now listed on miranda side. Closing.