RnD/EVOLV
1
0
Fork 0
Code Issues 10 Pull Requests Actions Packages Projects Releases Wiki Activity

Relocate prediction/ML modules to external service #28

New Issue
Open
opened 2026-03-12 08:36:54 +00:00 by vps1_gitea_admin · 0 comments
vps1_gitea_admin commented 2026-03-12 08:36:54 +00:00
Owner
Copy Link

TensorFlow-based influent prediction code was removed from monster node (was broken/incomplete). The prediction functionality needs a new home.

Details:

  • LSTM model for 24-hour flow prediction based on precipitation data
  • Standardization constants: hours (mean=11.504, std=6.922), precipitation (mean=0.090, std=0.439), response (mean=1188.01, std=1024.19)
  • Model was served from http://127.0.0.1:1880/generalFunctions/datasets/lstmData/tfjs_model/
  • Consider: separate microservice, Python-based inference, or ONNX runtime
  • Monster node should accept predictions via model_prediction message topic from external service

Related files removed: monster_class.js methods get_model_prediction(), model_loader()

TensorFlow-based influent prediction code was removed from monster node (was broken/incomplete). The prediction functionality needs a new home. ### Details: - LSTM model for 24-hour flow prediction based on precipitation data - Standardization constants: hours `(mean=11.504, std=6.922)`, precipitation `(mean=0.090, std=0.439)`, response `(mean=1188.01, std=1024.19)` - Model was served from `http://127.0.0.1:1880/generalFunctions/datasets/lstmData/tfjs_model/` - Consider: separate microservice, Python-based inference, or ONNX runtime - Monster node should accept predictions via `model_prediction` message topic from external service **Related files removed:** `monster_class.js` methods `get_model_prediction()`, `model_loader()`
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
P0-architecture
Must-do structural/design changes for scaling
 P1-cleanup
Quick wins: remove deprecated code, fix inconsistencies
 P2-extensibility
Plugin architecture, output formats, config versioning
 P3-documentation
Docs, wiki, READMEs, architecture diagrams
 P4-testing
Test coverage, CI pipeline, integration tests
 bug
Confirmed bugs
 enhancement
New features / improvements
 security
Credentials, auth, vulnerabilities
 tech-debt
Code quality / cleanup
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
vps1_gitea_admin
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: RnD/EVOLV#28
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?