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

improve PIMixin for Ensemble Data #1108

Open
SGeeversAtVortech opened this issue Feb 22, 2019 · 0 comments
Open

improve PIMixin for Ensemble Data #1108

SGeeversAtVortech opened this issue Feb 22, 2019 · 0 comments

Comments

@SGeeversAtVortech
Copy link
Contributor

In GitLab by @MaartenS on Feb 22, 2019, 15:10

There are basically two issues with the current PIMixin:

  • it does not read ensembleMemberId when an ensembleId is mentioned, only ensembleMemberIndex. As one cannot solve this on the FEWS side through ID mapping (and it probably not being wise to allow this), we should make sure that RTC can ingest ensemble data where either ensembleMemberId or ensembleMemberIndex is used, and not only the latter.
  • minor problem: upon import, RTC gives numbers to the ensembleMemberIndex and does not create a dictionary to keep track of this mapping, for example for writing outputs, or internal use in for example pre() to do something with known traces.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant