Progress note:

The new code was able to run the demo notebook without noticeable error, but with differences in result metrics.

A rigor test (run the code for all CMIP5/6 models/realizations) conducted.

1. Calendar-related error for non-standard calendar using models is found.
2. Some differences in the results are found. (Some sensitivity is not surprising because numbers used for the ratio (EWR) are very small.)

Code revision:

1. To avoid date comparison error from non-standard calendar using models, more simple and straightforward date comparison is applied. It is confirmed the error from the non-standard calendar models is resolved.
2. Common grid is changed from uniform grid to Gaussian grid to make the xCDAT code more consistent to the CDAT/CDMS version.

Next step:

• Another rigor test (run the code for all CMIP5/6 models/realizations) is launched. Its result will be analyzed once the test run is completed.
• Custom season capability when crossing calendar year is not been fully tested, and there to be potential issue (maybe using discontinued months, which could affect to NDJFMA season) → There should be no issue with custom season because for MJO it sub-slice segment using length of segment from the starting day of each year. (here)

• Usage of more consistent grid (uniform --> Gaussian) did not dramatically changed results (Compare below with above, which are for first ensemble members of CMIP5 (upper row) and 6 (lower row) models).

• CDAT vs xCDAT results seem to be acceptable (with high correlation and p<0.05), but more investigation for a few outliers would be helpful because their diagnostics fields are looking like identical (see second below figure).

• Progress note: after f455307, result of demo notebook 5 became much more consistent than before.
• The 3rd round of the rigorous test (running across all CMIP5/6 models) is in progress.

The above fix completed resolved the inconsistency! The 3rd round of he rigorous test results below.

• East West Power Ratio:

• East Power:

• West Power:

@acordonez I believe this PR is ready. Can you please try install code in this PR and run the demo 5 notebook to see if that works okay to you as well?