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

Specify directory stucture per path instead of per project in config-user.yml #129

Open
bouweandela opened this issue Dec 7, 2018 · 5 comments · May be fixed by #1894
Open

Specify directory stucture per path instead of per project in config-user.yml #129

bouweandela opened this issue Dec 7, 2018 · 5 comments · May be fixed by #1894
Labels
enhancement New feature or request preprocessor Related to the preprocessor

Comments

@bouweandela
Copy link
Member

At the moment all drs need to be the same per project, while it would make much more sense to be able to specify the drs per rootpath.

To make this more clear, now we have this:

rootpath:
  # Rootpath to CMIP5 data
  CMIP5:
    - /badc/cmip5/data/cmip5/output1
    - ~/some_other_path

# Directory structure for input data: [default]/BADC/DKRZ/ETHZ/etc
# See config-developer.yml for definitions.
drs:
  CMIP5: BADC

while I think this would be much more useful:

# Directory structure for input data in the format
# input_data:
#   project_a:
#     /path/to/dir_1: drs_1
#     /path/to/dir_2: drs_2
#   project_b:
#     /path/to/dir_3: drs_2
# See config-developer.yml for valid drs definitions per project.
input_data:
  CMIP5:
    /badc/cmip5/data/cmip5/output1: BADC
    ~/some_other_path: default
@valeriupredoi
Copy link
Contributor

slightly bit counter-intuitive since currently all the keys in config-user are system keys and their values are user-defined - @mattiarighi

@bouweandela bouweandela transferred this issue from ESMValGroup/ESMValTool Jun 28, 2019
@mattiarighi mattiarighi added enhancement New feature or request preprocessor Related to the preprocessor labels Jan 7, 2020
@mattiarighi mattiarighi added this to To do in Medium priority issues via automation May 25, 2020
@bouweandela
Copy link
Member Author

Related to #181

@bouweandela
Copy link
Member Author

I'll try to fix this for v2.8.

@valeriupredoi
Copy link
Contributor

this is #1894 as it's linked by @bouweandela above

@remi-kazeroni remi-kazeroni modified the milestones: v2.8.0, v2.9.0 Feb 21, 2023
@bouweandela bouweandela modified the milestones: v2.9.0, v2.10.0 May 31, 2023
@bouweandela
Copy link
Member Author

Bumping to the next milestone as there is no consensus on the implementation, see discussion in the linked pull request.

@bouweandela bouweandela removed this from the v2.10.0 milestone Sep 21, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request preprocessor Related to the preprocessor
Projects
Development

Successfully merging a pull request may close this issue.

4 participants