Closed dlebauer closed 8 years ago
Yes it always runs R in a new process, not sure I remember why it was implemented that way. We could just as easily run the R command inside the same R interpreter if it is local. https://github.com/PecanProject/pecan/blob/master/utils/R/remote.R#L180
As a side node, we should update this function to be similar as the others, getting passed in host so we can leverage of the tunnel if it exists.
Thanks I'll keep this open for the side note On Thu, Jul 21, 2016 at 12:26 AM Rob Kooper notifications@github.com wrote:
Yes it always runs R in a new process, not sure I remember why it was implemented that way. We could just as easily run the R command inside the same R interpreter if it is local. https://github.com/PecanProject/pecan/blob/master/utils/R/remote.R#L180
As a side node, we should update this function to be similar as the others, getting passed in host so we can leverage of the tunnel if it exists.
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/PecanProject/pecan/issues/918#issuecomment-234160232, or mute the thread https://github.com/notifications/unsubscribe-auth/AAcX5wRWOnpQKYfPMUHSYUdAXEp012dGks5qXwMegaJpZM4JRQ4G .
Moving tunnel issue to a new issue.
I suspect that the fail to find PEcAn.data.atmosphere in the new shell may have to do with where libraries are installed (e.g. by default RStudio and R put R libraries in different folders)
Running in a new shell (not a restart) was done to simplify met.process and convert.inputs -- it runs the same exact things in both environments (local vs remote), thus avoiding the need to maintain two parallel versions of the same commands, which we worried would lead to code divergence and difficulties with maintenance and debugging (remote is pretty hard to debug, but is simpler if you know the local code is exactly the same)
given this file
met.process_error.xml
The following code throws an error on ebi-forecast but not on the VM:
Here is the error:
It seems to restart R in the middle of the call. Is this expected?