Merge remote-tracking branch 'origin/master'
This commit is contained in:
commit
da1ca5536d
2
.obsidian/plugins/colored-tags/data.json
vendored
2
.obsidian/plugins/colored-tags/data.json
vendored
@ -1,7 +1,7 @@
|
||||
{
|
||||
"palette": {
|
||||
"seed": 0,
|
||||
"selected": "adaptive-soft",
|
||||
"selected": "custom",
|
||||
"custom": "EAFBD0-D989E1-E189C8-E189A8-E18989-E1A989-E1C989-D8E189-B8E189-98E189-89E19B-89E1BB-89E1DB-89C7E1-89A7E1-8C89E1-AC89E1-CC89E1"
|
||||
},
|
||||
"mixColors": true,
|
||||
|
||||
@ -5,55 +5,40 @@
|
||||
"color": "#ffffff",
|
||||
"heading": "Calendar Tasks"
|
||||
},
|
||||
{
|
||||
"type": "local",
|
||||
"color": "#e557c6",
|
||||
"directory": "900s Calendars/1. Other Work"
|
||||
},
|
||||
{
|
||||
"type": "local",
|
||||
"color": "#d93a3a",
|
||||
"directory": "900s Calendars/2. Research"
|
||||
},
|
||||
{
|
||||
"type": "local",
|
||||
"color": "#deff38",
|
||||
"directory": "900s Calendars/3. Events"
|
||||
},
|
||||
{
|
||||
"type": "local",
|
||||
"color": "#88c1dd",
|
||||
"directory": "300s School/ME 2016 - Nonlinear Dynamical Systems 1"
|
||||
},
|
||||
{
|
||||
"type": "local",
|
||||
"color": "#58fdc6",
|
||||
"directory": "300s School/NUCE 2100 - Fundamentals of Nuclear Engineering"
|
||||
},
|
||||
{
|
||||
"type": "local",
|
||||
"color": "#4e6ca6",
|
||||
"directory": "300s School/ME 2085 - Graduate Seminar"
|
||||
},
|
||||
{
|
||||
"type": "local",
|
||||
"color": "#ff841f",
|
||||
"directory": "900s Calendars/0. Deadlines"
|
||||
},
|
||||
{
|
||||
"type": "ical",
|
||||
"color": "#2b00ff",
|
||||
"color": "#89c4fb",
|
||||
"url": "https://outlook.office365.com/owa/calendar/40c8aa38153f4b1c81452964fc63cf83@pitt.edu/f450534d1f104a53b0b58f1d1953105416980344478428784892/calendar.ics"
|
||||
},
|
||||
{
|
||||
"type": "ical",
|
||||
"color": "#83ff7a",
|
||||
"color": "#e1dbe1",
|
||||
"url": "https://www.officeholidays.com/ics-fed/usa"
|
||||
},
|
||||
{
|
||||
"type": "local",
|
||||
"color": "#c2e660",
|
||||
"directory": "4 Qualifying Exam/2 Writing"
|
||||
"color": "#db5757",
|
||||
"directory": "900s Calendars/Research"
|
||||
},
|
||||
{
|
||||
"type": "local",
|
||||
"color": "#d28451",
|
||||
"directory": "900s Calendars/Learning"
|
||||
},
|
||||
{
|
||||
"type": "local",
|
||||
"color": "#abf85d",
|
||||
"directory": "900s Calendars/Service"
|
||||
},
|
||||
{
|
||||
"type": "local",
|
||||
"color": "#c787d9",
|
||||
"directory": "900s Calendars/Teaching"
|
||||
},
|
||||
{
|
||||
"type": "local",
|
||||
"color": "#b5b5b5",
|
||||
"directory": "900s Calendars/Personal"
|
||||
}
|
||||
],
|
||||
"defaultCalendar": 0,
|
||||
|
||||
@ -20,8 +20,9 @@ sort by function task.created.format("dddd")
|
||||
>not done
|
||||
>show urgency
|
||||
>filter by function task.urgency >12.999 && task.urgency<17.0
|
||||
>sort by urgency
|
||||
>group by tags
|
||||
>sort by urgency
|
||||
|
||||
> ```
|
||||
|
||||
>[!todo] **Medium Urgency Tasks**
|
||||
|
||||
@ -44,29 +44,6 @@
|
||||
- [[2025-02-24.md]]
|
||||
|
||||
## Summary
|
||||
This appears to be a collection of daily notes from an individual, each with a specific date range. The format is consistent across all dates, and the structure is easy to follow.
|
||||
|
||||
Here's a breakdown of the information I can gather from these notes:
|
||||
|
||||
1. **Date Range**: Each note has a start and end date range.
|
||||
2. **Tags**: Some notes include tags or keywords that provide additional context about the topic being discussed (e.g., "union", "retirement account", "bus").
|
||||
3. **Daily Tasks**: The notes list daily tasks, which can be broken down into:
|
||||
* Morning routines (e.g., shower and breakfast, gym)
|
||||
* Work or academic activities (e.g., studying for a paper, working on homework)
|
||||
* Meetings or appointments (e.g., ANS Paper)
|
||||
* Leisure activities (e.g., reading, lunch break)
|
||||
4. **Completed Tasks**: Some notes include completed tasks, which can be categorized as:
|
||||
* Finished projects or assignments
|
||||
* Meetings or appointments that have concluded
|
||||
5. **Notes and Reminders**: The notes often include brief comments, reminders, or observations about the day's events.
|
||||
6. **Weekly and Monthly Planning**: There are occasional mentions of planning for upcoming weeks or months (e.g., "union discord", "Docker desktop setup").
|
||||
|
||||
Overall, these daily notes provide a glimpse into an individual's daily life, work schedule, academic activities, and personal interests. They can be useful for:
|
||||
|
||||
* Research purposes (e.g., understanding daily habits, routines, or schedules)
|
||||
* Personal organization and goal-setting
|
||||
* Time management and prioritization
|
||||
|
||||
Please let me know if you'd like me to help with anything specific related to these notes!
|
||||
|
||||
Generated by llama3.2:latest
|
||||
|
||||
@ -9,7 +9,7 @@ tags:
|
||||
[[ Weekly Note 2025-02-10]]
|
||||
# Summary
|
||||
## What's the plan?
|
||||
- [<] Poke Antoine about NUCE classes available 🔼 ⏳ 2025-02-18 📅 2025-02-21
|
||||
- [<] Poke Antoine about NUCE classes available #Administrative 🔼 ⏳ 2025-02-18 📅 2025-02-21
|
||||
|
||||
## What's the results!
|
||||
```tasks
|
||||
|
||||
@ -11,6 +11,10 @@ tags:
|
||||
## What's the plan?
|
||||
- [<] TLA Learning Plan #TLA ⏫ ⏳ 2025-02-20 📅 2025-02-20
|
||||
- [ ] Do something with Robert's Email #Email 📅 2025-02-20 ⏳ 2025-02-20
|
||||
- [ ] Join union discord #Union ⏳ 2025-02-21 📅 2025-02-21
|
||||
- [ ] Invite Yiyang to signal chat #Union ⏳ 2025-02-21 📅 2025-02-21
|
||||
- [ ] Set up union github repo #Union ⏳ 2025-02-21 📅 2025-02-21
|
||||
|
||||
## What's the results!
|
||||
```tasks
|
||||
done 2025-02-20
|
||||
@ -20,8 +24,8 @@ group by tags
|
||||
|
||||
# Calendar Tasks
|
||||
- Drive Home [startTime:: 18:30] [endTime:: 19:00]
|
||||
- Drive back to school [startTime:: 15:45] [endTime:: 16:00]
|
||||
- Drive to School [startTime:: 10:00] [endTime:: 10:30]
|
||||
- Drive home [startTime:: 15:00] [endTime:: 15:15]
|
||||
- QSG SOTA [startTime:: 12:00] [endTime:: 13:00]
|
||||
- BORGER [startTime:: 15:00] [endTime:: 16:00]
|
||||
- Drive to School [startTime:: 12:40] [endTime:: 13:00]
|
||||
- Drive home [startTime:: 12:00] [endTime:: 12:15]
|
||||
- QSG SOTA [startTime:: 11:00] [endTime:: 12:00]
|
||||
- Gym Showah [startTime:: 20:30] [endTime:: 22:00]
|
||||
@ -9,6 +9,7 @@ tags:
|
||||
[[ Weekly Note 2025-02-17]]
|
||||
# Summary
|
||||
## What's the plan?
|
||||
- [ ] Chess Graduate Student Tournament Plan #GSA
|
||||
|
||||
## What's the results!
|
||||
```tasks
|
||||
@ -18,9 +19,3 @@ group by tags
|
||||
```
|
||||
|
||||
# Calendar Tasks
|
||||
- ME2046 HW3 [startTime:: 14:45] [endTime:: 16:00]
|
||||
- ME2046 HW3 [startTime:: 14:45] [endTime:: 16:00]
|
||||
- TLA Time [startTime:: 14:30] [endTime:: 15:30]
|
||||
- Read Papers [startTime:: 13:30] [endTime:: 14:30]
|
||||
- Reading Papers and Flex Time [startTime:: 12:00] [endTime:: 13:30]
|
||||
- QSG SOTA [startTime:: 08:00] [endTime:: 09:30]
|
||||
@ -0,0 +1,50 @@
|
||||
# Presentation Outline
|
||||
**I. Assertion**
|
||||
|
||||
* The State of the Art section is crucial in research as it defines the domain expertise,
|
||||
identifies the limits of current practice, and sets up the next section.
|
||||
|
||||
**II. Evidence 1: Definition of State of the Art**
|
||||
|
||||
* It's not just about listing existing work but also about understanding what others have
|
||||
done, what they didn't do well, and how your research can improve upon it.
|
||||
* (Source: "The State of the Art is the frenetic and relentless pursuit of doing what its
|
||||
best at that time!" - Da Anunciação Marco)
|
||||
|
||||
**III. Evidence 2: Importance of Clear Limitations**
|
||||
|
||||
* Clearly defining the limits of current practice is essential to identify what has been done
|
||||
well and what areas need improvement.
|
||||
* (Source: "Clearly you hope to improve on something with your research... It is best to
|
||||
clearly define the limits of current practice." - Unknown)
|
||||
|
||||
**IV. Evidence 3: Focus on Relevant Tools and Techniques**
|
||||
|
||||
* Focusing too much on individual researchers or their work can lead to confusion, while
|
||||
highlighting the technology or method itself as the main actor is more effective.
|
||||
* (Source: "Avoid focusing too much on individual researchers or their work; instead,
|
||||
highlight the technology or method itself as the main actor." - Unknown)
|
||||
|
||||
**V. Evidence 4: Clarity and Coherence**
|
||||
|
||||
* The writing should be clear, understandable, and concise, avoiding unnecessary details or
|
||||
jargon.
|
||||
* (Source: "The writing should be clear, understandable, and concise... avoid unnecessary
|
||||
details or jargon.")
|
||||
|
||||
**VI. Evidence 5: Importance of Storytelling**
|
||||
|
||||
* A coherent story or thread of ideas throughout the section is essential to effectively
|
||||
communicate the state of the art.
|
||||
* (Source: "Does the writer tell a coherent story? Can you follow thread of the story?" -
|
||||
Unknown)
|
||||
|
||||
**VII. Conclusion**
|
||||
|
||||
* The State of the Art section requires careful consideration and attention to detail to
|
||||
effectively communicate the current state of practice in research.
|
||||
|
||||
Note: The sources listed are from the original text, but may not be directly cited as
|
||||
evidence in a formal academic or professional setting.
|
||||
|
||||
|
||||
@ -0,0 +1,70 @@
|
||||
# Presentation Outline
|
||||
**Title:** Writing and Editing the Research Approach Section: Effective Strategies for PhD
|
||||
Proposals
|
||||
|
||||
**Slide 1: Introduction**
|
||||
|
||||
Welcome, everyone! In this section, we'll discuss the importance of writing and editing a
|
||||
clear and effective Research Approach section in your PhD proposal. This section is often one
|
||||
of the longest in a proposal, requiring careful consideration of methods, protocols,
|
||||
techniques, tools, and strategy.
|
||||
|
||||
**Slide 2: Purpose of the Research Approach Section**
|
||||
|
||||
The purpose of this section is to clearly describe:
|
||||
|
||||
* The methods and protocols used in the research
|
||||
* The techniques and tools employed
|
||||
* The strategy for moving from the limits identified in the previous section to the goals and
|
||||
objectives in the first section
|
||||
|
||||
**Slide 3: Key Principles**
|
||||
|
||||
When writing the Research Approach section, keep these key principles in mind:
|
||||
|
||||
* **Clearly explain what is new**: Make sure the reader understands what sets your research
|
||||
apart from existing work.
|
||||
* **Link limitations to objectives**: Show how your approach addresses the current state of
|
||||
practice and aligns with your desired outcomes.
|
||||
* **Use clear and concise language**: Avoid technical jargon and ensure that key concepts are
|
||||
explained in an accessible way.
|
||||
|
||||
**Slide 4: Strategies for Clarity**
|
||||
|
||||
To achieve clarity, consider the following strategies:
|
||||
|
||||
* **Use a logical structure**: Organize your approach into sections or subheadings to
|
||||
facilitate navigation.
|
||||
* **Focus on the most important information first**: Prioritize the most critical details and
|
||||
methods in the introduction or initial paragraphs.
|
||||
* **Use concise language and active voice**: Avoid unnecessary words and complex sentence
|
||||
structures.
|
||||
|
||||
**Slide 5: Editing and Review**
|
||||
|
||||
Editing is crucial in the Research Approach section. Consider the following tips:
|
||||
|
||||
* **Read your work aloud**: Ensure that the language is clear, concise, and easy to
|
||||
understand.
|
||||
* **Get feedback from peers or mentors**: Ask others to review your proposal and provide
|
||||
constructive feedback on clarity, coherence, and effectiveness.
|
||||
* **Use clear headings and labels**: Organize your approach with logical section headings and
|
||||
clearly labeled figures and tables.
|
||||
|
||||
**Slide 6: Critique and Rewrite**
|
||||
|
||||
When critiquing a Research Approach section, consider the following:
|
||||
|
||||
* **Read carefully**: Pay attention to language, structure, and clarity.
|
||||
* **Check for old information in the Topic position**: Ensure that new concepts are explained
|
||||
in the correct position.
|
||||
* **Identify stress-worthy information**: Determine what requires emphasis or explanation.
|
||||
|
||||
**Slide 7: Conclusion**
|
||||
|
||||
Writing and editing an effective Research Approach section takes time and effort. By applying
|
||||
these strategies, you can ensure that your proposal is clear, concise, and compelling.
|
||||
Remember to focus on clarity, coherence, and effectiveness, and don't hesitate to seek
|
||||
feedback from peers or mentors.
|
||||
|
||||
>
|
||||
@ -3,57 +3,14 @@
|
||||
## Files
|
||||
- [[2025-02-07 - Introduction.md]]
|
||||
- [[2025-02-14 - Goals and Outcomes.md]]
|
||||
- [[2025-02-21 - State of the Art.md]]
|
||||
- [[2025-02-28 - Research Approach.md]]
|
||||
- [[GO Presentation Outline.md]]
|
||||
- [[OLD Qualifier Support Group Plan.md]]
|
||||
- [[QSG Poster Notes.md]]
|
||||
- [[Qualifier Support Group Plan.md]]
|
||||
|
||||
## Summary
|
||||
Here's a rewritten version of the text in a more readable format:
|
||||
|
||||
**GSA Qualifier Support Group Plan**
|
||||
|
||||
**Session Dates and Deadlines:**
|
||||
|
||||
| Deadline | ME | MSE |
|
||||
| ------------ | ---- | ---- |
|
||||
| Abstract Due | 2/5 | 2/5 |
|
||||
| Approval | 2/12 | 2/12 |
|
||||
| Written Due | 4/9 | 3/26 |
|
||||
| Oral Due | 4/16 | 4/14 |
|
||||
|
||||
**Session Schedule:**
|
||||
|
||||
* **February 7th:** Introduction to Proposals
|
||||
+ Discuss what a proposal is and its purpose
|
||||
+ Introduce Zotero and LaTeX (optional)
|
||||
+ Talk about example proposals
|
||||
* **February 14th:** Goals and Outcomes/Hypothesis
|
||||
+ Discuss the importance of goals and outcomes in proposals
|
||||
+ Explore hypothesis-based approaches in proposals
|
||||
* **February 21st:** State of the Art
|
||||
+ Discuss the importance of conducting a literature review in proposals
|
||||
+ Provide guidelines for organizing and presenting research findings
|
||||
* **February 28th:** Research Approach
|
||||
+ Discuss how to develop a research approach in proposals
|
||||
+ Explore different research design approaches
|
||||
* **March 7th:** Spring Break - Catch Up (optional)
|
||||
+ Come if you want to chat about your proposal progress
|
||||
* **March 14th:** Metrics of Success, Risks and Contingencies
|
||||
+ Discuss how to evaluate the success of a project in proposals
|
||||
+ Explore risk management strategies for proposals
|
||||
* **March 21st:** Broader Impacts, and Organization / Peer Reviews
|
||||
+ Discuss the importance of broader impacts in proposals
|
||||
+ Provide guidelines for organizing proposal sections
|
||||
* **March 28th:** Presentations - What makes a successful presentation?
|
||||
+ Discuss how to prepare for presentations with peers
|
||||
+ Explore effective communication strategies
|
||||
|
||||
**Additional Deadlines:**
|
||||
|
||||
* April 4th: Presentation Peer Review
|
||||
* April 11th: Presentation Peer Review
|
||||
|
||||
Note: The dates and deadlines are subject to change, and it's recommended to check the GSA website for updates.
|
||||
|
||||
Generated by llama3.2:latest
|
||||
|
||||
@ -5,12 +5,6 @@
|
||||
- [[Untitled.md]]
|
||||
|
||||
## Summary
|
||||
Here is the description:
|
||||
|
||||
This folder contains a collection of notes and resources related to Assembly. It includes a canvas file, [[Assembly Canvas.canvas]], which may serve as an interactive template or framework for working on Assembly-related projects.
|
||||
|
||||
Additionally, there are two text-based files: `[[Untitled.md]]`, which appears to be an untitled note that can be expanded upon or modified as needed.
|
||||
|
||||
These files provide a foundation for exploring and learning about Assembly in various contexts.
|
||||
|
||||
Generated by llama3.2:latest
|
||||
|
||||
@ -1,7 +1,7 @@
|
||||
https://learnyouahaskell.github.io/chapters.html
|
||||
- [x] Chapter 1: Introduction #Haskell ⏳ 2025-02-18 📅 2025-02-12 ✅ 2025-02-19
|
||||
- [/] Chapter 2: Starting Out #Haskell ⏳ 2025-02-25 📅 2025-02-19
|
||||
- [ ] Chapter 3: Types and Typeclasses #Haskell 📅 2025-02-26 ⏳ 2025-03-04
|
||||
- [/] Chapter 2: Starting Out #Haskell ⏳ 2025-02-19 📅 2025-02-25
|
||||
- [ ] Chapter 3: Types and Typeclasses #Haskell ⏳ 2025-02-26 📅 2025-03-04
|
||||
- [ ] Chapter 4: Syntax in Functions #Haskell 📅 2025-03-05 ⏳ 2025-03-11
|
||||
- [ ] Chapter 5: Recursion #Haskell 📅 2025-03-12 ⏳ 2025-03-18
|
||||
- [ ] Chapter 6: Higher Order Functions #Haskell 📅 2025-03-19 ⏳ 2025-03-25
|
||||
|
||||
@ -1,6 +1,6 @@
|
||||
- [x] Chapter 1: Getting Started #Rust ⏳ 2025-02-17 📅 2025-02-11 ✅ 2025-02-17
|
||||
- [ ] Chapter 2: Programming a Guessing Game #Rust 📅 2025-02-18 ⏳ 2025-02-24
|
||||
- [ ] Chapter 3: Common Programming Concepts #Rust 📅 2025-02-25 ⏳ 2025-03-03
|
||||
- [ ] Chapter 2: Programming a Guessing Game #Rust ⏳ 2025-02-18 📅 2025-02-24
|
||||
- [ ] Chapter 3: Common Programming Concepts #Rust ⏳ 2025-02-25 📅 2025-03-03
|
||||
- [ ] Chapter 4: Understanding Ownership #Rust 📅 2025-03-04 ⏳ 2025-03-10
|
||||
- [ ] Chapter 5: Using Structs to Structure Related Data #Rust 📅 2025-03-11 ⏳ 2025-03-17
|
||||
- [ ] Chapter 6: Enums and Pattern Matching #Rust 📅 2025-03-18 ⏳ 2025-03-24
|
||||
|
||||
@ -7,13 +7,6 @@
|
||||
- [[What the hell is liveness?.md]]
|
||||
|
||||
## Summary
|
||||
Here's a concise description of what's inside the folder:
|
||||
|
||||
This folder contains documentation and resources for [[TLA]] (Temporal Logic of Actions), a formal specification language. The main files include:
|
||||
|
||||
* [[TLA Canvas.canvas]], likely a canvas file used to visualize [[TLA]] concepts
|
||||
* [[Untitled.md]], an untitled Markdown file containing notes on the benefits of using [[TLA]]
|
||||
* [[What is TLA?.md]], a Markdown file providing an introduction to [[TLA]], including its history, features, and usage
|
||||
* [[What the hell is liveness?.md]], a Markdown file exploring the concept of liveness in [[TLA]]
|
||||
|
||||
Generated by llama3.2:latest
|
||||
|
||||
@ -4,10 +4,6 @@
|
||||
- [[Untitled.md]]
|
||||
|
||||
## Summary
|
||||
This folder contains notes and a table of contents related to the idea of creating a thesis. The contents include:
|
||||
|
||||
* A list of files organized under [[5 Thesis/1 Ideas]], with the most notable being [[Untitled.md]]
|
||||
|
||||
Please note that there is only one file in this folder, but it is worth mentioning as part of the overall structure.
|
||||
|
||||
Generated by llama3.2:latest
|
||||
|
||||
@ -1,22 +0,0 @@
|
||||
# Table of Contents for 2. Research
|
||||
|
||||
## Files
|
||||
- [[2024-08-26 Fighting with the BeagleBone.md]]
|
||||
- [[2024-08-28 HAIS Journal Club.md]]
|
||||
- [[2024-09-10 Nuclear Engineering Steering Committee - Conf Room A UClub.md]]
|
||||
|
||||
## Summary
|
||||
Here's a concise description of the contents in the folder:
|
||||
|
||||
This folder contains notes and meeting schedules from various research-related events and meetings.
|
||||
|
||||
* **Meeting Notes**
|
||||
|
||||
* [[2024-08-26 Fighting with the BeagleBone]]: Notes on an experiment involving the BeagleBone board, including issues with virtual environments and connecting to a server.
|
||||
* [[2 pymodbus On the BeagleBone]]: Additional information on using pymodbus on the BeagleBone board for hardware-in-the-loop HIL (Hardware-In-The-Loop) experiments.
|
||||
* **Event Schedules**
|
||||
|
||||
* [[2024-08-28 HAIS Journal Club]]: A schedule for a journal club meeting, including start and end times, date, and location.
|
||||
* [[Nuclear Engineering Steering Committee - Conf Room A UClub]]: A schedule for a Nuclear Engineering Steering Committee meeting, including start and end times, date, and location.
|
||||
|
||||
Generated by llama3.2:latest
|
||||
@ -3,17 +3,13 @@
|
||||
## Subdirectories
|
||||
- [[0. Deadlines/0. Deadlines - README]]
|
||||
- [[1. Other Work/1. Other Work - README]]
|
||||
- [[2. Research/2. Research - README]]
|
||||
- [[3. Events/3. Events - README]]
|
||||
- [[Learning/Learning - README]]
|
||||
- [[Personal/Personal - README]]
|
||||
- [[Research/Research - README]]
|
||||
- [[Service/Service - README]]
|
||||
- [[Teaching/Teaching - README]]
|
||||
|
||||
## Summary
|
||||
# Contents of the [Calendar Notes] Folder
|
||||
|
||||
This folder contains notes related to calendars for the 900s. The contents include:
|
||||
|
||||
* Deadlines-related notes, including a [[0. Deadlines/0. Deadlines - README]] that outlines important dates and milestones
|
||||
* Work-related notes, including a [[1. Other Work/1. Other Work - README]] on ongoing projects and tasks
|
||||
* Research notes, including a [[2. Research/2. Research - README]] on studies and findings related to the 900s
|
||||
* Event-related notes, including a [[3. Events/3. Events - README]] that summarizes important events and milestones from the era
|
||||
|
||||
Generated by llama3.2:latest
|
||||
|
||||
@ -0,0 +1,8 @@
|
||||
---
|
||||
title: ME 2150 Microkit part 3 and 4
|
||||
allDay: false
|
||||
startTime: 13:30
|
||||
endTime: 14:30
|
||||
date: 2025-02-21
|
||||
completed: null
|
||||
---
|
||||
8
900s Calendars/Learning/Learning - README.md
Normal file
8
900s Calendars/Learning/Learning - README.md
Normal file
@ -0,0 +1,8 @@
|
||||
# Table of Contents for Learning
|
||||
|
||||
## Files
|
||||
- [[2025-02-21 ME 2150 Microkit part 3 and 4.md]]
|
||||
|
||||
## Summary
|
||||
|
||||
Generated by llama3.2:latest
|
||||
10
900s Calendars/Personal/(Every F) Drive Home.md
Normal file
10
900s Calendars/Personal/(Every F) Drive Home.md
Normal file
@ -0,0 +1,10 @@
|
||||
---
|
||||
title: Drive Home
|
||||
allDay: false
|
||||
startTime: 11:30
|
||||
endTime: 12:00
|
||||
type: recurring
|
||||
daysOfWeek: [F]
|
||||
startRecur: 2025-02-21
|
||||
endRecur: 2025-04-11
|
||||
---
|
||||
10
900s Calendars/Personal/(Every F,W,M) Drive In.md
Normal file
10
900s Calendars/Personal/(Every F,W,M) Drive In.md
Normal file
@ -0,0 +1,10 @@
|
||||
---
|
||||
title: Drive In
|
||||
allDay: false
|
||||
startTime: 07:30
|
||||
endTime: 08:00
|
||||
type: recurring
|
||||
daysOfWeek: [F,W,M]
|
||||
startRecur: 2025-02-21
|
||||
endRecur: 2025-04-18
|
||||
---
|
||||
10
900s Calendars/Personal/(Every F,W,M) Lunch.md
Normal file
10
900s Calendars/Personal/(Every F,W,M) Lunch.md
Normal file
@ -0,0 +1,10 @@
|
||||
---
|
||||
title: Lunch
|
||||
allDay: false
|
||||
startTime: 12:00
|
||||
endTime: 13:00
|
||||
type: recurring
|
||||
daysOfWeek: [F,W,M]
|
||||
startRecur: 2025-02-21
|
||||
endRecur: 2025-04-16
|
||||
---
|
||||
10
900s Calendars/Personal/(Every T) Bus In.md
Normal file
10
900s Calendars/Personal/(Every T) Bus In.md
Normal file
@ -0,0 +1,10 @@
|
||||
---
|
||||
title: Bus In
|
||||
allDay: false
|
||||
startTime: 12:00
|
||||
endTime: 12:45
|
||||
type: recurring
|
||||
daysOfWeek: [T]
|
||||
startRecur: 2025-02-25
|
||||
endRecur: 2025-04-22
|
||||
---
|
||||
10
900s Calendars/Personal/(Every T) Dinner.md
Normal file
10
900s Calendars/Personal/(Every T) Dinner.md
Normal file
@ -0,0 +1,10 @@
|
||||
---
|
||||
title: Dinner
|
||||
allDay: false
|
||||
startTime: 17:00
|
||||
endTime: 18:00
|
||||
type: recurring
|
||||
daysOfWeek: [T]
|
||||
startRecur: 2025-02-25
|
||||
endRecur: 2025-04-22
|
||||
---
|
||||
12
900s Calendars/Personal/Personal - README.md
Normal file
12
900s Calendars/Personal/Personal - README.md
Normal file
@ -0,0 +1,12 @@
|
||||
# Table of Contents for Personal
|
||||
|
||||
## Files
|
||||
- [[(Every F) Drive Home.md]]
|
||||
- [[(Every F,W,M) Drive In.md]]
|
||||
- [[(Every F,W,M) Lunch.md]]
|
||||
- [[(Every T) Bus In.md]]
|
||||
- [[(Every T) Dinner.md]]
|
||||
|
||||
## Summary
|
||||
|
||||
Generated by llama3.2:latest
|
||||
8
900s Calendars/Research/2025-02-21 LEAN.md
Normal file
8
900s Calendars/Research/2025-02-21 LEAN.md
Normal file
@ -0,0 +1,8 @@
|
||||
---
|
||||
title: LEAN
|
||||
allDay: false
|
||||
startTime: 16:00
|
||||
endTime: 17:00
|
||||
date: 2025-02-21
|
||||
completed: null
|
||||
---
|
||||
@ -0,0 +1,8 @@
|
||||
---
|
||||
title: TLA Learning Plan and Notes
|
||||
allDay: false
|
||||
startTime: 14:30
|
||||
endTime: 16:00
|
||||
date: 2025-02-21
|
||||
completed: null
|
||||
---
|
||||
12
900s Calendars/Research/Research - README.md
Normal file
12
900s Calendars/Research/Research - README.md
Normal file
@ -0,0 +1,12 @@
|
||||
# Table of Contents for Research
|
||||
|
||||
## Files
|
||||
- [[2024-08-26 Fighting with the BeagleBone.md]]
|
||||
- [[2024-08-28 HAIS Journal Club.md]]
|
||||
- [[2024-09-10 Nuclear Engineering Steering Committee - Conf Room A UClub.md]]
|
||||
- [[2025-02-21 LEAN.md]]
|
||||
- [[2025-02-21 TLA Learning Plan and Notes.md]]
|
||||
|
||||
## Summary
|
||||
|
||||
Generated by llama3.2:latest
|
||||
6
900s Calendars/Service/Service - README.md
Normal file
6
900s Calendars/Service/Service - README.md
Normal file
@ -0,0 +1,6 @@
|
||||
# Table of Contents for Service
|
||||
|
||||
## Summary
|
||||
|
||||
|
||||
Generated by llama3.2:latest
|
||||
8
900s Calendars/Teaching/2025-02-21 QSG SOTA PREP.md
Normal file
8
900s Calendars/Teaching/2025-02-21 QSG SOTA PREP.md
Normal file
@ -0,0 +1,8 @@
|
||||
---
|
||||
title: QSG SOTA PREP
|
||||
allDay: false
|
||||
startTime: 08:30
|
||||
endTime: 09:00
|
||||
date: 2025-02-21
|
||||
completed: null
|
||||
---
|
||||
9
900s Calendars/Teaching/Teaching - README.md
Normal file
9
900s Calendars/Teaching/Teaching - README.md
Normal file
@ -0,0 +1,9 @@
|
||||
# Table of Contents for Teaching
|
||||
|
||||
## Files
|
||||
- [[2025-02-21 QSG SOTA PREP.md]]
|
||||
|
||||
## Summary
|
||||
|
||||
|
||||
Generated by llama3.2:latest
|
||||
23
reddup.sh
23
reddup.sh
@ -114,7 +114,7 @@ if [ -f "$readme" ]; then
|
||||
fi
|
||||
|
||||
if [ $static_changed -eq 0 ]; then
|
||||
echo "[$count/$total] No change: $dir"
|
||||
#echo "[$count/$total] No change: $dir"
|
||||
rm "$tmp_static"
|
||||
continue
|
||||
fi
|
||||
@ -139,6 +139,7 @@ unset 'FIND_CONDITIONS[${#FIND_CONDITIONS[@]}-1]'
|
||||
|
||||
# Now use find with these conditions.
|
||||
# Pull in the content of all markdown files in this folder (excluding the generated README)
|
||||
|
||||
folder_md=$(find "$dir" -maxdepth 1 -type f \( "${FIND_CONDITIONS[@]}" \) ! -path "$readme" \
|
||||
-exec sh -c 'for file; do
|
||||
echo "=======$file========="
|
||||
@ -153,22 +154,22 @@ $(cat "$tmp_static")
|
||||
Item 2:
|
||||
$folder_md"
|
||||
|
||||
echo ""
|
||||
echo "Prompt:"
|
||||
echo "================="
|
||||
echo $prompt
|
||||
summary=$(ollama run llama3.2 "$prompt")
|
||||
echo ""
|
||||
echo "Summary:"
|
||||
echo "================="
|
||||
echo $summary
|
||||
#echo ""
|
||||
#echo "Prompt:"
|
||||
#echo "================="
|
||||
#echo $prompt
|
||||
#summary=$(/usr/local/bin/ollama run llama3.2 "$prompt")
|
||||
#echo ""
|
||||
#echo "Summary:"
|
||||
#echo "================="
|
||||
#echo $summary
|
||||
|
||||
|
||||
# Build the full new content: static portion + summary section.
|
||||
{
|
||||
cat "$tmp_static"
|
||||
echo "## Summary"
|
||||
echo "$summary"
|
||||
# echo "$summary"
|
||||
echo ""
|
||||
echo "Generated by llama3.2:latest"
|
||||
} > "$readme"
|
||||
|
||||
Loading…
x
Reference in New Issue
Block a user