Welcome to FatPy Discussions!

[Vybornak2]

👋 Welcome!

We’re using Discussions as a place to connect with other members of our community. We hope that you:

• Ask questions you’re wondering about.
• Share ideas.
• Engage with other community members.
• Welcome others and are open-minded. Remember that this is a community we
  build together 💪.

To get started, comment below with an introduction of yourself and tell us about what you do with this community.

[gokberkozcicek]

Hi All,

I have some thoughts regarding fatpy.

The scope of fatpy must be clearly defined. The following questions should be addressed:

Which operating system(s) will be targeted?

What is the overall scope of the tool?

What features will fatpy include when it's completed, say five years from now?

There are many SN and EN methods for fatigue assessment. Which of these approaches will be included in fatpy?

Will fatpy support industrial standards such as FKM or VDI? These methods should be clearly defined, possibly by other working groups.

Fatigue assessment may require a large amount of stress or strain input. Therefore, the I/O format of fatpy is crucial when defining the boundaries of the core structure. Classical string or JSON-based inputs may lead to memory issues. HDF5 or a custom memory-mapped file format could be considered as alternatives.

Which UI framework will be used? (e.g., Qt, wxWidgets, FLTK)

Additionally, an abstract mechanism is needed for fatigue method and input definitions.

Finally, benchmark studies using both open-source and commercial fatigue codes, such as PyLife and FEMFAT, should be conducted before beginning the design of the Fatpy structure.

Regards,

[Vybornak2]

Hello @gokberkozcicek,
you raised a good questions here, so let me address few of your questions.

Scope:

Scope of the project is yet to be defined, because we are in early development phase.
Project is being developed under the FABER initiative. So it depends on the currently forming group what will get implemented.

Current work:

We are in Architecture design phase. At this moment comparison analysis is taking place to design meaningful structure of the package. We are also estabilishing communication channels, documentation and other tools to streamline the contribution and collaboration.

We are also looking for contributors, members of FABER to help us reach our common goals.

What has been estabilished:

1. Not a sovler, but a library of granular, vesatile methods related to Fatigue evaluation
2. System agnostic
3. No GUI in early development states
4. Will utilized .hdf5 and VMAP format
5. FEM common files reading is not a goal, but might get included through 3rd party packages / options

Discussions:

Since we want public engagement, here are the discussions for the topics:
Methods to implement: #16
Norms to implement: #15

[Vybornak2]

@gokberkozcicek Further update on methods in #16