refactor derive_annotations to allow output path #535
Merged
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.
added a flag that lets you specify an output path
represented by the 'output_set'
Public API unchanged
I needed a way to direct my
AcousticsDerivatoroutput to some folder, and this works wellI could've changed some of the steps towards the end of
derive_annotations, where it imports the changes into the annotation metadata, but this turned out to be messy and tricky.In fact, there was an easy and very elegant way to do it! We can actually run an automated importation that puts it in the format expected of ChildProject.
The only caveat now is that such an importation requires a
rawfolder with the file stems the same as those for the recordings, so we need to do a bit of renaming after running the derivation.In code that looks something like this in the end