Closed dankelley closed 2 years ago
The Stale-bot has marked this issue as Stale, because no new comments have been added in the past 30 days. Unless a comment is added within the next 7 days, the Stale-bot will close the issue. The purpose of these automated actions is to prevent the developers from forgetting about unattended tasks. Note that adding a "pinned" label will turn this action off for a given issue.
Perhaps this should be examined before we let it close.
The Stale-bot has marked this issue as Stale, because no new comments have been added in the past 30 days. Unless a comment is added within the next 7 days, the Stale-bot will close the issue. The purpose of these automated actions is to prevent the developers from forgetting about unattended tasks. Note that adding a "pinned" label will turn this action off for a given issue.
@j-harbin, I think parts of argoFloats can be speeded up. The issue is that gsub() can be slow, unless
perl=TRUE
is supplied. A demonstration, usingf
asindex$file
in anargoFloatsIndex
object) is:You might not get the same results, because I am on the beta version of R, which is handling strings in a new (and slower) way. But, in a few weeks, that beta version will be the normal version, and so users will be on that version in a month or so, assuming they update frequently (which I think many do).
For context, trimming 4 seconds out of 7 seconds is not a lot, but it's not nothing, either. And I think we might have several instances in which we do that. When I run
in the argoFloats/R directory, I get as below. Notice that we do this for both ID and for cycle. (We also seem to be repeating things, but I've not examined the code to see if that's true.)