Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

ScmEnsemble #98

Open
lewisjared opened this issue Aug 19, 2020 · 0 comments · May be fixed by #128
Open

ScmEnsemble #98

lewisjared opened this issue Aug 19, 2020 · 0 comments · May be fixed by #128
Assignees
Labels
enhancement New feature or request

Comments

@lewisjared
Copy link
Collaborator

Is your feature request related to a problem? Please describe.
An ScmRun requires timeseries to be on the same timebase. This requires an expensive resample when joining different scenarios.

Describe the solution you'd like

An ScmEnsemble object which is a container for 1 or more ScmRun's. This object proxies commands like filter and timeseries to ScmRun and then combines the result.

There will be an implicit meta column to which will be unique for each ensemble member. This allows the unique identification of a timeseries.

Describe alternatives you've considered

Not requiring identical an identical timebase within ScmRun. This may be useful in future, but would not allow run-specific metadata i.e. magicc metadata to be associated with a set of output.

@lewisjared lewisjared self-assigned this Aug 19, 2020
@znicholls znicholls added the enhancement New feature or request label Sep 11, 2020
@lewisjared lewisjared linked a pull request Sep 28, 2020 that will close this issue
4 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants