Add wildcards options in config and restructure config files #729
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Closes #622 and continues from #264
Changes proposed in this Pull Request
This is a re-attempt to restructure config files by categorizing sector and adding wildcard options specifying if its enable or not.
The first stage is to integrate the options wildcard in config (see
config.default.yaml). It tries to have backward compatibility but fails partially due to the addition of co2 as a section in config.The second stage is to integrate the sector options wildcard in config (see
config.new.yaml). This was the propose design from me and @FabianHofmann. We are looking forward for more suggestion!Problems/Challanges that might arise
Checklist
envs/environment.yaml.config.default.yaml.doc/configtables/*.csv.doc/release_notes.rstis added.