search

ProvTools / provR

GNU General Public License v2.0
7 stars 3 forks source link

Submit to CRAN #75

Open MKLau opened 6 years ago

MKLau commented 6 years ago

Blocked by Issues #10, #11, #14, #34, #42, #43, #44, #50, #53, #54, #55, #58, #61, #73, #76, #77, #78, #79

MKLau commented 6 years ago

Parsing the user's code by inserting prov capture code into the stack may also be an issue, according to https://github.com/NCEAS/recordr/issues/73. There is a suggested fix, which is a refactor to use the utils::trace function. Not sure how difficult this would be.

MKLau commented 6 years ago

Potential issue with assignments when internals are turned off: https://github.com/End-to-end-provenance/RDataTracker/issues/386

MKLau commented 6 years ago

Potential issue with capturing user defined functions when internals are turned off: https://github.com/End-to-end-provenance/RDataTracker/issues/385

blernermhc commented 6 years ago

I have looked at recordR issue you mentioned and have been thinking that I would like to try working with the trace function as they suggest doing as well. I don't think that trick will work, though, for collecting provenance internal to functions, but I am hoping it could be used at the entry and exit of functions. This might allow us to fix the problems we are having when we are collecting provenance both internal to functions and internal to control constructs.

MKLau commented 6 years ago

Thanks for taking a look, Barb. Good to hear that if might help in capturing that prov from functions and control statements. Hope you can carve out some time to do some experimenting.