bunjii / ptk Goto Github PK

I noticed in the Node, Elem Classes that an Element Class instance carries node class instances, while a Node Class instance carries element class instances. This is kind of a recursive owning each other, like node 1 owns element 1 owns node 1...

I think the usual solution is not to own entities of Class instances in another Class instance but to reference it by ID. I'll look into the code (mainly Assemble Component, Functions ,Node & Element Class) to see if improvement is possible for this.

It's rather a To-Do than an issue...

I'll make the mock-up of this component to connect our Assemble model to Karamba's Analyze Th. I component.

Add Logics

gh file for download
ptk_test_truss_small.zip

something seems gone wrong with the numbering of node element.

related to #43 , current situation is like this, when you read a CSV file with comma decimal separator in a locale employing period decimal separator.

please take this card in your Project (John's case: https://github.com/bunjii/PTK/projects/4 ) from "add cards" on the top-right area of the page into either of your "to-do", "in progress" or "done" column.

task:
to learn general concept of git and GitHub with one of the sources below (or of your preferred alternatives):

• Git Essential Training by Kevin Skoglund (Beginner Level) 6h25m
  https://www.lynda.com/Git-tutorials/Introduction/100222/111245-4.html

• Git Essential Training (Intermediate Level) duration: 1h21m
  https://www.lynda.com/Git-tutorials/Up-Running-Git-GitHub/409275-2.html

• Git Tutorial for Beginners: Command-Line Fundamentals
  https://www.youtube.com/watch?v=HVsySz-h9r4&authuser=1

• Add check: If all corners are on same side of cut, no cut cut is valid
• Report???
• Does not identify plane/curve intersection-> Change to -Curve

download test_truss.gh data:
ptk_test_truss.zip

I came across a problem in materializer when I made a primitive truss model. The orientation of cross-section seems inappropriate. I figured out this happens as the "yz plane" data in materializer is not set correctly. Let me know @johnhaddalmork if you allow me to mend some part in materializer to fix this, or if you will mend this by your own? I think I'll be able to tackle this on Tuesday 20th.

in the same model as in issue #35 , I also noticed that the element id increases everytime I reload the file, and that sometimes the sub-element is not assigned to the top and bottom chord of truss (See the edges of those elems).

test issue
test issue
test issue

Relevant when selecting node details:

to be implemented as Node function

urgent.

Unlike Element or Node, Material Property's class instance owns a lot of properties. Because of this, it will become inefficient or will have a long code when you check whether the material properties are the same or not by comparing values property by property. (Comparison will be needed when you register materials in the Assemble component to avoid duplication).

Sorry Marcin, I need to work in the master, but the two files you updated some hours ago are conflicting with those in my branch. I downloaded those two manually, so it'll be recovered.

• PTKClasses.cs
• PTKTest.csproj

should be the center of its parent.

European countries use comma for the decimal separator, while we(JP) as well as US, UK use period for it. No solution for it at the moment about how to deal with it (input/output) but need to be aware of it.

I think we need to be more clear about priority list of member. Current "materializer" has an input for list of integer but I can't imagine a way it works. Hence, the followings:

Priority list will be introduced in order to determine which member(s) will be cut against others at each node. We have decided at Ver. 0.5 we will focus on this way only, at Ver. 1.0 we will start think about the opposite way (= priority will be determined according to the result of structural analysis.)

Suppose we have a simple truss structure, and we have a priority list shown at the right side of the page 1 (below). We can expect the result cut shown at the bottom of the page 1.

In order to achieve this, there are two options occurred to me. One is to define this at "materializer" component, and the other at "Assemble Model" component. For the former way, the materializer will have an input (type: item, integer) and for the latter, we don't need priority list in the materilizer but instead we will need a text item input in the "assemble model" component.

I don't really have preference for this, but I would like to fix it. Let me know your opinion, so we can go on.

Description:

The composite cross-section class as well as the composite cross-section component.
The class will inherit <> CrossSection class.

It will have properties such as:

• List
• Alignment

methods such as:

• GetHeight()
• GetWidth()

The component will ...