gbionics / gbionics/robot-log-visualizer
Signal provider root name is hard coded
- Dominant language
- Python
- Stars
- 32
- Forks
- 7
- PR merge metrics
- No merged PRs in 30d
Description
As per title, the signal provider root name is hard coded (line 66)
https://github.com/ami-iit/robot-log-visualizer/blob/1a61360411a0100529c8011c8d9fb6273f62bbe4/robot_log_visualizer/file_reader/signal_provider.py#L32-L70
For our use cases it be useful to use the filename of the loaded `.mat` as the `root_name`, but have no idea of other applications (and neither how much is difficult to implement it)
Contributor guide
No contributing guide indexed for this repository
Research direction
Start in robot_log_visualizer/file_reader/signal_provider.py around the linked lines and inspect how the signal provider root name is assigned when a .mat file is loaded. Confirm how the filename should become root_name without breaking other uses, then verify the visualizer still loads the file correctly.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- data-visualization
- Issue type
- Feature
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 55/100