1. 05 Aug, 2020 1 commit
  2. 25 Jun, 2020 1 commit
  3. 10 Mar, 2020 1 commit
  4. 26 Nov, 2019 1 commit
  5. 17 Sep, 2019 2 commits
  6. 04 Sep, 2019 2 commits
  7. 19 Aug, 2019 1 commit
  8. 30 Jul, 2019 2 commits
  9. 24 Jul, 2019 2 commits
    • Samuel GAIST's avatar
      [experiment] WARNING Refactor of the loop handling · 3f345759
      Samuel GAIST authored
      Rather than having a loops field containing only the "loop"
      blocks, they have now become their own entity like "blocks" and
      "analyzers".
      
      This new type of block will contain all the information needed
      for both the loop user algorithm and for the loop itself as
      they work in pair anyway.
      3f345759
    • Samuel GAIST's avatar
      [toolchain] WARNING Refactor of the loop handling · 50b4c0d2
      Samuel GAIST authored
      Rather than having a loops field containing only the "loop"
      blocks, they have now become their own entity like "blocks" and
      "analyzers".
      
      This new type of block will contain all the information needed
      for both the loop user algorithm and for the loop itself as
      they work in pair anyway.
      50b4c0d2
  10. 15 Jul, 2019 2 commits
  11. 11 Jul, 2019 1 commit
  12. 14 Jun, 2019 1 commit
  13. 18 Apr, 2019 1 commit
  14. 17 Apr, 2019 3 commits
  15. 20 Mar, 2019 1 commit
  16. 15 Mar, 2019 1 commit
  17. 13 Mar, 2019 1 commit
  18. 21 Feb, 2019 1 commit
    • Samuel GAIST's avatar
      [algorithm] Refactor prototype loading · 8b2f5dbe
      Samuel GAIST authored
      When a new algorithm is created the prototype is used to generate
      the new object. In order to comply with the new fixed version of
      the schema (inputs and outputs must has at least one value), the
      prototype must also have one of each. Since the dataformat used
      is also validated as part of the creation, it must exist on the
      platform. In order to ensure that we are using a valid dataformat,
      the "integers" format is used and searched in the prefix to ensure
      the correct author is used as it might be different depending on
      how the platform was setup.
      8b2f5dbe
  19. 20 Feb, 2019 1 commit
  20. 29 Nov, 2018 6 commits
  21. 19 Nov, 2018 1 commit
  22. 09 Nov, 2018 1 commit
    • Samuel GAIST's avatar
      [schema] Refactored v1 and v2 schema · 91ba93e1
      Samuel GAIST authored
      V2 information were kept in the v1 version of the schema.
      
      This refactoring, while duplicating a bit of information about blocks
      and analyzer, allows to have a better separation taking into account
      the limitation of the json schema with regards to "object oriented"
      definition. The main point being that new properties can't be added
      to "subdefinitions" when setting "additionalProperties" to false.
      91ba93e1
  23. 08 Oct, 2018 1 commit
  24. 01 Oct, 2018 1 commit
  25. 19 Jul, 2018 1 commit
  26. 05 May, 2018 2 commits
  27. 26 Apr, 2018 1 commit