-
Notifications
You must be signed in to change notification settings - Fork 26
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
Error in find_rainflow_ranges for boundary cases #14
Comments
Hey @abhijeet-pandey, Since you mention "arbitrary": Are there more cases which gives error than if an array does not contain any cycles? For the case of no cycles in the array, there should at the very least be a different error (FatpackError?) and more descriptive error message. A better solution would perhaps be if an empty array was returned since there are no cycles. I will think a bit more on this issue, but I welcome any help or comments. Best regards, |
I agree, that in case of no cycles - it should return empty array or None. |
Just thinking out loud but would a strain history of |
Half cycle as per the pagoda method.
…On Mon, 26 June 2023, 19:43 wweijtje, ***@***.***> wrote:
Just thinking out loud but would a strain history of np.array([1,2,3,4,5]
result in a single residual/half cycle as there is a cycle initiated but
not closed.
—
Reply to this email directly, view it on GitHub
<#14 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AF3LUVYPYRRDJ67XDK3NXOLXNFKVBANCNFSM6AAAAAARNPHLZI>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
find_rainflow_ranges gives error for arbitrary numpy array. For example if the array doesn't contain any cycles - fatpack.find_rainflow_ranges(np.array([1,2,3,4,5]), return_means=True, k=2**14) produces error.
The text was updated successfully, but these errors were encountered: