-
Notifications
You must be signed in to change notification settings - Fork 3
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
princurve 2.0.2 #20
Comments
Dear Robrecht,
Thanks for letting me know; I'll prepare some updates to analogue. I'm
unlikely to have analogue ready to submit to CRAN before August as I am
travelling a lot this summer for work and vacation. Will something change
on CRAN as of July 1st that will result in analogue failing checks - I will
be out of the office for a month from June 30th so if there's going to be a
problem with CRAN I can be a bit more proactive or spend some of my flight
time getting the in devel version of analogue ready to go.
All the best and thanks for maintaining the package - I know that it had
been orphaned some years back but I wasn't in a position to take on further
coding activities at the time!
All the best
Gavin
…On Tue, 12 Jun 2018 at 10:52, Robrecht Cannoodt ***@***.***> wrote:
Hello Gavin @gavinsimpson <https://github.com/gavinsimpson>,
princurve 2.0.2
<https://cran.r-project.org/web/packages/princurve/index.html> was just
pushed to CRAN. I notice your package uses princurve and wish to notify
you of the changes so you can update your package accordingly.
I believe what is relevant for you is that get.lam has been renamed to
project_to_curve, in order to match the name of the function better with
what its purpose is. In addition, the input argument and output variable
tag has been renamed to ord.
The function get.lam still exists in the package, for now, as not to
break analogue, but get.lam will be deprecated on July 1st and later on
removed.
If you have any remarks or questions, feel free to let me know!
Robrecht
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#20>, or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAfaiEwC_rboAOkPcfsqrPNTs9AAghuIks5t7_HFgaJpZM4Uky-8>
.
--
Gavin Simpson, PhD
|
There are but a couple of places where the |
I think the changes will indeed be fairly minimal. It's just substituting Are there any features you would like to see in |
Hello @gavinsimpson and @jarioksa, I wish to move forward with deprecating Kind regards, |
Hello @gavinsimpson and @jarioksa,
Robrecht |
Thanks @rcannood I got the email from CRAN this morning about the change. I'll be dealing with this later in the week. |
… get.lam(), replacing it with project_to_curve() (Issue #20 )
This is now fixed and is on CRAN. Thanks @rcannood |
Hello Gavin @gavinsimpson,
princurve 2.0.2 was just pushed to CRAN. I notice your package uses
princurve
and wish to notify you of the changes so you can update your package accordingly.I believe what is relevant for you is that
get.lam
has been renamed toproject_to_curve
, in order to match the name of the function better with what its purpose is. In addition, the input argument and output variabletag
has been renamed toord
.The function
get.lam
still exists in the package, for now, as not to breakanalogue
, butget.lam
will be deprecated on July 1st and later on removed.If you have any remarks or questions, feel free to let me know!
Robrecht
The text was updated successfully, but these errors were encountered: