In cases like in the following this height_change outputs a negative value which in turn causes an error in the return function:
This is because for the roll_pass.height PyRolL only looks at the tip depth of the groove and if that is grater than the incoming profile it thinks, that both dont touch at all so no contact length would be there.
Proposed Solution
As the picture above shows though there would logically be a contact_length.
Would it be feasible, to handle the contact length calculation differently in these cases, by looking at the intersection of groove and in_profile instead?
The contact_length is currently calculated like this: https://github.com/pyroll-project/pyroll-core/blob/93bfbaf21d057b63e7d5023491470a41ca0b49d6/pyroll/core/roll_pass/hookimpls/roll.py#L11-L14
Problem
In cases like in the following this height_change outputs a negative value which in turn causes an error in the return function:
This is because for the roll_pass.height PyRolL only looks at the tip depth of the groove and if that is grater than the incoming profile it thinks, that both dont touch at all so no contact length would be there.
Proposed Solution
As the picture above shows though there would logically be a contact_length. Would it be feasible, to handle the contact length calculation differently in these cases, by looking at the intersection of groove and in_profile instead?
P.S.: The Error that is output with the above: