Nilofar tests

.markdownlint.yml

@@ -1,3 +1,7 @@
 ignore:
   - venv
   - .github
+
+MD013:
+  line_length: 500
+  ignore_urls: true

.vscode/settings.json

@@ -113,5 +113,14 @@
   },
 
   // Enable/disable update table of contents on save
-  "markdown.extension.toc.updateOnSave": false
+  "markdown.extension.toc.updateOnSave": false,
+  "cSpell.words": [
+    "Versity"
+  ],
+  "githubPullRequests.ignoredPullRequestBranches": [
+    "main"
+  ],
+  "[python]": {
+    "editor.defaultFormatter": "ms-python.black-formatter"
+  }
 }

README.md

@@ -0,0 +1,5 @@
+# PyVersity
+
+******
+
+welcome to Pyversity main repository

collaboration/README.md

@@ -2,4 +2,53 @@
 
 <!-- group norms summary -->
 
+## Summary
+
+Our group values respect, collaboration, and inclusivity by fostering a safe space,
+valuing diverse perspectives,
+and being punctual and prepared. We follow standardized coding practices, ensure
+thorough testing,
+and use pull requests for repository management. Committed to learning and growth,
+we support each other, respond promptly to queries, and resolve conflicts fairly
+through voting.
+
 <!-- group norms list -->
+
+## Finalized Norms
+
+### Respect
+
+* Be respectful and considerate when providing feedback or suggestions.
+* We must communicate respectfully to build trust.
+* We will value each other's time by being prepared and punctual. (Waiting time
+for every meeting will be 5 minutes).
+* Respecting everyone’s cultural/emotional background.
+* We will value each other’s diverse perspectives and create a safe, collaborative
+space.
+
+### Standardization
+
+* Follow the agreed upon coding standards and guidelines (e.g., naming conventions,
+indentations, comments).
+* Provide descriptive commit messages summarizing the changes.
+* Perform testing when applicable and document any test cases; ensure all tests pass
+before creating or merging a pull request.
+* Never push directly to the main branch; always create a pull request.
+
+### Team’s Learning
+
+* Group members must think about the whole team’s improvement and practice good
+leadership.
+* We will actively assist and support each other to overcome challenges and
+achieve success together.
+
+### Availability
+
+* Respond to queries or comments within 24-48 hours whenever possible.
+* Every member should answer questions of the member asked on Slack or
+WhatsApp if they have the answer and do not leave it for others.
+
+### Conflict resolution
+
+* Every member will have equal rights. If there is any conflict, it should be
+resolved within the group through voting.

collaboration/communication.md

@@ -14,16 +14,26 @@ ______________________________________________________________________
 ## Communication Schedule
 
 | Day | How | The topic of discussion | | --- | :-: | ----------------------- |
-| | | |
+| 21st Dec | Zoom | How to proceed with the group project? |
+| 25th Dec | Zoom | Progress and Discussions on Solutions |
+| 7th Jan | Zoom | Finalization |
+| 8th Jan | Zoom | Merging |
 
 ## Communication Channels
 
-how often will we get in touch on each channel, and what we will discuss there:
+We shall have weekly/bi-weekly meetings on slcka/zoom to discuss any issues and progress.
 
 - **Issues**:
+<https://github.com/MIT-Emerging-Talent/ET6-foundations-group-29/issues/3>
+<https://github.com/MIT-Emerging-Talent/ET6-foundations-group-29/issues/10>
+<https://github.com/MIT-Emerging-Talent/ET6-foundations-group-29/issues/2>
+
 - **Pull Requests**:
-- **Slack/Discord**:
-- **Video Calls**:
+<https://github.com/MIT-Emerging-Talent/ET6-foundations-group-29/pull/9>
+<https://github.com/MIT-Emerging-Talent/ET6-foundations-group-29/pull/8>
+<https://github.com/MIT-Emerging-Talent/ET6-foundations-group-29/pull/7>
+<https://github.com/MIT-Emerging-Talent/ET6-foundations-group-29/pull/5>
+<https://github.com/MIT-Emerging-Talent/ET6-foundations-group-29/pull/1>
 
 ______________________________________________________________________
 
