some renaming of variables
All checks were successful
Build, test and publish / verify (push) Successful in 5m55s
All checks were successful
Build, test and publish / verify (push) Successful in 5m55s
This commit is contained in:
@@ -5,12 +5,12 @@ calendar dates. Counts do not restart on a new date.
|
||||
|
||||
## Required performances
|
||||
|
||||
The manager chooses **x**, the desired number of distinct dayparts, per show.
|
||||
The manager chooses **preferredDayParts**, the desired number of distinct dayparts, per show.
|
||||
It defaults to two, or one for a show with only one daypart. A show can be saved
|
||||
without dayparts but cannot be scheduled. If dayparts are removed, x is retained
|
||||
without dayparts but cannot be scheduled. If dayparts are removed, preferredDayParts is retained
|
||||
and must be corrected before scheduling when it exceeds the remaining count.
|
||||
|
||||
Every nonempty regular, selection and pre-education group performs in exactly x
|
||||
Every nonempty regular, selection and pre-education group performs in exactly preferredDayParts
|
||||
dayparts, once in each. Each preschool group performs exactly once in the whole
|
||||
show. Every showcase performs once in every daypart. Groups without dancers are
|
||||
skipped completely, including for showcase positions and balancing.
|
||||
@@ -22,17 +22,17 @@ twice in the same daypart. Without showcases there is no opening/closing rule.
|
||||
|
||||
## People and changing clothes
|
||||
|
||||
An ordinary dancer must perform in no more than x distinct dayparts across all
|
||||
An ordinary dancer must perform in no more than preferredDayParts distinct dayparts across all
|
||||
of their groups. The same dancer registration must be used in every group.
|
||||
|
||||
Showcase participants necessarily perform in every daypart. For their other
|
||||
performances, exceeding x dayparts is allowed but discouraged. We count their
|
||||
non-showcase dayparts, subtract x, and count only positive excesses. The planner's
|
||||
performances, exceeding preferredDayParts dayparts is allowed but discouraged. We count their
|
||||
non-showcase dayparts, subtract preferredDayParts, and count only positive excesses. The planner's
|
||||
first preference is to minimize the sum of these excesses across dancers.
|
||||
|
||||
A coach registration must be explicitly linked to the corresponding dancer;
|
||||
names are not used to guess identity. Coaches are available throughout the show
|
||||
and are exempt from both the x limit and the excess penalty. A coach only performs
|
||||
and are exempt from both the preferredDayParts limit and the excess penalty. A coach only performs
|
||||
with a group if included in its dancer membership. Being a group's coach alone
|
||||
never adds a performance or forces that group into extra dayparts.
|
||||
|
||||
@@ -85,5 +85,5 @@ Preferences alone never block finalization.
|
||||
Manual edits and relevant membership, dancer-age, coach-link or show-setting
|
||||
changes return final schedules to draft. Existing schedules and imported schedules
|
||||
are drafts. Import retains assignment order and recalculates violations. Export
|
||||
is available for both statuses and records status, x and coach identity links;
|
||||
is available for both statuses and records status, preferredDayParts and coach identity links;
|
||||
reimport always requires a fresh finalization.
|
||||
|
||||
Reference in New Issue
Block a user