Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
O order_prediction_methods
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 0
    • Issues 0
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Merge requests 3
    • Merge requests 3
  • Operations
    • Operations
    • Incidents
  • Analytics
    • Analytics
    • Repository
    • Value Stream
  • Wiki
    • Wiki
  • Members
    • Members
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar
  • Douglas
  • order_prediction_methods
  • Merge requests
  • !2

Open
Created Nov 05, 2015 by Jérome Perrin@jerome
  • Report abuse
Report abuse

Some suggested changes for the clone order section

  • Overview 2
  • Commits 1
  • Changes
  • explain DateTime's arithmetic that reader might not be familiar with
  • do not set dates on the lines. We have dates on the order and they are acquired on the line.
  • do not use activate to pass workflow transition. It is usually slower to spawn one activity for very simple things like this.
  • generate 1 year of data ( I think this what you explain below )
Assignee
Assign to
Reviewer
Request review from
None
Milestone
None
Assign milestone
Time tracking
Source branch: script_generating_orders
GitLab Nexedi Edition | About GitLab | About Nexedi | 沪ICP备2021021310号-2 | 沪ICP备2021021310号-7