BHoM / BHoM/LifeCycleAssessment_Toolkit

LCA Toolkit clean up discussion notes

Open
#302 0 comments 0 reactions 0 assignees View on GitHub
type:question
Dominant language
C#
Stars
26
Forks
8
Avg merge
2d 17h
Merged PRs (30d)
1

Description

#### Description:

Notes from a discussion with @mchaf @shivanierambaran @IsakNaslundBh @kayleighhoude regarding toolkit cleanup during our PR closure event. Notes below should be ticked off as addressed in the coming sprints/milestones and this issue should be closed when all points have been discussed.

#### Notes from the discussion
- [ ] Refactor of EPD class (full sprint, planning session required)
- [ ] Align project scope fields based on desired database host metadata requirements
- [ ] Raw material LCA composition is used as an input often in lieu of EPD. Similar to TM65 magic (@kayleighhoude @IsakNaslundBh)
- [ ] https://github.com/BHoM/LifeCycleAssessment_Toolkit/issues/204
- [ ] https://github.com/BHoM/LifeCycleAssessment_Toolkit/issues/162
- [ ] Strategy for reporting in general. How do we want to display and store results for data visualisations downstream (planning session required)
- [ ] Documentation refresh
- [ ] Sample scripts added to OS repo and all documentation used externally (@mchaf)
- [ ] Description refresh for all methods and updation with the API
- [ ] https://github.com/BHoM/LifeCycleAssessment_Toolkit/issues/252 (@kayleighhoude to check)
- [ ] https://github.com/BHoM/LifeCycleAssessment_Toolkit/issues/286 (@IsakNaslundBh to check)

#### Other outcomes from the discussion
- [x] Moved this issue https://github.com/BHoM/BHoM/issues/1464 (FYI @FraserGreenroyd )

Contributor guide

Open the contributing guide

Research direction

No files, tests, or entry points are named. Start by reviewing linked issues 204, 162, 252, and 286 alongside the checklist, then identify which items are still open; done means all discussion points have been addressed and the issue can be closed.

Written by the indexing model from the issue text.

Assessment

Domain
tooling
Issue type
Refactor
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
15/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.