Spaces:
Running
Running
devjas1
commited on
Commit
·
8a41ab5
1
Parent(s):
e7d7472
(refactor): update project objectives and outline strategic expansion paths
Browse files
README.md
CHANGED
@@ -167,11 +167,46 @@ These files are intentionally excluded from version control via `.gitignore`
|
|
167 |
|
168 |
---
|
169 |
|
170 |
-
##
|
171 |
|
172 |
-
-
|
173 |
-
- 🔬 Conduct small-scale hyperparameter sweeps
|
174 |
-
- 📈 Visual tools and presentation assets for showcase-ready delivery
|
175 |
-
- 🪪 Prepare presentation-ready visuals and model cards for final reporting
|
176 |
-
- ✅ Canonical validation completed (`@validation-loop-complete`)
|
177 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
167 |
|
168 |
---
|
169 |
|
170 |
+
## 🎯 Strategic Expansion Objectives
|
171 |
|
172 |
+
> Following Dr. Kuppannagari’s updated guidance, the project scope now extends beyond the Raman-only validated baseline. The roadmap defines three major expansion paths designed to broaden the system’s capabilities and impact:
|
|
|
|
|
|
|
|
|
173 |
|
174 |
+
1. **Model Expansion: Multi-Model Dashboard**
|
175 |
+
|
176 |
+
> The dashboard will evolve into a hub for multiple model architectures rather than being tied to a single baseline. Planned work includes:
|
177 |
+
|
178 |
+
- **Retraining & Fine-Tuning**: Incorporating publicly available vision models and retraining them with the polymer dataset.
|
179 |
+
- **Model Registry**: Automatically detecting available .pth weights and exposing them in the dashboard for easy selection.
|
180 |
+
- **Side-by-Side Reporting**: Running comparative experiments and reporting each model’s accuracy and diagnostics in a standardized format.
|
181 |
+
- **Reproducible Integration**: Maintaining modular scripts and pipelines so each model’s results can be replicated without conflict.
|
182 |
+
|
183 |
+
This ensures flexibility for future research and transparency in performance comparisons.
|
184 |
+
|
185 |
+
2. **Image Input Modality**
|
186 |
+
|
187 |
+
> The system will support classification on images as an additional modality, extending beyond spectra. Key features will include:
|
188 |
+
|
189 |
+
- **Upload Support**: Users can upload single images or batches directly through the dashboard.
|
190 |
+
- **Multi-Model Execution**: Selected models from the registry can be applied to all uploaded images simultaneously.
|
191 |
+
- **Batch Results**: Output will be returned in a structured, accessible way, showing both individual predictions and aggregate statistics.
|
192 |
+
- **Enhanced Feedback**: Outputs will include predicted class, model confidence, and potentially annotated image previews.
|
193 |
+
|
194 |
+
This expands the system toward a multi-modal framework, supporting broader research workflows.
|
195 |
+
|
196 |
+
3. **FTIR Dataset Integration**
|
197 |
+
|
198 |
+
> Although previously deferred, FTIR support will be added back in a modular, distinct fashion. Planned steps are:
|
199 |
+
|
200 |
+
- **Dedicated Preprocessing**: Tailored scripts to handle FTIR-specific signal characteristics (multi-layer handling, baseline correction, normalization).
|
201 |
+
- **Architecture Compatibility**: Ensuring existing and retrained models can process FTIR data without mixing it with Raman workflows.
|
202 |
+
- **UI Integration**: Introducing FTIR as a separate option in the modality selector, keeping Raman, Image, and FTIR workflows clearly delineated.
|
203 |
+
- **Phased Development**: Implementation details to be refined during meetings to ensure scientific rigor.
|
204 |
+
|
205 |
+
This guarantees FTIR becomes a supported modality without undermining the validated Raman foundation.
|
206 |
+
|
207 |
+
## 🔑 Guiding Principles
|
208 |
+
|
209 |
+
- **Preserve the Raman baseline** as the reproducible ground truth
|
210 |
+
- **Additive modularity**: Models, images, and FTIR added as clean, distinct layers rather than overwriting core functionality
|
211 |
+
- **Transparency & reproducibility**: All expansions documented, tested, and logged with clear outputs.
|
212 |
+
- **Future-oriented design**: Workflows structured to support ongoing collaboration and successor-safe research.
|