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

Workspace, experiment and configuration maturation #1340

Closed
markusdregi opened this issue Jan 28, 2021 · 2 comments
Closed

Workspace, experiment and configuration maturation #1340

markusdregi opened this issue Jan 28, 2021 · 2 comments

Comments

@markusdregi
Copy link
Contributor

Currently, the state of the workspace and the configuration is persisted in the two submodules ert3.workspace and ert3.config. While ert3workspace is a very thin utility module on top of the file system, ert3.config loads the different configuration files separately. We should probably unify this such that one can explore a workspace programmatically without the file system leaking through and it being possible to load the configuration of an experiment in a single load operation.

@markusdregi
Copy link
Contributor Author

There is some cross-file validation in the workspace that is needed. When taking on this work that should either be addressed or created issues on!

@sondreso
Copy link
Collaborator

Very related to #2168

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants