Adding AkimaMonotonicInterpolation

[wg030]

I added the new interpolation type AkimaMonotonicInterpolation and tested the implementation by comparing the results with the results of working code for Akima splines. I also ran the tests for @testset "Monotonic" successfully and checked the plots created by test/plots/monotonic/sanity.jl

[codecov[bot]]

Codecov Report

Base: 87.10% // Head: 87.17% // Increases project coverage by +0.06% :tada:

Coverage data is based on head (7e51dff) compared to base (d38ae2e). Patch coverage: 97.95% of modified lines in pull request are covered.

Additional details and impacted files

```diff @@ Coverage Diff @@ ## master #522 +/- ## ========================================== + Coverage 87.10% 87.17% +0.06% ========================================== Files 28 28 Lines 1846 1856 +10 ========================================== + Hits 1608 1618 +10 Misses 238 238 ``` | [Impacted Files](https://codecov.io/gh/JuliaMath/Interpolations.jl/pull/522?src=pr&el=tree&utm_medium=referral&utm_source=github&utm_content=comment&utm_campaign=pr+comments&utm_term=JuliaMath) | Coverage Δ | | |---|---|---| | [src/monotonic/monotonic.jl](https://codecov.io/gh/JuliaMath/Interpolations.jl/pull/522/diff?src=pr&el=tree&utm_medium=referral&utm_source=github&utm_content=comment&utm_campaign=pr+comments&utm_term=JuliaMath#diff-c3JjL21vbm90b25pYy9tb25vdG9uaWMuamw=) | `94.88% <97.95%> (+0.30%)` | :arrow_up: | Help us with your feedback. Take ten seconds to tell us [how you rate us](https://about.codecov.io/nps?utm_medium=referral&utm_source=github&utm_content=comment&utm_campaign=pr+comments&utm_term=JuliaMath). Have a feature suggestion? [Share it here.](https://app.codecov.io/gh/feedback/?utm_medium=referral&utm_source=github&utm_content=comment&utm_campaign=pr+comments&utm_term=JuliaMath)

:umbrella: View full report at Codecov.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.

[wg030]

@mkitti Thanks for reviewing my contribution! I wrote down my thoughts on your comments. For now, I will correct the spelling misstakes and we can discuss the other suggestions.

[mkitti]

ready to merge?

[wg030]

ready to merge?

Today I thought about adding some convenience constructors for all those monotonic interpolations types, too, which I might do in the next few days. But if you want to merge this PR already, go ahead, it is already mergeable!

[mkitti]

ready to merge?

Today I thought about adding some convenience constructors for all those monotonic interpolations types, too, which I might do in the next few days. But if you want to merge this PR already, go ahead, it is already mergeable!

Could you sketch out the thoughts for convenience constructors in an issue so we can discuss?

[wg030]

Could you sketch out the thoughts for convenience constructors in an issue so we can discuss?

Sure! I would suggest that we merge this one and I will open a new issue for the discussion of adding convenience constructors outlining my idea!

[mkitti]

merged

[wg030]

Thanks for merging, @mkitti

Do you know how long it will take until updating the package with (@v1.8) pkg> up will apply theses changes, too? I know that (@v1.8) pkg> add Interpolations#master will do the job, but I always wondered how the mechanism of the official update process works. Honestly, I thought that changing version = "0.14.5" to version = "0.14.6" in Project.toml within the PR like I did would already trigger the official update,too. Turns out that was a false assumption 😂

[mkitti]

I need to register it.

[wg030]

I need to register it.

Alright, I see. It's rather a manual process that an automatic one. Now I understand why some packages are officially updated half a year or so later after their update on github.

[dkarrasch]

If that's the case, then you could file an issue or comment on the last commit to master and suggest registering the current state. The registration process is highly automated and efficient, but it requires a maintainer to launch it.

[wg030]

If that's the case, then you could file an issue or comment on the last commit to master and suggest registering the current state. The registration process is highly automated and efficient, but it requires a maintainer to launch it.

Ah ok, thanks for the clearfication. I think i got it now. It's bascially an automated process which is triggered by the maintainer by commenting

@JuliaRegistrator register

to the latest commit, isn't it? At least that's what happened here and now (@v1.8) pkg> up seems to be up to date with the content of this github repo.

[JuliaRegistrator]

Error while trying to register: Register Failed @wg030, it looks like you are not a publicly listed member/owner in the parent organization (JuliaMath). If you are a member/owner, you will need to change your membership to public. See GitHub Help