Legend

| Category | Status | Notes | |———–|——–|——-| | CT to Text | ✅ | Fully operational | | CT Images to Text | 🔧 | Debugging issues | | X-ray Log Files to Github | 🔧 | Debugging issues | | Robust Microservices | 🚧 | In development | | Automated Annotation and Blogging | 🔴 | Not started |

Raspi Log Files to Github Release

Metadata-parsing.md

✅ Uploading-metadata-to-github.md

✅ distributing-metadata-with-github-actions

✅ Onboarding new Facility using Github Pages

Empty Scan Parameters

##

New Morphosource –> Github Release

✅ Setting up Github Actions & Repo (secrets, .github folders, runtime workflow)

✅ Inspect Element to find page features

✅ Pulling Metadata from Morphosource

✅ Parse Morphosource Workflow Development

✅ Github Actions to Update last_count.txt

✅ Creating a Release when new Morphosource data is found

✅ CT to Text Workflow Development

✅ Challenges Developing CT to Text in Production (AI Generation limited to

✅ Developing Microservices (Parse Morphosource and CT to Text)

✅ Using Sellenium/Chrome to Analyze Media

✅ 2D vs. 3D Challenges High Level

✅ Integrating Slices Scrolling for 2D

✅ Integrating Orientation Adjustments for 3D

Creating a Microservice for 2D/3D media to OpenAI

Challenges with 2D Specific

Challenges with 3D Specific

Integrating this complex microservice with prior microservices

🔴 IN PROGRESS 2D Slices to OpenAI

🚧 3D Data to OpenAI

🚧 Creating a 3D Mesh Data Analysis Release

🔴 IN PROGRESS Creating a 2D Slice Analysis

🚧 A Robust Microservice for 2D/3D (webpage error handling, release checking, 2D/3D check, 2D to OpenAI, 3D to OpenAI)

End to End: Morphosource upload –> Publish Releases –> Export OpenAI Cost

Future Work: Automate annotation using generative AI and Github Actions

Future Work: Automate measurement

Future Work: Summarize Weekly Morphosource Uploads into Github Posts