Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

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

Open
old2rng opened this issue Nov 27, 2024 · 0 comments
Assignees
Labels
bug Something isn't working

Comments

@old2rng
Copy link
Contributor

old2rng commented Nov 27, 2024

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)
@old2rng old2rng added the bug Something isn't working label Nov 27, 2024
@old2rng old2rng self-assigned this Nov 27, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant