Skip to content

Commit

Permalink
chore: fix the readme item numbering
Browse files Browse the repository at this point in the history
  • Loading branch information
DanySK committed Nov 30, 2022
1 parent 878b7b6 commit 4cda012
Showing 1 changed file with 20 additions and 20 deletions.
40 changes: 20 additions & 20 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -50,23 +50,23 @@ and the graphical interface usage description available [here](https://alchemist
try to solve the following exercises:

1. Add two nodes to an empty, continuous environment, and make them connected
1. Create 10000 nodes randomly displaced inside a circle centered in (0,0) and radius 10
1. Create a grid of nodes from (-5,-5) to (5,5), with nodes every (0.25,0.25) distance units, and no perturbance
1. Create a perturbed grid from the example above
1. Put some {token} LSAs in some nodes of the system
1. Write a "dodgeball" program
1. See how YAML can be used to write personalised sections and how they can be referred
1. Modify the dodgeball program so that it *counts* in the LSA the number of passes
1. Write an LSA diffusion program: after some time, every node of the network must have the {token} LSA. Use the `*` operator
1. Look at the `10-math.yml` file. Esperiment with it and try to move nodes around manually.
1. Write a gradient, it should:
1. convert a `{source}` to a `{gradient, 0}` (don't delete the source!)
1. diffuse to neighbors the gradient, whose value is increased of `#D`
1. if there are multiple copies of the gradient, keep only the lowest (immediately!)
1. every some time "age" the information by increasing its value
1. delete gradients whose value is higher than some threshold (e.g. 20).
1. Take a look to `12-sets.yml`, and see how the set arithmetic works. Run it, and see the result.
1. Modify the program above by changing the time distribution, using a personalised one: a DiracComb with parameter 0.5
1. Take a look to `14-yaml.vars.yml`, and make sure to understand how the variables system works
1. Take a look to `15-move.yml`, run it and play with its variables
1. Try to run `16-maps.yml` (note: it can take some time on the first load). Get a glance of the possible complexity of advanced scenarios. Discuss the result, modify the example as you like.
2. Create 10000 nodes randomly displaced inside a circle centered in (0,0) and radius 10
3. Create a grid of nodes from (-5,-5) to (5,5), with nodes every (0.25,0.25) distance units, and no perturbance
4. Create a perturbed grid from the example above
5. Put some {token} LSAs in some nodes of the system
6. Write a "dodgeball" program
7. See how YAML can be used to write personalised sections and how they can be referred
8. Modify the dodgeball program so that it *counts* in the LSA the number of passes
9. Write an LSA diffusion program: after some time, every node of the network must have the {token} LSA. Use the `*` operator
10. Look at the `10-math.yml` file. Esperiment with it and try to move nodes around manually.
11. Write a gradient, it should:
1. convert a `{source}` to a `{gradient, 0}` (don't delete the source!)
2. diffuse to neighbors the gradient, whose value is increased of `#D`
3. if there are multiple copies of the gradient, keep only the lowest (immediately!)
4. every some time "age" the information by increasing its value
5. delete gradients whose value is higher than some threshold (e.g. 20).
12. Take a look to `12-sets.yml`, and see how the set arithmetic works. Run it, and see the result.
13. Modify the program above by changing the time distribution, using a personalised one: a DiracComb with parameter 0.5
14. Take a look to `14-yaml.vars.yml`, and make sure to understand how the variables system works
15. Take a look to `15-move.yml`, run it and play with its variables
16. Try to run `16-maps.yml` (note: it can take some time on the first load). Get a glance of the possible complexity of advanced scenarios. Discuss the result, modify the example as you like.

0 comments on commit 4cda012

Please sign in to comment.