Continued maintenance of ITU-Rpy

[brownericm]

I tried reaching out via email. @inigodelportillo Do you intend to continue maintaining this repository? It is being used in industry and there are several substantive changes to the ITU Recommendations over the past year. I would be willing to take over development or a broader team can be identified.

[petrushy]

I think this is a great library but would indeed need some maintenance and care as models change over time and some bugs have been identified. @inigodelportillo let us know if you would like to have help / support on this. It is of course possible to fork it but better to do a joint action.

[vianneylan]

@petrushy @brownericm The author does not respond for a time: do we take next step and fork it so that we can have continuation ?

[honglei]

Try https://github.com/DarrellPaul/ITU-Rpy ,but it cannot pass all test cases under:
https://www.itu.int/en/ITU-R/study-groups/rsg3/rwp3m/Validation%20Example/CG-3M3J-13-ValEx-Rev8.3.0.xlsx
(Validation examples for parts of Recs. ITU-R P.453-14, P.618-14, P.676-13, P.836-6, P.837-7, P.838-3, P.839-4, P.840-9, P.1510-1, P.1511-3, P.1623-1, P.1815-1, P.2145-0)

builtins.AssertionError: np.float64(52.823599016404465) != 52.8337206157614 within 0.01 delta (np.float64(0.010121599356935462) difference) : [P.618-14 A_Rain] row 81 lat=28.717 lon=77.3 f=29.0GHz el=48.2411705405115° hs=0.209383698952704km p=0.01% expected=52.8337206157614 got=52.823599016404465

[brownericm]

@inigodelportillo You're back! are you going to keep including the maps in the package? The higher resolution maps for P.2145 are very large.

[inigodelportillo]

@brownericm , I am not familiar with P.2145 and the itur package doesn't include this recommendation currently. Is it recommended as part of some of the other recommendations?

Given the formatting of the maps, I was planning on including them as part of the package. We could have some lazy-download system (e.g., the first time somebody uses a model-version, download the files if not present in a cache), but I am not sure if it's worth it.

[brownericm]

It's used in P.676-13. Off the top of my head I think Annex 2. I have it implemented on a branch in my fork, with a change to the reader and an extra utility script to download the pre-converted .npz files from zenodo. Each file is 30MB or more.

[brownericm]

We can close this issue, I'll do a PR when I get a chance tonight. I have a different implementation of 676, so you are free to just deny it if it's too much work to merge.