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.
This adds a YAML parser to make is pretty easy to write high-level model merging configs.
It should be used so:
python yamlconfig.py some.yml
It operates on yaml files with this structure:
This config does all kinds of model merging by slices. Slices can be copied from various source models, or combined in various ways in various orders. There is also a simpler 'model' based merging system, where similar models can be merged by just linear or spherical interpolation.
Note, the current low-level method for this code:
would be:
Currently, the model identity is not needed, and so the format is:
layer, layer, weight, weight
However, if we were working with more than 2 models, or the order changed, this would confuse us. e.g. we want to try merging 3 models, and sometimes were are merging [1,2], and other times [2,3], or we might have the order reversed [2,1].
Perhaps we should use the format:
model, model, layer, layer, weigh, weight
If this format seems better, I will update the parser to match.