Skip to main content
ConductScienceScienceDex
zenodoopen

Job Shop Scheduling instances (SS + RD + EC)

<h1>Instance Structure</h1> <h2>📁 Definition:</h2> <p>For example, the filename `5_5_0_2_5_0.json` is defined as follows: 5 represents the number of jobs, 5 represents the number of machines, 0 indicates the type of distribution (0 = exponential, 1 = normal, 2 = uniform), 2 indicates the type of release and due date (0 = no restriction, 1 = by job, 2 = by operations), 5 denotes the quantity of speed scaling options for each machine, and 0 is the instance number.</p> <h2>📊 Job IDs:&nbsp;</h2> <p>An array of integers representing the job IDs (from 0 to 4).</p> <p><code>"nbJobs": [0, 1, 2, 3, 4]</code></p> <h2>🛠 Number of Machines:&nbsp;</h2> <p>An array of integers representing the number of machines (from 0 to 4). Each machine refeer an operation of a job that should be procedeed.</p> <p><code>"nbMchs": [0, 1, 2, 3, 4]</code></p> <p>&nbsp;</p> <h2>⏱️ Time and Energy:</h2> <p>An array of objects, each containing information about a job processed on a machine, including multiple speed-scaling options. Each job object includes the job ID, operations (with operation IDs as keys), and details such as processing time, energy consumption, release date, and due date.</p> <p><code>"timeEnergy": [</code><br><code>&nbsp; &nbsp; {</code><br><code>&nbsp; &nbsp; &nbsp; &nbsp; "jobId": 0,</code><br><code>&nbsp; &nbsp; &nbsp; &nbsp; "operations": {</code><br><code>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; "1": {</code><br><code>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; "speed-scaling": [</code><br><code>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; {"procTime": 209, "energyCons": 12},</code><br><code>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; ...</code><br><code>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; ],</code><br><code>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; "release-date": 0,</code><br><code>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; "due-date": 31</code><br><code>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; },</code><br><code>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; ...</code><br><code>&nbsp; &nbsp; &nbsp; &nbsp; }</code><br><code>&nbsp; &nbsp; },</code><br><code>&nbsp; &nbsp; ...</code><br><code>]</code></p> <h2>📅 Due Dates and Release Dates:</h2> <p>Within each operation in the `timeEnergy` array, the `release-date` represents the release date of the operation (in milliseconds) and the `due-date` represents the due date of the operation (in milliseconds).</p> <h2>🔄 Speed Scaling Options:</h2> <p>&nbsp;Each operation contains multiple speed-scaling options, providing different combinations of processing times and energy consumption levels.</p> <p><code>"speed-scaling": [</code><br><code>&nbsp; &nbsp; {"procTime": 209, "energyCons": 12},</code><br><code>&nbsp; &nbsp; {"procTime": 52, "energyCons": 59},</code><br><code>&nbsp; &nbsp; {"procTime": 40, "energyCons": 67},</code><br><code>&nbsp; &nbsp; {"procTime": 32, "energyCons": 72},</code><br><code>&nbsp; &nbsp; {"procTime": 30, "energyCons": 74}</code><br><code>]</code><br><br></p> <h2>🧩 Example:</h2> <p>Here is an example of how the data is structured for a specific job and its operations:</p> <p><br><code>{</code><br><code>&nbsp; &nbsp; "nbJobs": [0, 1, 2, 3, 4],</code><br><code>&nbsp; &nbsp; "nbMchs": [0, 1, 2, 3, 4],</code><br><code>&nbsp; &nbsp; "timeEnergy": [</code><br><code>&nbsp; &nbsp; &nbsp; &nbsp; {</code><br><code>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; "jobId": 0,</code><br><code>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; "operations": {</code><br><code>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; "1": {</code><br><code>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; "speed-scaling": [</code><br><code>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; {"procTime": 209, "energyCons": 12},</code><br><code>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; {"procTime": 52, "energyCons": 59},</code><br><code>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; {"procTime": 40, "energyCons": 67},</code><br><code>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; {"procTime": 32, "energyCons": 72},</code><br><code>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; {"procTime": 30, "energyCons": 74}</code><br><code>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; ],</code><br><code>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; "release-date": 0,</code><br><code>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; "due-date": 31</code><br><code>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; },</code><br><code>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; "3": {</code><br><code>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; "speed-scaling": [</code><br><code>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; {"procTime": 135, "energyCons": 25},</code><br><code>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; {"procTime": 40, "energyCons": 67},</code><br><code>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; {"procTime": 30, "energyCons": 74},</code><br><code>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; {"procTime": 28, "energyCons": 75},</code><br><code>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; {"procTime": 23, "energyCons": 79}</code><br><code>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; ],</code><br><code>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; "release-date": 32,</code><br><code>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; "due-date": 72</code><br><code>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; },</code><br><code>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; ...</code><br><code>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; }</code><br><code>&nbsp; &nbsp; &nbsp; &nbsp; },</code><br><code>&nbsp; &nbsp; &nbsp; &nbsp; ...</code><br><code>&nbsp; &nbsp; ]</code><br><code>}</code><br><br></p>

ShareScore

36/100

Overall dataset sharing score

Score breakdown

These five areas show where the dataset supports — or may limit — practical reuse.

Stewardship
4
Harmonization
4
Access
16
Reuse readiness
8
Engagement
4

Dataset details

Repository
zenodo
Published
July 16, 2024
License
mit-license
DOI
10.5281/zenodo.12750148

Scored with release 0.9.0

ScienceDex for faculty

Your academic CV and NIH biosketch

Make your CV in your school's format and your NIH biosketch from it, then download both as Word files.