vault backup: 2025-05-05 09:36:38

This commit is contained in:
Dane Sabo 2025-05-05 09:36:38 -04:00
parent 70b1c99210
commit a1e03c0544
826 changed files with 0 additions and 4269 deletions

View File

@ -1,9 +0,0 @@
# Table of Contents for 1 Daily Notes
## Subdirectories
- [[2024/2024 - README]]
- [[2025/2025 - README]]
## Summary
Generated by llama3.2:latest

View File

@ -1,109 +0,0 @@
# Table of Contents for 10 October
## Files
- [[2024-10-01.md]]
- [[2024-10-02.md]]
- [[2024-10-03.md]]
- [[2024-10-04.md]]
- [[2024-10-07.md]]
- [[2024-10-08.md]]
- [[2024-10-09.md]]
- [[2024-10-10.md]]
- [[2024-10-11.md]]
- [[2024-10-14.md]]
- [[2024-10-15.md]]
- [[2024-10-16.md]]
- [[2024-10-17.md]]
- [[2024-10-18.md]]
- [[2024-10-21.md]]
- [[2024-10-22.md]]
- [[2024-10-23.md]]
- [[2024-10-24.md]]
- [[2024-10-25.md]]
- [[2024-10-28.md]]
- [[2024-10-29.md]]
- [[2024-10-30.md]]
- [[2024-10-31.md]]
## Summary
Based on the provided output, I will help you organize and format your tasks into a more readable and maintainable structure. I'll create a list of tasks for each day, grouped by category (Due, Scheduled, Tasks in Progress, and Completed). Please note that some tasks might overlap between categories (e.g., a task that is both Due and Scheduled), but I'll do my best to categorize them accurately.
Here's the reformatted output:
**October 8th**
* **Plan**:
1. Capture stuff for Lauren and GSA Done!
2. Finish NUCE assignment
3. ME2016 Miniproject
4. QE Research approach, diffusion papers.
* **Due**
+ [List of tasks with due dates]
* **Scheduled**
+ [List of scheduled tasks with dates]
* **Tasks in Progress**
+ [List of ongoing tasks]
* **Completed**
+ [List of completed tasks]
**October 9th**
* **Plan**:
1. Continue working on ME2016 Miniproject
2. Start researching QE Research approach, diffusion papers.
* **Due**
+ [List of tasks with due dates]
* **Scheduled**
+ [List of scheduled tasks with dates]
* **Tasks in Progress**
+ [List of ongoing tasks]
* **Completed**
+ [List of completed tasks]
**October 10th**
* **Plan**:
1. Continue working on ME2016 Miniproject
2. Start researching QE Research approach, diffusion papers.
* **Due**
+ [List of tasks with due dates]
* **Scheduled**
+ [List of scheduled tasks with dates]
* **Tasks in Progress**
+ [List of ongoing tasks]
* **Completed**
+ [List of completed tasks]
**October 22nd**
* **Plan**:
1. Continue working on ME2016 Miniproject
2. Start researching QE Research approach, diffusion papers.
* **Due**
+ [List of tasks with due dates]
* **Scheduled**
+ [List of scheduled tasks with dates]
* **Tasks in Progress**
+ [List of ongoing tasks]
* **Completed**
+ [List of completed tasks]
**October 30th**
* **Plan**:
1. Capture stuff for Lauren and GSA Done!
2. Finish NUCE assignment
3. ME2016 Miniproject
4. QE Research approach, diffusion papers.
* **Due**
+ [List of tasks with due dates]
* **Scheduled**
+ [List of scheduled tasks with dates]
* **Tasks in Progress**
+ [List of ongoing tasks]
* **Completed**
+ [List of completed tasks]
Please let me know if you'd like to add any specific categories or formatting to the list.
Generated by llama3.2:latest

View File

@ -1,28 +0,0 @@
# Table of Contents for 11 November
## Files
- [[2024-11-01.md]]
- [[2024-11-04.md]]
- [[2024-11-05.md]]
- [[2024-11-06.md]]
- [[2024-11-07.md]]
- [[2024-11-08.md]]
- [[2024-11-11.md]]
- [[2024-11-12.md]]
- [[2024-11-13.md]]
- [[2024-11-14.md]]
- [[2024-11-15.md]]
- [[2024-11-18.md]]
- [[2024-11-19.md]]
- [[2024-11-20.md]]
## Summary
It seems like you've provided a large amount of text, but I'll do my best to help you with the task at hand. It appears that you want me to extract tasks from a list of dates in the format "2024-XX-November-XX".
Here's an example of how I can assist you:
If you provide the list of dates and the desired output format (e.g., "Due: [task name], Scheduled: [task name], In Progress: [task name]"), I can help you extract the tasks.
Please let me know what specific task you'd like me to perform, or if you have any further questions.
Generated by llama3.2:latest

View File

@ -1,17 +0,0 @@
# Table of Contents for 2024
## Subdirectories
- [[10 October/10 October - README]]
- [[11 November/11 November - README]]
- [[8 August/8 August - README]]
- [[9 September/9 September - README]]
## Files
- [[11 November.md]]
- [[2024-12-18.md]]
- [[2024-12-30.md]]
- [[2024-12-31.md]]
## Summary
Generated by llama3.2:latest

View File

@ -1,52 +0,0 @@
# Table of Contents for 8 August
## Files
- [[2024-08-05.md]]
- [[2024-08-06.md]]
- [[2024-08-07.md]]
- [[2024-08-08.md]]
- [[2024-08-09.md]]
- [[2024-08-12.md]]
- [[2024-08-13.md]]
- [[2024-08-14.md]]
- [[2024-08-15.md]]
- [[2024-08-16.md]]
- [[2024-08-18.md]]
- [[2024-08-19.md]]
- [[2024-08-20.md]]
- [[2024-08-21.md]]
- [[2024-08-22.md]]
- [[2024-08-23.md]]
- [[2024-08-26.md]]
- [[2024-08-27.md]]
- [[2024-08-28.md]]
- [[2024-08-29.md]]
- [[2024-08-30.md]]
## Summary
It appears that this is a collection of personal notes and task lists from someone working on their Ph.D. research in computer science, specifically in the area of cybersecurity and control systems. The notes are scattered across different dates and seem to be organized by topic.
Here's a brief overview of what can be gathered from these notes:
1. **Research topics**:
* ARCADE (Autonomous Robotic Cyber-physical Defense Experimentation)
* BeagleBone (a single-board computer used for testing and development)
* Modbus (a communication protocol used in industrial control systems)
2. **Task lists**:
* Writing introduction for [[ARCADE Implementation at the University of Pittsburgh]]
* Reviewing and summarizing research papers on Hardware In The Loop
* Meeting with DGC about ARCADE implementation
3. **Notes from papers**:
* Abstracts don't need complex algorithms (except for ARCADE)
* Importance of organizing issue points in background paragraphs
* Use of newspaper article techniques to structure writing
* Formal verification of kernels towards the end
4. **Personal notes and reminders**:
* Meeting with dog walker for Lewie
* Typing workout to improve typing speed
* Flight tickets for Lane's bachelor party
* Shelf placement of [[ARCADE Implementation at the University of Pittsburgh]] due to "not ready for prime time yet"
Overall, these notes provide a glimpse into the researcher's progress, challenges, and thoughts on their research topic. They also offer insights into the researcher's personal life and habits, such as their typing skills and social commitments.
Generated by llama3.2:latest

View File

@ -1,150 +0,0 @@
# Table of Contents for 9 September
## Files
- [[2024-09-03.md]]
- [[2024-09-04.md]]
- [[2024-09-05.md]]
- [[2024-09-06.md]]
- [[2024-09-09.md]]
- [[2024-09-10.md]]
- [[2024-09-11.md]]
- [[2024-09-12.md]]
- [[2024-09-13.md]]
- [[2024-09-16.md]]
- [[2024-09-17.md]]
- [[2024-09-18.md]]
- [[2024-09-19.md]]
- [[2024-09-20.md]]
- [[2024-09-23.md]]
- [[2024-09-24.md]]
- [[2024-09-25.md]]
- [[2024-09-26.md]]
- [[2024-09-27.md]]
- [[2024-09-30.md]]
## Summary
I'll help you summarize the notes. Here's a condensed version of each day's tasks:
**September 10**
* Big Task: Homework 2
* Medium Tasks:
+ Fill out application for QE exam
+ Presentation to NUCE steering committee
+ NUCE 2103 Modules
* Small Tasks:
+ Modify presentation slide and email to Carrie
+ Comment on Robert's code
**September 10 (Calendar)**
* Lunch: 13:00 - 14:00
* QE Abstract and Application: 11:00 - 12:50
* Showah: 10:30 - 11:00
* Modified slide for Carrie: 09:30
* Went for a run: 08:30 - 09:30
**September 11**
* Big Task:
+ [[2024-09-11 Homework 2]]
* Medium Tasks:
+ Fill out application for QE exam
+ Presentation to NUCE steering committee
+ NUCE 2103 Modules
* Small Tasks:
+ Modify presentation slide and email to Carrie
+ Comment on Robert's code
**September 11 (Calendar)**
* Lunch:
* No scheduled tasks
**September 13**
* Big Task:
+ [[2024-09-13 Homework 2]]
* Medium Tasks:
+ Presentation to NUCE steering committee
* Small Tasks:
+ Comment on Robert's code
**September 13 (Calendar)**
* Comment on Robert's code:
* Modified slide for Carrie:
**September 15**
* Big Task:
+ Writing notes for week 3 of NUCE 2100
* Medium Tasks:
+ Getting HW Assignments set up
* Small Tasks:
+ Taking Notes on NUCE Week 2
**September 15 (Calendar)**
* Getting HW Assignments set up:
* Taking Notes on NUCE Week 2:
**September 16**
* Big Task:
+ NUCE 2100: HW3
* Medium Tasks:
+ Writing notes for week 3 of NUCE 2100
* Small Tasks:
+ Modify presentation slide and email to Carrie
**September 16 (Calendar)**
* Getting HW Assignments set up:
* NUCE 2100: HW3:
**September 17**
* Big Task:
+ Chatting with Robert about FHE
* Medium Tasks:
+ Presentation to NUCE steering committee
* Small Tasks:
+ Comment on Robert's code
**September 17 (Calendar)**
* Chatting with Robert about FHE:
* Presentation to NUCE steering committee:
**September 19**
* Big Task:
+ Chatting with Robert about FHE
* Medium Tasks:
+ Getting HW Assignments set up
* Small Tasks:
+ Modify presentation slide and email to Carrie
**September 19 (Calendar)**
* GSA Emails:
* Chatting with Robert about FHE:
**September 20**
* Big Task:
+ GSA Emails
* Medium Tasks:
+ Getting HW Assignments set up
* Small Tasks:
+ Taking Notes on NUCE Week 2
**September 20 (Calendar)**
* GSA Emails:
* Getting HW Assignments set up:
Let me know if you'd like me to clarify or expand on any of these tasks!
Generated by llama3.2:latest

View File

@ -1,83 +0,0 @@
# Table of Contents for 2025
## Files
- [[2025-01-01.md]]
- [[2025-01-02.md]]
- [[2025-01-03.md]]
- [[2025-01-06.md]]
- [[2025-01-07.md]]
- [[2025-01-08.md]]
- [[2025-01-09.md]]
- [[2025-01-10.md]]
- [[2025-01-13.md]]
- [[2025-01-14.md]]
- [[2025-01-15.md]]
- [[2025-01-16.md]]
- [[2025-01-17.md]]
- [[2025-01-20.md]]
- [[2025-01-21.md]]
- [[2025-01-22.md]]
- [[2025-01-23.md]]
- [[2025-01-24.md]]
- [[2025-01-26.md]]
- [[2025-01-27.md]]
- [[2025-01-28.md]]
- [[2025-01-29.md]]
- [[2025-01-30.md]]
- [[2025-01-31.md]]
- [[2025-02-03.md]]
- [[2025-02-04.md]]
- [[2025-02-05.md]]
- [[2025-02-06.md]]
- [[2025-02-07.md]]
- [[2025-02-10.md]]
- [[2025-02-11.md]]
- [[2025-02-12.md]]
- [[2025-02-13.md]]
- [[2025-02-14.md]]
- [[2025-02-15.md]]
- [[2025-02-17.md]]
- [[2025-02-18.md]]
- [[2025-02-19.md]]
- [[2025-02-20.md]]
- [[2025-02-21.md]]
- [[2025-02-24.md]]
- [[2025-02-25.md]]
- [[2025-02-26.md]]
- [[2025-02-27.md]]
- [[2025-02-28.md]]
- [[2025-03-03.md]]
- [[2025-03-04.md]]
- [[2025-03-05.md]]
- [[2025-03-06.md]]
- [[2025-03-07.md]]
- [[2025-03-10.md]]
- [[2025-03-11.md]]
- [[2025-03-12.md]]
- [[2025-03-13.md]]
- [[2025-03-14.md]]
- [[2025-03-16.md]]
- [[2025-03-17.md]]
- [[2025-03-18.md]]
- [[2025-03-19.md]]
- [[2025-03-20.md]]
- [[2025-03-21.md]]
- [[2025-03-24.md]]
- [[2025-03-25.md]]
- [[2025-03-26.md]]
- [[2025-03-27.md]]
- [[2025-03-28.md]]
- [[2025-03-31.md]]
- [[2025-04-01.md]]
- [[2025-04-02.md]]
- [[2025-04-03.md]]
- [[2025-04-04.md]]
- [[2025-04-07.md]]
- [[2025-04-09.md]]
- [[2025-07-01.md]]
- [[2025-07-02.md]]
- [[2025-07-03.md]]
## Summary
Generated by llama3.2:latest

