Reintroduced some malfunction parameters but are not used.

At each step we first check for possible malfunctions.
THen we apply them and do all the agent steps
At the end we look at what agents should be fixed. This lead so to:

Current malfunction value says how many step calls are necessary till agent can move again

e.g. malfunction = 2, we have to call step() twice untill the agent can move again.

Code cleanup

At each step we first check for possible malfunctions.
THen we apply them and do all the agent steps
At the end we look at what agents should be fixed. This lead so to:

Current malfunction value says how many step calls are necessary till agent can move again

e.g. malfunction = 2, we have to call step() twice untill the agent can move again.

It now gives the probability that an agent breaks at given time step
given the number of agents and the rate of failures of a single agent.
These number now need to be much larger.... otherwise we will have alot of failures

Updated example

# Conflicts:
#   flatland/envs/rail_env.py
#   tests/test_flatland_malfunction.py

Updated example

# Conflicts:
#	flatland/envs/rail_env.py

Adresses issue #263

Adresses issue #263

refactoring of the fixing agent code part

Added fixed to attributes in agent_utils.py

Adresses issue #263

264 fixed examples branch 2

Closes #264

See merge request flatland/flatland!251

Merge branch '264_fixed_examples_branch_2' of gitlab.aicrowd.com:flatland/flatland into 264_fixing_examples

reverted all the versioning problems

Merge branch '264_fixed_examples_branch_2' of gitlab.aicrowd.com:flatland/flatland into 264_fixing_examples

# Conflicts:
#	examples/complex_rail_benchmark.py
#	examples/custom_observation_example_02_SingleAgentNavigationObs.py

updated to newest master branch

# Conflicts:
#	flatland/envs/rail_env.py

# Conflicts:
#   flatland/envs/rail_env.py

196 comparison with 0

Closes #198

See merge request flatland/flatland!244