[kepler-users] Exec Component Binary Data

[Jianwu Wang]

Hi David,

External execution assume the data for output port is string and process 
it accordingly. So I don't think it can correctly send binary data from 
its output port.

One way workaround is to redirect the binary output into a file and the 
next 'External execution' actor will read data from the file. If it fits 
your needs, I can send a demo workflow for it.

Best wishes

Sincerely yours

Jianwu Wang, Ph.D.
jianwu at sdsc.edu
http://users.sdsc.edu/~jianwu/

Assistant Project Scientist
Scientific Workflow Automation Technologies (SWAT) Laboratory
San Diego Supercomputer Center
University of California, San Diego
San Diego, CA, U.S.A.

On 4/18/13 11:02 AM, Brown, David M JR wrote:
> To whom it may concern,
> I’ve got a set of binary tools that use standard unix style pipes to 
> communicate and process data. So to write this up in Kepler I chose to 
> use the external execution component and run each command separately 
> connecting one components standard output to the other components 
> standard input. However, the communication isn’t in text its binary. 
> I’m having issues where the first part of the process doesn’t 
> recognize the header sent to the program as valid.
> Are there any issues with sending binary data from external execution 
> components output port?
> Thanks,
> - David Brown
>
>
> _______________________________________________
> Kepler-users mailing list
> Kepler-users at kepler-project.org
> http://lists.nceas.ucsb.edu/kepler/mailman/listinfo/kepler-users

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.nceas.ucsb.edu/kepler/pipermail/kepler-users/attachments/20130419/4e666e00/attachment.html>