Matter_Engine: Add material mapping methods

[IsakNaslundBh]

Issues addressed by this PR

Closes #2900

• Add method for mapping properties from a set of pre-defined material maps on a set of Materials
• Add methods for mapping onto MaterialCompositiona and Takeoffs
• Add methods for getting mapped Takeoffs and Compositions from a list of IElementM

Test files

https://burohappold.sharepoint.com/:f:/s/BHoM/ElafUY8_5_dOs1UN37qQ1kQBFOo2qUahCMBTEbp2g7uEag?e=rRgCke

Changelog

Additional comments

[IsakNaslundBh]

@BHoMBot check compliance

[bhombot-ci]

@IsakNaslundBh to confirm, the following actions are now queued:

• check code-compliance
• check documentation-compliance
• check project-compliance
• check branch-compliance
• check dataset-compliance
• check copyright-compliance

[IsakNaslundBh]

@BHoMBot check compliance
@BHoMBot check null-handling

[bhombot-ci]

@IsakNaslundBh to confirm, the following actions are now queued:

• check code-compliance
• check documentation-compliance
• check project-compliance
• check branch-compliance
• check dataset-compliance
• check copyright-compliance
• check null-handling

[IsakNaslundBh]

@BHoMBot check compliance
@BHoMBot check null-handling

[bhombot-ci]

@IsakNaslundBh to confirm, the following actions are now queued:

• check code-compliance
• check documentation-compliance
• check project-compliance
• check branch-compliance
• check dataset-compliance
• check copyright-compliance
• check null-handling

[IsakNaslundBh]

@michaelhoehn this should be good to go for testing now. Happy to have a quick call if needed.

Will add UTs to this PR once the approach taken in the PR has been approved and agreed.

[kayleighhoude]

Finally got a chance to review this one- love the template, really simple to use. One issue on my end, when assigning a material from a traditional EPD dataset vs the concatenated one you provided, I received the following errors:

Is this because those datasets are missing the new material attribute?

[michaelhoehn]

I'm happy with the additions, but I think Kayleigh's observations should be addressed, likely in the LCA toolkit PR. I'm fine to see this merged personally, but I do find it interesting and somewhat concerning that a user may instinctually combine or "inject" another elementM upstream of the solver (which is what I'm assuming was done here, @kayleighhoude please correct me if I'm mistaken) which do not have mapped data, to begin with.

In this case the methods will produce a null value for anything that is not properly mapped (as they should) and produce typical results for those that have mapped data. I'll add some additional thoughts on the LCA PR referenced above to cover these cases. But perhaps there's some null handling to be added here?

[michaelhoehn]

Please see the comment here BHoM/LifeCycleAssessment_Toolkit#288 (review)

[michaelhoehn]

Branch naming inconsistencies have required me to fork this branch for compliance purposes FYI @FraserGreenroyd

[michaelhoehn]

@BHoMBot check core

[bhombot-ci]

@michaelhoehn to confirm, the following actions are now queued:

• check core

[michaelhoehn]

@BHoMBot check required

[bhombot-ci]

@michaelhoehn to confirm, the following actions are now queued:

• check code-compliance
• check documentation-compliance
• check project-compliance
• check core
• check null-handling
• check serialisation
• check versioning
• check installer

[bhombot-ci]

The check core has already been run previously and recorded as a successful check. This check has not been run again at this time.

[bhombot-ci]

The check installer has already been run previously and recorded as a successful check. This check has not been run again at this time.

[michaelhoehn]

@BHoMBot check documentation-compliance

[bhombot-ci]

@michaelhoehn to confirm, the following actions are now queued:

• check documentation-compliance

[michaelhoehn]

@BHoMBot check required

[bhombot-ci]

@michaelhoehn to confirm, the following actions are now queued:

• check code-compliance
• check documentation-compliance
• check project-compliance
• check core
• check null-handling
• check serialisation
• check versioning
• check installer

[bhombot-ci]

The check installer has already been run previously and recorded as a successful check. This check has not been run again at this time.

[FraserGreenroyd]

@BHoMBot check unit-tests
@BHoMBot check copyright-compliance
@BHoMBot check dataset-compliance

[bhombot-ci]

@FraserGreenroyd to confirm, the following actions are now queued:

• check unit-tests
• check copyright-compliance
• check dataset-compliance

[FraserGreenroyd]

@BHoMBot check ready-to-merge

[bhombot-ci]

@FraserGreenroyd to confirm, the following actions are now queued:

• check ready-to-merge

There are 8 requests in the queue ahead of you.

[FraserGreenroyd]

See here.