52 lines
2.5 KiB
Markdown
Executable File
52 lines
2.5 KiB
Markdown
Executable File
---
|
|
creation date: 2024-08-07
|
|
modification date: Wednesday 7th August 2024 09:45:29
|
|
tags: []
|
|
---
|
|
<< [[Weekly Note 2024-07-31]] | [[Weekly Note 2024-08-14]] >>
|
|
|
|
## This Week's Daily Notes
|
|
[[2024-07-31]]
|
|
[[2024-08-01]]
|
|
[[2024-08-02]]
|
|
[[2024-08-03]]
|
|
[[2024-08-04]]
|
|
[[2024-08-05]]
|
|
[[2024-08-06]]
|
|
|
|
## Last Week's Plan
|
|
## Accomplishments
|
|
### Tasks and Notes From This Past Week
|
|
|
|
```dataview
|
|
TASK
|
|
where completed and file.mtime >= this.file.mday - dur(7 days)
|
|
and file.mtime <= this.file.mday
|
|
group by file.link
|
|
sort rows.file.mtime asc
|
|
|
|
```
|
|
### Remarks
|
|
* Had our meeting with Chris Potts about the possible server. May have successfully convinced DGC
|
|
* Finished the week at INL, did presentation after writing it in a couple of days
|
|
* Switched to Obsidian from Notion
|
|
* Wrote down some ideas for things to do with ARCADE:
|
|
* One cool one is thinking about how we would actually implement a monitor like Lance talks about. I suspect in his vision that is a software monitoring system, but I think we could do it by just building an observer of the system, and if the error signal does strange things, that's our indication that something is wrong.
|
|
* Implementing something like this on KOs where everything is happening on the same hardware could be very interesting.
|
|
* Started writing a vision paper for Mai's workshop. Talking about synergy between physical proofs and software proofs. Talk about how managing these proofs of different components will eventually become a problem.
|
|
## This Week's Plan
|
|
1. ARCADE
|
|
1. Spin up the second beagleboard
|
|
2. Read a presentation from Andrew. Talks about future of ARCADE. Mentions HITL. [[Andrew's May 2024 ARCADE Presentation]]
|
|
3. Write about ARCADE Capabilities and what we want to use ARCADE to prove stuff with at Pitt. Reference [[2. (SR-CIST) Workshop on Security and Resiliency of Critical Infrastructure and Space Technologies]] website to look at topics. DGC mentioned security and resiliency of critical infrastructure
|
|
2. Diffusion
|
|
1. Presentation is presentable. Reverse process isn't super clear in the slides but I think I could explain it.
|
|
2. Need to talk about learning the NOISE versus the image
|
|
3. Write reverse process for simple 1D signal.
|
|
3. Rust
|
|
1. Eh 🤷♂️
|
|
4. [[Models All The Way Down - A Path Towards Software and Physical System Proof Synergy]]
|
|
1. DGC - Prevent talking out my ass.
|
|
2. New topic! [[ARCADE Implementation at the University of Pittsburgh]]
|
|
1. [[NUCE 2103 Final Exam]]
|
|
2. Look into if [[A Means to Formally Verify Controller Code Behaves as the Mathematical Model]] already exists |