Week 3
February 24, 2024
- Separate Azure notebooks into two. Github issue https://github.com/gqc/compute-canada/issues/62#issuecomment-1442820137
February 23, 2023
- Creating the plumbing to generate fake data and send to TDengine in USB-to-HTTPS.
- Cleaning up the weekly notes.
- Connecting S3 root node to another S3 to handle socket sending part.

February 22, 2023
- Adding Elsevier API documentation to the colab notebook.
- Needs to clean and commit the notebook to github.
- Testing HTTPS POST requests to TDEngine cloud.
- Debugged the HTTPS POST component throwing
stack overflow,panicerrors randomly.- It was due to the stack allocation to the task being not sufficient. Allocating more memory for stack resolved the issue.
Sudhir
- Add the HTTPS POST functionality to USB-to-Socket repo.
February 21, 2023
Documenting and reviwing new found sensor mesh issues.
Explore the data subscription feature in TDEngine on the possibility of using it for alerting.
After testing the code from the example on the local TDEngine installation, I've figured out how to connect with the TDEngine cloud for topic creation and subscription.
This is the colab notebook I created: https://colab.research.google.com/drive/1uFNM5CW577G5hEpRu-Ec_bEbqLSr2gzn?usp=sharing
From what I've found so far, we should be able to filter out the data to create custom messages with nested SQL statements. (As long as we don't hit the limitations from the TDEngine side such as aggregating tables or so). And it seems that on the Consumer side (subscriber), every message has to be read and processed, otherwise they will be queued up.
Sudhir
- Find more on the logging function used in
systemctl.- Modifying logging level, etc.
- Clear the log at each restart of the service
- Rewrite the readme of the deep_vibe_app repo.
- Find where to place the exe file for a service (compared to referring to the exe in the repo folder)
- Check CEEMDAN literature on what to make out from the analysis on conditional analysis.