Remove need of saving images before logging.
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 35/100
- Issue type
- Refactor
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- cpp
- Domain
- data-visualization
Research direction
Start by reading the Image support code and tracing how armadillo matrices are logged as images. Review the discussion linked from PR #6 for the existing encoded-format context. Done means matrices can be logged without temporary image files while retaining the current visualization behavior.
Written by the indexing model from the issue text.
Description
While logging armadillo matrices as Images for visualization in mlboard currently it is mandatory to save armadillo matrices as an image temporarily before logging. The reason we do that is to get the armadillo matrices in encoded format in the form of binary string. However, due to this, it needs quite a lot of reading and writing to the file system which can be avoided. It might also lead to increased time while logging thousands of images.
So the best solution to tackle this issue is to remove the need of saving images. This issue might need a good understanding of the Image support code. For more info on the topic you can see the following comment.
https://github.com/mlpack/mlboard/pull/6#discussion_r452971739
- Dominant language
- C++
- Stars
- 13
- Forks
- 8
- PR merge metrics
- No merged PRs in 30d
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from mlpack/mlboard
-
Fix Broken Build Open
-
build system help wanted
Difficulty 3/5 1-2 days Newbie friendliness 45/100
-
build system help wanted
Difficulty 2/5 1-3 hours Newbie friendliness 45/100
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
-
Sensor initialization takes very long when `--initial-sim-time` is set to current UNIX timestamp Open
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
gazebosim/gz-sensors#662 · 1 comment ·
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
-
comp-datalake
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
ClickHouse/ClickHouse#121222 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
LadybirdBrowser/ladybird#12123 ·