[kepler-dev] [Bug 3173] - Improve data frame handling between RExpression actors

[ben leinfelder]

Dan,
That's certainly a good point - and one that Matt and Jim (Regetz) and  
I were discussing at some length yesterday.
I think the end goal is to have a true dataframe type within Kepler,  
but until that time it seems reasonable that dataframes (and other  
complex R objects) can only be passed between R actors  
(automagically).  If a workflow author wants to pass the object to non- 
R actors then they can do that particular [text serialization] within  
their custom R script.  Reasonable?

-ben

On Mar 13, 2008, at 8:41 AM, Dan Higgins wrote:

> Ben (and others)
>
>   I deliberately avoided the R serialization approach when I  
> originally implemented the RExpression actor because the serialized  
> dataframe cannot be accessed by non-R actors, while the text file  
> table that was previously written could be read by other Kepler  
> actors. I fear making Kepler too R-centric will lessen its general  
> usefulness.
>
>
> Dan Higgins
>
> bugzilla-daemon at ecoinformatics.org wrote:
>> http://bugzilla.ecoinformatics.org/show_bug.cgi?id=3173
>>
>>
>> leinfelder at nceas.ucsb.edu changed:
>>
>>           What    |Removed                     |Added
>> ----------------------------------------------------------------------------
>>             Status|NEW                         |RESOLVED
>>         Resolution|                            |FIXED
>>
>>
>>
>>
>> ------- Comment #2 from leinfelder at nceas.ucsb.edu  2008-03-12 23:57  
>> -------
>> The R actor now uses the serialize/unserialize method described by  
>> jim for data
>> frames and also for other complex R objects (the result of lm() for  
>> example).
>>
>> The sample workflow mentioned in this bug, also works (due to  
>> previous changes
>> to support floating point numbers)
>> _______________________________________________
>> Kepler-dev mailing list
>> Kepler-dev at ecoinformatics.org
>> http://mercury.nceas.ucsb.edu/ecoinformatics/mailman/listinfo/kepler-dev
>>
>>
>
>