Automatically generated schedules should be attachable to a base schedule #3170
Comments
|
@rjsparks@nostrum.com changed status from |
|
@jennifer@painless-security.com changed status from |
|
@jennifer@painless-security.com set owner to |
|
@jennifer@painless-security.com commented It looks like it is already possible to attach a base schedule by editing schedule properties and selecting a base schedule. Is that enough for this ticket? |
|
@rjsparks@nostrum.com commented Possibly - the question is if there's anything in the base schedule that the automated scheduler should schedule around - if so, then there would need to be a way to specify a base schedule when running the generator so that it could attach the base before running its algorithms. If there's no way something in the base would make a difference to the scheduler then attaching it after the fact by editing its properties would be fine. |
|
@jennifer@painless-security.com commented In the base schedules I've checked, I think this would be enough - they only seem to contain scheduled items for non-regular timeslots, which I believe are ignored by the generator. However, I don't see any mechanism that prevents a regular assignment from being put in a base schedule. Without that, then it does need to consider the base schedule before running. I assume that base schedule entries should be treated as fixed and filled timeslots should be excluded from the optimization. Is that a good assumption? |
|
@rjsparks@nostrum.com commented That's what I had in mind as a possible future use. A concrete possible example - the base schedule might have a mini-conference, like ANRW, already placed in regular sessions. I was thinking an option on the management command would let us specify the base to use to allow this, but if we're not using it now, we could table the idea and work on it when we need it, accepting that we can attach base schedules after generation. (Also adding Liz in case she has a perspective to add). |
|
@jennifer@painless-security.com commented The management command option makes sense - I think it should be straightforward to load the schedule and filter timeslots that are in use before running the scheduler. I am halfway there without any obvious roadblocks. Unless something unexpected crops up, I think it makes sense to implement this now. |
|
@jennifer@painless-security.com changed status from |
|
@jennifer@painless-security.com set resolution to |
|
@jennifer@painless-security.com commented Fixed in b88a695: Allow generated schedules to inherit from a base schedule. Fixes #3170. Commit ready for merge. |
|
@rjsparks@nostrum.com commented Fixed in 0dbd389: Merged in b88a695 from jennifer@painless-security.com: |
owner:jennifer@painless-security.comresolution_fixedtype_defect| by rjsparks@nostrum.comRight now Autogenerated schedules do not inherit from a base schedule - it should either be possible to specify a base schedule at generation time, or apply a base schedule afterwards.
Issue migrated from trac:3170 at 2022-03-04 08:09:04 +0000
The text was updated successfully, but these errors were encountered: