Is drc still maintained?

[eduardszoecs]

Is see open Pull Requests, Issues not answered, last commit 4 years ago, Out-dated CRAN version (compared to github).

IMHO it's the best and most-complete dose-response package out there... Should be getting some love...

[hreinwald]

Hi @eduardszoecs I started some re-factoring of the package today. Hope I will be able to launch a re-factored version soon.
if anyone wants to support or co-develop feel free to reach out to me. 😸
@Zhenglei-BCS maybe we can join forces here as well?

[hreinwald]

I started the re-factoring of the R package. You can find my re-factoring fork version here.
Feel free to check it out and test it yourself. The dev branch is highly experimental.

I submitted a first pull request for my first changes #46. This was only an initial clean up without changing anything in the source code of the R functions. I guess there will be more to come in the next days...
Stay tuned!

Note: In my fork I did not fully test main branch yet. So no promises that i did not break anything ;)

[hreinwald]

I have submitted the merge request #47 of my refactored drc version 3.3.0. You can install the beta version from here

[eduardszoecs]

Happy to join if you need help...
I see also some activity here: https://github.com/daniel-gerhard/drcTMB

[eduardszoecs]

Do you want to add claude as co-author ^^
It's quite a bit to review...

I'd let claude write tests to checks from the examples to check same results with the old version?

[hreinwald]

If you would run more unit tests and cross check with claude that would be fantastic @eduardszoecs 😻
I think the new claude model would deserve a spot in the author list.

Thanks for hinting me towards drcTMB. Will definitely check it out.

FYI: I have added the data from the drcData package directly now in the drc beta version 3.3.0.01, added more unit tests, vignettes and a first version of github docs and made sure that the devtools::check() runs smoothly now.

[Zhenglei-BCS]

I didn't realized I was mentioned, just saw it in my notification box. @hreinwald, happy to join you, I can add some vignettes on a few confusions in using the package when I got the capacity. I see the pull request hasn't been reviewed and accepted.

[eduardszoecs]

I think this PR is not reviewable (too many changes) and suggest a fork?

[hreinwald]

I think this PR is not reviewable (too many changes) and suggest a fork?

Agreed. Maybe after re-factoring and testing we just bump up the fork to a much higher version number e.g. 4.0.0 to indicate that a lot of the previous code was re-factored.