Print metadata: add standard keys like "Overall dimensions", "first layer dimensions", "total filament length/weight"
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 35/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Stale
- Domain
- tooling
Research direction
No files, tests, or entry points are identified. Start by locating how metadata keys are represented and written, then define the standard key set and verify that overall dimensions, first-layer dimensions, and total filament measurements are exposed consistently.
Written by the indexing model from the issue text.
Description
It would be great to have a standard set of keys for the metadata.
For instance:
- Overall dimensions. The printer might reject or warn the user in case the printed model will not fit into the print volume
- Dimensions of the "first layer". It might be helpful so the printer could probe the relevant bed surface with a probe. It could reduce the probing time and, it could improve the quality of the bed mesh
- Total filament length for the print. It might be helpful on the info screen before user accepts the print
- Dominant language
- G-code
- Stars
- 73
- Forks
- 24
- PR merge metrics
- No merged PRs in 30d
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
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 prusa3d/libbgcode
-
Extending bgcodeOpen
Difficulty 5/5 Over a week Newbie friendliness 25/100
-
Broken on big-endian architecturesPossibly taken @onitake claimed this 334 days ago. Open
Difficulty 4/5 3-5 days Newbie friendliness 35/100
-
PyPI releaseMay be free again @tomasbedrich claimed this 1035 days ago, and no pull request is open. Open
-
Difficulty 5/5 Over a week Newbie friendliness 25/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 55/100
All issues in prusa3d/libbgcode
Similar issues
-
decision
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
btclib-org/claude-process#609 · 1 comment ·
-
documentation
Difficulty 2/5 1-3 hours Newbie friendliness 67/100
hemilabs/ui-monorepo#2739 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
fancysnake/vekna#300 ·
Maintainers usually reply within 1 day
-
area:indexer bug needs-triage
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
seanb4t/codegraph-go#385 ·
Maintainers usually reply within 1 day
-
good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
bradley499/sss-guis#45 ·