Closed youngser closed 7 years ago
I see that most of the wrappers have lines source(*.interface.R)
.
The JPL guy said that this won't work, because all they will have/take is a python file!
So, my (and the JPL guy's) questions are
Can we modify the wrappers so that they don't have source
lines? I remember that's what we have earlier?
Is it possible to have all the wrappers as a single python package == pip installable ??
For no. 1 above, will it be better if I include all the *.interface.R
files inside a new R package I'm writing (let's call it JHUD3M
?? Then, I think it minimizes the revision of the wrappers? No?
The guy said our files that will be installed on the D3M system will be
That's all!
So, I guess including those .interface.R functions inside one of my packages won't work, because Python cannot call R functions directly? Again, I remember you put the content of .interface.R inside double quotes at the very first attempt, and I think that's the only way?
On Sep 15, 2017, at 1:10 PM, Disa Mhembere notifications@github.com wrote:
I use full paths like this: line 30 https://github.com/youngser/D3M/blob/api/ase/SRC/ase.py#L30. How won't this work when it is it populated based upon the location of the calling file see line 27 https://github.com/youngser/D3M/blob/api/ase/SRC/ase.py#L27 ?
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/youngser/D3M/issues/5#issuecomment-329842430, or mute the thread https://github.com/notifications/unsubscribe-auth/AFeZLU9Q9G9xjr35Nl6NOekVdfBChvLkks5siq-YgaJpZM4PYYTq.
From @DSP137: