-
Notifications
You must be signed in to change notification settings - Fork 2
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
Please do not change future options #1
Comments
Just checking back in on this one. I see you submitted on parseRPDR 1.1.1 on 2024-04-03 to CRAN, after I filed this issue. |
Dear Henrik,
Thank you so much for pointing out this implementation of future. I
acknowledge that hard coding the parallelization is not optimal,
furthermore, it is not advised by the developers. However parseRPDR is a R
package designed to be used by medical professionals who do not know how to
code to be able to parse outputs of the Harvard patient data registry into
csv formats. Therefore 99.9% of the users do not know how to set the
backend for parallelization and do not wish to change it but want to have a
tool that works out of the box without needing any technical knowledge.
Therefore, I would like to keep the current implementation to support the
ease of use of the software package.
Thank you for your kind consideration.
Marton Kolossvary
…On Sat, Jul 27, 2024 at 2:30 PM Henrik Bengtsson ***@***.***> wrote:
Just checking back in on this one. I see you submitted on parseRPDR 1.1.1
on 2024-04-03 to CRAN, after I filed this issue.
—
Reply to this email directly, view it on GitHub
<#1 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AGORGP33RIOPRE3OMIP4U63ZOOHFLAVCNFSM6AAAAABEA2VLZWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDENJUGEZTMNBYGE>
.
You are receiving this because you are subscribed to this thread.Message
ID: ***@***.***>
|
Hi. Please see what I wrote and the link I refer to in my top comment. I'm asking you to not set this when the package is attached. You can still set it temporarily inside the functions where you need it. https://future.futureverse.org/articles/future-7-for-package-developers.html#avoid-changing-the-future-options has almost cut'n'pastable instructions for how to do this. Also, there are no future R options |
I and lots of people using futureverse would appreciate it if you fixed this. As I said, the fix is possible. |
To the best of my knowledge I have in the latest release on cran v1.1.2
…On Sat, Jan 25, 2025 at 3:30 PM Henrik Bengtsson ***@***.***> wrote:
I and lots of people using futureverse would appreciate it if you fixed
this. As I said, the fix is possible.
—
Reply to this email directly, view it on GitHub
<#1 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AGORGP5CTWKH22W45QUKW232MONXZAVCNFSM6AAAAABEA2VLZWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDMMJTHE4DINBXHE>
.
You are receiving this because you modified the open/close state.Message
ID: ***@***.***>
|
Oh, I see. Great. Thanks. I didn't see any commits or updates here in this repository, which still has the old code - I guess they still need to be pushed here. |
Yes, it takes some time until the package is also pushed to github not only
cran
…On Sat, Jan 25, 2025 at 3:44 PM Henrik Bengtsson ***@***.***> wrote:
Oh, I see. Great. Thanks. I didn't see any commits or updates here in this
repository, which still has the old code - I guess they still need to be
pushed here.
—
Reply to this email directly, view it on GitHub
<#1 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AGORGP4UTL7LELDK72WB3S32MOPLLAVCNFSM6AAAAABEA2VLZWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDMMJTHE4DQNRQGE>
.
You are receiving this because you modified the open/close state.Message
ID: ***@***.***>
|
Hello. Please do not set future options from within your package, as in:
parseRPDR/R/ZZZ.R
Lines 1 to 4 in aec45d7
R options are meant for end-users, not developers. If you need to tweak the settings, please do so temporarily, as explained in https://future.futureverse.org/articles/future-7-for-package-developers.html#avoid-changing-the-future-options.
The text was updated successfully, but these errors were encountered: