1. 03 Apr, 2019 1 commit
  2. 01 Mar, 2019 1 commit
  3. 28 Feb, 2019 1 commit
  4. 20 Feb, 2019 1 commit
  5. 18 Feb, 2019 1 commit
  6. 25 Jan, 2019 1 commit
  7. 15 Jan, 2019 1 commit
  8. 09 Jan, 2019 1 commit
  9. 29 Nov, 2018 1 commit
  10. 28 Nov, 2018 1 commit
  11. 11 Oct, 2018 1 commit
  12. 10 Oct, 2018 1 commit
    • Sébastien Villemot's avatar
      Add copy constructors / assignment operators for the DataTree class hierarchy · f2cf86b7
      Sébastien Villemot authored
      In particular, it is necessary to turn back DataTree::AddVariable() into a
      non-virtual method, because it is called from DataTree's constructor. Enforcing
      the absence of leads/lags is now done using a new boolean DataTree::is_static.
      
      Take advantage of the new copy constructor for handling
      PlannerObjectiveStatement more elegantly.
      
      Unfortunately it is not possible to implement *move* constructor / assigment
      operators, because the reference ExprNode::datatree is not mutable.
      f2cf86b7
  13. 04 Oct, 2018 2 commits
  14. 28 Sep, 2018 1 commit
  15. 14 Sep, 2018 1 commit
  16. 05 Sep, 2018 1 commit
  17. 22 Aug, 2018 2 commits
  18. 17 Aug, 2018 1 commit
  19. 02 Aug, 2018 1 commit
    • Sébastien Villemot's avatar
      New var_expectation_model statement and re-design of var_expectation operator · f3c2a1bf
      Sébastien Villemot authored
      Given a previously declared var_model, the var_expectation_model statement is
      used to declare a way of forming expectations with this VAR (possibly using a
      finite or infinite discounted sum). The var_expectation operator now takes a
      single argument, the name of the var_expectation_model.
      
      For the moment, this only works when the var_model is using equations
      explicitly declared in the model block.
      f3c2a1bf
  20. 31 Jul, 2018 2 commits
    • Sébastien Villemot's avatar
      PlannerObjectiveStatement now owns its model_tree · 122e1547
      Sébastien Villemot authored
      By the way, error out if the planner_objective statement is used two times.
      122e1547
    • Sébastien Villemot's avatar
      Several fixes to computing tasks statements · 725b91e5
      Sébastien Villemot authored
      - store objects whose persistence is not guaranteed (e.g. strings) as values
        instead of references (to avoid possible segfaults)
      - on the contrary, always store the SymbolTable as a reference, since its
        persistence is guaranteed, and we don't want to copy it
      - use pass-by-value in constructors whenever possible
      - remove useless const keyword when passing by value
      725b91e5
  21. 18 Jul, 2018 1 commit
  22. 15 Jun, 2018 1 commit
  23. 05 Jun, 2018 1 commit
  24. 04 Jun, 2018 6 commits
  25. 17 Apr, 2018 1 commit
  26. 04 Apr, 2018 1 commit
  27. 07 Mar, 2018 1 commit
  28. 06 Mar, 2018 1 commit
  29. 15 Feb, 2018 1 commit
  30. 09 Feb, 2018 1 commit
  31. 08 Feb, 2018 1 commit
  32. 06 Feb, 2018 1 commit