-
Notifications
You must be signed in to change notification settings - Fork 0
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
Add magmaR to this repo #64
Conversation
See mountetna/monoetna#139 for previous discussion, but I will comment soon to continue ongoing discussion here. |
Re: mountetna/monoetna#139 (comment), I recognize the value in having a centralized pointer to which Etna environment in most cases, but I think that magmaR is unique in that it will ALSO be distributed outside of Etna itself. So I'd like help in deciding the path forward. @coleshaw @graft Context:@graft's comment
Term definition: I’m going to use “Etna environment” to refer generically to a (privileged) user’s current production/staging/dev target. Places with "ucsf.edu":
Relevant uniqueness of magmaR compared to previously build piecesThere are two major use cases for the R package magmaR which differ in where they will be used, and how they will be installed:
For 1, I agree with the intended goal that it would be useful to embed a way to have a set Potential Paths ForwardI can think of 2 options here, but there may be others:
I prefer 2 because it wouldn’t complicate the package for users who will only ever look to production (most users), and also because default_adjustment_functions, like for 1, use non-standard methods that might complicate an eventual CRAN submission. But I would need help setting 2 up. |
Thanks for writing this up! I have a couple of thoughts:
I think this is going to go back to the same discussion with @corps around ease-of-initial-use and trying to minimize configuration for the command-line interface ... however that looks in the R context. One idea we had floated during the CLI discussion was, is it possible to have a single-line prompt for an R package installation (not just an R session, but like one-time forever), that prompts the user for the default domain to use? I guess like a more permanent version of option 1 above. |
Oh, sorry, I re-read @graft 's comment and I see why you pushed this PR here :-) Haha, sorry! I think he was suggesting that you move the |
Add the magma <=> R client, R package
magmaR
, which I have been working on for a bit now.