Fix the redefinition of the f! function of models (side effect of
previously loaded model). The package warns when this happen. Several benchmarks for the data structure. Now we chose the row buffer method according to results (mainly because the trajectory access with far way faster, but strangly not that much differences in other cases).
Showing
- bench/array_memory_order/access_trajectory_sir.jl 49 additions, 0 deletionsbench/array_memory_order/access_trajectory_sir.jl
- bench/array_memory_order/multiple_sim_sir.jl 48 additions, 0 deletionsbench/array_memory_order/multiple_sim_sir.jl
- bench/array_memory_order/read_random_state_trajectory.jl 51 additions, 0 deletionsbench/array_memory_order/read_random_state_trajectory.jl
- bench/array_memory_order/read_trajectory_sir.jl 53 additions, 0 deletionsbench/array_memory_order/read_trajectory_sir.jl
- bench/array_memory_order/sim_sir.jl 48 additions, 0 deletionsbench/array_memory_order/sim_sir.jl
- bench/pygmalion/read_random_state_trajectory.jl 6 additions, 1 deletionbench/pygmalion/read_random_state_trajectory.jl
- core/_tests_simulate.jl 4 additions, 4 deletionscore/_tests_simulate.jl
- core/model.jl 8 additions, 0 deletionscore/model.jl
- core/observations.jl 3 additions, 3 deletionscore/observations.jl
- models/SIR.jl 3 additions, 3 deletionsmodels/SIR.jl
- models/_bench_perf_test/SIR_col.jl 3 additions, 3 deletionsmodels/_bench_perf_test/SIR_col.jl
- models/_bench_perf_test/SIR_col_buffer.jl 3 additions, 3 deletionsmodels/_bench_perf_test/SIR_col_buffer.jl
- models/_bench_perf_test/SIR_row_buffer.jl 3 additions, 3 deletionsmodels/_bench_perf_test/SIR_row_buffer.jl
Loading
Please register or sign in to comment