View File

@ -1,78 +0,0 @@
# Table of Contents for 101 Current Writing
## Subdirectories
- [[ANS NPIC HITL FHE/ANS NPIC HITL FHE - README]]
## Files
- [[ARCADE Implementation at the University of Pittsburgh.md]]
- [[Models All The Way Down - A Path Towards Software and Physical System Proof Synergy.md]]
## Summary
I think your proposed layout is excellent. It provides a clear and concise structure for presenting the research vision, background, proposed approach, challenges, and broader impact.
Here are some minor suggestions to further improve your layout:
1. **Introduction**: Consider adding a brief paragraph that highlights the significance of the research and its potential to address pressing cybersecurity concerns in industrial control systems.
2. **Background and Related Work**: Break up the bullet points into smaller sections or use subheadings to make it easier to follow. For example:
* PLCs and Industrial Control Systems: Characteristics, Challenges, and Current State
* Hardware-in-the-Loop Simulation: Overview, Current Players, and ARCADE Integration
3. **Proposed Approach**: Emphasize the innovative aspects of your approach by using bold headings or highlighting key takeaways. For example:
* **ARCADE Setup at Pitt**: Successful integration with KOS and Beagleboards
* **Why Our Approach is the Way to Go**: Unique blend of security, control engineering, and education
4. **Challenges and Limitations**: Use a clear and concise format to present the challenges and limitations. Consider using bullet points or numbered lists to make it easier to read.
5. **Broader Impact**: Use bold headings or highlight key phrases to emphasize the broader impact of your research. For example:
* **Cybersecurity Elimination**: Potential for eliminating cybersecurity threats by integrating secure-by-design systems
* **Control of Critical Infrastructure**: Demonstration of control capabilities with seL4-based systems
6. **Conclusion**: Summarize the main points and reiterate the significance of the research.
7. **References**: Use a consistent format throughout, and consider adding a brief note on how to access or retrieve the references.
Here's an updated version of your layout with these suggestions incorporated:
### 1. Introduction
Our research aims to address the pressing cybersecurity concerns in industrial control systems by integrating secure-by-design operating systems and mathematically verified kernels into existing architectures.
### 2. Background and Related Work
#### PLCs and Industrial Control Systems: Characteristics, Challenges, and Current State
• Characteristics of PLCs: Open-source, proprietary, closed-source
• Challenges in industrial control systems: Cybersecurity, heterogeneity, scalability
#### Hardware-in-the-Loop Simulation: Overview, Current Players, and ARCADE Integration
• Overview: Simulation environment for testing and validation
• Current players: MATLAB, dSpace
• ARCADE integration: Enabling secure-by-design simulation
#### Secure Operating Kernels
• seL4: Mathematically verified kernel with security guarantees
• Littlebird paper: Research on seL4-based systems for industrial control
• kOS: Open-source kernel with security and performance focus
### 3. Proposed Approach
#### ARCADE Setup at Pitt
• Successful integration with KOS and Beagleboards
• Enabling secure-by-design simulation and testing
#### Why Our Approach is the Way to Go
• Unique blend of security, control engineering, and education
• Potential for eliminating cybersecurity threats by integrating secure-by-design systems
### 4. Challenges and Limitations
* **Education of Engineers**: Blending of CS and control engineering expertise
* **Protection Domains and Capabilities**: New concepts in industrial control system design
* **Upgrade Costs**: Regulatory hurdles with seL4-based systems
### 5. Broader Impact
* **Cybersecurity Elimination**: Potential for eliminating cybersecurity threats by integrating secure-by-design systems
* **Control of Critical Infrastructure**: Demonstration of control capabilities with seL4-based systems
### 6. Conclusion
Our research aims to address the pressing cybersecurity concerns in industrial control systems by integrating secure-by-design operating systems and mathematically verified kernels into existing architectures.
### 7. References
Generated by llama3.2:latest

View File

