Feature/subset_years #1023
Feature/subset_years #1023
Conversation
sarah-hlsn
left a comment
sarah-hlsn
left a comment
There was a problem hiding this comment.
Function and tests look great to me, made a minor suggestion for the docstrings. It might be worth it to add functionalities to filter by date, which could be useful for some users, though admittedly not to the same degree as filtering by year so we may want to avoid spending more time on this.
Otherwise, ready for merge from my side!
climada/hazard/tc_tracks.py
Outdated
| year = date_array.astype("datetime64[Y]").item().year | ||
| except AttributeError: | ||
| raise ValueError( | ||
| f"Invalid date format in track {i}, could not extract year." |
There was a problem hiding this comment.
We could consider to use id as a fallback since the id strings provided by IBTrACS start with the year. Then again this would only work for IBTrACS (or at least I don't know for other datasets) so this may overcomplicate things.
There was a problem hiding this comment.
I would rather not, for the reason you just mentioned, that it would only work for IBtracks. But, I will check the most common tracks source and see if the method works for them. So far, Emmanuel, chaz, FAST works. The problem is that the time vector has different formats between different sources... So the way I used to access "year" may not work for all of them; I will double-check.
climada/hazard/tc_tracks.py
Outdated
|
|
||
| return out | ||
|
|
||
| def subset_year(self, start_year: int = None, end_year: int = None): |
There was a problem hiding this comment.
This is such a useful new function to have! I am wondering whether it could be worthwile to extend the functionality for the user to also be able to select based on months and days. It would make this function more complex but give much more flexibility for a variety of applications...up to you @NicolasColombi
There was a problem hiding this comment.
Thank you @sarah-hlsn! Indeed it would be a good idea, and in principle, it should not be much more work to implement. I will carve out some time to do it.
Co-authored-by: Sarah Hülsen <49907095+sarah-hlsn@users.noreply.github.com>
Thank you Sarah. By date do you mean being able to select in this format: e.g. from 2025-02-15 to 2027-08-03 ? |
|
Yes, I was thinking both could be useful! (YY-mm-dd format, as well as filtering across years by month) |
|
@sarah-hlsn I updated the function as discussed: you can now select by date, filter by year or month or day or a combination of those. The tests are modified accordingly. Let me know if you can have a quick look 🙃 |
|
Thanks for implementing these changes, looks good to me! |
Changes proposed in this PR:
This PR adds a function that allows to subset tracks by year after having them loaded into a TCTtracks object, as not all methods to load tracks allow filtering by year (e.g.
from_simulations_emanuel())-
climada.hazard.tc_tracks.TCTracks.subset_year()-
climada.hazard.test.ttest_c_tracks.TestFuncs.test_subset_year()PR Author Checklist
develop)PR Reviewer Checklist