Minimal viable state

[130s]

Get the tool working for just one input.

CoS

• [x] In the loop where persons get assigned per day, there are the same set of persons already assigned in a subsequent day's object. Now one issue is resolved in https://github.com/kinu-garage/nton_matching/issues/6#issuecomment-1938855631 then got a new one.

• [x] Some, not all, persons that just got assigned in a previous round of an iteration for a date get emptied.

  Example. You see leaders in 04-01 got assigned then later emptied. In fact looks like it happens even before the date iteration moves to the next date.

  ``` INFO:n_to_n_matching.matcher:Debug: 116 Memory addr of date.assignees_leader: 139920641240384: Date=2024-04-01 assignees stored. Leader: [guardian-name1], Committee: [guardian-name2, guardian-name3], Non-commitee: [guardian-name6, guardian-name7, guardian-name8] INFO:n_to_n_matching.matcher:Debug: 116 Memory addr of date.assignees_leader: 139920641240384: Date=2024-04-08 assignees stored. Leader: [], Committee: [], Non-commitee: [] INFO:n_to_n_matching.matcher:Debug: 116 Memory addr of date.assignees_leader: 139920641240384: Date=2024-04-15 assignees stored. Leader: [], Committee: [], Non-commitee: [] INFO:n_to_n_matching.matcher:Debug: 116 Memory addr of date.assignees_leader: 139920641240384: Date=2024-04-22 assignees stored. Leader: [], Committee: [], Non-commitee: [] INFO:n_to_n_matching.matcher:AFTER assigning a day: Date=2024-04-01 assignees stored. Leader: [], Committee: [guardian-name2, guardian-name3], Non-commitee: [guardian-name6, guardian-name7, guardian-name8] INFO:n_to_n_matching.matcher:AFTER assigning a day: All dates_need_attention=[, , , ] dates_lgtm=[] INFO:n_to_n_matching.matcher:BEFORE assigning: Date=2024-04-08 assignees stored. Leader: [], Committee: [], Non-commitee: [] INFO:n_to_n_matching.matcher:Debug: 116 Memory addr of date.assignees_leader: 139920641240256: Date=2024-04-01 assignees stored. Leader: [], Committee: [guardian-name2, guardian-name3], Non-commitee: [guardian-name6, guardian-name7, guardian-name8] INFO:n_to_n_matching.matcher:Debug: 116 Memory addr of date.assignees_leader: 139920641240256: Date=2024-04-08 assignees stored. Leader: [guardian-name1], Committee: [], Non-commitee: [] INFO:n_to_n_matching.matcher:Debug: 116 Memory addr of date.assignees_leader: 139920641240256: Date=2024-04-15 assignees stored. Leader: [], Committee: [], Non-commitee: [] INFO:n_to_n_matching.matcher:Debug: 116 Memory addr of date.assignees_leader: 139920641240256: Date=2024-04-22 assignees stored. Leader: [], Committee: [], Non-commitee: [] INFO:n_to_n_matching.matcher:Debug: 116 Memory addr of date.assignees_leader: 139920641240256: Date=2024-04-01 assignees stored. Leader: [], Committee: [guardian-name2, guardian-name3], Non-commitee: [guardian-name6, guardian-name7, guardian-name8] ```
• [x] All 4 days the same persons are assigned. Every person is put into free_workers stack and no one in the other stacks is absolutely wrong. There must be a bug.

  INFO:n_to_n_matching.matcher:151 free_workers [guardian-name1, guardian-name2, guardian-name3, guardian-name4, guardian-name5, guardian-name6, guardian-name7, guardian-name8, guardian-name9, guardian-name10]
  fullybookd_workers []
  overlybooked_workers []

• [x] max_occurence is ignored. In the cases above, it's 2 for all three roles but number goes up to 4.

• [x] Error in the custom branch of the upstream matching module. TypeError: cannot convert dictionary update sequence element #0 to a sequence

  log

  ``` INFO:n_to_n_matching.matcher: Date=2024-04-01 assignees stored. Leader: [guardian-name1], Committee: [guardian-name2, guardian-name3], Non-commitee: [guardian-name6, guardian-name7, guardian-name8] INFO:n_to_n_matching.matcher: Date=2024-04-08 assignees stored. Leader: [guardian-name1], Committee: [guardian-name2, guardian-name3, guardian-name5], Non-commitee: [guardian-name6, guardian-name7, guardian-name8, guardian-name9] INFO:n_to_n_matching.matcher: Date=2024-04-15 assignees stored. Leader: [guardian-name4], Committee: [guardian-name2, guardian-name3], Non-commitee: [guardian-name9, guardian-name10, guardian-name6] INFO:n_to_n_matching.matcher: Date=2024-04-22 assignees stored. Leader: [guardian-name4], Committee: [guardian-name5, guardian-name2], Non-commitee: [guardian-name10, guardian-name7, guardian-name8] INFO:n_to_n_matching.matcher:AFTER assigning a day: Date=2024-04-22 assignees stored. Leader: [guardian-name4], Committee: [guardian-name5, guardian-name2], Non-commitee: [guardian-name10, guardian-name7, guardian-name8] INFO:n_to_n_matching.matcher:AFTER assigning a day: All dates_need_attention=[, , , ] dates_lgtm=[, , , ] Traceback (most recent call last): File "/usr/local/bin/gjls_match", line 8, in sys.exit(main()) File "/cws/src/130s/nton_matching/n_to_n_matching/src/n_to_n_matching/__main__.py", line 8, in main test_1() File "/cws/src/130s/nton_matching/n_to_n_matching/src/n_to_n_matching/test_main.py", line 133, in test_1 solution = game.solve() File "/cws/src/130s/nton_matching/n_to_n_matching/src/n_to_n_matching/matcher.py", line 618, in solve self._matching = GjVolunteerMatching( File "/cws/src/130s/nton_matching/n_to_n_matching/src/n_to_n_matching/matcher.py", line 85, in __init__ super().__init__(dictionary) File "/cws/src/daffidwilde/matching/src/matching/matchings.py", line 83, in __init__ super().__init__(dictionary) File "/cws/src/daffidwilde/matching/src/matching/base.py", line 225, in __init__ self._data.update(dictionary) TypeError: cannot convert dictionary update sequence element #0 to a sequence ```

