Currently, when Caliper software sends a vector over COM, RDCOMClient leaves it as a pointer. The caliper package checks to see if that pointer is pointing to a vector and, if so, converts it to an array using the GISDK V2A() and then sends it over COM.
This process is incredibly slow. If it can work, the ideal solution would be to modify the C++ code in RDCOMClient to understand what the vector is and translate it into data R can understand.
Although ugly, an interim solution would be to write the vector to a temp file and read it into R. This is almost assuredly faster than the current code.
Currently, when Caliper software sends a vector over COM, RDCOMClient leaves it as a pointer. The caliper package checks to see if that pointer is pointing to a vector and, if so, converts it to an array using the GISDK
V2A()and then sends it over COM.This process is incredibly slow. If it can work, the ideal solution would be to modify the C++ code in RDCOMClient to understand what the vector is and translate it into data R can understand.
Although ugly, an interim solution would be to write the vector to a temp file and read it into R. This is almost assuredly faster than the current code.