unrealsolver / frame3dd Goto Github PK

• Add status badge to README.md

• Build the app using default GH Actions tools
• Add status badge to README.md

Structs are easier to work with, and this will allow us to map them to JSON and back later.

Subtasks:

• #7
• #12

Frame data:

• Nodes list
• DoF
• Edges list

Load case data:

• Point loads
• Uniform loads
• Trapezoidal loads
• Internal concentrated loads
• Temperature loads
• Prescribed displacements
• Dynamic load cases

Simulation options:

• Simulation options

Root struct:

• Root struct

There are should be a single data type with all relevant data represented as a struct. This will allow easier JSON serialization.

Static data:

• As an option, include input data
• Node displacements (global)
• Frame element end forces (local)
• Frame element transerverse displacements (local) see 'if' files
• Reactions (global)
• RMS REE

Modal:

• Peak frame element internal forces (local)
• Modal Analysis masses
• Nodal masses (diagonal of the mass matrix / global)
• Natural frequencies & mass normalized mode shapes
• Modes (frequencies)

Related to:

• #5

Might not be immediately required, because original code assumes that array index == uid. And arrays intentionally have blank spaces, like [null, null, node(2), null, node(4), ...].

3dd and csv i/o formats aren't user friendly enough, JSON have much better user experience. That's why adding JSON i/o is one of the major goals.

• Read input data from JSON
• Write simulation results to JSON

Nodes and Edges follow pattern of having size and data properties in the struct. It's better to refactor LoadcaseData to work the same way. And also because nL variable should not be required.

• Point force arrows are visible on the chart
• Arrow starts at deformed mesh node position
• Arrow sizes (length) are normalized accordingly with the scale of mesh and other point forces
• Write numerical value of the force

Currently, gh-pages branch is used as an intermediate storage for the files, which is not required and just adds garbage files to the git history.

Tasks:

• Remove gh-pages branch completely when the fix is deployed

There should be a convenient way to integrate with Frame3DD into other pieces of software. Existing approach with run_kernel isn't good enough, because tight coupling to files io, argc/argv, does not return any values. In order to make possible implementation of JSON-io, we should consider this:

• Return Result with ExitCode
• Handle Frame, LoadCases and Options structs as input
• Csv, txt, matlab and other IO should be a compile-time option
• #16
• #17

Acceptance criteria:

• Code (re)written in Rust language
• Code covered with tests
• main.c should not be removed and should work as before

Requirements:

• New CLI must be similar to other modern CLI programs
• NO backward/forward required
• NO colors
• Ability to pick desired output format(s)
• Sane defaults
• Tests

Where to start:

• main.c

• Make a release on some condition (tag?)
• Package .deb
• Package linux .tar.gz build
• Build documentation

• #11
• #10
• Run lint on each main build
• #3