• [x] mvp-6. Overbook number keeps soaring beyond the limit of overbook threshold.

  Log

  ``` 2024-04-01 Leader: [guardian-name1] Commitee assignee: [guardian-name2, guardian-name3] General assignee: [guardian-name6, guardian-name7, guardian-name8] 2024-04-08 Leader: [guardian-name1] Commitee assignee: [guardian-name2, guardian-name3, guardian-name5] General assignee: [guardian-name6, guardian-name7, guardian-name8, guardian-name9] 2024-04-15 Leader: [guardian-name1] Commitee assignee: [guardian-name2, guardian-name3] General assignee: [guardian-name6, guardian-name7, guardian-name8] 2024-04-22 Leader: [guardian-name1] Commitee assignee: [guardian-name2, guardian-name3] General assignee: [guardian-name6, guardian-name7, guardian-name8] 2024-04-29 Leader: [guardian-name4] Commitee assignee: [guardian-name2, guardian-name3] General assignee: [guardian-name6, guardian-name7, guardian-name8] 2024-05-06 Leader: [guardian-name4] Commitee assignee: [guardian-name5, guardian-name2] General assignee: [guardian-name9, guardian-name10, guardian-name6] 2024-05-13 Leader: [guardian-name4] Commitee assignee: [guardian-name5, guardian-name3] General assignee: [guardian-name9, guardian-name10, guardian-name7] 2024-05-20 Leader: [guardian-name4] Commitee assignee: [guardian-name5] General assignee: [guardian-name9, guardian-name10, guardian-name8] ```

• [x] mvp-7. Among persons with the same role, the diff of #assigned dated should be 1 at most (where the largest #assigned dates must be withing the #overbook threshhold). But I see the diff to be 2.

  See ppl with role 2 in the following result.

  *****************Result***************** Max allowance: {: {'max_occurence': 2, 'num_unlucky_person': 2}, : {'max_occurence': 4, 'num_unlucky_person': 1}, : {'max_occurence': 3, 'num_unlucky_person': 1}} P-ID 1, role: 1, #assigned date: 3 P-ID 2, role: 2, #assigned date: 5 P-ID 3, role: 2, #assigned date: 4 P-ID 4, role: 1, #assigned date: 3 P-ID 5, role: 2, #assigned date: 4 P-ID 6, role: 3, #assigned date: 4 P-ID 7, role: 3, #assigned date: 4 P-ID 8, role: 3, #assigned date: 3 P-ID 9, role: 3, #assigned date: 3 P-ID 10, role: 3, #assigned date: 3 P-ID 11, role: 1, #assigned date: 2 P-ID 12, role: 3, #assigned date: 3 P-ID 13, role: 2, #assigned date: 4 P-ID 14, role: 3, #assigned date: 3 P-ID 15, role: 3, #assigned date: 2 2024-04-01 Leader: [guardian-name1] Commitee assignee: [guardian-name2, guardian-name3] General assignee: [guardian-name6, guardian-name7, guardian-name8] 2024-04-08 Leader: [guardian-name1] Commitee assignee: [guardian-name2, guardian-name3, guardian-name5] General assignee: [guardian-name6, guardian-name7, guardian-name8, guardian-name9] 2024-04-15 Leader: [guardian-name4] Commitee assignee: [guardian-name2, guardian-name3] General assignee: [guardian-name6, guardian-name7, guardian-name8] 2024-04-22 Leader: [guardian-name4] Commitee assignee: [guardian-name2, guardian-name3] General assignee: [guardian-name9, guardian-name10, guardian-name12] 2024-04-29 Leader: [guardian-name11] Commitee assignee: [guardian-name5, guardian-name13] General assignee: [guardian-name9, guardian-name10, guardian-name12] 2024-05-06 Leader: [guardian-name11] Commitee assignee: [guardian-name5, guardian-name13] General assignee: [guardian-name10, guardian-name12, guardian-name14] 2024-05-13 Leader: [guardian-name1] Commitee assignee: [guardian-name5, guardian-name13] General assignee: [guardian-name14, guardian-name15, guardian-name6] 2024-05-20 Leader: [guardian-name4] Commitee assignee: [guardian-name13, guardian-name2] General assignee: [guardian-name14, guardian-name15, guardian-name7] See role-id=3: P-ID 6, role: 3, #assigned date: 4 P-ID 7, role: 3, #assigned date: 4 P-ID 8, role: 3, #assigned date: 3 P-ID 9, role: 3, #assigned date: 3 P-ID 10, role: 3, #assigned date: 3 P-ID 12, role: 3, #assigned date: 3 P-ID 14, role: 3, #assigned date: 3 P-ID 15, role: 3, #assigned date: 2
• [x] mvp-8. See the log in mvp-7. Same person tends to be assigned to dates closer, most likely on consecutive weekends, which is not supposed to happen.

