Matter_Engine: Improve Density Management for Physical materials

[IsakNaslundBh]

NOTE: Depends on

BHoM/BHoM#1443

Issues addressed by this PR

• Align with Density added to Material
• Add methods for extracting Density from a set of IDensityProviders
• Add method to set density to a material based on its Properties
• Update Material Create methods to scan Properties used to create for Density

Test files

https://burohappold.sharepoint.com/:f:/s/BHoM/Eg7Y5NfGykJKr5Bc1wfki6ABOXhTCqmW-pr3oNrYvFzKYA?e=tJxtni

Changelog

Additional comments

[IsakNaslundBh]

@BHoMBot check compliance
@BHoMBot check null-handling
@BHoMBot check unit-tests

[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
• check unit-tests

[IsakNaslundBh]

@BHoMBot check unit-tests

[bhombot-ci]

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

• check unit-tests

[IsakNaslundBh]

Have investigated the failing UTs for VolumetricMaterialTakeoff and MaterialComposition and both boils down to the same reason for the failure. Both failing cases are that the density is set to 7850 when run on this branch, while on main the non-existing value returned is 0:

Creating a composition or takeoff straight from a structural material it is valid to pass the density to the physical material, hence the change in behaviour is expected and an improvement.

Will for those reasons regenerate those UTs to what is returned on this branch.

[IsakNaslundBh]

@BHoMBot check unit-tests

[bhombot-ci]

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

• check unit-tests

There are 2 requests in the queue ahead of you.

[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

There are 2 requests in the queue ahead of you.

[IsakNaslundBh]

@BHoMBot check versioning

[bhombot-ci]

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

• check versioning

[bhombot-ci]

@IsakNaslundBh just to let you know, I have provided a check-installer result to this Pull Request as it was detected to be linked to other Pull Requests in a series. The comment which triggered this check came from @IsakNaslundBh on BHoM

[IsakNaslundBh]

@BHoMBot check unit-tests

[bhombot-ci]

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

• check unit-tests

[IsakNaslundBh]

@BHoMBot check versioning

[bhombot-ci]

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

• check versioning

[bhombot-ci]

@IsakNaslundBh just to let you know, I have provided a check-versioning result to this Pull Request as it was detected to be linked to other Pull Requests in a series. The comment which triggered this check came from @IsakNaslundBh on BHoM

[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

There are 9 requests in the queue ahead of you.

[IsakNaslundBh]

@BHoMBot check null-handling
@BHoMBot check serialisation
@BHoMBot check installer

[bhombot-ci]

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

• check null-handling
• check serialisation
• check installer

There are 10 requests in the queue ahead of you.

[IsakNaslundBh]

@BHoMBot check core

[bhombot-ci]

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

• check core

There are 17 requests in the queue ahead of you.

[al-fisher]

Approving based on review and commentary in oM PR - see BHoM/BHoM#1443

[al-fisher]

@BHoMBot check ready-to-merge

[bhombot-ci]

@al-fisher to confirm, the following actions are now queued:

• check ready-to-merge

There are 2 requests in the queue ahead of you.