@@ -33,15 +43,21 @@ ______________________________________________________________________
 
 | Day | Monday | Tuesday | Wednesday | Thursday | Friday | Saturday | Sunday | |
 ------ | :----: | :-----: | :-------: | :------: | :----: | :------: | :----: |
-| _name_ | | | | | | | |
+| Muqaddas | No | No | No | No | Yes | No | Yes |
+| Nilofar | No | Yes | No | No | Yes | No | Yes |
+| Shagun | No | No | No | No | Yes | No | Yes |
+| Anik | No | No | No | No | Yes | No | Yes |
+| Momtaz | No | No | No | No | Yes | No | Yes |
+| M. Ahmed | No | No | No | No | Yes | No | Yes |
 
 ### How many hours everyone has per day
 
-- name: _5h_;
-- name: _6h_;
-- name: _5h_;
-- name: _4h_;
-- name: _3h_;
+- Muqaddas: _1.5h_;
+- Shagun: _2h_;
+- Nilofar: _2h_;
+- Anik: _2h_;
+- M. Ahmed: _2h_;
+- Momtaz: _2h_;
 
 ## Asking for Help
 

collaboration/constraints.md

@@ -6,6 +6,8 @@ Some boundaries around our project.
 
 ## External
 
+The project must be completed by 8th Jan 2025.
+
 <!--
   constraints coming from the outside that your team has no control over:
   - project deadlines
@@ -17,6 +19,7 @@ Some boundaries around our project.
 
 ## Internal: Involuntary
 
+Team members have varying levels of experience with Python, requiring additional time for learning.
 <!--
   constraints that come from within your team, and you have no control over:
   - each of your individual skill levels
@@ -25,6 +28,9 @@ Some boundaries around our project.
 
 ## Internal: Voluntary
 
+Every pull request must pass a peer code review before merging.
+Agree to use GitHub for version control and task management.
+
 <!--
   constraints that your team decided on to help scope the project. they may include:
   - coding style & conventions

collaboration/learning_goals.md

@@ -2,4 +2,22 @@
 
 ## Collective
 
+The collective learning goals for a beginner group learning Python include
+understanding basic syntax, data types, and control structures, along
+with practicing functions, loops, and error handling. Learners
+will also explore data structures, file handling, and an
+introduction to object-oriented programming to build a solid foundation for coding.
+
 ## Individual
+
+Muqaddas: To learn new data science skills.
+
+Nilofar: To learn about github and how the coding collaboration works.
+
+Shagun: To learn how to effectively collaborate and documentation.
+
+Anik: To learn unit testing and predictive testing.
+
+Momtaz: Learning how to collaborate as a team, working on the same project together.
+
+M. Ahmed: To learn how to use GitHub as a team.

collaboration/retrospective.md

@@ -4,20 +4,63 @@
 
 ## Stop Doing
 
+Spending too much time trying to figure
+things out on my own without asking for help sooner.
+Overthinking small tasks instead of
+just starting and learning along the way.
+
 ## Continue Doing
 
+Working step by step and focusing on
+one part of the task at a time.
+Asking my teammates for advice and
+reviewing their work to learn from them.
+Using GitHub features like branches
+and pull requests to stay organized.
+
 ## Start Doing
 
+Practicing math and coding challenges
+more often so I can solve them faster in the future.
+Writing down notes about what I’m
+learning so I can remember it for next time.
+Paying more attention to small
+details in documentation and instructions.
+
 ## Lessons Learned
 
+I realized that working in a team
+helps a lot, especially when I don’t know something.
+GitHub tools like pull requests and
+labels are very useful once you understand how to use them.
+Breaking the project into small steps
+makes everything easier and less stressful.
+
 ______________________________________________________________________
 
 ## Strategy vs. Board
 
 ### What parts of your plan went as expected?
 
