Completed the assignment 2. Data display, summary calculator, and zer…#2
Open
Completed the assignment 2. Data display, summary calculator, and zer…#2
Conversation
…os checker. Sihan He
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.
…os checker. Sihan He
What changes are you trying to make? (e.g. Adding or removing code, refactoring existing code, adding reports)
Added code to achieve three goals: 1. Display the content of the first checkin data. 2. Create a function to calculate the important basic statistics of the data (mean, maximum, minimum). 3. Create a problem detector function that detect irregular checkin entries (the ones containing zero means) based on the provided zero checker function.
What did you learn from the changes you have made?
Numpy is a very useful package that makes the code much more compact.
Was there another approach you were thinking about making? If so, what approach(es) were you thinking of?
I thought of using for loop, which would make the code much longer and less manageable.
Were there any challenges? If so, what issue(s) did you face? How did you overcome it?
Not really.
How were these changes tested?
They were tested with appropriate inputs in the subsequent cells. I also identified that checkins 3 and 10 were irregular using the problem detector.
A reference to a related issue in your repository (if applicable)
Checklist