• [ ] mvp-9: Same person assigned on the same day. --> Cont'd https://github.com/kinu-garage/nton_matching/issues/8

  log

  ``` *****************Result***************** Max allowance: {: {'max_occurence': 1, 'num_unlucky_person': 3}, : {'max_occurence': 2, 'num_unlucky_person': 5}, : {'max_occurence': 1, 'num_unlucky_person': 11}} P-ID 1, role: 1, #assigned date: 1 P-ID 2, role: 2, #assigned date: 1 P-ID 3, role: 2, #assigned date: 1 P-ID 4, role: 1, #assigned date: 1 P-ID 5, role: 2, #assigned date: 1 P-ID 6, role: 3, #assigned date: 1 P-ID 7, role: 3, #assigned date: 1 P-ID 8, role: 3, #assigned date: 1 P-ID 9, role: 3, #assigned date: 1 P-ID 10, role: 3, #assigned date: 1 P-ID 11, role: 1, #assigned date: 1 P-ID 12, role: 3, #assigned date: 1 P-ID 13, role: 2, #assigned date: 1 P-ID 14, role: 3, #assigned date: 1 P-ID 15, role: 3, #assigned date: 1 P-ID 16, role: 1, #assigned date: 1 P-ID 17, role: 3, #assigned date: 2 P-ID 18, role: 2, #assigned date: 1 P-ID 19, role: 3, #assigned date: 1 P-ID 20, role: 3, #assigned date: 1 P-ID 21, role: 1, #assigned date: 1 P-ID 22, role: 3, #assigned date: 1 P-ID 23, role: 2, #assigned date: 1 P-ID 24, role: 3, #assigned date: 1 P-ID 25, role: 3, #assigned date: 1 2024-04-01 Leader: [guardian-name11] Commitee assignee: [guardian-name13, guardian-name23] General assignee: [guardian-name24, guardian-name14, guardian-name15] 2024-04-08 Leader: [guardian-name4] Commitee assignee: [guardian-name3, guardian-name2, guardian-name18] General assignee: [guardian-name20, guardian-name6, guardian-name25, guardian-name19] 2024-04-15 Leader: [guardian-name1] Commitee assignee: [guardian-name5] General assignee: [guardian-name10, guardian-name9, guardian-name22] 2024-04-22 Leader: [guardian-name16] Commitee assignee: [] General assignee: [guardian-name8, guardian-name12, guardian-name7] 2024-04-29 Leader: [guardian-name21] Commitee assignee: [] General assignee: [guardian-name17, guardian-name17] 2024-05-06 Leader: [] Commitee assignee: [] General assignee: [] 2024-05-13 Leader: [] Commitee assignee: [] General assignee: [] 2024-05-20 Leader: [] Commitee assignee: [] General assignee: [] ```

• [x] mvp-10: Interval is falsely taken as #day, not #week

  log

  ``` WARNING:n_to_n_matching.match_game:Overbooking is triggered.:=^20 WARNING:n_to_n_matching.match_game:person.last_assigned_date=datetime.date(2024, 4, 1), date_wd.date=datetime.date(2024, 5, 20), req_space_days=5, days_interval=49 WARNING:n_to_n_matching.match_game:Can't assign this person (ID=3) on 2024-05-20 as there must be 5 days since the last assignment i.e. 2024-04-01. WARNING:n_to_n_matching.match_game:person.last_assigned_date=datetime.date(2024, 4, 15), date_wd.date=datetime.date(2024, 5, 20), req_space_days=4, days_interval=35 WARNING:n_to_n_matching.match_game:Can't assign this person (ID=1) on 2024-05-20 as there must be 4 days since the last assignment i.e. 2024-04-15. WARNING:n_to_n_matching.match_game:person.last_assigned_date=datetime.date(2024, 4, 22), date_wd.date=datetime.date(2024, 5, 20), req_space_days=5, days_interval=28 WARNING:n_to_n_matching.match_game:Can't assign this person (ID=3) on 2024-05-20 as there must be 5 days since the last assignment i.e. 2024-04-22. ```

• [ ] mvp-11: Unassigned roles although there's a room for many ppl to be assigned to that role more. --> Cont'd https://github.com/kinu-garage/nton_matching/issues/9

  log

  ``` P-ID 5, role: 2, #assigned date: 2 P-ID 6, role: 3, #assigned date: 2 P-ID 7, role: 3, #assigned date: 1 P-ID 8, role: 3, #assigned date: 1 P-ID 9, role: 3, #assigned date: 1 P-ID 10, role: 3, #assigned date: 1 P-ID 11, role: 1, #assigned date: 2 P-ID 12, role: 3, #assigned date: 2 P-ID 13, role: 2, #assigned date: 1 P-ID 14, role: 3, #assigned date: 1 P-ID 15, role: 3, #assigned date: 1 P-ID 16, role: 1, #assigned date: 2 P-ID 17, role: 3, #assigned date: 1 P-ID 18, role: 2, #assigned date: 2 P-ID 19, role: 3, #assigned date: 2 P-ID 20, role: 3, #assigned date: 2 P-ID 21, role: 3, #assigned date: 1 P-ID 22, role: 3, #assigned date: 1 P-ID 23, role: 2, #assigned date: 1 P-ID 24, role: 3, #assigned date: 1 P-ID 25, role: 3, #assigned date: 1 P-ID 26, role: 3, #assigned date: 1 P-ID 27, role: 3, #assigned date: 2 P-ID 28, role: 2, #assigned date: 2 P-ID 29, role: 3, #assigned date: 1 P-ID 30, role: 3, #assigned date: 1 P-ID 31, role: 2, #assigned date: 2 P-ID 32, role: 3, #assigned date: 1 P-ID 33, role: 2, #assigned date: 2 P-ID 34, role: 3, #assigned date: 1 P-ID 35, role: 3, #assigned date: 1 2024-04-01 Leader: [guardian-name11] Commitee assignee: [guardian-name13, guardian-name23] General assignee: [guardian-name10, guardian-name15, guardian-name25] 2024-04-08 Leader: [guardian-name11] Commitee assignee: [guardian-name3, guardian-name5, guardian-name2] General assignee: [guardian-name34, guardian-name30, guardian-name24, guardian-name26] 2024-04-15 Leader: [guardian-name4] Commitee assignee: [guardian-name31, guardian-name28] General assignee: [guardian-name32, guardian-name9, guardian-name35] 2024-04-22 Leader: [guardian-name4] Commitee assignee: [guardian-name18, guardian-name33] General assignee: [guardian-name6, guardian-name19, guardian-name12] 2024-04-29 Leader: [guardian-name16] Commitee assignee: [guardian-name2, guardian-name33] General assignee: [guardian-name22, guardian-name20, guardian-name27] 2024-05-06 Leader: [guardian-name1] Commitee assignee: [guardian-name5, guardian-name18] General assignee: [guardian-name14, guardian-name7, guardian-name21] 2024-05-13 Leader: [guardian-name16] Commitee assignee: [guardian-name28, guardian-name31] General assignee: [guardian-name29, guardian-name17, guardian-name8] 2024-05-20 Leader: [guardian-name1] Commitee assignee: [] General assignee: [guardian-name6, guardian-name19, guardian-name27, guardian-name12, guardian-name20] ```

