Fix of a major issue in the simulation: sometimes the number of states
wasn't consistent. Add of test to check the consistency of the
Trajectory structure (unit/check_trajectory_consistency).

Implementation of the lp distance for trajectories.
Add of unit tests for lp distance.

can be set by the user. Changes of SIR and ER.

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).

- a script to run the different categories
- now the execution of simulation/ scripts is checked
- several minor changes and add of tests

New directory : models/_bench_perf_tests.  Models for performance benchmarking purposes.

In fine I give the Abstract and Static arrays types up.

- Real => Float64 for better performance (Real is an abstract type)
- Should not create a type inside the model because the compiler fails
at estimating the type of the output of the f function (detected with
@code_warntype)
- Intentionaly ER is not as well improved as SIR in order to check the
differences of performance.

- Add of benchmark scripts that compares perf wrt pygmalion.
=> As expected it is bad in terms of reading cost (because of row by row
matrix read) but it is also not good in terms of simulation cost.
hcat seems to perform badly, should investigate.

Files should have the same name as the exported model variable (<:Model)

SIR model.

- Evolution of the ContinuousTimeModel type
- simulate, easy access to Trajectory fields
- fix of several errors

run the tests
Function load_module in core + test

Two folders:
- core/ which contains the essential files for the packages
- tests/ which contains tests and benchmarks of other packages / methods

For now on:
- we wrote minimal tests in tests/ (a simulation of SIR model) that should run for
a first minimal version of the package
- we described in core/ the general structure of essential
types, how they articulate each others and the minimum methods we should
implement for a first version that runs the tests.