IFC export doesn't write a circuit's rating
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 49/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- typescript
- Domain
- backend-api-design
Research direction
Start in packages/bim-ifc/src/export.ts:940-951, where service link properties are written, and trace how the IFC export represents IfcDistributionCircuit and property sets. Check whether the electrical add-on exposes the rating and its unit, then see if a standard property set fits. Done means the exported circuit carries its rating with a unit; the broader add-on mechanism is an inferred direction.
Written by the indexing model from the issue text.
Description
The problem
As an electrical engineer, I want each circuit in the IFC file to carry its rating, so that a reader can check it against the board and the loads. The model stores "electrical": {"ratingA": 20} on each service_link (observed). The exported circuit system carries only (observed):
circuit sets: {"MutinyBIM_Circuit":{"Adapter":"electrical","Positions":"1","Role":"branch"}}
Where in the code (observed, at 94513ba): packages/bim-ifc/src/export.ts:940-951 writes Role, Adapter and Positions for each service link, and nothing from its electrical block.
An AI agent helped find this and ran the repro on its own machine against 94513ba; I reviewed the output.
What you would like to happen
The circuit's rating (20 A) is written with its unit, in a standard pset if one fits IfcDistributionCircuit. Otherwise in MutinyBIM_Circuit. Other fields of the trade block might come too (poles, wire size), if the model has them (not checked).
The shared idea underneath
Service links are a kernel idea, and the electrical block comes from an add-on. A general way for the add-on that owns a link's block to name its IFC properties would cover plumbing and mechanical links too (inferred).
Discipline
Electrical
Area
Sheets, PDF or IFC
Engineering content
- This involves an engineering calculation, code rule or design default (it will need review by a licensed professional).
Helping
- I would like to work on this.
- Dominant language
- TypeScript
- Stars
- 85
- Forks
- 10
- Avg merge
- 1h 28m
- Merged PRs (30d)
- 20
Getting set up
- Ships a Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
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 permitzip/mutinybim
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
area: docs documentation
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
Maintainers usually reply within 1 day
-
area: web-app bug
Difficulty 2/5 1-3 hours Newbie friendliness 83/100
permitzip/mutinybim#27 · 1 comment ·
Maintainers usually reply within 1 day
-
enhancement
Difficulty 5/5 Over a week Newbie friendliness 35/100
permitzip/mutinybim#66 · 2 comments ·
Maintainers usually reply within 1 day
-
enhancement
Difficulty 4/5 3-5 days Newbie friendliness 48/100
permitzip/mutinybim#65 · 2 comments ·
Maintainers usually reply within 1 day
All issues in permitzip/mutinybim
Similar issues
-
🐛 The Rulekeeper - An index run that gives up on the lock ends SucceededPossibly taken @github-actions claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
SSWConsulting/SSW.Rules#2809 · 1 comment ·
Maintainers usually reply within 1 day
-
automated-triage type/bug type/ci
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
📦 expo-router Android contributor: external needs review sdk-58 severity: medium
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
Translate the READMEOpendocumentation good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
asasemahmed/openboard#68 ·
Maintainers usually reply within 1 day
-
bug good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 72/100