ENH: Added Crop and Clip Methods to Function Class

[Rickisterr]

Pull request type

• Code changes (enhancement, features)

Checklist

• Lint (black rocketpy/ tests/) has passed locally
• All tests (pytest tests --runslow) have passed locally
• CHANGELOG.md has been updated (if relevant)

Current behavior

RocketPy Function class has no methods to crop or clip the input and output values of a function to a specific range.

This PR is related to the following issue:
ENH: give me a scissor or apply Function.clip and Function.crop - #546

New behavior

It is now possible to specify a limited range of values for input or output variables for an object created from the Function class at any point after initialization of the object by using the crop and clip methods respectively. These methods work for any type of allowed Function source.

Breaking change

No

Additional information

To use the new methods, some examples are provided below to exemplify their syntax in brief:
f.crop([(-1, 1), (-2, 2)]) - For two input variables
f.clip([(-2, 2)]) - For output variable

[Gui-FernandesBR]

WE no longer use black, can you please run make format so we can review the PR faster?

[Rickisterr]

All required changes have been updated. Thank you!

[Gui-FernandesBR]

Great PR! We will review this implementation as soon as possible

[Copilot]

Pull Request Overview

This PR introduces new crop and clip methods to the Function class, enabling users to restrict input and output ranges of functions. Key changes include new test cases for 1-D and 2-D functions, modifications in the Function class to implement cropping and clipping behaviors, and an updated CHANGELOG entry.

Reviewed Changes

Copilot reviewed 3 out of 3 changed files in this pull request and generated 2 comments.

File	Description
tests/unit/test_function.py	Added tests for crop and clip methods with various input scenarios, including handling None values for unconstrained axes.
rocketpy/mathutils/function.py	Implemented crop and clip methods, updating set_discrete and interpolation boundaries accordingly.
CHANGELOG.md	Added an entry documenting the enhancement.

[Copilot]

Consider updating the crop() docstring to clarify that passing None for a dimension means no cropping constraint on that axis, as illustrated by the example.

[Copilot]

[nitpick] Review the constant-function logic in the clip() method; the branch checking for NUMERICAL_TYPES on a callable source may be ambiguous. Consider refactoring this logic to clearly distinguish constant functions from other callables.

Suggested change

	elif callable(self.source):
	if isinstance(self.source, NUMERICAL_TYPES):
	try:
	if self.source < y_lim[0][0]:
	raise ArithmeticError("Constant function outside range")
	if self.source > y_lim[0][1]:
	raise ArithmeticError("Constant function outside range")
	except TypeError as e:
	raise TypeError("y_lim must be same type as function source") from e
	else:
	f = self.source
	self.source = lambda x: max(y_lim[0][0], min(y_lim[0][1], f(x)))
	elif isinstance(self.source, NUMERICAL_TYPES):
	try:
	if self.source < y_lim[0][0]:
	raise ArithmeticError("Constant function outside range")
	if self.source > y_lim[0][1]:
	raise ArithmeticError("Constant function outside range")
	except TypeError as e:
	raise TypeError("y_lim must be the same type as the function source") from e
	elif callable(self.source):
	f = self.source
	self.source = lambda x: max(y_lim[0][0], min(y_lim[0][1], f(x)))