IGJSP 0.0.5__tar.gz → 0.0.7__tar.gz

igjsp-0.0.7/.gitattributes

@@ -0,0 +1,2 @@
+*.whl filter=lfs diff=lfs merge=lfs -text
+*.tar.gz filter=lfs diff=lfs merge=lfs -text

igjsp-0.0.7/.gitignore

@@ -0,0 +1,171 @@
+# Byte-compiled / optimized / DLL files
+__pycache__/
+*.py[cod]
+*$py.class
+
+# C extensions
+*.so
+
+# Distribution / packaging
+.Python
+build/
+develop-eggs/
+dist/
+downloads/
+eggs/
+.eggs/
+lib/
+lib64/
+parts/
+sdist/
+var/
+wheels/
+share/python-wheels/
+*.egg-info/
+.installed.cfg
+*.egg
+MANIFEST
+
+# PyInstaller
+#  Usually these files are written by a python script from a template
+#  before PyInstaller builds the exe, so as to inject date/other infos into it.
+*.manifest
+*.spec
+
+# Installer logs
+pip-log.txt
+pip-delete-this-directory.txt
+
+# Unit test / coverage reports
+htmlcov/
+.tox/
+.nox/
+.coverage
+.coverage.*
+.cache
+nosetests.xml
+coverage.xml
+*.cover
+*.py,cover
+.hypothesis/
+.pytest_cache/
+cover/
+
+# Translations
+*.mo
+*.pot
+
+# Django stuff:
+*.log
+local_settings.py
+db.sqlite3
+db.sqlite3-journal
+
+# Flask stuff:
+instance/
+.webassets-cache
+
+# Scrapy stuff:
+.scrapy
+
+# Sphinx documentation
+docs/_build/
+
+# PyBuilder
+.pybuilder/
+target/
+
+# Jupyter Notebook
+.ipynb_checkpoints
+
+# IPython
+profile_default/
+ipython_config.py
+
+# pyenv
+#   For a library or package, you might want to ignore these files since the code is
+#   intended to run in multiple environments; otherwise, check them in:
+# .python-version
+
+# pipenv
+#   According to pypa/pipenv#598, it is recommended to include Pipfile.lock in version control.
+#   However, in case of collaboration, if having platform-specific dependencies or dependencies
+#   having no cross-platform support, pipenv may install dependencies that don't work, or not
+#   install all needed dependencies.
+#Pipfile.lock
+
+# UV
+#   Similar to Pipfile.lock, it is generally recommended to include uv.lock in version control.
+#   This is especially recommended for binary packages to ensure reproducibility, and is more
+#   commonly ignored for libraries.
+#uv.lock
+
+# poetry
+#   Similar to Pipfile.lock, it is generally recommended to include poetry.lock in version control.
+#   This is especially recommended for binary packages to ensure reproducibility, and is more
+#   commonly ignored for libraries.
+#   https://python-poetry.org/docs/basic-usage/#commit-your-poetrylock-file-to-version-control
+#poetry.lock
+
+# pdm
+#   Similar to Pipfile.lock, it is generally recommended to include pdm.lock in version control.
+#pdm.lock
+#   pdm stores project-wide configurations in .pdm.toml, but it is recommended to not include it
+#   in version control.
+#   https://pdm.fming.dev/latest/usage/project/#working-with-version-control
+.pdm.toml
+.pdm-python
+.pdm-build/
+
+# PEP 582; used by e.g. github.com/David-OConnor/pyflow and github.com/pdm-project/pdm
+__pypackages__/
+
+# Celery stuff
+celerybeat-schedule
+celerybeat.pid
+
+# SageMath parsed files
+*.sage.py
+
+# Environments
+.env
+.venv
+env/
+venv/
+ENV/
+env.bak/
+venv.bak/
+
+# Spyder project settings
+.spyderproject
+.spyproject
+
+# Rope project settings
+.ropeproject
+
+# mkdocs documentation
+/site
+
+# mypy
+.mypy_cache/
+.dmypy.json
+dmypy.json
+
+# Pyre type checker
+.pyre/
+
+# pytype static type analyzer
+.pytype/
+
+# Cython debug symbols
+cython_debug/
+
+# PyCharm
+#  JetBrains specific template is maintained in a separate JetBrains.gitignore that can
+#  be found at https://github.com/github/gitignore/blob/main/Global/JetBrains.gitignore
+#  and can be added to the global gitignore or merged into this file.  For a more nuclear
+#  option (not recommended) you can uncomment the following to ignore the entire idea folder.
+#.idea/
+
+# PyPI configuration file
+.pypirc