[130s]

Output 2/09

``` # gjls_match /cws/src/daffidwilde/matching/src/matching/matchings.py:3: DeprecationWarning: Pyarrow will become a required dependency of pandas in the next major release of pandas (pandas 3.0), (to allow more performant data types, such as the Arrow string type, and better interoperability with other libraries) but was not found to be installed on your system. If this would cause problems for you, please provide us feedback at https://github.com/pandas-dev/pandas/issues/54466 import pandas Python sys.path: ['/usr/local/bin', '/usr/local/lib/python39.zip', '/usr/local/lib/python3.9', '/usr/local/lib/python3.9/lib-dynload', '/root/.local/lib/python3.9/site-packages', '/cws/src/daffidwilde/matching/src', '/usr/local/lib/python3.9/site-packages', '/cws/src/130s/nton_matching/n_to_n_matching/src'] INFO:n_to_n_matching.matcher:dates_attention: [, , , ] dates_lgtm: [] INFO:n_to_n_matching.matcher:#dates 4 INFO:n_to_n_matching.matcher:max_allowance: {: {'max_occurence': 2, 'num_unlucky_person': 0}, : {'max_occurence': 2, 'num_unlucky_person': 2}, : {'max_occurence': 2, 'num_unlucky_person': 2}} INFO:n_to_n_matching.matcher:BEFORE assigning: Date=2024-04-01 assignees stored. Leader: [], Committee: [], Non-commitee: [] WARNING:n_to_n_matching.matcher:TBD hmmm not sure what this means, needs looked into. _enough_leaders: True, _enough_committee: True, _enough_noncommittee: False WARNING:n_to_n_matching.matcher:TBD hmmm not sure what this means, needs looked into. _enough_leaders: True, _enough_committee: True, _enough_noncommittee: False INFO:n_to_n_matching.matcher:At the end of `_assign_day` Date=2024-04-01 assignees stored. Leader: [guardian-name1], Committee: [guardian-name2, guardian-name3], Non-commitee: [guardian-name6, guardian-name7, guardian-name8] INFO:n_to_n_matching.matcher:AFTER assigning a day: Date=2024-04-01 assignees stored. Leader: [guardian-name1], Committee: [guardian-name2, guardian-name3], Non-commitee: [guardian-name6, guardian-name7, guardian-name8] INFO:n_to_n_matching.matcher:BEFORE assigning: Date=2024-04-08 assignees stored. Leader: [guardian-name1], Committee: [guardian-name2, guardian-name3], Non-commitee: [guardian-name6, guardian-name7, guardian-name8] INFO:n_to_n_matching.matcher:At the end of `_assign_day` Date=2024-04-08 assignees stored. Leader: [guardian-name1], Committee: [guardian-name2, guardian-name3], Non-commitee: [guardian-name6, guardian-name7, guardian-name8] INFO:n_to_n_matching.matcher:AFTER assigning a day: Date=2024-04-08 assignees stored. Leader: [guardian-name1], Committee: [guardian-name2, guardian-name3], Non-commitee: [guardian-name6, guardian-name7, guardian-name8] INFO:n_to_n_matching.matcher:BEFORE assigning: Date=2024-04-15 assignees stored. Leader: [guardian-name1], Committee: [guardian-name2, guardian-name3], Non-commitee: [guardian-name6, guardian-name7, guardian-name8] INFO:n_to_n_matching.matcher:At the end of `_assign_day` Date=2024-04-15 assignees stored. Leader: [guardian-name1], Committee: [guardian-name2, guardian-name3], Non-commitee: [guardian-name6, guardian-name7, guardian-name8] INFO:n_to_n_matching.matcher:AFTER assigning a day: Date=2024-04-15 assignees stored. Leader: [guardian-name1], Committee: [guardian-name2, guardian-name3], Non-commitee: [guardian-name6, guardian-name7, guardian-name8] INFO:n_to_n_matching.matcher:BEFORE assigning: Date=2024-04-22 assignees stored. Leader: [guardian-name1], Committee: [guardian-name2, guardian-name3], Non-commitee: [guardian-name6, guardian-name7, guardian-name8] INFO:n_to_n_matching.matcher:At the end of `_assign_day` Date=2024-04-22 assignees stored. Leader: [guardian-name1], Committee: [guardian-name2, guardian-name3], Non-commitee: [guardian-name6, guardian-name7, guardian-name8] INFO:n_to_n_matching.matcher:AFTER assigning a day: Date=2024-04-22 assignees stored. Leader: [guardian-name1], Committee: [guardian-name2, guardian-name3], Non-commitee: [guardian-name6, guardian-name7, guardian-name8] Traceback (most recent call last): File "/usr/local/bin/gjls_match", line 8, in sys.exit(main()) File "/cws/src/130s/nton_matching/n_to_n_matching/src/n_to_n_matching/__main__.py", line 8, in main test_1() File "/cws/src/130s/nton_matching/n_to_n_matching/src/n_to_n_matching/test_main.py", line 128, in test_1 solution = game.solve() File "/cws/src/130s/nton_matching/n_to_n_matching/src/n_to_n_matching/matcher.py", line 580, in solve self._matching = GjVolunteerMatching( File "/cws/src/130s/nton_matching/n_to_n_matching/src/n_to_n_matching/matcher.py", line 84, in __init__ super().__init__(dictionary) File "/cws/src/daffidwilde/matching/src/matching/matchings.py", line 83, in __init__ super().__init__(dictionary) File "/cws/src/daffidwilde/matching/src/matching/base.py", line 225, in __init__ self._data.update(dictionary) TypeError: cannot convert dictionary update sequence element #0 to a sequence ```

