steps-dev steps issues - Githubissues

steps-dev / steps

steps: Spatially- and Temporally- Explicit Population Simulator

19 stars 7 forks source link

issues

Newest

Newest Most commented Recently updated Oldest Least commented Least recently updated

Please do not change future options

#37 HenrikBengtsson opened 6 months ago
0
Any chance we can pass multiple options to cc function via dots?

#36 skiptoniam opened 1 year ago
1
ETA for next release? Removing defunct future::values()

#35 HenrikBengtsson closed 1 year ago
4
DESCRIPTION fields URL and BugReports

#34 HenrikBengtsson closed 3 years ago
1
Can't handle single mortality layer

#33 geryan closed 3 years ago
4
Description of stochasticity input is a little confusing.

#32 geryan closed 3 years ago
2
Description of arguments in ?modified_transition is backwards

#31 geryan closed 3 years ago
1
Steps crashes when population goes extinct: `Error in transition_array[1, , ]: incorrect number of dimensions`

#30 geryan closed 4 years ago
8
Feature request: Plot population size from time zero

#29 geryan closed 3 years ago
5
Mortality layers saving brick in simulation output for each timestep

#28 geryan closed 4 years ago
1
Mortality description is so confusion

#27 geryan closed 4 years ago
1
fix up vignette

#26 goldingn closed 5 years ago
1
still no vignettes

#25 goldingn closed 5 years ago
1
cluttered namespace

#24 goldingn closed 3 years ago
1
Plot method fails when when timesteps <= 5

#23 geryan closed 5 years ago
1
Feature request: Write rasters to disc

#22 geryan opened 5 years ago
5
Activated/modified print method & added bind_simulation_repetitions

#21 geryan closed 3 years ago
2
Error in if (any(pop_new[!missing] > 0)) { : missing value where TRUE/FALSE needed

#20 geryan closed 5 years ago
2
Error in getGlobalsAndPackages(expr, envir = envir, tweak = tweakExpression, : The total size of the 6 globals that need to be exported for the future expression (‘{; ...future.globals.maxSize.org <- getOption("future.globals.maxSize"); if (!identical(...future.globals.maxSize.org, ...future.globals.maxSize)) {; oopts <- options(future.globals.maxSize = ...future.globals.maxSize); on.exit(options(oopts), add = TRUE); }; ...; ...future.FUN(...future.X_jj, ...); }); }’) is 753.76 MiB. This exceeds the maximum allowed size of 500.00 MiB (option 'future.globals.maxSize'). The three largest globals are ‘future.call.arguments’ (753.67 MiB of class ‘list’), ‘...future.FUN’ (75.41 KiB of class ‘function’) and ‘as_class’ (12.36 KiB of class ‘function’).

#19 geryan closed 5 years ago
3
Error in stats::rmultinom(1, sum(population), population) : invalid second argument 'size' In addition: Warning message: In stats::rmultinom(1, sum(population), population) : NAs introduced by coercion to integer range

#18 geryan closed 5 years ago
4
Error in 1:width : result would be too long a vector

#17 geryan closed 5 years ago
1
Api redesign

#16 skiptoniam closed 5 years ago
3
split dispersal functions based on Will's updates and FFT

#15 cvisintin closed 6 years ago
2
user defined distance function

#14 wkmor1 closed 6 years ago
0
round cell values when demo_stoch is true

#13 wkmor1 closed 6 years ago
0
add option to make arrival probability depend on density

#12 wkmor1 closed 6 years ago
0
memory efficient and performant kernel dispersal

#11 wkmor1 closed 6 years ago
0
Vignettes

#10 skiptoniam closed 5 years ago
0
added permutation

#9 goldingn closed 6 years ago
0
rescale dispersal function to fix FFT dispersal

#8 goldingn closed 6 years ago
1
Comments in code

#7 skiptoniam closed 5 years ago
0
What's in a name? What should we call this package?

#6 skiptoniam closed 5 years ago
0
To do list

#5 skiptoniam closed 5 years ago
0
merge fft and cellular automata dispersal methods into a single function.

#4 skiptoniam closed 6 years ago
0
Keeping track of patches through time.

#3 skiptoniam closed 6 years ago
0
deal with warnings in patchify

#2 johnbaums closed 8 years ago
0
bugfix for substitute(x)

#1 johnbaums closed 8 years ago
0