{igjsp-0.0.5 → igjsp-0.0.7}/LICENSE

@@ -1,6 +1,6 @@
 MIT License
 
-Copyright (c) 2024 GPS
+Copyright (c) 2025 Planning and Scheduling Research Group
 
 Permission is hereby granted, free of charge, to any person obtaining a copy
 of this software and associated documentation files (the "Software"), to deal
@@ -18,4 +18,4 @@ FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
 AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
 LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
 OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
-SOFTWARE.
+SOFTWARE.

{igjsp-0.0.5 → igjsp-0.0.7}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: IGJSP
-Version: 0.0.5
+Version: 0.0.7
 Summary: Instance generator for JSP
 Project-URL: Homepage, https://gps.blogs.upv.es/
 Author-email: GPS-UPV <gps@dsic.upv.es>
@@ -14,31 +14,31 @@ Requires-Dist: scipy
 Requires-Dist: tqdm
 Description-Content-Type: text/markdown
 
-# JSP Generator
+# Instance Generator Job Shop Scheduling
 
 ## Description
 Benchmark generator for the Job Shop Problem (BG-JSP)
 
 ## Generating a JSP problem instance
 
-To generate an instance of the problem we will use the Generator class, located at the generador module.
+To generate an instance of the problem, we will use the Generator class, located in the Generador module.
 To do this, we initialize the generator, giving it the following parameters:
 
 1. **JSON:`json`**
    - **Description**: Parameter that indicates if the generated instance will be stored in JSON format.
-   - **Possible values**: Boolean value. Only can get the values True or False.
+   - **Possible values**: Boolean value. Only the values True or False can be obtained.
    - **Example of possible values**: `True`, `False`
    - **Default value**: `False`
 
 2. **DZN:`dzn`**
    - **Description**: Parameter that indicates if the generated instance will be stored in DZN format.
-   - **Possible values**: Boolean value. Only can get the values True or False.
+   - **Possible values**: Boolean value. Only the values True or False can be obtained.
    - **Example of possible values**: `True`, `False`
    - **Default value**: `False`
 
 3. **Taillard:`taillard`**
    - **Description**: Parameter that indicates if the generated instance will be stored in taillard format.
-   - **Possible values**: Boolean value. Only can get the values True or False.
+   - **Possible values**: Boolean value. Only the values True or False can be obtained.
    - **Example of possible values**: `True`, `False`
    - **Default value**: `False`
 
@@ -49,7 +49,7 @@ To do this, we initialize the generator, giving it the following parameters:
    - **Default value**: `./output`
 
 
-Once the generator has been initialized we proceed to generate different instances of the JSP problem with different values for this initialization, for that we use the following function, using the following parameters to customize the generated instances:
+Once the generator has been initialized, we proceed to generate different instances of the JSP problem with different values for this initialization; for that we use the following function using the following parameters to customize the generated instances:
 
 1. **Jobs:`jobs`**
    - **Description**: Number of jobs that will have the problem generated.
@@ -64,10 +64,10 @@ Once the generator has been initialized we proceed to generate different instanc
    - **Default value**: `4`
 
 3. **Release and Due Date:`ReleaseDateDueDate`**
-   - **Descripción**: Establish that each task has an instant of release and an instant of completion limit.
+   - **Descripción**: Establish that each task has an instant of release and completion limit.
    - **Possible values**: 