+I was able to clone the repository,
+create my branch, and push my code.
+Submitting a pull request and reviewing
+others’ work was smooth and worked as planned.
+
 ### What parts of your plan did not work out?
 
+Some of the math problems were harder than
+I expected, and I had to spend extra time on them.
+I didn’t fully understand the CI checks at
+first, so fixing errors took more time.
+
 ### Did you need to add things that weren't in your strategy?
 
+Yes, I had to look up tutorials on GitHub
+features like labeling pull requests and managing CI errors.
+
 ### Or remove extra steps?
+
+I simplified things by focusing only on the steps
+needed to complete the assignment and skipping
+any unnecessary experiments with GitHub.

solutions/SumList.py

@@ -0,0 +1,26 @@
+"""
+Author: @arvidon
+Created on: jan 7 2025.
+"""
+
+
+def SumList(numbers):
+    """
+    The SumList function takes a list of numbers as input and returns the sum of all the elements in the list.
+    It utilizes Python's built-in sum() function to calculate the sum of the numbers.
+
+    PARAMETERS:
+    numbers (List of int or float): A list containing numerical values (either integers or floating-point numbers)
+    that need to be summed up.
+
+    RETURN VALUES:
+    int or float: The sum of the values in the numbers list. The return type will depend on the types of numbers in the list.
+    """
+    # Return the sum of all numbers in the list
+    return sum(numbers)
+
+
+# Example usage
+numbers = [1, 2, 3, 4, 5]
+result = SumList(numbers)
+print(f"The sum of the list is: {result}")

solutions/add_numbers.py

@@ -0,0 +1,25 @@
+"""
+A module for adding two numbers
+
+Created on 11 1 2025
+@author: momtaz-yaqubi
+"""
+
+
+def add_numbers(a, b):
+    """
+    Adds two numbers together.
+
+    Parameters:
+        a (int, float): The first number to add.
+        b (int, float): The second number to add.
+
+    Returns:
+        int, float: The result of adding `a` and `b`.
+
+    Raises:
+        TypeError: If either `a` or `b` is not a number.
+    """
+    if not isinstance(a, (int, float)) or not isinstance(b, (int, float)):
+        raise TypeError("Both arguments must be numbers")
+    return a + b

solutions/arith_prog.py

@@ -0,0 +1,53 @@
+"""
+A module that that generates an arithmetic progression (AP).
+
+Module contents:
+  - generate_arithmetic_progression generates an arithmetic progression
+
+Created on 11/25/2024
+@author: Anik Kumar Adhikary
+"""
+
+
+def generate_arithmetic_progression(start, difference, terms):
+    """
+    It generates an arithmetic progression given a start value,
+    a difference, and the number of terms.
+
+    Parameters:
+    - start (int/float): The first term of the AP.
+    - difference (int/float): The common difference between terms.
+    - terms (int): The number of terms to generate.
+
+    Returns:
+    - list: A list containing the arithmetic progression
+
+    Example:
+    >>> generate_arithmetic_progression(2, 3, 5)
+    [2,5,8,11,14]
+
+    Explanation:
+    start = 2
+
+    difference = 3
+
+    terms = 5
+
+    The range generates the sequence 0, 1, 2, 3, 4.
+
+    For each value of i, we calculate start + i * difference:
+
+    For i = 0: 2 + 0 * 3 = 2
+    For i = 1: 2 + 1 * 3 = 5
+    For i = 2: 2 + 2 * 3 = 8
+    For i = 3: 2 + 3 * 3 = 11
+    For i = 4: 2 + 4 * 3 = 14
+
+    The result is [2, 5, 8, 11, 14], and this is returned by the function
+    """
+    # A concise way to create a list in Python
+    return [start + i * difference for i in range(terms)]
+
+
+# Expression: start + i * difference; gives the value of the nth term, starting from the first term
+# Iteration: for i in range(terms); generates a sequence of numbers from 0 to terms-1