Rscript 和 Incredibuild
我在“functions.txt”文件中有一个简单的函数 f1(paramter)。
我编写了一个批处理文件 test.bat 如下
FOR /L %%G in (-100,1,100) do xgSubmit.exe /group=tt1Test /command Rscript.exe -e
"source('functions.txt');f1(%%G)" > "Out.%%G.txt"
在 Windows 命令提示符中我使用
xgConsole.exe test.bat /openmonitor /AvoidLocal=ON
我想要做的是使用 incredibuild 在不同的机器中计算函数 f1() 。
我观察到的是本地运行的函数返回文件中的值 Out.%%G.txt 但远程运行的函数失败并出现以下错误
Error in structure(.Internal(Sys.getenv(as.character(x), as.character(unset))), :
unsupported conversion to 'UCS-2LE' from codepage 1252
Calls: local ... eval -> eval -> as.vector -> Sys.getenv -> structure
Execution halted.
远程计算机没有安装 R 程序。
我做的事正确吗? 即使远程计算机上没有安装 R 程序,incredibuild 和 Rscipt 是否也能工作?
如果能提供详细的答案将非常感激。
I have a simple function f1(paramter) in a "functions.txt" file.
I write a batch file test.bat as follows
FOR /L %%G in (-100,1,100) do xgSubmit.exe /group=tt1Test /command Rscript.exe -e
"source('functions.txt');f1(%%G)" > "Out.%%G.txt"
In the windows command prompt I use
xgConsole.exe test.bat /openmonitor /AvoidLocal=ON
What I am trying to do is compute function f1() in different machines using incredibuild.
What I observe is the function that are running locally returns a value in files
Out.%%G.txt but the functions running remotely fails with the following error
Error in structure(.Internal(Sys.getenv(as.character(x), as.character(unset))), :
unsupported conversion to 'UCS-2LE' from codepage 1252
Calls: local ... eval -> eval -> as.vector -> Sys.getenv -> structure
Execution halted.
The remote machines do not have R program installed.
Am I doing the correct thing ?
Should incredibuild and Rscipt be able to work even though R program is not installed in the remote computer ?
It would be very kind to provide a detailed answer.
如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱,如果其他用户或者作者回复了您的评论,将不能在第一时间通知您!
发布评论
评论(1)
这似乎是远程计算机中的 Unicode 问题。
自提交此问题以来,许多 Unicode 问题已得到解决。
我假设您的错误已在最新版本的 IncrediBuild 中修复。
It seems like a Unicode problem in the remote machines.
Many Unicode problems have been fixed since this question was submitted.
I assume your bug is already fixed in the latest version of IncrediBuild.