MIT-Emerging-Talent · Kuhai9801 · Jun 2, 2025 · Jun 2, 2025 · Jun 2, 2025 · Jun 2, 2025
diff --git a/.github/workflows/ci-checks.yml b/.github/workflows/ci-checks.yml
@@ -18,6 +18,8 @@ jobs:
         files: .
         config_file: .markdownlint.yml
 
+
+
   py_formatting:
     runs-on: ubuntu-latest
     steps:

diff --git a/0_domain_study/README.md b/0_domain_study/README.md
@@ -1 +1,117 @@
 # Domain Research
+
+## Research Question Table
+
+### Research Question 1 (Alona)
+
+**Research Question:**  
+How are the frequency and size of wildfires in North America related  
+to health problems caused by air pollution?
+
+**Research Novelty:**  
+Not really new  
+<https://pmc.ncbi.nlm.nih.gov/articles/PMC3492003/>  
+<https://jamanetwork.com/journals/jamanetworkopen/fullarticle/2828029>
+
+**Expected Data Availability:**  
+Quite available
+
+**Problems:**  
+Although there is a lot of data, the topic is not really new and  
+doesn't seem very promising
+
+**Sources or Brief Explanation:**  
+Studies on PM2.5 in the US  
+<https://cwfis.cfs.nrcan.gc.ca/>  
+<https://www.canada.ca/en/health-canada/services/air-quality.html>  
+<https://ourworldindata.org/wildfires>
+
+---
+
+### Research Question 2 (Alona)
+
+**Research Question:**  
+How are income level and the source of antibiotic prescriptions  
+related in Ukraine?
+
+**Research Novelty:**  
+Seems to be quite new  
+<https://www.sciencedirect.com/science/article/abs/pii/S0196655316310896>  
+<https://academic.oup.com/jacamr/article/6/2/dlae041/7633112?login=false>
+
+**Expected Data Availability:**  
+We might get some data from government statistics or surveys,  
+but haven't checked yet
+
+**Problems:**  
+Prescription and purchase data may be incomplete or unofficial
+
+**Sources or Brief Explanation:**  
+WHO and UNICEF reports
+
+---
+
+### Research Question 3 (Alona)
+
+**Research Question:**  
+How does the intensity of shelling in residential areas of Ukraine  
+affect access to and quality of online education?
+
+**Research Novelty:**  
+Very high
+
+**Expected Data Availability:**  
+Damage data:  
+[ACLED report on Russian targeting in Ukraine](https://acleddata.com/2025/02/21/bombing-into-submission-russian-targeting-of-civilians-and-infrastructure-in-ukraine/)
+
+Education data: Kolibri, Coursera for Refugees, UNICEF
+
+**Problems:**  
+Educational data is tricky to get. We should ask some big platforms  
+and wait a long time. They don’t usually specify regions in Ukraine.
+
+**Sources or Brief Explanation:**  
+UNICEF and UN reports
+
+---
+
+### Research Question 4 (Alona)
+
+**Research Question:**  
+How does the availability of a well-developed public transportation  
+system influence processed food consumption in car-free households in Canada?
+
+**Research Novelty:**  
+High – haven’t found an exact match in literature
+
+**Expected Data Availability:**  
+Not sure
+
+**Problems:**  
+Very area-specific. Requires filtering by income level, car ownership,  
+and food type
+
+**Sources or Brief Explanation:**  
+_(Not specified)_
+
+---
+
+### Research Question 5 (Alona)
+
+**Research Question:**  
+How does non-prescription antibiotic use affect the spread of  
+antibiotic-resistant infections in Ukraine?
+
+**Research Novelty:**  
+Haven’t seen studies on this for Ukraine
+
+**Expected Data Availability:**  
+Some lab data from universities or public health sources.  
+Survey/pharmacy data limited
+
+**Problems:**  
+Black market access to antibiotics; unclear where we can  
+get microbiological data
+
+**Sources or Brief Explanation:**  
+WHO AMR reports
diff --git a/Exploring_Kittens.png b/Exploring_Kittens.png
diff --git a/README.md b/README.md
@@ -0,0 +1,36 @@
+# Collaboration
+
+## Group Norms Summary
+
+Just like the game it is based on (Exploding Kittens), Exploring Kittens
+is a fun-loving group of researchers who want to explore the world.
+Our goal is to help each other, learn from one another, and grow together
+as we explore the world of Computer and Data science.
+
+## Group Agreements (Intention-Based)
+
+- Open and respectful communication between members. Voices are not equally
+loud but they are equally important.
+- Consistent collaboration. We expect members to regularly participate and
+contribute to the group.
+We will however also be understanding if a member
+needs some time off due to personal or professional commitments.
+- Punctuality. We should expect to wait no more than 5 minutes for meetings
+to start and people to be present.
+- Curiosity. We all come from different backgrounds and places,
+the only bad questions we can ask are questions that have been answered.
+- Togetherness. Our group members are supportive of one another's needs, feelings
+or circumstances. No one in the group is alone.
+- Adaptibility. We are more focused on identifying solutions rather than
+complaining about the problems or pointing fingers. We will be quick to change
+our approach or methodology if need be.
+- Respect. We are all human, we are all equal. We intend to value everyone's
+time, commitments, and resources just like we value our own.
+- Humor. Jokes are encouraged, we will strive to keep the atmosphere light
+and refreshing so that meetings don't feel like a drag.
+- Communication. We don't expect members to reply in real time, but
+a response to messages or questions should have a reply in a day,
+no more than 2 if the member is busy.
+- Exploding Kittens. We will one day all play a game of Exploding Kittens
+together.
+![Alt text](Exploring_Kittens.png)
diff --git a/collaboration/README.md b/collaboration/README.md
diff --git a/collaboration/communication.md b/collaboration/communication.md
@@ -15,32 +15,37 @@
 
 | Day    | How | The topic of discussion |
 | :----: | :-: | ----------------------: |
-|        |     |                         |
+| June 2nd | Google Meet  | Respecting deadlines, collaboration |
 
 ## Communication Channels
 
 How often we will get in touch on each channel, and what we will discuss there:
 
-- **Issues**:
-- **Pull Requests**:
-- **Slack/Discord**:
-- **Video Calls**:
+- **Issues**: To be discussed
+- **Pull Requests**: Every day
+- **Slack/Discord**: Every day
+- **Video Calls**: Every 3 days
 
 ## Availability
 
 ### Availability for calling/messaging
 
-| Day     | Mon | Tue | Wed | Thu | Fri | Sat | Sun |
-|--------|:---:|:---:|:---:|:---:|:---:|:---:|:---:|
-| _name_ |     |     |     |     |     |     |     |
+| Day   | Mon   | Tue    | Wed    | Thu    | Fri   | Sat | Sun|
+|-------|:-----:|:------:|:------:|:------:|:-----:|:---:|:----:|
+| Alona |5–8 PM | 5–8 PM | 3–8 PM | 5–8 PM | 5–8 PM| No     |9–8 PM EST|
+| Asia  |5–10 PM| 5–10 PM| 5–10 PM| 5–10 PM| No    | 5–10 PM| 5–10 PM |
+| Vahab |10–14 *| 10–14 *| 10–14 *| 10–14 *| 10–14 *| Can't plan in advanced||
+| Zaid| 7 PM-11 AM EST|7 PM-10 AM EST|7 PM-8 AM EST|7 PM-8 AM EST|No|No|No|
+
+\* Subject to change depending on other commitments.  
+Currently based in **Canada (Edmonton Time Zone - MST/MDT)**.  
+In **June**, located in **Central European Time Zone (CET/CEST)**.
 
 ### How many hours everyone has per day
 
-- name: _5h_
-- name: _6h_
-- name: _5h_
-- name: _4h_
-- name: _3h_
+- Alona: _3h_
+- Vahab: _4h_ weekdays.
+- Zaid: _3h_
 
 ## Asking for Help
 

diff --git a/collaboration/constraints.md b/collaboration/constraints.md
@@ -15,6 +15,14 @@ Some boundaries around our project.
   - ...
 -->
 
+- *Deadlines Set by MIT-ET*  
+  The schedule and priorities of the project are largely influenced by
+  deadlines established by MIT-ET.
+
+- *Organizational Requirements*  
+  MIT-ET enforces specific tools, workflows, and approval processes that
+  the team must adhere to.
+
 ## Internal: Involuntary
 
 <!--
@@ -23,6 +31,23 @@ Some boundaries around our project.
   - amount of time available to work on the project
 -->
 
+- *Differences in Skill Levels*  
+  Team members have varying levels of experience in Python, programming, and
+  collaboration tools, requiring additional time for knowledge sharing and
+  onboarding.
+
+- *Limited Availability*  
+  Some members manage full-time jobs or family responsibilities,
+  reducing their availability for meetings, reviews, or coding sessions.
+
+- *Unexpected Disruptions*  
+  Personal issues or emergencies may occasionally hinder
+   participation or delay deliverables.
+
+- *Workload Imbalance*  
+  Uneven contribution may occur, with some members needing to take on
+  extra tasks due to others' limited availability.
+
 ## Internal: Voluntary
 
 <!--
@@ -32,3 +57,23 @@ Some boundaries around our project.
   - the number of hours you want to spend working
   - only using the colors black and white
 -->
+
+- *Agreed-Upon Coding Standards*  
+  The team has chosen to follow consistent coding conventions
+  to improve readability and maintainability.
+
+- *Standardized Git Workflow*  
+  A version control strategy recommended by MIT-ET has been
+  adopted to ensure consistency and traceability.
+
+- *Task Prioritization Approach*  
+  The group aligns on priorities, sets milestones, and commits
+  to internal deadlines.
+
+- *Commit Message Format*  
+  Members use a unified format for commit messages
+  to maintain clarity and track changes effectively.
+
+- *Mandatory Peer Code Reviews*  
+  All pull requests must be reviewed and approved by at least
+  one or two members before merging into the main branch.
diff --git a/collaboration/learning_goals.md b/collaboration/learning_goals.md
@@ -2,4 +2,40 @@
 
 ## Collective
 
+- Learn how to find, analyze, and critically assess academic
+research and other credible sources.
+- Use previously acquired statistical knowledge to
+ analyze data and build real models.
+- Learn to accurately define research problems and
+design appropriate methodologies to address them.
+
 ## Individual
+
+### Alona
+
+- Understand and learn the collaboration work process while
+ working on the group project in GitHub
+- Gain experience in reviewing others' work and
+ contributing to open-source projects confidently.
+- Improve collaboration skills by participating in group
+  projects, sharing ideas clearly, and communicating with the team.
+
+### Asia
+
+- I can improve my GitHub skills.
+- Managing my time to meet deadlines.
+- Gaining more knowledge and confidence dealing with different people.
+
+### Vahab
+
+- Understand how to use real-world data to define problems and uncover insights.
+- Practice building models that help explain or solve real-world issues.
+- Learn to use Jupiter Notebooks effectively for data exploration and modeling.
+- Gain confidence in documenting, sharing, and communicating data science work clearly.
+
+### Zaid
+
+- Refresh my GitHub and Python skills.
+- Learn something new.
+- Improve my teamwork abilities.
+- Gain experience working with vastly different time zones.