jonathangb / faulty-robots-simulation Goto Github PK

maybe will simplified some code

First need to decide a format. JSON would be the easy/obvious way.

[
  {
    "label": Integer
    "faulty": Bool,
    "x": Number
  },
  ...
]

• canvas must have the x-axis
• hovering over the x-axis shows a circle that follows the mouse; on click, add a robot at this point
  • add a label
  • in a bubble, show x value, label, and state (radio); all modifiable
  • on right-click, default to faulty-robot?
• show list of previous setups to start from (stored in localStorage)
  • button to store setup, which prompts for a setup name before
• possibility to paste a custom setup into textarea
• "start generating" button, which starts generating in the background [next issue] and blocks further changes to the setup

Could obviously be useful. Start with calculator.js, then move to more I/O (visual) tests

• Only enable when there is >= 2 robots
• On click, disable event listeners on "setup" robots
  • keep listeners on double click
  • make top inputs & textarea disabled (change css cursor on disabled too?)
• display generation "001"
  • pre-generate 10 generations in advance using the webworker?
  • show icon on the side to generate next "wave"?

would make it much easier to understand what is happening under the hood

Jean-Lou needs to press the document before the "enter" keypress to generate the new waves, maybe should add a listener to the canvas?

I'm not able to recreate it locally.

To easily draw graphs in scientific papers, a certain library is used which requires coordinates, labels and such in a specific XML format.

I'm thinking to put a button beside every generation in the UI which, when clicked, outputs the XML string to be copied.

including itself

Methods in paper.js that could be helpful:

• onMouseDrag
• scale

What logic needs to be modified to work in the new context?

• bubble needs to show a "y" input
• canvas should show the y axis
• signatures taking only "x" should in most/all cases handle y too
• 2D doesn't need a visualization of the origin (at least not as a tick on a line)
• range visualization (orange bar) needs to be a circle
• height of a generation panel is bigger in 2D
• algo to find new position is different (center of smallest circle)
  • split calculator.js into calculator1d.js and calculator2d.js, logic is distinct between the two
• command input needs to add "y" parameters
• save input broken (1d & 2d)

Some trigo to be added

weird behaviour, need to investigate the root cause

Results will be used to compare which is better and will be incorporated in the results of the report. Currently I use batches of 10, but maybe 25, 50, 100 would be better?

Chains should be of the same colour

• Add how to run (Go not necessary as for now)
  • 1d vs 2d
• Mention new features

Probably more...