I'm seeing issues: (moved to OP)

[130s]

I see the inner list objects are all pointing to the same memory address...

``` INFO:n_to_n_matching.matcher:Debug: 142: Date=2024-04-22 assignees stored. Leader: [], Committee: [], Non-commitee: [] [1894/30291] INFO:n_to_n_matching.matcher:Debug: 116 Memory addr of date.assignees_leader: 139812035944064: Date=2024-04-01 assignees stored. Leader: [guardian-name1], Committee: [], Non-commitee: [] INFO:n_to_n_matching.matcher:Debug: 116 Memory addr of date.assignees_leader: 139812035944064: Date=2024-04-08 assignees stored. Leader: [guardian-name1], Committee: [], Non-commitee: [] INFO:n_to_n_matching.matcher:Debug: 116 Memory addr of date.assignees_leader: 139812035944064: Date=2024-04-15 assignees stored. Leader: [guardian-name1], Committee: [], Non-commitee: [] INFO:n_to_n_matching.matcher:Debug: 116 Memory addr of date.assignees_leader: 139812035944064: Date=2024-04-22 assignees stored. Leader: [guardian-name1], Committee: [], Non-commitee: [] INFO:n_to_n_matching.matcher:Debug: 114: Date=2024-04-01 assignees stored. Leader: [guardian-name1], Committee: [], Non-commitee: [] INFO:n_to_n_matching.matcher:Debug: 114: Date=2024-04-08 assignees stored. Leader: [guardian-name1], Committee: [], Non-commitee: [] INFO:n_to_n_matching.matcher:Debug: 114: Date=2024-04-15 assignees stored. Leader: [guardian-name1], Committee: [], Non-commitee: [] INFO:n_to_n_matching.matcher:Debug: 114: Date=2024-04-22 assignees stored. Leader: [guardian-name1], Committee: [], Non-commitee: [] INFO:n_to_n_matching.matcher:Debug: 141: Date=2024-04-01 assignees stored. Leader: [guardian-name1], Committee: [], Non-commitee: [] INFO:n_to_n_matching.matcher:Debug: 141: Date=2024-04-08 assignees stored. Leader: [guardian-name1], Committee: [], Non-commitee: [] ```

[130s]

Now one issue is resolved in https://github.com/kinu-garage/nton_matching/issues/6#issuecomment-1938855631 then got a new one.

• [ ] Some, not all, persons that just got assigned in a previous round of an iteration for a date get emptied.

  Example. You see leaders in 04-01 got assigned then later emptied. In fact looks like it happens even before the date iteration moves to the next date.

  ``` INFO:n_to_n_matching.matcher:Debug: 116 Memory addr of date.assignees_leader: 139920641240384: Date=2024-04-01 assignees stored. Leader: [guardian-name1], Committee: [guardian-name2, guardian-name3], Non-commitee: [guardian-name6, guardian-name7, guardian-name8] INFO:n_to_n_matching.matcher:Debug: 116 Memory addr of date.assignees_leader: 139920641240384: Date=2024-04-08 assignees stored. Leader: [], Committee: [], Non-commitee: [] INFO:n_to_n_matching.matcher:Debug: 116 Memory addr of date.assignees_leader: 139920641240384: Date=2024-04-15 assignees stored. Leader: [], Committee: [], Non-commitee: [] INFO:n_to_n_matching.matcher:Debug: 116 Memory addr of date.assignees_leader: 139920641240384: Date=2024-04-22 assignees stored. Leader: [], Committee: [], Non-commitee: [] INFO:n_to_n_matching.matcher:AFTER assigning a day: Date=2024-04-01 assignees stored. Leader: [], Committee: [guardian-name2, guardian-name3], Non-commitee: [guardian-name6, guardian-name7, guardian-name8] INFO:n_to_n_matching.matcher:AFTER assigning a day: All dates_need_attention=[, , , ] dates_lgtm=[] INFO:n_to_n_matching.matcher:BEFORE assigning: Date=2024-04-08 assignees stored. Leader: [], Committee: [], Non-commitee: [] INFO:n_to_n_matching.matcher:Debug: 116 Memory addr of date.assignees_leader: 139920641240256: Date=2024-04-01 assignees stored. Leader: [], Committee: [guardian-name2, guardian-name3], Non-commitee: [guardian-name6, guardian-name7, guardian-name8] INFO:n_to_n_matching.matcher:Debug: 116 Memory addr of date.assignees_leader: 139920641240256: Date=2024-04-08 assignees stored. Leader: [guardian-name1], Committee: [], Non-commitee: [] INFO:n_to_n_matching.matcher:Debug: 116 Memory addr of date.assignees_leader: 139920641240256: Date=2024-04-15 assignees stored. Leader: [], Committee: [], Non-commitee: [] INFO:n_to_n_matching.matcher:Debug: 116 Memory addr of date.assignees_leader: 139920641240256: Date=2024-04-22 assignees stored. Leader: [], Committee: [], Non-commitee: [] INFO:n_to_n_matching.matcher:Debug: 116 Memory addr of date.assignees_leader: 139920641240256: Date=2024-04-01 assignees stored. Leader: [], Committee: [guardian-name2, guardian-name3], Non-commitee: [guardian-name6, guardian-name7, guardian-name8] ```

[130s]

• [ ] Some, not all, persons that just got assigned in a previous round of an iteration for a date get emptied.

This was caused by a temporary debug code, which is removed now so no issue.

[130s]

• [ ] All 4 days the same persons are assigned.

Every person is put into free_workers stack and no one in the other stacks is absolutely wrong. There must be a bug.

INFO:n_to_n_matching.matcher:151 free_workers [guardian-name1, guardian-name2, guardian-name3, guardian-name4, guardian-name5, guardian-name6, guardian-name7, guardian-name8, guardian-name9, guardian-name10]
fullybookd_workers []
overlybooked_workers []

[130s]

• [ ] Error in the custom branch of the upstream matching module. TypeError: cannot convert dictionary update sequence element #0 to a sequence

  log

  ``` INFO:n_to_n_matching.matcher: Date=2024-04-01 assignees stored. Leader: [guardian-name1], Committee: [guardian-name2, guardian-name3], Non-commitee: [guardian-name6, guardian-name7, guardian-name8] INFO:n_to_n_matching.matcher: Date=2024-04-08 assignees stored. Leader: [guardian-name1], Committee: [guardian-name2, guardian-name3, guardian-name5], Non-commitee: [guardian-name6, guardian-name7, guardian-name8, guardian-name9] INFO:n_to_n_matching.matcher: Date=2024-04-15 assignees stored. Leader: [guardian-name4], Committee: [guardian-name2, guardian-name3], Non-commitee: [guardian-name9, guardian-name10, guardian-name6] INFO:n_to_n_matching.matcher: Date=2024-04-22 assignees stored. Leader: [guardian-name4], Committee: [guardian-name5, guardian-name2], Non-commitee: [guardian-name10, guardian-name7, guardian-name8] INFO:n_to_n_matching.matcher:AFTER assigning a day: Date=2024-04-22 assignees stored. Leader: [guardian-name4], Committee: [guardian-name5, guardian-name2], Non-commitee: [guardian-name10, guardian-name7, guardian-name8] INFO:n_to_n_matching.matcher:AFTER assigning a day: All dates_need_attention=[, , , ] dates_lgtm=[, , , ] Traceback (most recent call last): File "/usr/local/bin/gjls_match", line 8, in sys.exit(main()) File "/cws/src/130s/nton_matching/n_to_n_matching/src/n_to_n_matching/__main__.py", line 8, in main test_1() File "/cws/src/130s/nton_matching/n_to_n_matching/src/n_to_n_matching/test_main.py", line 133, in test_1 solution = game.solve() File "/cws/src/130s/nton_matching/n_to_n_matching/src/n_to_n_matching/matcher.py", line 618, in solve self._matching = GjVolunteerMatching( File "/cws/src/130s/nton_matching/n_to_n_matching/src/n_to_n_matching/matcher.py", line 85, in __init__ super().__init__(dictionary) File "/cws/src/daffidwilde/matching/src/matching/matchings.py", line 83, in __init__ super().__init__(dictionary) File "/cws/src/daffidwilde/matching/src/matching/base.py", line 225, in __init__ self._data.update(dictionary) TypeError: cannot convert dictionary update sequence element #0 to a sequence ```

[130s]

• [ ] Overbook number keeps soaring beyond the limit of overbook threshold.

  Log

  INFO:n_to_n_matching.matcher:118: Date=2024-04-01 assignees stored. Leader: [guardian-name1], Committee: [guardian-name2, guardian-name3], Non-commitee: [guardian-name6, guardian-name7, guardian-name8] INFO:n_to_n_matching.matcher:118: Date=2024-04-08 assignees stored. Leader: [guardian-name1], Committee: [guardian-name2, guardian-name3, guardian-name5], Non-commitee: [guardian-name6, guardian-name7, guardian-name8, guardian-name9] INFO:n_to_n_matching.matcher:118: Date=2024-04-15 assignees stored. Leader: [guardian-name1], Committee: [guardian-name2, guardian-name3], Non-commitee: [guardian-name6, guardian-name7, guardian-name8] INFO:n_to_n_matching.matcher:118: Date=2024-04-22 assignees stored. Leader: [guardian-name1], Committee: [guardian-name2, guardian-name3], Non-commitee: [guardian-name6, guardian-name7, guardian-name8] INFO:n_to_n_matching.matcher:118: Date=2024-04-29 assignees stored. Leader: [guardian-name4], Committee: [guardian-name2, guardian-name3], Non-commitee: [guardian-name6, guardian-name7, guardian-name8] INFO:n_to_n_matching.matcher:118: Date=2024-05-06 assignees stored. Leader: [guardian-name4], Committee: [guardian-name5, guardian-name2], Non-commitee: [guardian-name9, guardian-name10, guardian-name6] INFO:n_to_n_matching.matcher:118: Date=2024-05-13 assignees stored. Leader: [guardian-name4], Committee: [guardian-name5, guardian-name3], Non-commitee: [guardian-name9, guardian-name10, guardian-name7] INFO:n_to_n_matching.matcher:118: Date=2024-05-20 assignees stored. Leader: [guardian-name4], Committee: [guardian-name5], Non-commitee: [guardian-name9, guardian-name10, guardian-name8] INFO:n_to_n_matching.matcher:AFTER assigning a day: Date=2024-05-20 assignees stored. Leader: [guardian-name4], Committee: [guardian-name5], Non-commitee: [guardian-name9, guardian-name10, guardian-name8] INFO:n_to_n_matching.matcher:AFTER assigning a day: All dates_need_attention=[, , , , , , , ] dates_lgtm=[, , , , , , , ]

[130s]

• [ ] Among persons with the same role, the diff of #assigned dated should be 1 at most (where the largest #assigned dates must be withing the #overbook threshhold). But I see the diff to be 2.

  See ppl with role 2 in the following result.

  ``` *****************Result***************** Max allowance: {: {'max_occurence': 2, 'num_unlucky_person': 2}, : {'max_occurence': 4, 'num_unlucky_person': 1}, : {'max_occurence': 3, 'num_unlucky_person': 1}} P-ID 1, role: 1, #assigned date: 3 P-ID 2, role: 2, #assigned date: 5 P-ID 3, role: 2, #assigned date: 4 P-ID 4, role: 1, #assigned date: 3 P-ID 5, role: 2, #assigned date: 4 P-ID 6, role: 3, #assigned date: 4 P-ID 7, role: 3, #assigned date: 4 P-ID 8, role: 3, #assigned date: 3 P-ID 9, role: 3, #assigned date: 3 P-ID 10, role: 3, #assigned date: 3 P-ID 11, role: 1, #assigned date: 2 P-ID 12, role: 3, #assigned date: 3 P-ID 13, role: 2, #assigned date: 4 P-ID 14, role: 3, #assigned date: 3 P-ID 15, role: 3, #assigned date: 2 2024-04-01 Leader: [guardian-name1] Commitee assignee: [guardian-name2, guardian-name3] General assignee: [guardian-name6, guardian-name7, guardian-name8] 2024-04-08 Leader: [guardian-name1] Commitee assignee: [guardian-name2, guardian-name3, guardian-name5] General assignee: [guardian-name6, guardian-name7, guardian-name8, guardian-name9] 2024-04-15 Leader: [guardian-name4] Commitee assignee: [guardian-name2, guardian-name3] General assignee: [guardian-name6, guardian-name7, guardian-name8] 2024-04-22 Leader: [guardian-name4] Commitee assignee: [guardian-name2, guardian-name3] General assignee: [guardian-name9, guardian-name10, guardian-name12] 2024-04-29 Leader: [guardian-name11] Commitee assignee: [guardian-name5, guardian-name13] General assignee: [guardian-name9, guardian-name10, guardian-name12] 2024-05-06 Leader: [guardian-name11] Commitee assignee: [guardian-name5, guardian-name13] General assignee: [guardian-name10, guardian-name12, guardian-name14] 2024-05-13 Leader: [guardian-name1] Commitee assignee: [guardian-name5, guardian-name13] General assignee: [guardian-name14, guardian-name15, guardian-name6] 2024-05-20 Leader: [guardian-name4] Commitee assignee: [guardian-name13, guardian-name2] General assignee: [guardian-name14, guardian-name15, guardian-name7] ```

[130s]

• [ ] mvp-9: Same person assigned on the same day.

  log

  ``` *****************Result***************** Max allowance: {: {'max_occurence': 1, 'num_unlucky_person': 3}, : {'max_occurence': 2, 'num_unlucky_person': 5}, : {'max_occurence': 1, 'num_unlucky_person': 11}} P-ID 1, role: 1, #assigned date: 1 P-ID 2, role: 2, #assigned date: 1 P-ID 3, role: 2, #assigned date: 1 P-ID 4, role: 1, #assigned date: 1 P-ID 5, role: 2, #assigned date: 1 P-ID 6, role: 3, #assigned date: 1 P-ID 7, role: 3, #assigned date: 1 P-ID 8, role: 3, #assigned date: 1 P-ID 9, role: 3, #assigned date: 1 P-ID 10, role: 3, #assigned date: 1 P-ID 11, role: 1, #assigned date: 1 P-ID 12, role: 3, #assigned date: 1 P-ID 13, role: 2, #assigned date: 1 P-ID 14, role: 3, #assigned date: 1 P-ID 15, role: 3, #assigned date: 1 P-ID 16, role: 1, #assigned date: 1 P-ID 17, role: 3, #assigned date: 2 P-ID 18, role: 2, #assigned date: 1 P-ID 19, role: 3, #assigned date: 1 P-ID 20, role: 3, #assigned date: 1 P-ID 21, role: 1, #assigned date: 1 P-ID 22, role: 3, #assigned date: 1 P-ID 23, role: 2, #assigned date: 1 P-ID 24, role: 3, #assigned date: 1 P-ID 25, role: 3, #assigned date: 1 2024-04-01 Leader: [guardian-name11] Commitee assignee: [guardian-name13, guardian-name23] General assignee: [guardian-name24, guardian-name14, guardian-name15] 2024-04-08 Leader: [guardian-name4] Commitee assignee: [guardian-name3, guardian-name2, guardian-name18] General assignee: [guardian-name20, guardian-name6, guardian-name25, guardian-name19] 2024-04-15 Leader: [guardian-name1] Commitee assignee: [guardian-name5] General assignee: [guardian-name10, guardian-name9, guardian-name22] 2024-04-22 Leader: [guardian-name16] Commitee assignee: [] General assignee: [guardian-name8, guardian-name12, guardian-name7] 2024-04-29 Leader: [guardian-name21] Commitee assignee: [] General assignee: [guardian-name17, guardian-name17] 2024-05-06 Leader: [] Commitee assignee: [] General assignee: [] 2024-05-13 Leader: [] Commitee assignee: [] General assignee: [] 2024-05-20 Leader: [] Commitee assignee: [] General assignee: [] ```

[130s]

• [ ] mvp-10: Interval is falsely taken as #day, not #week

  log

  ``` WARNING:n_to_n_matching.match_game:Overbooking is triggered.:=^20 WARNING:n_to_n_matching.match_game:person.last_assigned_date=datetime.date(2024, 4, 1), date_wd.date=datetime.date(2024, 5, 20), req_space_days=5, days_interval=49 WARNING:n_to_n_matching.match_game:Can't assign this person (ID=3) on 2024-05-20 as there must be 5 days since the last assignment i.e. 2024-04-01. WARNING:n_to_n_matching.match_game:person.last_assigned_date=datetime.date(2024, 4, 15), date_wd.date=datetime.date(2024, 5, 20), req_space_days=4, days_interval=35 WARNING:n_to_n_matching.match_game:Can't assign this person (ID=1) on 2024-05-20 as there must be 4 days since the last assignment i.e. 2024-04-15. WARNING:n_to_n_matching.match_game:person.last_assigned_date=datetime.date(2024, 4, 22), date_wd.date=datetime.date(2024, 5, 20), req_space_days=5, days_interval=28 WARNING:n_to_n_matching.match_game:Can't assign this person (ID=3) on 2024-05-20 as there must be 5 days since the last assignment i.e. 2024-04-22. ```

[130s]

• [ ] mvp-11: Unassigned roles although there's a room for many ppl to be assigned to that role more.

  log

  ``` P-ID 5, role: 2, #assigned date: 2 P-ID 6, role: 3, #assigned date: 2 P-ID 7, role: 3, #assigned date: 1 P-ID 8, role: 3, #assigned date: 1 P-ID 9, role: 3, #assigned date: 1 P-ID 10, role: 3, #assigned date: 1 P-ID 11, role: 1, #assigned date: 2 P-ID 12, role: 3, #assigned date: 2 P-ID 13, role: 2, #assigned date: 1 P-ID 14, role: 3, #assigned date: 1 P-ID 15, role: 3, #assigned date: 1 P-ID 16, role: 1, #assigned date: 2 P-ID 17, role: 3, #assigned date: 1 P-ID 18, role: 2, #assigned date: 2 P-ID 19, role: 3, #assigned date: 2 P-ID 20, role: 3, #assigned date: 2 P-ID 21, role: 3, #assigned date: 1 P-ID 22, role: 3, #assigned date: 1 P-ID 23, role: 2, #assigned date: 1 P-ID 24, role: 3, #assigned date: 1 P-ID 25, role: 3, #assigned date: 1 P-ID 26, role: 3, #assigned date: 1 P-ID 27, role: 3, #assigned date: 2 P-ID 28, role: 2, #assigned date: 2 P-ID 29, role: 3, #assigned date: 1 P-ID 30, role: 3, #assigned date: 1 P-ID 31, role: 2, #assigned date: 2 P-ID 32, role: 3, #assigned date: 1 P-ID 33, role: 2, #assigned date: 2 P-ID 34, role: 3, #assigned date: 1 P-ID 35, role: 3, #assigned date: 1 2024-04-01 Leader: [guardian-name11] Commitee assignee: [guardian-name13, guardian-name23] General assignee: [guardian-name10, guardian-name15, guardian-name25] 2024-04-08 Leader: [guardian-name11] Commitee assignee: [guardian-name3, guardian-name5, guardian-name2] General assignee: [guardian-name34, guardian-name30, guardian-name24, guardian-name26] 2024-04-15 Leader: [guardian-name4] Commitee assignee: [guardian-name31, guardian-name28] General assignee: [guardian-name32, guardian-name9, guardian-name35] 2024-04-22 Leader: [guardian-name4] Commitee assignee: [guardian-name18, guardian-name33] General assignee: [guardian-name6, guardian-name19, guardian-name12] 2024-04-29 Leader: [guardian-name16] Commitee assignee: [guardian-name2, guardian-name33] General assignee: [guardian-name22, guardian-name20, guardian-name27] 2024-05-06 Leader: [guardian-name1] Commitee assignee: [guardian-name5, guardian-name18] General assignee: [guardian-name14, guardian-name7, guardian-name21] 2024-05-13 Leader: [guardian-name16] Commitee assignee: [guardian-name28, guardian-name31] General assignee: [guardian-name29, guardian-name17, guardian-name8] 2024-05-20 Leader: [guardian-name1] Commitee assignee: [] General assignee: [guardian-name6, guardian-name19, guardian-name27, guardian-name12, guardian-name20] ```

[130s]

Released 0.1.1.