Rename samples field of WeightedIntervalTraining to points and clean tstops_loss logic

[sathvikbhagavan]

Renaming would be consistent with other strategies StochasticTraining, QuasiRandomTraining etc. as it contains the number of points.

Cleaning up tstops_loss to avoid redundant function evaluation.

[ai-maintainer]

AI-Maintainer Review for PR - Rename samples field of WeightedIntervalTraining to points and clean tstops_loss logic

Title and Description 👍

The Title and Description are clear and concise

The title and description of the pull request are clear and concise. They effectively communicate the purpose of the changes, which is to rename the `samples` field of `WeightedIntervalTraining` to `points` and clean up the `tstops_loss` logic. The renaming is consistent with other strategies and the cleaning up is done to avoid redundant function evaluation.

Scope of Changes 👍

The changes are narrowly focused

The changes in the pull request are narrowly focused. The author is primarily addressing two specific issues: renaming the `samples` field of `WeightedIntervalTraining` to `points` and cleaning up the `tstops_loss` logic. These changes are related and seem to be part of a single cohesive effort to improve the codebase.

Documentation 👍

All new functions, classes, or methods have appropriate docstrings

All newly added functions, classes, or methods have docstrings describing their behavior, arguments, and return values. There are no functions, classes, or methods in the diff that need docstrings.

Testing 👎

The description does not describe how the author tested the changes

The description does not describe how the author tested the changes. It primarily focuses on explaining the purpose of the changes rather than providing details about the testing process. It would be beneficial to include information about the testing process in the description.

Suggested Changes

• Please provide information about how you tested these changes. This could include the specific test cases you ran, any edge cases you considered, and the results of the tests.

• Please ensure that all tests pass after your changes, including any existing tests that may be affected by your changes.

• Please consider adding new tests to cover the changes you have made. This will help ensure that future changes do not unintentionally break this functionality.

Reviewed with AI Maintainer