{"action":"created","issue":{"url":"https://api.github.com/repos/timnon/pyschedule/issues/70","repository_url":"https://api.github.com/repos/timnon/pyschedule","labels_url":"https://api.github.com/repos/timnon/pyschedule/issues/70/labels{/name}","comments_url":"https://api.github.com/repos/timnon/pyschedule/issues/70/comments","events_url":"https://api.github.com/repos/timnon/pyschedule/issues/70/events","html_url":"https://github.com/timnon/pyschedule/issues/70","id":374664566,"node_id":"MDU6SXNzdWUzNzQ2NjQ1NjY=","number":70,"title":"Constrains for a group of tasks","user":{"login":"jm-imca","id":7795920,"node_id":"MDQ6VXNlcjc3OTU5MjA=","avatar_url":"https://avatars2.githubusercontent.com/u/7795920?v=4","gravatar_id":"","url":"https://api.github.com/users/jm-imca","html_url":"https://github.com/jm-imca","followers_url":"https://api.github.com/users/jm-imca/followers","following_url":"https://api.github.com/users/jm-imca/following{/other_user}","gists_url":"https://api.github.com/users/jm-imca/gists{/gist_id}","starred_url":"https://api.github.com/users/jm-imca/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/jm-imca/subscriptions","organizations_url":"https://api.github.com/users/jm-imca/orgs","repos_url":"https://api.github.com/users/jm-imca/repos","events_url":"https://api.github.com/users/jm-imca/events{/privacy}","received_events_url":"https://api.github.com/users/jm-imca/received_events","type":"User","site_admin":false},"labels":[],"state":"closed","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":2,"created_at":"2018-10-27T16:45:19Z","updated_at":"2018-10-29T11:45:55Z","closed_at":"2018-10-28T18:36:17Z","author_association":"NONE","body":"Hi there, first thing first, thanks a lot for your effort you put into this project!\r\nFirst time I am playing with this type of thing, but I get stuck with one condition that I can not bring to work:\r\nFirst I created three long task and was wondering how to make it that the tasks are automatically assigned to multiple people. I think this is not possible in a way that they share the work. So I splitted the tasks into group of tasks each one day long. This works well, the day task are shared between two persons.\r\n\r\n But one group of development tasks (webback_d) should be scheduled AFTER the task \"sysarch\", but I can not bring it to work. Here is my code: \r\n\r\n\r\n```\r\n# Load pyschedule and create a scenario with ten steps planning horizon\r\nfrom pyschedule import Scenario, solvers, plotters\r\nS = Scenario('hello_pyschedule',horizon=50)\r\n\r\n\r\n# Create some resources\r\nNick, Jim, Peter, Bob = S.Resource('Nick',size=1), S.Resource('Jim',size=1), S.Resource('Peter',size=1), S.Resource('Bob',size=1)\r\n\r\n\r\nsysarch = S.Task('ARC',3,plot_color='#66FFff')\r\nwebfront_d = S.Tasks('GUI',num=10,length=1,is_group=True,plot_color='#6699ff')\r\nwebback_d = S.Tasks('SRV',num=15,length=1,is_group=True,plot_color='#FF99ff')\r\n   \r\n# Assign tasks to resources\r\nwebfront_d += Jim\r\nwebback_d += Peter | Nick\r\nsysarch += Nick | Bob\r\n\r\n#Here I try to define that all tasks in the group webback_d should only happen after the task sysarch is completed:\r\nfor task in webback_d:\r\n    S += sysarch < task\r\n\r\nsolvers.mip.solve(S,msg=1)\r\n\r\nprint(S.solution())\r\nplotters.matplotlib.plot(S,show_task_labels=True,fig_size=(10,5))\r\n```"},"comment":{"url":"https://api.github.com/repos/timnon/pyschedule/issues/comments/433880951","html_url":"https://github.com/timnon/pyschedule/issues/70#issuecomment-433880951","issue_url":"https://api.github.com/repos/timnon/pyschedule/issues/70","id":433880951,"node_id":"MDEyOklzc3VlQ29tbWVudDQzMzg4MDk1MQ==","user":{"login":"timnon","id":5597397,"node_id":"MDQ6VXNlcjU1OTczOTc=","avatar_url":"https://avatars2.githubusercontent.com/u/5597397?v=4","gravatar_id":"","url":"https://api.github.com/users/timnon","html_url":"https://github.com/timnon","followers_url":"https://api.github.com/users/timnon/followers","following_url":"https://api.github.com/users/timnon/following{/other_user}","gists_url":"https://api.github.com/users/timnon/gists{/gist_id}","starred_url":"https://api.github.com/users/timnon/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/timnon/subscriptions","organizations_url":"https://api.github.com/users/timnon/orgs","repos_url":"https://api.github.com/users/timnon/repos","events_url":"https://api.github.com/users/timnon/events{/privacy}","received_events_url":"https://api.github.com/users/timnon/received_events","type":"User","site_admin":false},"created_at":"2018-10-29T11:45:55Z","updated_at":"2018-10-29T11:45:55Z","author_association":"OWNER","body":"Yes, your approach is exactly right, because all the parts of the long tasks are interchangeable, so it's good to organize them in a group for performance reasons."}}
{"actor":{"display_login":"timnon"}}