Skip to content

Fuction set_finite_infinite_transition() is neglected if irrelevant_runouts_dropped() is used #136

@old2rng

Description

@old2rng

Describe the bug
When a users sets a specific value for the transition zone by calling set_finite_infinite_transition() and the data set has two pure run-out levels (being at the lowest load levels), the fatigue_data class is initialized again resetting the transition zone by default value.

To Reproduce
Easy to reproduce. Just use a data-set containing 2 pure run-out load levels and set the function 'set_finite_infinite_transition()' to a arbitrary value. After running any analyzer (e.g. Probit, Elementary) the .finite_infinite_transition value has changed.

Expected result
.finite_infinite_transition should not change. Therefore pass the value to the function.

Something like this:

return FatigueData(df).set_finite_infinite_transition(self._obj.finite_infinite_transition)

Instead of just this:

return FatigueData(df)

Metadata

Metadata

Assignees

Labels

bugSomething isn't working

Type

No type

Projects

No projects

Milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions