Input dialect extension and initial usage - #14
Merged
Conversation
Signed-off-by: Lars Schneidenbach <schneidenbach@us.ibm.com>
Signed-off-by: Lars Schneidenbach <schneidenbach@us.ibm.com>
Signed-off-by: Lars Schneidenbach <schneidenbach@us.ibm.com>
Signed-off-by: Lars Schneidenbach <schneidenbach@us.ibm.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Introducing code to deal with different 'input dialects' (using singleton patterns) for the data ingestion.
Each event already has a reference pointing to it's data source file and this item has been extended to include the dialect so that for each event we can retrieve it's 'dialect'.
Initial usage has been added to tb_refinement and bw computation.
For this to work, the cleanup of the file-reference hash had to be moved to after the tb_refinement stage.