-      - `0`: Neither the works and operations of each of them will have an instant of release or time limit for completion.
-      - `1`: The work will have instant of release and instant of completion limit.
+      - `0`: Neither the works nor the operations of each of them will have an instant release or time limit for completion.
+      - `1`: The work will have an instant of release and instant of completion limit.
       - `2`: The operations of each job will have a release time and a limiting end time.
    - **Example of possible values**: `1`, `2`
    - **Default value**: `0`
@@ -80,7 +80,7 @@ Once the generator has been initialized we proceed to generate different instanc
 
 5. **Distribution:`distribution`**
    - **Description**: Type of distribution to be followed for data generation.
-   - **Possible values**: You can only set one of the following values: `uniform` `normal` `exponential`
+   - **Possible values**: You can only set one of the following values: `uniform` `normal` `exponential.`
    - **Example of possible values**: `uniform`, `exponential`
    - **Default value**: `normal`
 
@@ -92,7 +92,7 @@ Once the generator has been initialized we proceed to generate different instanc
 
 ## Example of JSON generated
 
-This JSON shows how the data generated from an JSP problem with 2 machines and 4 jobs will look like. For this generation we have the following code:
+This JSON shows how the data generated from a JSP problem with 2 machines and 4 jobs will look. For this generation, we have the following code:
 ``` python
 from IGJSP.generador import Generator
 generator = Generator(json=True,savepath="output")
@@ -213,4 +213,4 @@ generator.generate_new_instance(jobs=4,machines=2,ReleaseDateDueDate=2,distribut
     "maxMinMakespan": 14,
     "maxMinEnergy": 0
 }
-```
+```

{igjsp-0.0.5 → igjsp-0.0.7}/README.md

@@ -1,28 +1,28 @@
-# JSP Generator
+# Instance Generator Job Shop Scheduling
 
 ## Description
 Benchmark generator for the Job Shop Problem (BG-JSP)
 
 ## Generating a JSP problem instance
 
-To generate an instance of the problem we will use the Generator class, located at the generador module.
+To generate an instance of the problem, we will use the Generator class, located in the Generador module.
 To do this, we initialize the generator, giving it the following parameters:
 
 1. **JSON:`json`**
    - **Description**: Parameter that indicates if the generated instance will be stored in JSON format.
-   - **Possible values**: Boolean value. Only can get the values True or False.
+   - **Possible values**: Boolean value. Only the values True or False can be obtained.
    - **Example of possible values**: `True`, `False`
    - **Default value**: `False`
 
 2. **DZN:`dzn`**
    - **Description**: Parameter that indicates if the generated instance will be stored in DZN format.
-   - **Possible values**: Boolean value. Only can get the values True or False.
+   - **Possible values**: Boolean value. Only the values True or False can be obtained.
    - **Example of possible values**: `True`, `False`
    - **Default value**: `False`
 
 3. **Taillard:`taillard`**
    - **Description**: Parameter that indicates if the generated instance will be stored in taillard format.
-   - **Possible values**: Boolean value. Only can get the values True or False.
+   - **Possible values**: Boolean value. Only the values True or False can be obtained.
    - **Example of possible values**: `True`, `False`
    - **Default value**: `False`
 
@@ -33,7 +33,7 @@ To do this, we initialize the generator, giving it the following parameters:
    - **Default value**: `./output`
 
 
-Once the generator has been initialized we proceed to generate different instances of the JSP problem with different values for this initialization, for that we use the following function, using the following parameters to customize the generated instances:
+Once the generator has been initialized, we proceed to generate different instances of the JSP problem with different values for this initialization; for that we use the following function using the following parameters to customize the generated instances:
 
 1. **Jobs:`jobs`**
    - **Description**: Number of jobs that will have the problem generated.
@@ -48,10 +48,10 @@ Once the generator has been initialized we proceed to generate different instanc
    - **Default value**: `4`
 
 3. **Release and Due Date:`ReleaseDateDueDate`**
-   - **Descripción**: Establish that each task has an instant of release and an instant of completion limit.
+   - **Descripción**: Establish that each task has an instant of release and completion limit.
    - **Possible values**: 
-      - `0`: Neither the works and operations of each of them will have an instant of release or time limit for completion.
-      - `1`: The work will have instant of release and instant of completion limit.
+      - `0`: Neither the works nor the operations of each of them will have an instant release or time limit for completion.
+      - `1`: The work will have an instant of release and instant of completion limit.
       - `2`: The operations of each job will have a release time and a limiting end time.
    - **Example of possible values**: `1`, `2`
    - **Default value**: `0`
@@ -64,7 +64,7 @@ Once the generator has been initialized we proceed to generate different instanc
 
 5. **Distribution:`distribution`**
    - **Description**: Type of distribution to be followed for data generation.
-   - **Possible values**: You can only set one of the following values: `uniform` `normal` `exponential`
+   - **Possible values**: You can only set one of the following values: `uniform` `normal` `exponential.`
    - **Example of possible values**: `uniform`, `exponential`
    - **Default value**: `normal`
 
@@ -76,7 +76,7 @@ Once the generator has been initialized we proceed to generate different instanc
 
 ## Example of JSON generated
 
-This JSON shows how the data generated from an JSP problem with 2 machines and 4 jobs will look like. For this generation we have the following code:
+This JSON shows how the data generated from a JSP problem with 2 machines and 4 jobs will look. For this generation, we have the following code:
 ``` python
 from IGJSP.generador import Generator
 generator = Generator(json=True,savepath="output")
@@ -197,4 +197,4 @@ generator.generate_new_instance(jobs=4,machines=2,ReleaseDateDueDate=2,distribut
     "maxMinMakespan": 14,
     "maxMinEnergy": 0
 }
-```
+```

{igjsp-0.0.5 → igjsp-0.0.7}/pyproject.toml

@@ -4,7 +4,7 @@ build-backend = "hatchling.build"
 
 [project]
 name = "IGJSP"
-version = "0.0.5"
+version = "0.0.7"
 authors = [
   { name="GPS-UPV", email="gps@dsic.upv.es" },
 ]

{igjsp-0.0.5 → igjsp-0.0.7}/src/IGJSP/generador.py

@@ -27,11 +27,11 @@ class JSP:
     def __init__(self, jobs, machines, ProcessingTime=np.array([]), EnergyConsumption=np.array([]), ReleaseDateDueDate=np.array([]), Orden=np.array([])) -> None:       
         self.numJobs = jobs
         self.numMchs = machines
-        self.speed = ProcessingTime.shape[-1] if ProcessingTime else 0
+        self.speed = ProcessingTime.shape[-1] if ProcessingTime.size else 0
         self.ProcessingTime = ProcessingTime
         self.EnergyConsumption = EnergyConsumption
         self.Orden = Orden
-        self.rddd = ReleaseDateDueDate.ndim - 1 if ReleaseDateDueDate else 0
+        self.rddd = ReleaseDateDueDate.ndim - 1 if ReleaseDateDueDate.size else 0
         
     def fill_random_values(self, speed, rddd, distribution, seed, tpm=[]):
         np.random.seed(seed)
@@ -451,8 +451,8 @@ class Generator:
         self.taillard = taillard
         self.savepath = savepath
         
-    def generate_new_instance(self, jobs = 10, machines = 4, ProcessingTime=[], EnergyConsumption=[], Orden=[],speed = 1, ReleaseDateDueDate = 0, distribution = "uniform" , seed = 0, tpm=[]):
-        jsp = JSP(jobs=jobs, machines=machines,ProcessingTime=ProcessingTime,EnergyConsumption=EnergyConsumption,Orden=Orden)
+    def generate_new_instance(self, jobs = 10, machines = 4,speed = 1, ReleaseDateDueDate = 0, distribution = "uniform" , seed = 0, tpm=[]):
+        jsp = JSP(jobs=jobs, machines=machines)
         jsp.fill_random_values(speed = speed, rddd = ReleaseDateDueDate, distribution = distribution, seed = seed,tpm = tpm)
         if not (self.json or self.dzn or self.taillard): return jsp