Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Feat: Allows specifying a weight function for individual ranges for the Connected Ranges collector #820

Open
Christopher-Chianelli opened this issue Apr 30, 2024 · 0 comments
Labels
enhancement New feature or request

Comments

@Christopher-Chianelli
Copy link
Contributor

Is your feature request related to a problem? Please describe.
Sometimes a Job requires multiple of the same resource. For instance, a Job might require either 2 or 3 forklifts.
If there are a limited number of forklifts, then schedules where the number of required forklifts at any given time is over the limit is infeasible.

The Connected Range collector is useful when the Job will always require 1 forklift, but cannot handle cases where each Job require a different number of forklifts.

Describe the solution you'd like
The connected ranges collector takes an optional weighting function parameter from range to int (defaulting to range -> 1).
For instance,

toConnectedTemporalRanges(Job::getStart, Job::getEnd, Job::getRequiredForkliftCount)

Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.

Additional context
Add any other context or screenshots about the feature request here.

@Christopher-Chianelli Christopher-Chianelli added enhancement New feature or request process/needs triage Requires initial assessment of validity, priority etc. labels Apr 30, 2024
@triceo triceo removed the process/needs triage Requires initial assessment of validity, priority etc. label Apr 30, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants