-
Notifications
You must be signed in to change notification settings - Fork 40
Fix spelling issues #106
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Open
codewithbear
wants to merge
2
commits into
google:copybara_push
Choose a base branch
from
codewithbear:fix-issue-53-spellcheck
base: copybara_push
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
+113
−118
Open
Fix spelling issues #106
Changes from all commits
Commits
Show all changes
2 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -34,13 +34,13 @@ | |
| # that designates exterior space in the file input. | ||
| EXTERIOR_SPACE_VALUE_IN_FILE_INPUT = 2 | ||
|
|
||
| # Here we designate a specific placeholder to help use demarcate which CVs | ||
| # Here we designate a specific placeholder to help us demarcate which CVs | ||
| # are for exterior space once processed in the function. It is intentionally | ||
| # set to -1 so that the connectedComponent function can have access to all | ||
| # nonzero integers to count upwards in an unbounded way. | ||
| EXTERIOR_SPACE_VALUE_IN_FUNCTION = -1 | ||
|
|
||
| # Here we designate a specific placeholder to help use demarcate which CVs | ||
| # Here we designate a specific placeholder to help us demarcate which CVs | ||
| # are for exterior space are noted in the component. It is intentionally | ||
| # set to -1 so that the connectedComponent function can have access to all | ||
| # nonzero integers to count upwards in an unbounded way. | ||
|
|
@@ -52,7 +52,7 @@ | |
|
|
||
| # Here we pick out a specific value that we know will code for interior space | ||
| # after connectedComponents() processes it. We know this because we have ensured | ||
| # that the CV at index (0,0) will always be an "space" CV when ready for | ||
| # that the CV at index (0,0) will always be a "space" CV when ready for | ||
| # input to connectedComponents, but we previously index the exterior space CVs | ||
| # in their own data array. Thus, after overwriting the exterior space CVs to | ||
| # the value _EXTERIOR_SPACE_VALUE_IN_FUNCTION, all connectedComponents of | ||
|
|
@@ -82,17 +82,11 @@ | |
| # returning expanded exterior walls when calling enlarge_component() | ||
| WALLS_AND_EXPANDED_BOOLS = 2 | ||
|
|
||
| # Here we wish to specifically set exterior space as indistinguishable | ||
| # from exterior walls, as we wish to perform connectedComponents only on | ||
| # connected groups of interior space. Thus, we set exterior space to a generic | ||
| # space value, i.e. 0. | ||
| GENERIC_SPACE_VALUE_IN_CONNECTION_INPUT = 0 | ||
|
|
||
|
Comment on lines
-85
to
-90
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. removed a duplicated block
Collaborator
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. MJR TODO: verify duplicate block exists |
||
| # Here we use a specific placeholder value, matching with the file input schema, | ||
| # that designates interior space in the file input. | ||
| INTERIOR_WALL_VALUE_IN_FILE_INPUT = 1 | ||
|
|
||
| # Here we designate a specific placeholder to help use demarcate which CVs | ||
| # Here we designate a specific placeholder to help us demarcate which CVs | ||
| # are for interior walls once processed in the function. It is intentionally | ||
| # set to -3 so that the connectedComponent function can have access to all | ||
| # nonzero integers to count upwards in an unbounded way. | ||
|
|
||
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
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
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
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
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
OK. https://stackoverflow.com/questions/15539937/whats-the-difference-between-logging-warn-and-logging-warning-in-python