Conversation
What changes are you trying to make? (e.g. Adding or removing code, refactoring existing code, adding reports)I created two new functions: patient_summary() and detect_problems() to enhance the data analysis workflow for the inflammation dataset. patient_summary function helped to calculates the per-patient summary statistics (mean, max, or min) using NumPy; and detect_problems function helped use patient_summary() to calculate each patient’s mean inflammation score. Together, these functions allow automated summarization and basic data validation for all inflammation data files. What did you learn from the changes you have made?I learned how to 1) Use NumPy’s operations (np.mean, np.max, np.min) with the axis argument to efficiently compute statistics across rows or columns. 2) Build modular code by separating functionality into reusable helper functions (patient_summary, check_zeros, and detect_problems). 3) Combine data summarization and validation logic in a structured and readable way. Was there another approach you were thinking about making? If so, what approach(es) were you thinking of?N/A Were there any challenges? If so, what issue(s) did you face? How did you overcome it?At first, it was slightly confusing how NumPy applies functions like np.mean() or np.max() across different axes. I initially got unexpected results (single values instead of arrays) because I forgot to specify axis=1. To overcome this, I printed the shape of the data and experimented with small arrays to visualize how axis=0 (per day) and axis=1 (per patient) affect the results. How were these changes tested?I tested the updated function with csv data. A reference to a related issue in your repository (if applicable)N/A Checklist
|
2 participants
What changes are you trying to make? (e.g. Adding or removing code, refactoring existing code, adding reports)
I created an anagram_checker based on sorting and comparing letters in a word list. I then added a new boolean parameter is_case_sensitive to the anagram_checker() function. This parameter allows users to choose whether the anagram comparison should be case-sensitive.
What did you learn from the changes you have made?
I learned how to add optional parameters to functions and handle conditional logic based on input. I also gained a clearer understanding of how string manipulation and sorting can be used to compare character patterns efficiently.
Was there another approach you were thinking about making? If so, what approach(es) were you thinking of?
Yes, I also thought about using the python Counter method to count each letter in both words and compare the counts instead of sorting them. It would give the same result in a different way.
Were there any challenges? If so, what issue(s) did you face? How did you overcome it?
Initially, I had to ensure that the case conversion only applied when is_case_sensitive was False, without affecting the original input strings. I solved this by using conditional statements and storing the lowercase versions in temporary variables before comparison.
How were these changes tested?
I tested the updated function with multiple test cases.
A reference to a related issue in your repository (if applicable)
N/A
Checklist