search for: sammo3182

Displaying 6 results from an estimated 6 matches for "sammo3182".

2019 Oct 30
2
set.seed() in a package
Hi all, I recently found several calls of set.seed() in a CRAN package. These calls are in a plot function, which could lead to unexpected behaviour. See https://github.com/sammo3182/interplot/issues/33 <https://github.com/sammo3182/interplot/issues/33> for a description of the problem. I checked the CRAN repository policies and could not find anything about this. I would have expected a policy against setting fixed seeds somewhere in a package. Am I missing something?...
2019 Oct 30
2
set.seed() in a package
...Murdoch <murdoch.duncan at gmail.com> wrote: > > On 30/10/2019 3:28 a.m., Marvin Wright wrote: >> Hi all, >> I recently found several calls of set.seed() in a CRAN package. These calls are in a plot function, which could lead to unexpected behaviour. See https://github.com/sammo3182/interplot/issues/33 <https://github.com/sammo3182/interplot/issues/33> for a description of the problem. >> I checked the CRAN repository policies and could not find anything about this. I would have expected a policy against setting fixed seeds somewhere in a package. Am I missing some...
2019 Oct 30
2
set.seed() in a package
...l.com> wrote: > >> > >> On 30/10/2019 3:28 a.m., Marvin Wright wrote: > >>> Hi all, > >>> I recently found several calls of set.seed() in a CRAN package. These calls are in a plot function, which could lead to unexpected behaviour. See https://github.com/sammo3182/interplot/issues/33 <https://github.com/sammo3182/interplot/issues/33> for a description of the problem. > >>> I checked the CRAN repository policies and could not find anything about this. I would have expected a policy against setting fixed seeds somewhere in a package. Am I mis...
2019 Oct 30
0
set.seed() in a package
On 30/10/2019 3:28 a.m., Marvin Wright wrote: > Hi all, > > I recently found several calls of set.seed() in a CRAN package. These calls are in a plot function, which could lead to unexpected behaviour. See https://github.com/sammo3182/interplot/issues/33 <https://github.com/sammo3182/interplot/issues/33> for a description of the problem. > > I checked the CRAN repository policies and could not find anything about this. I would have expected a policy against setting fixed seeds somewhere in a package. Am I missing so...
2019 Oct 30
0
set.seed() in a package
...rdoch.duncan at gmail.com> wrote: >> >> On 30/10/2019 3:28 a.m., Marvin Wright wrote: >>> Hi all, >>> I recently found several calls of set.seed() in a CRAN package. These calls are in a plot function, which could lead to unexpected behaviour. See https://github.com/sammo3182/interplot/issues/33 <https://github.com/sammo3182/interplot/issues/33> for a description of the problem. >>> I checked the CRAN repository policies and could not find anything about this. I would have expected a policy against setting fixed seeds somewhere in a package. Am I missing...
2019 Oct 30
0
set.seed() in a package
...; > >> > > >> On 30/10/2019 3:28 a.m., Marvin Wright wrote: > > >>> Hi all, > > >>> I recently found several calls of set.seed() in a CRAN package. These calls are in a plot function, which could lead to unexpected behaviour. See https://github.com/sammo3182/interplot/issues/33 <https://github.com/sammo3182/interplot/issues/33> for a description of the problem. > > >>> I checked the CRAN repository policies and could not find anything about this. I would have expected a policy against setting fixed seeds somewhere in a package. Am...