| Latest revision |
Your text |
| Line 28: |
Line 28: |
| | *June 19 studying the code to handle the unhandeled command *ElEMENT_SOLID. | | *June 19 studying the code to handle the unhandeled command *ElEMENT_SOLID. |
| | *June 20 studying the code to handle the unhandeled command *ElEMENT_SOLID. | | *June 20 studying the code to handle the unhandeled command *ElEMENT_SOLID. |
| − | *June 21 I more or less figured out how to handle the solid elements, I have to creat a solid struct where to store all the solid element properties parsed from the .key file then on the other side I have to creat functions to write the element as arb4, arb6 or arb8 . starting to develope the code today | + | *June 21 |
| − | *June 22 I have put a plan for developing ELEMENT_SOLID and added solid.h and solid.cpp to the buildig system.
| |
| − | *June 23 Developing Element Solid.
| |
| − | *June 24 Developing Element Solid.
| |
| − | *June 25 Developing Element Solid.
| |
| − | *June 26 on the side of parsing the element solid is ready no I need to figure out how to write it to an intermediate structure.
| |
| − | *June 28 strugling to add arb8 to the data base, in the code there seems to be multiple ways to do that.
| |
| − | *June 29 I wrote a prlimanry code to write the arb into the data base then adding all the arbs into a single reagion.
| |
| − | *June 30 tody is for writing the code from yesterday into the class Solid. we decided on different configuration. I wrote the class Arb and I was going to put inside a class Solid which will behave as a fake Bag of arbs then put Bot class and Solid inside a super calss Geometry.
| |
| − | *July 1 I wrote the code and submitted a pull reqest to check with mentors about which classes should I implement for dealing with the solid element.
| |
| − | *July 2 sick day.
| |
| − | *July 3 I updated the pull request with Arbs class, and did the necessary modifications for writing the arbs.
| |
| − | *July 4 submitted a small pull request related to case insensitive keywords. I was checking some examples from ls-dyna to plan on what to implement after element solid, I found the sloshing example has keywords that are not implemented like *MESH_SURFACE_ELEMENT and *ICFD_PART, although i didn't find anything on this commands in the documentation. but it's possible to convert them if we include these keywords and the elmements are almost like triangular shell elements.
| |
| − | *July 5 Implementd a Geomtry class to incapsulate the geometry of an LS-DYNA part.
| |
| − | *July 6 working on the Geomtry class.
| |
| − | *July 7 updated the caseinsensitve keywords pull request and did some test for conversion of special charachters using toupper() function. I also read some documentation to plan for future development.
| |
| − | *July 8 Working on Geometry class. and will update the pull request.
| |
| − | *July 9 Working on Geometry class.
| |
| − | *July 10 updated the pull request with Geomtry.write() function still need some work
| |
| − | *July 11 working on missing commands . found a bug realted to freeeing the Bot object it was getting freed twice. now everything is fine .
| |
| − | *July 12 I am working on a pull request to handle *ElEMENT_BEAM, *ELEMENT_DISCRETE , *ELEMENT_MASS, *SECTION_BEAM and *SECTION_DISCRETE.
| |
| − | *July 13 still stuck in yesterday's pull request and the Geometry class, it doesn't seem that I am naming the objects correctly or sometimes I name them twice.
| |
| − | *July 14 updated the pull request for Geomtry class.
| |
| − | *July 15 writing code to handle *PART_CONTACT *SECTION_BEAM *SECTION_DISCRETE *ELEMENT_MASS and I notecied that we need to have additional functions to read element and section properties similar to read_line_node_standard() function.
| |
