Rename TimeExtrapolationError to OutsideTimeIntervalError

[erikvansebille]

Now that we won’t support allow_timeextrapolation anymore in Parcels v4, the naming of the Error related to sampling out of the time interval is also not so appropriate anymore.

We could rename it to e.g. OutsideTimeInterval error, so make the linke with the fieldset.time_interval clearer

[Mixire]

1. Locate Current Error Definition

Identify the file(s) where the current error for “sampling out of the time interval” is defined (likely in the exceptions or error handling module).

Search the codebase for references to the existing error class to map all usages.

2. Decide on New Naming Convention

Rename the error class to OutsideTimeIntervalError (or as agreed upon by maintainers) to clearly link it to fieldset.time_interval.

Ensure the name aligns with the project’s general naming style for exceptions.

3. Update All References

Replace all occurrences of the old error name in the codebase with the new one.

Update related docstrings, inline comments, and logging messages to reflect the new terminology.

4. Adjust Tests

Locate unit/integration tests that check for the old error and update them to expect OutsideTimeIntervalError.

Ensure all tests still pass after the rename.

5. Documentation Updates

Update any developer or user-facing documentation mentioning the old error name, especially sections related to fieldset.time_interval and time extrapolation behavior.

6. Backward Compatibility Check

Since Parcels v4 drops allow_timeextrapolation, confirm that no legacy code paths still reference the old error.

If needed, provide a temporary alias from the old error name to the new one with a deprecation warning for developers migrating from v3.

7. Pull Request Submission

Open a PR referencing Issue #2145.

In the PR description, summarize:

Old error name and its limitations

New name and its connection to fieldset.time_interval

Test/documentation updates included.

[vicenzodarezzo]

Hey, I'm a new contributor looking for a good first issue to get to know the project. I'm leaving this comment to flag my interest in working on this issue, as recommended in "Contributing to Parcels". I'll start by forking the repository and setting up the development version locally.

[VeckoTheGecko]

Hey @vicenzodarezzo ! Thanks for the interest here - always happy to have new contributors 🙌 - that's how I got started with the project too. Just a note to make sure when browsing the docs to use the v4-dev version https://docs.oceanparcels.org/en/v4-dev - but they're not too different from the instructions in our latest documentation version.

Let me know if you have any further questions - happy to help :)

PS: Just a heads up - our developer workflow (installation instructions and important commands) will be updated in the coming weeks once #2205 is fixed and we have native Pixi support for environment management. This won't affect the old developer workflow, but will introduce an alternative (easier) developer workflow.

[VeckoTheGecko]

Hey @vicenzodarezzo , will you be attending the Parcels 10 year anniversary event online from 1-3 Oct? We will have a virtual room which will be used to sprint on Parcels which you might be interested in.