Update coverage file in BabelStream case study #51
Conversation
This file contains 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
Pennycook
added
bug
We forgot to update the BabelStream case study when we changed the coverage schema. Running the example as it was gave an error due to schema validation. This commit is a best-effort attempt to convert the old coverage file into the new format. It is "best-effort" because: - The old format did not include filenames, but the new format requires them. Since the case study already uses anonymized platforms and languages, the simplest solution here was to generate names like "file1" and "file2". - The old format stored lines as regions containing the number of "real" lines of code in the range (start, end), rather than storing the specific lines of code that were used. However, since all the data was generated by the same version of Code Base Investigator parsing the same files, all the regions line up. The simplest solution therefore was to pretend that the region represented a contiguous run of lines. The information about the number of comments and amount of whitespace in a region is destroyed by this transformation, but it isn't necessary to compute divergence. Signed-off-by: John Pennycook <[email protected]>
Pennycook
force-pushed
the
update-babelstream-coverage
branch
from
452cc26
to
f737bfb
Compare
laserkelvin
approved these changes
Jul 19, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
We forgot to update the BabelStream case study when we changed the coverage schema. Running the example as it was gave an error due to schema validation.
This commit is a best-effort attempt to convert the old coverage file into the new format. It is "best-effort" because:
The old format did not include filenames, but the new format requires them. Since the case study already uses anonymized platforms and languages, the simplest solution here was to generate names like "file1" and "file2".
The old format stored lines as regions containing the number of "real" lines of code in the range (start, end), rather than storing the specific lines of code that were used. However, since all the data was generated by the same version of Code Base Investigator parsing the same files, all the regions line up. The simplest solution therefore was to pretend that the region represented a contiguous run of lines. The information about the number of comments and amount of whitespace in a region is destroyed by this transformation, but it isn't necessary to compute divergence.
Related issues
Closes #50.
Proposed changes