Tom Vo

@lee1043 Thanks for trying to this out and providing an example script! I'll debug the stack trace.

Hi @oliviermarti, thanks for your interest in this feature. I've had minimal time to work on it and plan to ramp up development soon. I don't have a set timeline...

> @tomvothecoder it looks like when custom season go beyond calendar year (Nov, Dec, Jan) there is error as follows. > > ```python > import os > import xcdat as...

After thorough testing, I actually think this PR is close to complete.

Hey @oliviermarti, @arfriedman, and @DamienIrving, would any of you be interested in checking out this branch to test the custom season functionality? If so, please check out our [contributing guide](https://xcdat.readthedocs.io/en/stable/contributing.html#version-control-git-and-github)....

> @tomvothecoder : this version seems perfect to me :-) > > (I've got the branch feature/416-custom-season-span : correct ? ) > > Thanks !! > > I join my...

> On real data, version 0.7.1 returns a result, but a wrong result. It's hards to have an easy check on real data. Hence this academic test case. > >...

As discussed in our meeting today (06/05/24), we decided that @lee1043 will open a PR with his function from the PMP [commented](https://github.com/xCDAT/xcdat/issues/576#issuecomment-2145739246) above since this feature seems to be useful...

Hi @pochedls and @chengzhuzhang, here's what I came up with based on your comments. ### Suspected Root Cause As Jill pointed out in #143, `data_vars="all"` concatenates the `time` dimension to...

Just opening this issue to have it in our backlog for further consideration