Release dates ignored in scheduling problem

[nicola-gigante]

I'm modeling a scheduling problem and I'm surely doing something wrong here because I cannot make the UP (with aries) fulfill the release date of my activities.

This example:

from unified_planning.shortcuts import *
import unified_planning.model.scheduling as sched
import unified_planning.engines as engines

problem = sched.SchedulingProblem()

a = problem.add_activity('a', 10)

a.add_release_date(20)

print(problem)

with OneshotPlanner(name='aries') as planner:
    solution = planner.solve(problem)
    print(solution)

prints the following:

fluents = [
]

initial fluents default = [
]

initial values = [
]


BASE: {
  }

Activities:
  a {
    duration = [10, 10]
    constraints = [
      (20 <= start(a))
    ]
  }
  
status: SOLVED_SATISFICING
engine: aries
plan: Schedule:
    [0, 10] a

So I can clearly see the (20 <= start(a)) constraint but in the solution the activity starts at zero.

Am I doing something wrong?

Best,
Nicola

[mikand]

@arbimo Is the "release_date" feature supported by ARIES?

[arbimo]

Yes, I was just checking it and it seems to be properly handled in the development version of Aries.
Could you check that it works as expected there ? To install it:

pip install --force https://github.com/plaans/aries/releases/download/latest/up_aries.tar.gz

For this kind of strange behavior, it may be better to open it on the aries tracker directly. And we can move it here if it involves the UP.

[nicola-gigante]

I get numpy errors if I install up_aries that way.

Traceback (most recent call last):
  File "<frozen runpy>", line 198, in _run_module_as_main
  File "<frozen runpy>", line 88, in _run_code
  File "/Users/gigabytes/Projects/telaio/src/Telaio/Test.py", line 3, in <module>
    from unified_planning.shortcuts import *
  File "/Users/gigabytes/Projects/telaio/.venv/lib/python3.12/site-packages/unified_planning/shortcuts.py", line 28, in <module>
    from unified_planning.engines import (
  File "/Users/gigabytes/Projects/telaio/.venv/lib/python3.12/site-packages/unified_planning/engines/__init__.py", line 17, in <module>
    from unified_planning.engines.engine import Engine, OperationMode
  File "/Users/gigabytes/Projects/telaio/.venv/lib/python3.12/site-packages/unified_planning/engines/engine.py", line 20, in <module>
    from ConfigSpace import ConfigurationSpace
  File "/Users/gigabytes/Projects/telaio/.venv/lib/python3.12/site-packages/ConfigSpace/__init__.py", line 31, in <module>
    from ConfigSpace.api import (
  File "/Users/gigabytes/Projects/telaio/.venv/lib/python3.12/site-packages/ConfigSpace/api/__init__.py", line 1, in <module>
    from ConfigSpace.api import distributions, types
  File "/Users/gigabytes/Projects/telaio/.venv/lib/python3.12/site-packages/ConfigSpace/api/types/__init__.py", line 1, in <module>
    from ConfigSpace.api.types.categorical import Categorical
  File "/Users/gigabytes/Projects/telaio/.venv/lib/python3.12/site-packages/ConfigSpace/api/types/categorical.py", line 10, in <module>
    from ConfigSpace.hyperparameters import CategoricalHyperparameter, OrdinalHyperparameter
  File "/Users/gigabytes/Projects/telaio/.venv/lib/python3.12/site-packages/ConfigSpace/hyperparameters/__init__.py", line 1, in <module>
    from .beta_float import BetaFloatHyperparameter
  File "ConfigSpace/hyperparameters/beta_float.pyx", line 1, in init ConfigSpace.hyperparameters.beta_float
  File "ConfigSpace/hyperparameters/uniform_float.pyx", line 1, in init ConfigSpace.hyperparameters.uniform_float
  File "ConfigSpace/hyperparameters/float_hyperparameter.pyx", line 1, in init ConfigSpace.hyperparameters.float_hyperparameter
  File "ConfigSpace/hyperparameters/numerical.pyx", line 1, in init ConfigSpace.hyperparameters.numerical
  File "ConfigSpace/hyperparameters/hyperparameter.pyx", line 1, in init ConfigSpace.hyperparameters.hyperparameter
ValueError: numpy.dtype size changed, may indicate binary incompatibility. Expected 96 from C header, got 88 from PyObject

[nicola-gigante]

Now it gives me this error even on a novel venv with the stable dependencies. WTF 🤣

[arbimo]

Yes, pip is hell -_-' (note that the dependencies did not change in up-aries)

I often add the --no-deps options to tell pip not to attempt anything smart and just replace the package.

[nicola-gigante]

It's hell indeed, I've removed every installed version of numpy from the system and installed everything in a clean virtual env and I still get that error....

[nicola-gigante]

Ok @arbimo, I've managed to fix my pip installation (two wasted hours of my life nobody will give me back 🤣).

I've tried the pre-release of aries and the example above works now. Thanks!