ms-structural / ms-structural/femdesign-api

Change so that timber factors (and creep data) are applied to object instead of material

Open
#603 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

framework:grasshopper priority:unset type:improvement xml-schema
Dominant language
C#
Stars
51
Forks
29
PR merge metrics
No merged PRs in 30d

Description

I think the way we define timber factors and concrete data onto the material is strange, because this data is actually object-specific in FEM-Design. I think it should be defined when creating the object, and look something like this:
image

I understand the way it is done now is kind of based on the struxml schema, but the schema is not really logical in this case 🤔 What do you guys think? (This issue is originally from a user who couldn't figure out how it works)

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reviewing how timber factors and concrete creep data are currently defined on materials and how objects are created in the FEM-Design API. Compare that structure with the attached object-level example and the struxml schema; the work is done when these values can be defined for the relevant object without relying on material-level data.

Written by the indexing model from the issue text.

Assessment

Tech stack
csharp
Domain
api
Issue type
Refactor
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.