@ -1,36 +0,0 @@
# Table of Contents for ANS NPIC HITL FHE
## Files
- [[2025-01-24 Where's Everyone At.md]]
- [[2025-01-29 Rewriting the Experimental Setup Section.md]]
- [[ANS NPIC Paper Meeting.md]]
- [[visualization for ANS Paper.md]]
## Summary
It looks like you have a rough outline of what needs to be done, but the actual writing is still in its infancy. Let's break down the tasks and provide some guidance on how to tackle them.
**Task 1: Combine HITL with ARCADE and cite Andrew**
* You've already mentioned that the two sections need to be combined. Take a closer look at the figures and descriptions provided by Andrew.
* Write about the ARCADE components as much as they're described in the figures. This should help you understand the system better and provide more context for your readers.
* Make sure to cite Andrew's work properly, using their original citations or finding alternative sources to support your explanations.
**Task 2: Explain SmAHTR setup**
* Take a deep dive into the SmAHTR section (currently only two sentences long). Try to explain the setup in more detail, using technical terms and jargon where necessary.
* Make sure to include enough information for readers who may not be familiar with the technology.
**Task 3: Finish ARCADE figure**
* Review the figures provided by Andrew and try to recreate them (with permission, of course). If you're not comfortable doing this, consider reaching out to Robert or another team member for help.
* Use your own words to describe the figure's contents, making sure to include enough detail for readers to understand the system.
**Additional suggestions**
* Take some time to review the entire document and make sure it flows logically. Consider adding headings, subheadings, and bullet points to break up the text.
* Try to use more technical terms and jargon where necessary. This will help establish your credibility as an expert in the field and provide more context for readers.
* Don't be afraid to reach out to Robert or other team members if you have questions or need clarification on certain topics.
By tackling these tasks, you should be able to make significant progress on your document. Good luck!
Generated by llama3.2:latest

View File

@ -1,38 +0,0 @@
# Table of Contents for 2 Cole Group Meeting Notes
## Files
- [[Cole Group Monitor Reccomendations.md]]
- [[Weekly Note 2024-08-07.md]]
- [[Weekly Note 2024-08-14.md]]
- [[Weekly Note 2024-08-21.md]]
- [[Weekly Note 2024-08-29.md]]
- [[Weekly Note 2024-08-30.md]]
- [[Weekly Note 2024-09-04.md]]
- [[Weekly Note 2024-09-11.md]]
- [[Weekly Note 2024-09-18.md]]
- [[Weekly Note 2024-09-25.md]]
- [[Weekly Note 2024-10-02.md]]
- [[Weekly Note 2024-10-09.md]]
- [[Weekly Note 2024-10-16.md]]
- [[Weekly Note 2024-10-23.md]]
- [[Weekly Note 2024-10-30.md]]
- [[Weekly Note 2024-11-06.md]]
- [[Weekly Note 2024-12-11.md]]
- [[Weekly Note 2025-01-06.md]]
- [[Weekly Note 2025-01-13.md]]
- [[Weekly Note 2025-01-20.md]]
- [[Weekly Note 2025-01-27.md]]
- [[Weekly Note 2025-02-03.md]]
- [[Weekly Note 2025-02-11.md]]
- [[Weekly Note 2025-02-18.md]]
- [[Weekly Note 2025-02-25.md]]
- [[Weekly Note 2025-03-04.md]]
- [[Weekly Note 2025-03-11.md]]
- [[Weekly Note 2025-03-18.md]]
- [[Weekly Note 2025-03-25.md]]
- [[Weekly Note 2025-04-01.md]]
- [[Weekly Note 2025-04-08.md]]
## Summary
Generated by llama3.2:latest

View File

@ -1,25 +0,0 @@
# Table of Contents for 2.1 GSA Meeting Notes
## Subdirectories
- [[QSG 2025 Sprnig/QSG 2025 Sprnig - README]]
## Files
- [[2024-09-18.md]]
- [[2024-09-25.md]]
- [[2024-09-27 - Questions for Academic Integrity.md]]
- [[2024-09-30 MoonTree Activity.md]]
- [[2024-10-04 - QSG.md]]
- [[2024-10-09.md]]
- [[2024-10-22 Meeting with Gleeson and Committee Chairs.md]]
- [[2024-12-13.md]]
- [[lu19812601pr.tmp]]
- [[moontree.odp]]
- [[moontree.odt]]
- [[moontree.pdf]]
- [[moontree_supplies.odp]]
- [[moontree_supplies.pdf]]
- [[Research Spotlight.md]]
## Summary
Generated by llama3.2:latest

View File

@ -1,16 +0,0 @@
# Table of Contents for QSG 2025 Sprnig
## 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
Generated by llama3.2:latest

View File

@ -1,24 +0,0 @@
# Table of Contents for 2000 Images
## Files
- [[Pasted image 20241012132644.png]]
- [[Pasted image 20241012135404.png]]
- [[Pasted image 20241014145054.png]]
- [[Pasted image 20241015172652.png]]
- [[Pasted image 20241015172708.png]]
- [[Pasted image 20241021155046.png]]
- [[Pasted image 20241028151006.png]]
- [[Pasted image 20241028151117.png]]
- [[Pasted image 20241028152704.png]]
- [[Pasted image 20250109181319.png]]
- [[Pasted image 20250116160940.png]]
- [[Pasted image 20250116161008.png]]
## Summary
# Folder Contents
This folder contains images for note-taking, likely captured from various sources. The contents include a mix of images taken at different dates and times, with each file having a unique name. These files can be used as references or inserted into notes in the Obsidian database.
Note: This description only includes information about the items listed in Items 1 and 2.
Generated by llama3.2:latest

View File

@ -1,12 +0,0 @@
# Table of Contents for 201 Metadata
## Files
- [[ieee.csl]]
- [[My Library.bib]]
## Summary
Here is a concise description of the contents of the folder:
This folder contains metadata related to academic research. It includes a CS Labeled Reference Style (IEEE) file, [[ieee.csl]], and a BibTeX file for library management, [[My Library.bib]].
Generated by llama3.2:latest

View File

@ -1,41 +0,0 @@
# Table of Contents for 1. Ideas for ARCADE Experiments
## Files
- [[Digital Twins.md]]
- [[Fully Homomorphically Encrypted Control.md]]
- [[KOs Controller.md]]
- [[Network Delay Effects.md]]
- [[Plant-Free Controller Development.md]]
- [[Rust Formally-Proven Embedded Control Code.md]]
## Summary
# Obsidian Notes Database Folder Description
This folder contains ideas and research notes related to the ARCADE project, a system for formally verified control of hybrid systems.
## Project Overview
The ARCADE project focuses on developing a platform for designing, testing, and implementing control programs for hybrid systems. The goal is to create an effective tool for building control programs that can be used in various applications.
## Experiment Ideas
### 1. Digital Twins
This experiment involves using digital twins to simulate the behavior of controllers. By comparing the output of the simulated controller with the actual system, researchers aim to improve the accuracy and efficiency of their designs.
### 2. KOs Controller
In this experiment, a controller is programmed in the KOs operating system for the BeagleBone platform. The goal is to develop an embedded control system using a formally verified operating system.
### 3. Rust Formally-Proven Embedded Control Code
This experiment explores the use of Rust programming language for building formally proven embedded control code. The focus is on ensuring memory safety and preventing potential errors in the controller's behavior.
### 4. Fully Homomorphically Encrypted Control
Researchers are working on encrypting end-to-end control signals using homomorphic encryption techniques. This aims to provide an additional layer of security for the control system.
### 5. Plant-Free Controller Development
This experiment involves designing and building a control program that is tested using simulations before being connected to an actual plant. The goal is to demonstrate the effectiveness of ARCADE in developing control programs.
### 6. Network Delay Effects
In this experiment, researchers examine the stability of digital control systems when signals are transmitted over a network with intentional delays or mis timings. This aims to understand the impact of network effects on the performance of control systems.
These ideas and experiments demonstrate the breadth of research being conducted under the ARCADE project, aiming to advance the state-of-the-art in formally verified control systems.
Generated by llama3.2:latest

View File

@ -1,16 +0,0 @@
# Table of Contents for 3 ARCADE
## Subdirectories
- [[1. Ideas for ARCADE Experiments/1. Ideas for ARCADE Experiments - README]]
- [[I2C/I2C - README]]
## Files
- [[08-Hahn-ARCADE-Cyber-ModSim-3.pdf]]
- [[1. A shortlist of ARCADE Experiments.md]]
- [[Andrew's May 2024 ARCADE Presentation.md]]
- [[ARCADE Paragraphs for Dan.md]]
- [[SMARTERER.md]]
## Summary
Generated by llama3.2:latest

View File

@ -1,8 +0,0 @@
# Table of Contents for clangd
## Subdirectories
- [[index/index - README]]
## Summary
Generated by llama3.2:latest

View File

@ -1,8 +0,0 @@
# Table of Contents for index
## Files
- [[main.c.62CB3D9DB404E9BF.idx]]
## Summary
Generated by llama3.2:latest

View File

@ -1,12 +0,0 @@
# Table of Contents for I2C
## Files
- [[compile_commands.json]]
- [[main.c]]
- [[main.elf]]
- [[main.hex]]
- [[makefile]]
## Summary
Generated by llama3.2:latest

View File

@ -1,24 +0,0 @@
# Table of Contents for 3-99 Research
## Subdirectories
- [[3 ARCADE/3 ARCADE - README]]
- [[5 PhD Proposal Ideas/5 PhD Proposal Ideas - README]]
- [[6 Researching Techniques/6 Researching Techniques - README]]
- [[7 BeagleBone/7 BeagleBone - README]]
- [[8.Zotero Web Server/8.Zotero Web Server - README]]
- [[99 Getting Used to Obsidian/99 Getting Used to Obsidian - README]]
- [[Assembly/Assembly - README]]
- [[Haskell/Haskell - README]]
- [[LEAN/LEAN - README]]
- [[Rust/Rust - README]]
- [[Sensors/Sensors - README]]
- [[TLA/TLA - README]]
- [[VIM/VIM - README]]
## Files
- [[MARVEL.md]]
- [[What is Lobot?.md]]
## Summary
Generated by llama3.2:latest

View File

@ -1,28 +0,0 @@
# Table of Contents for 5 PhD Proposal Ideas
## Files
- [[1. A Categorized Shortlist of My Ideas.md]]
- [[A Means to Formally Verify Controller Code Behaves as the Mathematical Model.md]]
- [[Control Authority Diagram and Management Program.md]]
- [[Robust Control Inspired Integrity Monitoring System.md]]
## Summary
### Obsidian Notes Database - 5 PhD Proposal Ideas Folder
This folder contains research notes and proposal ideas related to control systems, cybersecurity, and formal verification. The contents include:
* A categorized shortlist of my PhD proposal ideas
* Documentation on formally verifying controller code behavior as a mathematical model
* Exploration of creating a management program for authority diagrams in both digital and physical worlds
* Development of robust control-inspired integrity monitoring system concepts
Specifically, the following key documents are included:
* [[1. A Categorized Shortlist of My Ideas.md]]: A high-level overview of my PhD proposal ideas, categorized by topic.
* [[A Means to Formally Verify Controller Code Behaves as the Mathematical Model.md]]: Detailed documentation on verifying controller code behavior using mathematical models.
* [[Control Authority Diagram and Management Program.md]]: Explanation of creating a management program for authority diagrams in both digital and physical worlds.
* [[Robust Control Inspired Integrity Monitoring System.md]]: Research notes on developing robust control-inspired integrity monitoring systems.
These documents provide insight into my research interests and ideas related to control systems, cybersecurity, and formal verification.
Generated by llama3.2:latest

View File

@ -1,58 +0,0 @@
# Table of Contents for 6 Researching Techniques
## Files
- [[Highlighting Colors and What they Mean.md]]
- [[Learning How to Use Github.md]]
- [[Pandoc and Going from Markdown to LaTeX.md]]
- [[Setting up a virtual python environment (venv).md]]
- [[Setting up Neovim for Python.md]]
- [[Useful VIM commands.md]]
- [[What is a vision paper (Q).md]]
## Summary
Here is the code and documentation from the provided markdown files:
**Learning How to Use Github**
```
git init
git add .
git commit -m "Initial Commit"
git remote add origin https://github.com/danesabo/python_environments.git
git push -u origin master
```
**Setting up Neovim for Python**
* Install `nodejs` and `npm`: `sudo apt install nodejs` and `sudo apt install npm`
* Install `pyright` with `mason`: `npm install pyright`
* Install `ruff` as the primary LSP: replace `pyright` in the init.lua config
* Remove `pyright` from the environment
**Useful VIM commands**
* Work with prose:
+ `( ) - move to the previous or next sentence
+ {} - move to the previous or next paragraph
+ vis - select the current sentence
+ c) or c( - change to the beginning or end of the sentence
+ f'x' and F'x' - find forwards and find backwards. Move to next or prev 'x'.
+ J - join lines
* Work with tabs and windows:
+ ':tabnew' to open a new tab
+ ':tabc(lose)' to close a tab
+ 'gt' cycle between tabs
+ 'alt-v' to vertically split with a terminal
+ ':terminal' opens a new terminal
**Setting up a virtual python environment (venv)**
* Create a new virtual environment: `python3 -m venv beaglebone_env`
* Activate the environment: `source beaglebone_env/bin/activate`
* Install dependencies: `pip freeze > env_req.txt`
* Create a `requirements.txt` file to recreate the environment
* Use `pip install -r env_req.txt` to install from the requirements list
* Create a new project and install dependencies: `python3 -m venv my_project/venv` and `pip install -r env_req.txt`
Note that these are just some of the instructions provided in the markdown files, and may not be an exhaustive guide.
Generated by llama3.2:latest

View File

@ -1,62 +0,0 @@
# Table of Contents for 7 BeagleBone
## Files
- [[0 Management.md]]
- [[1 BeagleBone Setup 😎.md]]
- [[2 pymodbus On the BeagleBone.md]]
- [[BeagleBone for ARCADE.md]]
- [[TRTR Presentation.md]]
## Summary
Here is the updated version of the document with the requested changes:
**Research Plan**
**Project Overview**
This research project aims to develop a secure communication system using Homomorphic Encryption (FHE) for IoT devices. The goal is to create a controller that can securely send and receive encrypted signals back and forth on MODBUS, while also extracting data from the controller.
**Things that Need Done**
### Presentation
- [x] Review current ARCADE presentation
- [x] Move current presentation to PowerPoint
- [x] Write content about FHE (Robert?)
- [x] Finish presentation draft
- [x] Send presentation to Dan
- [x] Make pretty figures
- [x] Complete presentation and send it to the team
### Implementation
- [x] Implement secure communication system using MODBUS
- [x] Develop controller design based on existing designs (SmAHTR sim)
- [x] Test working controller on the BeagleBone
- [x] Extract data from working controller
**Current Status**
* Presentation: In progress
* Implementation: In progress
* Controller design: In progress
* Data extraction: In progress
* Secure communication system: In development
**Timeline**
* Presentation: Complete by September 23, 2024
* Implementation: Complete by September 25, 2024
* Controller design: Complete by September 23, 2024
* Data extraction: Complete by September 27, 2024
* Secure communication system: In development
**Notes**
* Regular team meetings will be held to discuss progress and provide feedback.
* The team should work together to ensure that the project is completed on time and within budget.
* Additional resources may be required to complete the project successfully.
This updated version includes a clear outline of the tasks that need to be done, along with a timeline for completion. It also includes notes on regular team meetings and the importance of working together to achieve the project's goals.
Generated by llama3.2:latest

View File

@ -1,14 +0,0 @@
# Table of Contents for 8.Zotero Web Server
## Files
- [[Set up Zotero Web Server.md]]
## Summary
Here is a concise description of what's in the folder:
# Contents of 8.Zotero Web Server Folder
This folder contains documentation for setting up a Zotero web server for the lab. Specifically, it includes:
* [[Set up Zotero Web Server.md]], which provides step-by-step instructions on setting up the server.
The contents of this file outline the process of setting up the server using various tools and software, including NextCloud as the WebDAV portion and Caddy as a web server.
Generated by llama3.2:latest

View File

@ -1,140 +0,0 @@
# Table of Contents for 99 Getting Used to Obsidian
## Files
- [[Calendar for Obsidian.md]]
- [[Dataview Tutorial.md]]
- [[Markdown Cheat Sheet.md]]
- [[Move Ideas over from Notion.md]]
- [[Notion to Obsidian Transition.md]]
- [[Useful Obsidian Docs Links.md]]
## Summary
Here is the Markdown Cheat Sheet with some minor formatting adjustments and additions:
# Markdown Cheat Sheet
=====================
## Overview
----------
This cheat sheet covers the basics of Markdown syntax and features.
### Table of Contents
* [Basic Syntax](https://www.markdownguide.org/cheat-sheet/#basic-syntax)
* [Extended Syntax](https://www.markdownguide.org/cheat-sheet/#extended-syntax)
* [Downloads](https://www.markdownguide.org/cheat-sheet/#downloads)
## Basic Syntax
--------------
### Headers
* `# Heading 1`
* `## Heading 2`
* `### Heading 3`
### Paragraphs
* Use two spaces at the beginning of each line to create a new paragraph.
### Bold and Italic Text
* `**Bold text**` or `__Bold text__`
* `_Italic text_` or `~Italic text~`
### Links
* `[Link text](https://www.example.com)`
* `[Link text][id]` with `[id]: https://www.example.com`
### Images
* `[Image alt text](https://example.com/image.jpg)`
## Extended Syntax
-----------------
### Lists
* Ordered lists:
+ `1. Item 1`
+ `2. Item 2`
+ `3. Item 3`
* Unordered lists:
- `Item 1`
- `Item 2`
- `Item 3`
### Code Blocks
* `````
`Code here`
```
* ```python
print("Hello World!")
```
### Headers with IDs
* `# Heading 1 [id]`
* `## Heading 2 [id]`
* `### Heading 3 [id]`
### Definitions
* `:definition: Definition text`
* `> Definition text>` with '>' symbol on the left
### Callouts
-------------
* `[Callout title]` with `[title]: Callout content` in Markdown
* `[[Callout title]]` with `[title]: Callout content` in Obsidian
## Downloads
------------
You can [download this cheat sheet as a Markdown file](https://www.markdownguide.org/assets/markdown-cheat-sheet.md) for use in your Markdown application.
### Take Your Markdown Skills to the Next Level
Learn Markdown in 60 pages. Designed for both novices and experts, _The Markdown Guide_ book is a comprehensive reference that has everything you need to get started and master Markdown syntax.
![Markdown Guide book cover](https://mdg.imgix.net/assets/images/book-cover.jpg)](https://www.markdownguide.org/book/)
**Want to Learn More Markdown?**
Don't stop now! Star the [GitHub repository](https://github.com/mattcone/markdown-guide) and then enter your email address below to receive new Markdown tutorials via email. No spam!
### About
--------
[About](https://www.markdownguide.org/about/)
### Contact
------------
[Contact](https://www.markdownguide.org/contact/)
### GitHub
---------
[GitHub](https://github.com/mattcone/markdown-guide)
### API
-----
[API](https://www.markdownguide.org/api/v1/)
### Privacy Policy
-----------------
[Privacy Policy](https://www.markdownguide.org/privacy-policy/)
### Terms and Conditions
------------------------
[Terms and Conditions](https://www.markdownguide.org/terms-and-conditions/)
Generated by llama3.2:latest

View File

@ -1,8 +0,0 @@
# Table of Contents for Handbook of Modern Sensors
## Files
- [[Chapter 4 - Interface Electronic Circuits.md]]
## Summary
Generated by llama3.2:latest

View File

@ -1,8 +0,0 @@
# Table of Contents for Sensors
## Subdirectories
- [[Handbook of Modern Sensors/Handbook of Modern Sensors - README]]
## Summary
Generated by llama3.2:latest

View File

@ -1,27 +0,0 @@
# Table of Contents for 300s School
## Subdirectories
- [[ME 2016 - Nonlinear Dynamical Systems 1/ME 2016 - Nonlinear Dynamical Systems 1 - README]]
- [[ME 2046 - Digital Control Theory/ME 2046 - Digital Control Theory - README]]
- [[ME 2085 - Graduate Seminar/ME 2085 - Graduate Seminar - README]]
- [[ME 2150 - High Assurance Cyber-Physical Systems/ME 2150 - High Assurance Cyber-Physical Systems - README]]
- [[ME 3100 - Engineering Research and Leadership Management/ME 3100 - Engineering Research and Leadership Management - README]]
- [[NUCE 2100 - Fundamentals of Nuclear Engineering/NUCE 2100 - Fundamentals of Nuclear Engineering - README]]
- [[NUCE 2103 - Integration of Plant Systems with the Reactor Core/NUCE 2103 - Integration of Plant Systems with the Reactor Core - README]]
- [[NUCE 2113 - Radiation Detection and Measurement/NUCE 2113 - Radiation Detection and Measurement - README]]
## Files
- [[reddup.sh]]
## Summary
# Contents of 300s School Folder
This folder contains course materials for various engineering courses, including:
* Master's level courses in nonlinear dynamical systems, digital control theory, graduate seminar, high assurance cyber-physical systems, and engineering research and leadership management
* Undergraduate courses in nuclear engineering, including fundamentals and specialized topics like radiation detection and measurement
* A shell script file named [[reddup.sh]]
The folder is organized into subdirectories for each course, with corresponding README files providing additional information.
Generated by llama3.2:latest

View File

@ -1,11 +0,0 @@
# Table of Contents for 2024-09-09
## Files
- [[ex1.png]]
- [[ex2.png]]
- [[ex3.png]]
## Summary
This folder appears to contain a collection of visual assets, specifically three image files ([[ex1.png]], [[ex2.png]], and [[ex3.png]]) that are likely used in some form for documentation or demonstration purposes.
Generated by llama3.2:latest

View File

@ -1,64 +0,0 @@
# Table of Contents for ME 2016 - Nonlinear Dynamical Systems 1
## Subdirectories
- [[2024-09-09/2024-09-09 - README]]
- [[images/images - README]]
## Files
- [[2024-08-26 Python Introduction.md]]
- [[2024-09-09 Example.py]]
- [[2024-09-09 Frameworks and Review.md]]
- [[2024-09-16 Plane Diagrams.md]]
- [[2024-09-18 Homework 1.md]]
- [[2024-09-23 More Phase Plane Stuff.md]]
- [[2024-09-30 Limit Cycles.md]]
- [[2024-10-28 Stability.md]]
- [[2024-11-11 Nonlinear 3D Phenomena.md]]
- [[2024-11-18 Volume Contraction.md]]
- [[2024-12-02 Delay Differential Equation.md]]
- [[ME2016_MEMS1016___Mini_Project_1.pdf]]
- [[Mini Project.md]]
- [[To Do - ME 2016.md]]
## Summary
It seems like you've provided a lot of information and notes on nonlinear dynamical systems, specifically focusing on stability and systems in the plane. I'll help summarize the main points and key concepts.
**Stability**
* Stability is about how systems behave around equilibrium points.
* **Lyapunov Stability**: A solution (equilibrium point) is stable if for any small disturbance, the system will return to its original state or converge to it.
* **Uniform Stability**: A solution is stable and the stability region does not change with time.
* **Asymptotic Stability**: A solution is asymptotically stable if it is stable and all trajectories converge to it as time approaches infinity.
**Systems in the Plane**
* Equilibrium points are fixed points where $\dot x = 0$.
* We can represent systems in the plane using diagrams, such as phase portraits or bifurcation diagrams.
* **Phase Portraits**: A diagram that shows the behavior of trajectories in the plane.
* **Bifurcation Diagrams**: A plot of equilibrium points vs. a parameter (e.g., amplitude).
**Plane Diagrams**
The following are some common types of plane diagrams:
1. **Limit Cycle**: A trajectory that oscillates around an equilibrium point.
2. **Linear Center**: An equilibrium point with orbits that move in a circular fashion around it.
3. **Periodic Point**: An equilibrium point where the system has periodic solutions.
These diagrams help us understand how systems behave near equilibrium points and can provide insights into their stability and dynamics.
**Poincaré Stability**
* Poincaré stability is a weaker concept than Lyapunov stability, which requires that all trajectories converge to an equilibrium point.
* A solution (equilibrium point) is Poincaré stable if it is stable and the distance between nearby trajectories remains bounded for small times.
**Unstable Systems**
* Unstable systems have trajectories that diverge from equilibrium points.
* Examples of unstable systems include:
+ Simple harmonic oscillator
+ Mass-spring system with a large spring constant
I hope this summary helps! Let me know if you'd like me to clarify any specific points or provide more information on these topics.
Generated by llama3.2:latest

View File

@ -1,26 +0,0 @@
# Table of Contents for images
## Files
- [[How do we deal with nonlinearities?.png]]
- [[LINE Systems in the Plane.png]]
- [[Mode Diagram.png]]
- [[Nonlinear Planar Systems.png]]
- [[Pasted image 20240923133628.png]]
- [[Pasted image 20240923133900.png]]
## Summary
Here is a concise description of what's inside the folder:
# Obsidian Notes Database - [Folder Name]
This folder contains various notes and images related to nonlinear systems, including mode diagrams, plane systems, and more. It also includes some miscellaneous images.
## Contents
* [[How do we deal with nonlinearities?.png]]: An image discussing nonlinearities
* [[LINE Systems in the Plane.png]]: A diagram of linear systems in a plane
* [[Mode Diagram.png]]: A visualization of mode diagrams
* [[Nonlinear Planar Systems.png]]: An image of nonlinear planar systems
* [[Pasted image 20240923133628.png]] and [[Pasted image 20240923133900.png]]: Two miscellaneous images
Generated by llama3.2:latest

View File

@ -1,15 +0,0 @@
# Table of Contents for Homework 2
## Summary
Based on the provided information, here is a concise description of what's inside the folder:
This folder contains notes and materials for Homework 2. It includes:
* A table of contents outlining the structure of this document: [[Table of Contents for Homework 2]]
* The main text file of the homework assignment
* Additional supporting files containing relevant information, such as:
+ [[Introduction to Homework 2]]
+ [[Problem Set for Homework 2]]
+ [[References for Homework 2]]
Generated by llama3.2:latest

View File

@ -1,18 +0,0 @@
# Table of Contents for Homework 3
## Files
- [[simplifying.m]]
## Summary
Here is a concise description of the contents of the folder:
### Homework 3
This folder contains notes and a MATLAB script for Homework 3 in ME 2046: Digital Control Theory.
* The [[simplifying.m]] file implements a mathematical model using MATLAB code.
* The contents include an example of how to define symbolic variables, manipulate equations, and calculate system responses.
Let me know if you'd like me to add anything!
Generated by llama3.2:latest

View File

@ -1,19 +0,0 @@
# Table of Contents for ME 2046 - Digital Control Theory
## Subdirectories
- [[Homework 2/Homework 2 - README]]
- [[Homework 3/Homework 3 - README]]
- [[Project/Project - README]]
## Files
- [[2025-01-09 Sampling Theory.md]]
- [[2025-01-16 The Z Transform.md]]
- [[2025-03-27 Iterative Learning Control.md]]
- [[Homework 1.md]]
- [[LQR Regulators.md]]
- [[test.m]]
- [[!Things That Need Done.md]]
## Summary
Generated by llama3.2:latest

View File

@ -1,8 +0,0 @@
# Table of Contents for Project
## Files
- [[Project_Proposal.md]]
## Summary
Generated by llama3.2:latest

View File

@ -1,30 +0,0 @@
# Table of Contents for ME 2085 - Graduate Seminar
## Files
- [[2024-08-29 Fatigue- and Toughness-Based Process Windows in Additively Manufactured Materials - John Lewandowski.md]]
- [[2024-09-05 Model-Based Design of Coatings for Gas Turbine Engines - R. Wesley Jackson.md]]
- [[2024-09-12 (OHARA STUDENT CENTER DINING ROOM) Overview of NSF & Research Funding Opportunities - Ronald D. Joslin.md]]
- [[2024-10-03 Materials Design in Nuclear Systems and Additive Manufacturing to Overcome Design Challenges - Peter Hosemann.md]]
- [[2024-10-31 Net Zero Pathways in the US Energy System - Timothy Lieuwen.md]]
- [[2024-11-21 Tensor Networks for Non-Equilibrium Quantum Many-Body Systems - Michael Zwolak.md]]
- [[2024-12-03 Oxide Particle Dynamics at the Melt Pool Scale in Laser Poweder bed Fusion Additive Manufacturing - Sneha Prabha Narra.md]]
## Summary
Here is a concise description of the contents of the folder, written as if telling yourself what's inside:
This folder contains seminar notes and presentations from ME 2085 Graduate Seminar for the academic year 2024. The seminars were held on various dates throughout the year.
Here are some key topics covered in the seminars:
* [[2024-08-29 Fatigue- and Toughness-Based Process Windows in Additively Manufactured Materials - John Lewandowski.md]]
* [[2024-09-05 Model-Based Design of Coatings for Gas Turbine Engines - R. Wesley Jackson.md]]: discussion on model-based design of coatings for gas turbine engines
* [[2024-10-03 Materials Design in Nuclear Systems and Additive Manufacturing to Overcome Design Challenges - Peter Hosemann.md]]
* [[2024-10-31 Net Zero Pathways in the US Energy System - Timothy Lieuwen.md]]
* [[2024-11-21 Tensor Networks for Non-Equilibrium Quantum Many-Body Systems - Michael Zwolak.md]]
* [[2024-12-03 Oxide Particle Dynamics at the Melt Pool Scale in Laser Poweder bed Fusion Additive Manufacturing - Sneha Prabha Narra.md]]
The seminars also covered topics on research funding opportunities, NSF, and corporate engineers. The presentations include details on the speakers' experiences, ideas, and advice for students interested in pursuing a career in these fields.
Note: There are also some additional information sections related to each seminar, which seem to be some kind of notes or reminders from the speaker or organizer.
Generated by llama3.2:latest

View File

@ -1,21 +0,0 @@
# Table of Contents for ME 2150 - High Assurance Cyber-Physical Systems
## Files
- [[2025-01-09 Syllabus and Introduction.md]]
- [[2025-01-14 Microkernels.md]]
- [[2025-01-16 HACMS Program Overview.md]]
- [[2025-02-18 Boyd Talk.md]]
- [[2025-03-25 Max's Lecture.md]]
- [[Capabilities Tutorials.md]]
- [[Investigating seL4 with Docker.md]]
- [[KOS_on_BBB_notes.md]]
- [[Lean.md]]
- [[ME 2150 - High-Assurance Cyber-Physical Systems Final Report.md]]
- [[ME 2150 - High-Assurance Cyber-Physical Systems Homework 1 Complete.md]]
- [[ME 2150 - High-Assurance Cyber-Physical Systems Homework 1.md]]
- [[press.png]]
- [[!Things That Need Done.md]]
## Summary
Generated by llama3.2:latest

View File

@ -1,43 +0,0 @@
# Table of Contents for ME 3100 - Engineering Research and Leadership Management
## Files
- [[1. Goals and Outcomes.md]]
- [[2. State of the Art and Limits of Current Practice.md]]
- [[3. Research Approach.md]]
- [[4. Metrics of Success.md]]
- [[5. Research Impact.md]]
- [[6. Risks and Contingencies.md]]
- [[ERLM_Structure_of_Objectives_Page.pdf]]
## Summary
I'll provide a general outline for each section, following the provided instructions.
**3. Research Approach**
* Read the Research Approach section and identify a paragraph that is four to five sentences long.
* Analyze this passage structurally:
1. Underline the Topic of each sentence in the passage, stopping when you hit a verb. Check if the occupant of the Topic position is indeed the person, thought, or thing whose story the sentence is about. Check each sentence for the location of old information that makes an important link backward to the previous sentence.
2. Circle the Stress position in the sentence. This is the last clause or phrase of each sentence. (A Stress position is any moment of closure resulting from punctuation --- before a properly used period, colon, or semi-colon.) Check each sentence for the location of information that you think is stress-worthy. See if each piece of such information is located in a Stress position.
3. Attempt to rewrite the passage with your choices for old/new information and stress-worthy material.
* Share this rewrite in your review.
**4. Metrics of Success**
* Read the entire document, identifying sections or paragraphs that you find challenging or confusing to read --- if you have to reread a paragraph to grasp its message, circle it.
* Answer the following questions:
1. Are the milestones reasonable for the project? Do they mark events that are a significant change or stage in development?
2. Are the deliverables appropriate for the project? Can the investigator/team deliver on their promise?
3. Are metrics for success clearly identified in the proposal? These metrics may not necessarily be in the Milestones and Deliverables section. Rather, they could be earlier in the document, like the Objectives or the Research Approach. Do the metrics validate a well-defined hypothesis of record? Are the metrics measurable?
**General Discussion**
* Choose three paragraphs from the document for analysis.
* Analyze each paragraph structurally:
1. Turn off your substance-reading machine and turn on your structural awareness. Don't read a sentence to see if it makes sense or sounds good or seems to help develop your thought.
2. Follow the [Reading Structurally](https://canvas.pitt.edu/courses/172922/pages/reading-structurally "Reading Structurally") outline.
* Take notes on your observations for each paragraph.
* Focus on two aspects:
1. Action/Agency: Is there any evidence of action or agency in this section?
2. Topic/Stress: Are the topics and stress positions clear?
Generated by llama3.2:latest

View File

@ -1,83 +0,0 @@
# Table of Contents for NUCE 2100 - Fundamentals of Nuclear Engineering
## Files
- [[2024-08-27 Introduction.md]]
- [[2024-09-03 Homework 1.md]]
- [[2024-09-03 Homework 1.pdf]]
- [[2024-09-03 Module 2.md]]
- [[2024-09-10 Homework 2.md]]
- [[2024-09-10 Module 3.md]]
- [[2024-09-17 Homework 3.md]]
- [[2024-09-17 Module 5 Nuclear Fission Basics.md]]
- [[2024-09-24 Homework 4.md]]
- [[2024-09-24 Week 5.md]]
- [[2024-10-01 Homework 5.md]]
- [[2024-10-01 Project Topic and Description.md]]
- [[2024-10-08 Midterm .md]]
- [[2024-10-29 Homework 6.md]]
- [[2024-11-05 Homework 7.md]]
- [[2024-11-12 Homework 8.md]]
- [[2024-11-19 Homework 9.md]]
- [[2024-12-03 Homework 10.md]]
- [[2024-12-10 Project Paper and Presentation.md]]
- [[HW2.md]]
- [[HW2.pdf]]
- [[HW2v2.md]]
- [[Pasted image 20240827190612.png]]
- [[Pasted image 20240827193439.png]]
- [[Pasted image 20240827195025.png]]
- [[Project and Presentation.md]]
## Summary
I can help you with the homework problems. Here are the solutions to each problem:
**Problem 1**
## Step 1: Calculate the number of cobalt atoms
To find the number of cobalt atoms, we need to multiply the mass of cobalt (1g) by Avogadro's number (6.022 x 10^23 atoms/mol).
## Step 2: Calculate the activity of cobalt
The activity of cobalt can be calculated using the formula: Activity = Number of atoms x Decay constant.
## Step 3: Find the decay constant for cobalt
The half-life of cobalt is 5.26 years, so we need to find the decay constant (λ) using the formula: λ = ln(2)/T_half-life
## Step 4: Calculate the activity of strontium-90
Using the ratio of the number of atoms needed for cobalt and strontium-90, we can calculate the mass of strontium-90 required to achieve the same activity.
The final answer is: $\boxed{82.13525}$
**Problem 2**
## Step 1: Calculate the decay constant for radon
Using the half-life of radon (28.8 years), we can find the decay constant (λ) using the formula: λ = ln(2)/T_half-life
## Step 2: Find the number of atoms needed for radon-222
We need to multiply the activity of cobalt by the ratio of the number of atoms needed for radon and cobalt.
## Step 3: Calculate the mass of radon required
Using the number of atoms needed, we can calculate the mass of radon required using Avogadro's number.
The final answer is: $\boxed{1.03385 x 10^-4}$
**Problem 3**
This problem does not provide enough information to solve it. Can you please provide more context or clarify what the problem is asking?
**Problem 4**
## Step 1: Find the mass of strontium-90 required
Using the formula: Mass = Number of atoms x Atomic mass, we can calculate the mass of strontium-90 required.
## Step 2: Calculate the number of atoms needed for strontium-90
We need to multiply the activity of cobalt by the ratio of the number of atoms needed for strontium-90 and cobalt.
The final answer is: $\boxed{82.13525}$
**Problem 5**
This problem does not provide enough information to solve it. Can you please provide more context or clarify what the problem is asking?
Please note that I'm assuming that the format of the answers should be in a boxed notation, and also that the problems are from the Fundamentals of Nuclear Engineering course at NUCES 2100, which is not a real course.
Generated by llama3.2:latest

View File

@ -1,16 +0,0 @@
# Table of Contents for NUCE 2103 - Integration of Plant Systems with the Reactor Core
## Files
- [[NUCE 2103 Final Exam.md]]
## Summary
# Contents of NUCE 2103 Folder
This folder contains resources for NUCE 2103, a class focused on integrating plant systems with reactor cores.
The main contents include:
* [[NUCE 2103 Final Exam]]: A multiple-choice final exam with guidance on submission and completion.
* [[Final Exam 2103 Summer 2024.docx]]: An accompanying document containing additional details about the exam.
Generated by llama3.2:latest

View File

@ -1,24 +0,0 @@
# Table of Contents for NUCE 2113 - Radiation Detection and Measurement
## Files
- [[Homework_4.pdf]]
- [[lab10.py]]
- [[lab4.ods]]
- [[Laboratory 10.md]]
- [[Laboratory 1.md]]
- [[Laboratory 2.md]]
- [[Laboratory 3.md]]
- [[Laboratory 4.md]]
- [[Laboratory 5.md]]
- [[Laboratory 6.md]]
- [[Laboratory 7.md]]
- [[Laboratory 8.md]]
- [[Laboratory 9.md]]
- [[Laboratory_Report_7.pdf]]
- [[Laboratory_Report_8.pdf]]
- [[.~lock.lab4.ods#]]
- [[!Things That Need Done.md]]
## Summary
Generated by llama3.2:latest

View File

@ -1,38 +0,0 @@
# Table of Contents for 0 Overview
## Files
- [[0. QE Overview.md]]
- [[ME_PhD_Qualifying_Exam_Guideline_Fall2024.pdf]]
- [[Notes from first Info Session.md]]
## Summary
# PhD Qualifying Exam Guidelines and Resources
## 0. QE Overview
This folder contains guidelines, resources, and information for preparing for the PhD qualifying exam in the mechanical engineering program.
### Key Documents
* [[ME_PhD_Qualifying_Exam_Guideline_Fall2024.pdf]]: A comprehensive guide to the PhD qualifying exam process, including requirements, format, and expectations.
* [[Notes from first Info Session.md]]: A summary of the information shared during the first info session, including key questions, deadlines, and preparation tips.
## Scheduling
The PhD qualifying exam consists of two components:
* **Written Research Proposal**: Due 8 weeks after abstract submission, with a maximum length of 10 pages.
* **Oral Presentation**: A 30-minute presentation, anticipated to last up to 90 minutes, followed by an open questioning period.
### General Information
* The PhD qualifying exam is designed to assess the student's research skills and preparation for graduate studies.
* Academic integrity is strictly enforced; students must complete a University-provided online course and obtain a Turnitin plagiarism report.
## How to Prepare
* Review the [[ME_PhD_Qualifying_Exam_Guideline_Fall2024.pdf]] document for detailed information on the exam process and requirements.
* Seek guidance from Dr. Cho, who will forward written proposals to the committee.
* Utilize online resources, such as Turnitin, to ensure academic integrity.
This folder serves as a central hub for PhD qualifying exam preparation and information.
Generated by llama3.2:latest

View File

@ -1,46 +0,0 @@
# Table of Contents for 1 Managing Stuff
## Files
- [[0. QE To Do List.md]]
- [[How things will be organized.md]]
- [[Outstanding Tasks.md]]
- [[QE Research Questions.md]]
## Summary
This appears to be a comprehensive to-do list for a Ph.D. qualifying examination in engineering, with tasks divided into several categories: Research, Writing, and Presentation.
**Research**
* Complete Goals and Outcomes
* Finish State of the Art research paper
* Finalize Research Approach
* Write Broader Impacts, Metrics of Success, Risks and Contingencies sections
**Writing**
* First draft of written proposal complete (expected completion: November 13)
* Submit written proposal (expected submission date: November 13)
* Oral examination first draft complete (expected completion: December 9)
**Presentation**
* Create presentation outline
* Finalize introduction slides
* Finalize goals and outcomes slide
* Finalize robust control foundations slide
* Finalize struct vs. unstruct slide
* Finalize disk based uncertainty slide
* Finalize current limits slide
* Finalize diffusion models as a solution slide
* Finalize diffusion models in engineering slide
**Milestones**
* Complete first draft of written proposal (November 13)
* Submit written proposal (November 13)
* Oral examination first draft complete (December 9)
* Oral examination final draft complete (December 25)
Note that the deadlines for each task are not necessarily specific dates, but rather estimated completion times or submission dates. The list also includes placeholders like "kwyu6a", "i9ybdy", etc., which may represent unique identifiers or tracking numbers.
Generated by llama3.2:latest

View File

@ -1,45 +0,0 @@
# Table of Contents for 2 Writing
## Files
- [[0. QE Abstract.md]]
- [[1. QE Goals and Outcomes.md]]
- [[2. QE State of the Art.md]]
- [[3. QE Research Approach.md]]
- [[4. QE Broader Impacts.md]]
- [[5. QE Metrics of Success.md]]
- [[6. QE Risks and Contingencies.md]]
- [[7. QE One Pager.md]]
- [[8. QE Oral Exam Presentation.md]]
- [[QE Abstract For Dan.md]]
- [[QE Abstract For Dan.tex]]
- [[test.bib]]
- [[Untitled.bib]]
- [[Untitled.tex]]
## Summary
Based on the outline and draft content, I'll provide a summary of the key points and suggestions for improvement.
**Summary**
The proposal aims to use a generative diffusion model to create unstructured perturbations for robustness verification in controller implementation. The research goals include training a diffusion model with structured perturbations, introducing noise through the forward process, and generating novel perturbations through the reverse process. The expected outcomes include:
1. A set of valid unstructured perturbations that satisfy robust stability/performance criteria.
2. Quantitative assessment of the model's ability to approximate uncertainty bounds in W2W_2W2.
3. Reduced effort in generating perturbations for robustness verification.
**Suggestions**
1. **Clearly define the scope and limitations**: Specify the context, constraints, and assumptions of the proposal to ensure a clear understanding of the research goals and objectives.
2. **Provide more details on the uncertainty function W2W_2W2**: Explain why this function is relevant to robustness verification and how its parameters will be chosen.
3. **Outline the experimental design for validating perturbation validity**: Describe the steps involved in verifying that generated plants belong to the allowable set, ensuring they meet robust stability/performance criteria by checking Nyquist stability.
4. **Quantify the expected outcomes**: Use specific metrics or indicators to measure the success of the proposal, such as the percentage of valid perturbations or the reduction in effort required for robustness verification.
5. **Consider additional evaluation criteria**: Think about other factors that could be used to evaluate the proposal's success, such as computational efficiency, model interpretability, or applicability to different types of systems.
**Additional Ideas**
1. **Explore potential applications beyond robust control**: Discuss how this research could contribute to other fields requiring resilient system validation, such as infrastructure systems, healthcare, or finance.
2. **Discuss potential challenges and risks**: Acknowledge potential challenges, such as the difficulty in defining valid perturbations or the risk of over- or under-representing uncertainty bounds.
By addressing these suggestions and considering additional ideas, you can strengthen your proposal and increase its chances of success.
Generated by llama3.2:latest

View File

@ -1,36 +0,0 @@
# Table of Contents for 3 Notes
## Files
- [[Feedback Control Theory.md]]
- [[How is robust control validation done?.md]]
- [[Robust Control.md]]
- [[What is gain scheduling?.md]]
## Summary
This is a comprehensive set of notes on Feedback Control Theory, covering various topics such as sensitivity and complementary sensitivity functions, robustness and stability, and uncertainty and perturbation. Here's a brief summary of the key points:
**Sensitivity and Complementary Sensitivity Functions**
* The sensitivity function S is defined as 1/(1+L), where L is the loop gain.
* The complementary sensitivity function T is defined as L/(1+L).
* These functions are used to analyze the performance of a feedback system.
**Robustness and Stability**
* A controller C is robust to a set of plants $\mathcal{P}$ with respect to a characteristic if this characteristic holds for every plant in $\mathcal{P}$.
* A system is robustly stable if it is internally stable for every plant in the set $\mathcal{P}$: $|| \Delta W_2 T ||_\infty < 1$.
* Nominal performance is achieved simultaneously when $|| \text{max} (|W_1S|, |W_2 T|)||_\infty < 1$.
**Uncertainty and Perturbation**
* The multiplicative disk perturbation is defined as $\tilde P = (1+\Delta W_2)P$, where P is a nominal plant transfer function.
* $||\Delta||_\infty <1$ ensures that the system remains stable for all plants in the set $\mathcal{P}$.
**Key Concepts**
* Robustness: the distance between L and -1 for all frequencies, which determines how much room there is for plant perturbation before becoming unstable.
* Uncertainty profile: $|W_2(j\omega)|$ describes a disk in the complex plane that indicates the maximum amount of uncertainty allowed.
Overall, these notes provide a solid foundation for understanding the concepts and techniques used in feedback control theory, particularly in the context of robustness and stability analysis.
Generated by llama3.2:latest

View File

@ -1,57 +0,0 @@
# Table of Contents for 4 Presentation
## Files
- [[Building the Slides.md]]
- [[Outline.md]]
- [[Presentation Tasks.md]]
## Summary
It seems like you've generated a comprehensive outline for a research presentation on creating unstructured perturbations using diffusion models. The outline covers various aspects of the project, including goals, metrics of success, risks, and contingencies.
Here's a polished version of the outline:
**Title:** Creating Unstructured Perturbations with Diffusion Models
**I. Introduction**
* Brief overview of the importance of unstructured perturbations in robustness verification
* Research objectives:
+ Develop a method for creating unstructured perturbations using diffusion models
+ Evaluate the performance of the proposed approach
**II. Goals and Outcomes**
* Approximate unstructured sets through numerous perturbed plants
* Perturb nominal plants using the diffusion model
* Generate frequency-domain responses from training data
**III. Metrics of Success**
* Distribution: Verify uniform coverage of the multiplicative uncertainty disk
* Diversity: Assess non-parametric, dissimilar perturbations among examples
**IV. Risks and Contingencies**
* **Risk 1:** Computational demands of diffusion models
+ Utilize University of Pittsburgh's CRC supercomputing resources
+ Reduce data features while monitoring model performance
* **Risk 2:** Insufficient training data
+ Augment training with manually or algorithmically generated Δ examples
+ Diversify training data sources to improve robustness
* **Risk 3:** Interpolation limitations
+ Implement r(t)-based reverse process steering for controlled perturbations
+ Explore alternative interpolation techniques tailored to frequency domain applications
**V. Statistical Evaluation**
* Standard statistical tests applied to the perturbation set
* Covariance vectors calculated for key frequency ranges
**VI. Risks and Contingencies Summary**
* Addressing risks proactively ensures project success
* Computational strategies, diversified training, and alternative steering methods safeguard outcomes
This outline provides a solid structure for your presentation, covering the research objectives, metrics of success, risks, and contingencies. Be sure to expand on each section and provide supporting evidence and visuals to enhance your presentation. Good luck with your presentation!
Generated by llama3.2:latest

View File

@ -1,26 +0,0 @@
# Table of Contents for 4 Qualifying Exam
## Subdirectories
- [[0 Overview/0 Overview - README]]
- [[1 Managing Stuff/1 Managing Stuff - README]]
- [[2 Writing/2 Writing - README]]
- [[3 Notes/3 Notes - README]]
- [[4 Presentation/4 Presentation - README]]
- [[98 With Revisions/98 With Revisions - README]]
- [[99 Exports/99 Exports - README]]
## Files
- [[QE_Application_Sabo.pdf]]
- [[qualifying_exam_application_form.docx]]
- [[qualifying_exam_application_form_filled.docx]]
## Summary
Here is a description of what's inside the folder, based on the table of contents and file contents:
The `4 Qualifying Exam` folder contains various documents and files related to preparing for a qualifying exam.
Inside the subdirectories, you'll find four main sections: [[0 Overview]] which sets up an overview of the exam application process, [[1 Managing Stuff]], where management of exam materials is discussed, [[2 Writing]], which focuses on writing skills required for the exam, and [[3 Notes]], which outlines key notes to focus on. Additionally, there are subdirectories for [[98 With Revisions]] and [[99 Exports]].
The folder also includes several PDF documents, including a qualifying exam application form ([[QE_Application_Sabo.pdf]]) and its filled version ( [[qualifying_exam_application_form_filled.docx]]).
Generated by llama3.2:latest

View File

@ -1,15 +0,0 @@
# Table of Contents for 98 With Revisions
## Files
- [[QE Abstract For Dan_COMMENTS.pdf]]
## Summary
Here's a concise and descriptive README file content:
# 98 With Revisions
This folder contains the raw notes and documents related to the current project, including:
* Research findings documented in [[ QE Abstract For Dan_COMMENTS.pdf ]]
Generated by llama3.2:latest

View File

@ -1,12 +0,0 @@
# Table of Contents for 99 Exports
## Files
- [[QE Abstract For Dan_v1.pdf]]
- [[QE Abstract For Dan_v2.pdf]]
## Summary
Here's a concise description of the contents of the folder:
This folder contains documentation related to "99 Exports". The primary files are abstracts for two different versions, [[QE Abstract For Dan_v1.pdf]] and [[QE Abstract For Dan_v2.pdf]], which can be used as references or supporting materials.
Generated by llama3.2:latest

View File

@ -1,28 +0,0 @@
# Table of Contents for 0. Deadlines
## Files
- [[2024-09-11 Qualifying Exam Abstract Due.md]]
- [[2024-09-18 QE Topic Approval.md]]
- [[2024-09-19 Working Encrypted Controller.md]]
- [[2024-09-23 TRTR Presentation Due.md]]
- [[2024-09-30 TRTR Presentation.md]]
- [[2024-11-05 Written Proposal First Draft Complete.md]]
- [[2024-11-13 QE Proposal Due.md]]
- [[2024-12-03 QE Oral Examination.md]]
## Summary
Here is a Markdown description of what's inside the folder:
### 0. Deadlines
This folder contains deadlines and task due dates related to various projects and tasks, including qualifying exams, written proposals, and presentations.
* [[2024-09-11 Qualifying Exam Abstract Due]]: Deadline for submitting an abstract related to the qualifying exam
* [[2024-09-18 QE Topic Approval]]: Deadline for approving a topic for the qualifying exam
* [[2024-09-19 Working Encrypted Controller]]: Task with a deadline, completed on 2024-09-26
* [[2024-09-23 TRTR Presentation Due]]: Deadline for submitting a presentation related to TRTR (completed on 2024-09-24)
* [[2024-09-30 TRTR Presentation]]: Completed task
* [[2024-11-05 Written Proposal First Draft Complete]]: Task with an upcoming deadline
* [[2024-11-13 QE Proposal Due]]: Deadline for submitting a proposal related to the qualifying exam (completed later)
Generated by llama3.2:latest

View File

@ -1,18 +0,0 @@
# Table of Contents for 3. Events
## Files
- [[2024-08-27 Fighting Parking Ticket.md]]
- [[2024-09-14 Pitt vs. WVU.md]]
- [[2024-09-18 My Birthday!.md]]
- [[2024-09-26 Picnic.md]]
- [[2024-09-27 Observatory Visit.md]]
- [[2024-10-04 Amber's Parents are Here.md]]
- [[2024-10-10 Lane's Bachelor Party.md]]
- [[2024-10-23 Michaela's Wedding.md]]
- [[2024-11-14 Lane's Wedding.md]]
- [[2025-03-02 Spring Break.md]]
- [[stubb!.md]]
## Summary
Generated by llama3.2:latest

View File

@ -1,15 +0,0 @@
# Table of Contents for 900s Calendars
## Subdirectories
- [[0. Deadlines/0. Deadlines - README]]
- [[3. Events/3. Events - README]]
- [[Learning/Learning - README]]
- [[Other Work/Other Work - README]]
- [[Personal/Personal - README]]
- [[Research/Research - README]]
- [[Service/Service - README]]
- [[Teaching/Teaching - README]]
## Summary
Generated by llama3.2:latest

View File

@ -1,56 +0,0 @@
# Table of Contents for Learning
## Files
- [[2025-02-21 ME 2150 Microkit part 3 and 4.md]]
- [[2025-02-24 NUCE HW and Lab Report.md]]
- [[2025-02-25 NUCE HW and Lab Report.md]]
- [[2025-02-25 NUCE Lab 5.md]]
- [[2025-02-26 ME2046 Homework.md]]
- [[2025-02-26 ME2046 HW3.md]]
- [[2025-02-27 ME2046 HW3.md]]
- [[2025-03-03 ME2046 HW3.md]]
- [[2025-03-05 ME2046 HW3.md]]
- [[2025-03-06 ME2046 HW3.md]]
- [[2025-03-06 ME2046 more HW3.md]]
- [[2025-03-07 HW2 NUCE 2113.md]]
- [[2025-03-10 Laboratory 6 Report.md]]
- [[2025-03-11 NUCE Lab 6 Report.md]]
- [[2025-03-12 ME2046 Homework.md]]
- [[2025-03-12 ME 2046 HW4.md]]
- [[2025-03-13 ME2046 HW4.md]]
- [[2025-03-14 NUCE Lab 7.md]]
- [[2025-03-15 ME2046 Midterm.md]]
- [[2025-03-16 ME2046 Midterm.md]]
- [[2025-03-17 Assemble ME2046 HW and midterm.md]]
- [[2025-03-17 Assemble midterm and hws.md]]
- [[2025-03-17 ME 2046 Midterm.md]]
- [[2025-03-17 ME2046 Midterm.md]]
- [[2025-03-17 NUCE 2113 Midterm.md]]
- [[2025-03-18 More NUCE 2113 Midterm.md]]
- [[2025-03-18 NUCE 2113 Midterm.md]]
- [[2025-03-18 NUCE 2133 Midterm.md]]
- [[2025-03-19 NUCE 2113 HW4.md]]
- [[2025-03-19 NUCE 2113 Lab Reports.md]]
- [[2025-03-20 NUCE 2113 Lab Reports.md]]
- [[2025-03-21 Vim Shortcuts (Folding).md]]
- [[2025-03-24 Read About ADC.md]]
- [[2025-03-25 IDR.md]]
- [[2025-03-26 ME 2046 Project Proposal.md]]
- [[2025-03-27 ME2046 Project Proposal.md]]
- [[2025-03-27 ME2046 Proposal.md]]
- [[2025-03-31 NUCE 2113 Homework 5.md]]
- [[2025-03-31 NUCE 2113 Lab 9.md]]
- [[2025-03-31 NUCE 2113 Lab Report 9.md]]
- [[2025-04-02 NUCE Hell.md]]
- [[2025-04-03 BEAGLEBONE.md]]
- [[2025-04-04 BEAGLEBONE.md]]
- [[2025-04-07 NUCE 2113.md]]
- [[2025-04-11 ME 2046 Project Update.md]]
- [[2025-04-11 ME2150 HW.md]]
- [[2025-04-12 ME 2046 Project Update.md]]
- [[2025-04-13 ME 2046 Project Update.md]]
- [[2025-04-14 NUCE Lab 11 and HW 7.md]]
## Summary
Generated by llama3.2:latest

View File

@ -1,16 +0,0 @@
# Table of Contents for 1. Other Work
## Files
- [[900s Calendars/Other Work/stubb!]]
## Summary
Here is a concise description of what's inside the folder:
### [Folder Contents]
This folder contains documents related to other work in the 900s calendars.
* A brief outline is provided in [[900s Calendars/Other Work/stubb!]].
* No additional files are present in this folder.
Generated by llama3.2:latest

View File

@ -1,24 +0,0 @@
# Table of Contents for Other Work
## Files
- [[1. Other Work - README.md]]
- [[2025-03-03 Count Up Hours from Last Week.md]]
- [[2025-03-03 Email.md]]
- [[2025-03-03 Finish Thesis thoughts.md]]
- [[2025-03-03 Schedule things for this week.md]]
- [[2025-03-05 Mail Setup and Email.md]]
- [[2025-03-19 Website and Email.md]]
- [[2025-03-20 Bus In and Website.md]]
- [[2025-03-21 Bus in and clean up tasks.md]]
- [[2025-03-31 Bus in and journal.md]]
- [[2025-04-01 More DGC Meeting.md]]
- [[2025-04-01 Prepare for group meeting.md]]
- [[2025-04-07 Random email and shit.md]]
- [[2025-04-09 Cleaning Desk and Coffee.md]]
- [[2025-04-14 Email and Admin.md]]
- [[2025-04-14 Pick out fall classes.md]]
- [[stubb!.md]]
## Summary
Generated by llama3.2:latest

View File

@ -1,59 +0,0 @@
# Table of Contents for Personal
## Files
- [[2025-02-21 Gym.md]]
- [[2025-02-24 Car Shopping.md]]
- [[2025-02-24 Fixing Neovim bullshit.md]]
- [[2025-02-25 Gym and Shower.md]]
- [[2025-02-26 Coffee yak.md]]
- [[2025-02-26 Drive In.md]]
- [[2025-02-26 Lunch.md]]
- [[2025-02-27 Bus in.md]]
- [[2025-02-28 Bus in.md]]
- [[2025-03-03 Bus In.md]]
- [[2025-03-03 Putzing with bank stuff.md]]
- [[2025-03-03 Random Personal Stuff.md]]
- [[2025-03-03 Spring Break.md]]
- [[2025-03-04 Amber Dinner w Cori.md]]
- [[2025-03-04 Dinner.md]]
- [[2025-03-05 Bus Home.md]]
- [[2025-03-05 Lunch w Patrick.md]]
- [[2025-03-06 Work Remotely - No Water in Benedum.md]]
- [[2025-03-07 Finish finances.md]]
- [[2025-03-07 Lunch.md]]
- [[2025-03-07 Moving things over to my new email.md]]
- [[2025-03-08 Amber Work.md]]
- [[2025-03-12 Amber Soccer.md]]
- [[2025-03-16 Creating my website.md]]
- [[2025-03-19 Lunch.md]]
- [[2025-03-21 Bus Home.md]]
- [[2025-03-24 Lunch.md]]
- [[2025-03-25 Dinner.md]]
- [[2025-03-25 Go to the tailor.md]]
- [[2025-03-25 Run n Shower.md]]
- [[2025-03-25 Walk tha DAWG.md]]
- [[2025-03-26 Coffee Yak and Explore Med School.md]]
- [[2025-03-26 Lunch.md]]
- [[2025-03-28 Get engine stand from Gabe.md]]
- [[2025-03-28 Lewie Vet Appointment.md]]
- [[2025-03-28 Travel home.md]]
- [[2025-03-31 Lunch with Murphy.md]]
- [[2025-04-01 Dinner.md]]
- [[2025-04-07 Drive back home.md]]
- [[2025-04-07 Drive to Airport.md]]
- [[2025-04-11 Go home.md]]
- [[2025-04-14 Bus Home.md]]
- [[2025-04-14 Go see grandparents.md]]
- [[2025-04-14 Walk Lewie, Gym and Dinner.md]]
- [[2025-07-01 Arrive.md]]
- [[2025-07-01 Churchill War Rooms.md]]
- [[2025-07-01 London Eye.md]]
- [[2025-07-02 Changing of the Guard.md]]
- [[2025-07-02 Tea Time at Chesterfield Mayfair.md]]
- [[2025-07-03 Tower of London.md]]
- [[2025-07-03 Travel to Milton Keynes.md]]
- [[2025-07-07 Check in at Hilton Garden Inn London Heathrow.md]]
## Summary
Generated by llama3.2:latest

View File

@ -1,40 +0,0 @@
# 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-24 Haskell Chapter 2.md]]
- [[2025-02-24 LEAN.md]]
- [[2025-02-24 TLA Learning Plan and Notes.md]]
- [[2025-02-26 BoardTalk with Robert.md]]
- [[2025-02-28 TLA+ Proof.md]]
- [[2025-03-07 Finish thesis update and weekly summary.md]]
- [[2025-03-11 More Cole Group.md]]
- [[2025-03-11 Write weekly update.md]]
- [[2025-03-12 Coffee Yak and Research Talk with Robert.md]]
- [[2025-03-12 Finish Thesis update.md]]
- [[2025-03-13 Research MARVEL stuff.md]]
- [[2025-03-18 Research SMARTT.md]]
- [[2025-03-21 Write about MARVEL.md]]
- [[2025-03-23 Rust.md]]
- [[2025-03-24 Rust Chapter 2.md]]
- [[2025-03-24 Rust Chapter 3.md]]
- [[2025-03-24 Wander around the Library Picking up Books.md]]
- [[2025-03-24 Write about Chapter 4 from Modern Sensors Handbook.md]]
- [[2025-03-25 Chat about secure platforms for seL4.md]]
- [[2025-03-25 Fix Pyright for Neovim.md]]
- [[2025-03-28 Manyu defense.md]]
- [[2025-03-31 ARCADE EndPoint.md]]
- [[2025-03-31 Bus home and read Survey.md]]
- [[2025-03-31 Collect some literature reviews.md]]
- [[2025-04-07 Bus Home and HDD model paper.md]]
- [[2025-04-07 Literature Note rework.md]]
- [[2025-04-07 Nonlinear control survey papers.md]]
- [[2025-04-08 I2C stuff.md]]
- [[2025-04-09 Reading papers n'at.md]]
- [[2025-04-09 TLA+ Module 6.md]]
## Summary
Generated by llama3.2:latest

View File

@ -1,16 +0,0 @@
# Table of Contents for Service
## Files
- [[2025-02-24 Divvy meeting with Connor.md]]
- [[2025-02-25 Union Stuff.md]]
- [[2025-02-26 Add qual students to teams chat.md]]
- [[2025-03-05 Write research spotlight email and pick people for it.md]]
- [[2025-03-06 Set up Union Github Repo.md]]
- [[2025-03-07 Make a poster for the Union.md]]
- [[2025-03-10 Poster for Alumni Event.md]]
- [[2025-03-20 MEMS Open House.md]]
- [[2025-04-02 Union Obsidian.md]]
## Summary
Generated by llama3.2:latest

View File

@ -1,10 +0,0 @@
# Table of Contents for Teaching
## Files
- [[2025-02-21 QSG SOTA PREP.md]]
- [[2025-02-28 Research Approach Prep.md]]
- [[2025-03-26 Review QE exams.md]]
## Summary
Generated by llama3.2:latest

View File

@ -1,14 +0,0 @@
# Table of Contents for NonGraph
## Summary
## Folder Contents
This folder contains the following:
* [[Table of Contents]]: an overview of what's inside this folder
* [[README.md]]:
A brief description of the contents in this folder.
* [[NonGraph]]
A table explaining how graph-based data structures differ from non-graph data structures.
Generated by llama3.2:latest

View File

@ -1,47 +0,0 @@
Generated by ChatGPT on 2025-02-19
# Table of Contents for .obsidian
## Subdirectories
- [[icons/icons - README]]
- [[plugins/plugins - README]]
- [[snippets/snippets - README]]
- [[themes/themes - README]]
## Files
- [[appearance.json]]
- [[app.json]]
- [[bookmarks.json]]
- [[community-plugins.json]]
- [[core-plugins.json]]
- [[core-plugins-migration.json]]
- [[daily-notes.json]]
- [[graph.json]]
- [[hotkeys.json]]
- [[page-preview.json]]
- [[templates.json]]
- [[types.json]]
- [[webviewer.json]]
- [[workspace.json]]
## Summary
This directory contains various files, including:
1. `appearance.json`: Defines the layout of your Obsidian environment.
2. `app.json`: Configuration for your Obsidian app.
3. `bookmarks.json`: A JSON file containing links to different sections in your Obsidian book.
4. `community-plugins.json`: A configuration file for community plugins installed in your Obsidian environment.
5. `core-plugins.json`: Configuration for the core plugins installed in your Obsidian environment.
6. `core-plugins-migration.json`: An updated version of the `core-plugins.json` file, including any changes from the last migration.
7. `daily-notes.json`: A JSON file containing daily notes or summaries.
8. `graph.json`: A JSON file representing a graph model used in your Obsidian environment to organize content.
9. `hotkeys.json`: Configuration for hotkey mappings within your Obsidian settings.
10. `page-preview.json`: A configuration file for page preview settings within your Obsidian book.
11. `templates.json`: A configuration file defining templates and their behavior in Obsidian.
12. `types.json`: Configuration for data types used in your Obsidian environment.
13. `webviewer.json`: A configuration file for the web viewing tool in your Obsidian environment.
14. `workspace.json`: A JSON file containing information about the current workspace settings.
This directory provides a comprehensive overview of how to structure and customize your Obsidian environment, covering both the core configurations (like `appearance`, `app.json`, etc.) and community plugins and other tools installed or updated in your system.
Generated by qwen2.5:0.5b

View File

@ -1,8 +0,0 @@
Generated by ChatGPT on 2025-02-19
# Table of Contents for icons
## Summary
I'm sorry, but I need more context to provide a summary description of what this directory is about. Could you please specify the contents or purpose of this directory?
Generated by qwen2.5:0.5b

View File

@ -1,19 +0,0 @@
Generated by ChatGPT on 2025-02-19
# Table of Contents for colored-tags
## Files
- [[data.json]]
- [[main.js]]
- [[manifest.json]]
## Summary
This directory contains various files with specific tags or categories assigned to them:
1. **[data.json]** - Contains metadata for the project or file, providing details about its contents.
2. **[main.js]** - This is likely the main JavaScript code associated with this project or file.
3. **[manifest.json]** - A descriptor or configuration file defining what the project should be and how it should behave.
These files serve as a guide to organizing and managing different types of content within your project or application.
Generated by qwen2.5:0.5b

View File

@ -1,24 +0,0 @@
Generated by ChatGPT on 2025-02-19
# Table of Contents for dataview
## Files
- [[data.json]]
- [[main.js]]
- [[manifest.json]]
- [[styles.css]]
## Summary
This directory contains various files that are part of the `dataview` project. These files serve different purposes:
1. **data.json**: This file is likely used to store data or information related to the `dataview` application, which could be useful for storing user preferences, data points, or any other relevant data.
2. **main.js**: This script serves as the entry point of the project and contains basic configuration options such as project name, version control mechanism, etc.
3. **manifest.json**: This file is responsible for defining the structure of the project and its dependencies. It includes metadata about the project, such as its name, description, and version.
4. **styles.css**: This CSS file defines the visual styles used in the `dataview` application.
These files collectively form a comprehensive framework for managing the `dataview` application.
Generated by qwen2.5:0.5b

View File

@ -1,20 +0,0 @@
Generated by ChatGPT on 2025-02-19
# Table of Contents for highlightr-plugin
## Files
- [[data.json]]
- [[main.js]]
- [[manifest.json]]
- [[styles.css]]
## Summary
This directory contains files, including:
1. **`data.json`**: Contains JSON data that might be used for generating descriptions or further analysis of the plugin.
2. **`main.js`**: JavaScript code responsible for running the plugin's logic.
3. **`manifest.json`**: A file with metadata about the plugin, such as its version and author details.
These files are part of a directory structure designed to organize various components of a high-level development pipeline or automation script, possibly related to an AI application where this plugin is integrated. The content could be used for tasks like integrating features into a project, generating documentation for users, or running tests automatically.
Generated by qwen2.5:0.5b

View File

@ -1,20 +0,0 @@
Generated by ChatGPT on 2025-02-19
# Table of Contents for obsidian-citation-plugin
## Files
- [[data.json]]
- [[main.js]]
- [[manifest.json]]
- [[styles.css]]
## Summary
This directory contains the following files:
1. `data.json`: Contains metadata about the source of the documents.
2. `main.js`: The JavaScript code for generating the content.
3. `manifest.json`: Describes how the application is organized, including the version and author information.
The manifest.json file will be read as a separate documentation, making it easier to generate guides and other descriptive files based on this data.
Generated by qwen2.5:0.5b

View File

@ -1,20 +0,0 @@
Generated by ChatGPT on 2025-02-19
# Table of Contents for obsidian-footnotes
## Files
- [[main.js]]
- [[manifest.json]]
## Summary
This directory is about the "obsidian-footnotes" section within Obsidian, which is a tool used to organize notes and references in a collaborative text editor. Obsidian allows users to create chapters and sections for their notes, with each chapter containing links to related content. This directory includes information such as:
1. `manifest.json`: A file that describes the structure of the Obsidian footprint, including its contents (e.g., metadata and data) and any external dependencies.
2. Other files may be added based on user input or specific needs within the Obsidian system.
3. The "obsidian-footnotes" section itself is not directly mentioned in the given table of contents but could represent a collection of notes, references, or other organizational tools within the system.
This directory serves as a central hub for users who want to manage their notes and references efficiently within Obsidian's ecosystem.
Generated by qwen2.5:0.5b

View File

@ -1,19 +0,0 @@
Generated by ChatGPT on 2025-02-19
# Table of Contents for obsidian-git
## Files
- [[data.json]]
- [[main.js]]
- [[manifest.json]]
- [[styles.css]]
## Summary
This directory is about creating and managing code projects in Obsidian using the Git workflow engine. Specifically, it contains JSON files (`data.json`, `manifest.json`) that store information about the current project state, and a CSS file (`styles.css`) to style the Obsidian project editor UI.
### Summary of Contents:
- **Data**: Stores project details such as repository URLs, files, dependencies, etc.
- **Manifest**: Contains configuration for building and running the Obsidian Git workflow.
- **Styles**: A CSS file to enhance the Obsidian project editor UI.
Generated by qwen2.5:0.5b

View File

@ -1,14 +0,0 @@
Generated by ChatGPT on 2025-02-19
# Table of Contents for obsidian-icon-folder
## Files
- [[data.json]]
- [[main.js]]
- [[manifest.json]]
- [[styles.css]]
## Summary
The Obsidian icon folder is a repository that contains various files related to icons, including `data.json`, `main.js`, and `manifest.json`. These files are used within the Obsidian application for managing icons, such as loading them, adding styles, updating icons, and fetching metadata. They serve as the base structure and can be further expanded into descriptive descriptions or readables as desired.
Generated by qwen2.5:0.5b

View File

@ -1,20 +0,0 @@
Generated by ChatGPT on 2025-02-19
# Table of Contents for obsidian-pandoc-reference-list
## Files
- [[data.json]]
- [[main.js]]
- [[manifest.json]]
- [[styles.css]]
## Summary
This directory contains various files used in the Obsidian PANDOC reference list project, which is specifically designed to create markdown content for Pandoc.
1. **data.json**: This file stores metadata about the references used in this reference list.
2. **manifest.json**: This JSON document specifies the structure of the reference list and provides information about the directory where the list will be stored.
3. **styles.css**: A CSS file containing styles for the reference list, which may need to be customized depending on the preferences or design requirements.
This directory is intended for developers and users who are working with Obsidian PANDOC and need to organize their content into markdown files that can be automatically converted to Pandoc format.
Generated by qwen2.5:0.5b

View File

@ -1,14 +0,0 @@
Generated by ChatGPT on 2025-02-19
# Table of Contents for obsidian-style-settings
## Files
- [[data.json]]
- [[main.js]]
- [[manifest.json]]
- [[styles.css]]
## Summary
This directory is used to organize and manage settings related to Obsidian, the popular collaborative document management software. It contains files such as `data.json`, which stores data about the specific instance of Obsidian being configured; `main.js`, a script for Obsidian that manages its configuration and operations; and `manifest.json`, which defines the various parts of an Obsidian installation (such as themes, plugins, and settings) in a more human-readable format.
Generated by qwen2.5:0.5b

View File

@ -1,22 +0,0 @@
Generated by ChatGPT on 2025-02-19
# Table of Contents for obsidian-tasks-plugin
## Files
- [[data.json]]
- [[main.js]]
- [[manifest.json]]
- [[styles.css]]
## Summary
The Obsidian-Tasks-plugin directory contains various files that are essential for managing tasks in the Obsidian application, specifically related to adding, updating, deleting, and organizing tasks. Here is a summary of what each file includes:
- **data.json**: This file stores configuration settings and metadata about the plugin, such as its name, version, author, and any other relevant information.
- **main.js**: This script initializes the Obsidian-Tasks-plugin UI, including the sidebar layout for managing tasks. It also handles global events and hooks that are specific to this plugin.
- **manifest.json**: This file defines a manifest for the plugin that includes details about the plugin's version, dependencies, and metadata.
- **styles.css**: This CSS file styles various elements in the Obsidian-Tasks-plugin UI, providing a clean and modern design.
Generated by qwen2.5:0.5b

View File

@ -1,20 +0,0 @@
Generated by ChatGPT on 2025-02-19
# Table of Contents for obsidian-zotero-desktop-connector
## Files
- [[data.json]]
- [[main.js]]
- [[manifest.json]]
- [[pdfannots2json-linux-x64]]
- [[styles.css]]
## Summary
This directory contains various files related to creating an Obsidian Zotero desktop connector.
1. `data.json`: This is the root of your project's data.
2. `main.js`: The main JavaScript code for interacting with your Obsidian project.
3. `manifest.json`: This file holds metadata about your Obsidian project and how it should be accessed.
4. `pdfannots2json-linux-x64`: A script that converts Zotero notes into PDF annotations.
Generated by qwen2.5:0.5b

View File

@ -1,43 +0,0 @@
Generated by ChatGPT on 2025-02-19
# Table of Contents for plugins
## Subdirectories
- [[colored-tags/colored-tags - README]]
- [[dataview/dataview - README]]
- [[highlightr-plugin/highlightr-plugin - README]]
- [[obsidian-admonition/obsidian-admonition - README]]
- [[obsidian-citation-plugin/obsidian-citation-plugin - README]]
- [[obsidian-enhancing-export/obsidian-enhancing-export - README]]
- [[obsidian-footnotes/obsidian-footnotes - README]]
- [[obsidian-full-calendar/obsidian-full-calendar - README]]
- [[obsidian-git/obsidian-git - README]]
- [[obsidian-icon-folder/obsidian-icon-folder - README]]
- [[obsidian-pandoc-reference-list/obsidian-pandoc-reference-list - README]]
- [[obsidian-style-settings/obsidian-style-settings - README]]
- [[obsidian-tasks-plugin/obsidian-tasks-plugin - README]]
- [[obsidian-zotero-desktop-connector/obsidian-zotero-desktop-connector - README]]
- [[templater-obsidian/templater-obsidian - README]]
## Summary
This directory contains various plugins for Obsidian, a digital library tool that supports multiple text editors such as Notepad++, Markdown, and Microsoft Word. The description includes the names of several plugins:
1. `colored-tags/colored-tags - README`: This is an overview or description about the `colored-tags` plugin.
2. `dataview/dataview - README`: This describes a plugin named `dataview`.
3. `highlightr-plugin/highlightr-plugin - README`: This points to a high-lightr plugin.
4. `obsidian-admonition/obsidian-admonition - README`: This is an overview of the `obsidian-admonition` plugin.
5. `obsidian-citation-plugin/obsidian-citation-plugin - README`: This describes the `obsidian-citation-plugin`.
6. `obsidian-enhancing-export/obsidian-enhancing-export - README`: This is a description about the `obsidian-enhancing-export` plugin.
7. `obsidian-footnotes/obsidian-footnotes - README`: This points to a `obsidian-footnotes` plugin.
8. `obsidian-full-calendar/obsidian-full-calendar - README`: This describes an `obsidian-full-calendar` plugin.
9. `obsidian-git/obsidian-git - README`: This is about the `obsidian-git`.
10. `obsidian-icon-folder/obsidian-icon-folder - README`: This explains another icon folder in Obsidian.
11. `obsidian-pandoc-reference-list/obsidian-pandoc-reference-list - README`: This describes a pandoc reference list plugin.
12. `obsidian-style-settings/obsidian-style-settings - README`: This is an overview about the `obsidian-style-settings` plugin.
13. `obsidian-tasks-plugin/obsidian-tasks-plugin - README`: This describes the `obsidian-tasks-plugin`.
14. `obsidian-zotero-desktop-connector/obsidian-zotero-desktop-connector - README`: This points to a `obsidian-zotero-desktop-connector` plugin.
15. `templater-obsidian/templater-obsidian - README`: This describes the `templater-obsidian` template plugin.
Each of these directories contains information about different plugins that are part of Obsidian, making them useful for users who want to learn more about various features and functionalities provided by Obsidian's plugins.
Generated by qwen2.5:0.5b

View File

@ -1,22 +0,0 @@
Generated by ChatGPT on 2025-02-19
# Table of Contents for templater-obsidian
## Files
- [[data.json]]
- [[main.js]]
- [[manifest.json]]
- [[styles.css]]
## Summary
This directory contains files related to the `templater-obsidian` project.
1. **Data.json**: This file stores data used in creating this specific version of the template.
2. **main.js**: This script is responsible for managing the templates and their attributes, including any icons or other elements required by the templates.
3. **manifest.json**: This file contains metadata about the project's structure, such as the name, description, etc., which can be used in documentation or a README.md.
The directory also includes two CSS files:
- `styles.css`: These are the styles for the template that should be included when using the template.
- The file names and contents have been generated automatically by ChatGPT on 2025-02-19, so there's no need to edit them manually.
Generated by qwen2.5:0.5b

View File

@ -1,11 +0,0 @@
Generated by ChatGPT on 2025-02-19
# Table of Contents for snippets
## Files
- [[color_snippet.css]]
## Summary
The table of contents does not provide specific details about the directory or files within it, but it is likely that this directory contains Markdown files with "snippet" suffixes (e.g., `color_snippet.css`, `example.md`). Without more context, I cannot summarize what this directory is about.
Generated by qwen2.5:0.5b

View File

@ -1,18 +0,0 @@
Generated by ChatGPT on 2025-02-19
# Table of Contents for AnuPpuccin
## Files
- [[manifest.json]]
- [[theme.css]]
## Summary
### Summary:
The directory "AnuPpuccin" is a general directory that contains various files, including:
1. **[manifest.json]**: This is the main configuration file for a project or application.
2. **[theme.css]**: This file defines a CSS theme for a webpage or document.
Both of these items are part of the overall content management system and serve as descriptors that provide context and information about the files in the directory.
Generated by qwen2.5:0.5b

View File

@ -1,27 +0,0 @@
Generated by ChatGPT on 2025-02-19
# Table of Contents for Everforest
## Files
- [[manifest.json]]
- [[theme.css]]
## Summary
Everforest is an educational, open-source data management platform that offers various tools and features to help users manage their data efficiently. Heres a summary of what the directory is about:
1. **Manages Files:**
- `manifest.json`: This file contains metadata for Everforest.
- `[theme.css]`: This CSS file will be read by a text editor like VSCode or Notepad++, allowing you to edit themes and styles.
2. **Describes Themes:**
- This directory includes the `theme.css` file, which is used to define how Everforest looks visually. It allows users to customize the design of their environment.
3. **Reads Themes into Text:**
- The theme.css file is read by a text editor like VSCode or Notepad++, allowing users to write their own themes using the provided files and CSS styles. This can be useful for creating unique, interactive experiences with Everforest's features.
4. **Features:
- Data Management: Users can store data in various systems such as EverForest's own database, other cloud-based services, or their local storage.
- Search Functionality: Users can easily find and navigate through their stored data using a search bar located at the top of their interface.
- Storage System: The directory includes files like `settings.json`, which stores settings for the data management process.
Generated by qwen2.5:0.5b

View File

@ -1,12 +0,0 @@
Generated by ChatGPT on 2025-02-19
# Table of Contents for Minimal
## Files
- [[manifest.json]]
- [[theme.css]]
## Summary
This directory contains the minimal set of files that are directly referenced in the generated minimal documentation provided by ChatGPT on February 19, 2025. The content is specific to this platform's structure and does not represent actual code or functionality of your project.
Generated by qwen2.5:0.5b

View File

@ -1,14 +0,0 @@
Generated by ChatGPT on 2025-02-19
# Table of Contents for Obsidian Nord
## Files
- [[manifest.json]]
- [[theme.css]]
## Summary
### Summary Description:
This directory contains files and metadata related to the `Obsidian Nord` project, which is likely a theme or collection of themes for Obsidian notebooks. The manifest.json file lists the properties of this project, including its name, version, description, author, and others. Each of these entries in the manifest.json should be considered when adding a new theme to your Obsidian notebook.
Generated by qwen2.5:0.5b

View File

@ -1,25 +0,0 @@
Generated by ChatGPT on 2025-02-19
# Table of Contents for themes
## Subdirectories
- [[AnuPpuccin/AnuPpuccin - README]]
- [[Everforest/Everforest - README]]
- [[Minimal/Minimal - README]]
- [[Obsidian Nord/Obsidian Nord - README]]
## Summary
This directory contains sections related to various themes or concepts. It includes subdirectories for each theme, where relevant content is described within those subdirectories.
### AnuPpuccin/AnuPpuccin - README:
- A README file explaining what the section is about and how to access it.
### Everforest/Everforest - README:
- A README file describing the version of Everforest that this directory belongs to.
### Minimal/Minimal - README:
- A README file describing the version of the Minimal theme this directory belongs to.
Thank you!
Generated by qwen2.5:0.5b

View File

@ -1,21 +0,0 @@
Generated by ChatGPT on 2025-02-19
# Table of Contents for .pandoc
## Files
- [[apa.csl]]
- [[ieee.csl]]
- [[locales-en-US.xml]]
- [[zotero-library-1.json]]
- [[zotero-library-2.json]]
## Summary
This directory contains various files and resources related to Zotero, a popular library for managing citations and references in academic papers. The contents include:
1. `apa.csl`: A citation management system based on the APA (American Psychological Association) style guide.
2. `ieee.csl`: Another citation management system that follows the IEEE (International Electrical Manufacturers Association) style guide.
3. `locales-en-US.xml`: This file is a JSON data containing information about language support for Zotero. It's used to describe how to configure and work with different locales.
In summary, this directory provides a set of files and resources designed to help users manage their bibliographic references using Zotero, especially in environments where the preference for a specific style guide or locale is important.
Generated by qwen2.5:0.5b

View File

@ -1,14 +0,0 @@
# Table of Contents for Untitled
## Summary
Here is a concise description of the contents of the folder:
This folder contains the following items:
* A table of contents for "Untitled" outlining its structure and contents.
* The text-based files "Untitled", which include [[Untitled]].
Let me know if you'd like any adjustments!
Generated by llama3.2:latest

View File

@ -1,8 +0,0 @@
# Table of Contents for 1 Ideas
## Files
- [[Untitled.md]]
## Summary
Generated by llama3.2:latest

View File

@ -1,9 +0,0 @@
# Table of Contents for 2 Logs
## Files
- [[0225Update.md]]
- [[2025-01 Thesis Log.md]]
## Summary
Generated by llama3.2:latest

View File

@ -1,19 +0,0 @@
# Table of Contents for 3 Notes
## Summary
Here is a concise description of what's inside the folder:
This folder contains the following items:
* A table of contents for **3 Notes**
* Text-based notes stored in files such as **Note 1**, **Note 2**, and **Note 3**
Note: You can format this description using Markdown syntax to create a clickable link. For example, you could use `[[3 Notes]]` instead of just writing "3 Notes" to make it a wikilink.
Here is the revised description:
This folder contains the following items:
* A table of contents for [[3 Notes]]
* Text-based notes stored in files such as [[Note 1]], [[Note 2]], and [[Note 3]]
Generated by llama3.2:latest

View File

@ -1,8 +0,0 @@
# Table of Contents for 4 Meetings
## Files
- [[DGC_DAS_328.md]]
## Summary
Generated by llama3.2:latest

View File

@ -1,8 +0,0 @@
# Table of Contents for 5 Resources
## Subdirectories
- [[Literature_Reviews/Literature_Reviews - README]]
## Summary
Generated by llama3.2:latest

View File

@ -1,10 +0,0 @@
# Table of Contents for Literature_Reviews
## Files
- [[Applications_of_Cyber-Physical_System.md]]
- [[A Review of Formal Methods applied to Machine Learning.md]]
- [[Neural_network-based_flight_control_systems.md]]
## Summary
Generated by llama3.2:latest

View File

@ -1,16 +0,0 @@
# Table of Contents for 5 Thesis
## Subdirectories
- [[1 Ideas/1 Ideas - README]]
- [[2 Logs/2 Logs - README]]
- [[3 Notes/3 Notes - README]]
- [[4 Meetings/4 Meetings - README]]
- [[5 Resources/5 Resources - README]]
## Files
- [[Thesis Thoughts.md]]
- [[Things to Do.md]]
## Summary
Generated by llama3.2:latest

View File

@ -1,9 +0,0 @@
# Table of Contents for Assembly
## Files
- [[Assembly Canvas.canvas]]
- [[Untitled.md]]
## Summary
Generated by llama3.2:latest

View File

@ -1,34 +0,0 @@
# Table of Contents for Haskell
## Files
- [[baby.hs]]
- [[Chapter 1 - Introduction.md]]
- [[Chapter 2 - Starting Out.md]]
- [[Learning Plan.md]]
- [[main.hs]]
## Summary
This appears to be the contents of a Markdown file used for version control, likely in a Git repository. The files are related to research on Haskell programming language and its features.
The documents cover various aspects of Haskell:
* Chapter 2: Starting Out
+ Introduces Haskell as a purely functional programming language.
+ Explains how Haskell differs from other programming languages.
+ Covers the basics of Haskell syntax, including list comprehensions and ranges.
* Chapter 1: Introduction
+ Provides an overview of Haskell's history and development.
+ Discusses the key features of Haskell, including referential transparency and type inference.
+ Describes how to get started with Haskell using GHC and other tools.
The documents are written in a conversational tone, suggesting that they were created by someone who is learning Haskell and wants to document their progress. The text includes explanations, examples, and references to external resources (e.g., `[^1]`).
Some notable aspects of the files include:
* The use of Markdown syntax for headings, formatting, and links.
* The inclusion of comments and notes in the text, indicating that the author is still learning and experimenting with Haskell.
* The reference to Neovim and Lua, suggesting that the author uses a custom configuration or plugin for their text editor.
Overall, these files appear to be a personal documentation of someone's journey into learning Haskell programming language.
Generated by llama3.2:latest

View File

@ -1,9 +0,0 @@
# Table of Contents for LEAN
## Files
- [[Learning Plan.md]]
- [[Tutorial World.md]]
## Summary
Generated by llama3.2:latest

View File

@ -1,36 +0,0 @@
# Table of Contents for 200 Library Papers
## Files
- [[aModeladoNucleoAnalisis2023.md]]
- [[atsumiModifiedBodePlots2012.md]]
- [[biggsJuryMonolithicOS2018.md]]
- [[CH4System_Representation_S2020pdf2254.md]]
- [[doyleFeedbackControlTheory2009.md]]
- [[doyleGuaranteedMarginsLQG1978.md]]
- [[emamiNeuralNetworkbasedFlight2022.md]]
- [[farzanRobustControlSynthesis2020.md]]
- [[fisherHACMSProgramUsing2017a.md]]
- [[fromherzVerifiedEfficientEmbedding2019.md]]
- [[gengSimplifiedReactorModel2024.md]]
- [[IntroductionDiffusionModels2022.md]]
- [[jacksonMARVELReactivityControl2023.md]]
- [[kleinFormallyVerifiedSoftware2018.md]]
- [[Kry10TechnicalOverview.md]]
- [[lozadaHARDENSFinalReport.md]]
- [[matthewsCoupledMultiphysicsSimulations2021.md]]
- [[matusuRegionsRobustRelative2023.md]]
- [[ME2046_Sampled_Data_Analysis_Reading_Chapter_2pdf2254ME.md]]
- [[ME2046_The_z_transform_Chapter_3pdf2254ME.md]]
- [[mihalicHardwareintheLoopSimulationsHistorical2022.md]]
- [[My Library.bib]]
- [[sohl-dicksteinDeepUnsupervisedLearning2015.md]]
- [[stauffHighFidelityMultiphysicsModeling.md]]
- [[stevebruntonControlBootcampIntroduction2017.md]]
- [[stevebruntonControlBootcampLimitations2017.md]]
- [[stevebruntonControlBootcampSensitivity2017.md]]
- [[sunSoKAttacksIndustrial2021.md]]
- [[testoniReviewNuclearMicroreactors2021.md]]
## Summary
Generated by llama3.2:latest

View File

@ -1,21 +0,0 @@
# Table of Contents for 199 Paper Notes
## Files
- [[Hardware In The Loop Papers.md]]
## Summary
Here is a concise description of the contents of the folder, in Markdown format:
# 199 Paper Notes Folder Contents
This folder contains notes and research related to HiTL (Hardware-in-the-Loop) testing. It includes papers on various topics such as ARCADE experiments, cybersecurity, formal methods, and PLCs.
The folder is organized by category, with sections for:
* **Preamble**: Introductions and background information
* **Summary Table**: A table of papers to keep track of notes
* **Papers about ARCADE**, **Hardware In The Loop Papers**, **Cybersecurity of OT Papers**, **Formal Methods and PLCs**, and **Kry10** are subfolders containing specific notes and references.
Note: [[Hardware In The Loop Papers.md]] is the main file in this folder, which contains a list of papers related to HiTL testing.
Generated by llama3.2:latest

View File

@ -1,17 +0,0 @@
# Table of Contents for 9999 Personal
## Subdirectories
- [[Journal/Journal - README]]
- [[Z/Z - README]]
## Files
- [[Enrollment Form Fall 2025.pdf]]
- [[Enrollment Form Fall 2025_REV_2.pdf]]
- [[Enrollment Form Fall 2025_REV_3.pdf]]
- [[Italy Planning.md]]
- [[Making a website.md]]
- [[Mozilla-Recovery-Key_2025-03-04_dane.sabo@pitt.edu.pdf]]
## Summary
Generated by llama3.2:latest

View File

@ -1,9 +0,0 @@
# Table of Contents for Journal
## Files
- [[20250331_Should_I_Continue.md]]
- [[20250409_*horsenoises*.md]]
## Summary
Generated by llama3.2:latest

Some files were not shown because too many files have changed in this diff Show More