Nanopublications

Matches in Nanopublications for { ?s ?p ?o <https://w3id.org/np/RAfGbCp681dyeD3nFVx652mftGsgsl0dMdYYo3kE2HkE0/assertion>. }

Showing items 1 to 100 of ±436 with 100 items per page.

0000-0003-2388-0744 type Agent assertion.
Workflow-RO-Crate type CreativeWork assertion.
about.workflowhub.eu type Organization assertion.
enrichment_service-account-enrichment type Agent assertion.
0000-0001-6401-6229_ type Person assertion.
7ab8a5dd-8bc6-46c1-8ca9-a0c245a896ad type ResearchObject assertion.
7ab8a5dd-8bc6-46c1-8ca9-a0c245a896ad type LiveRO assertion.
7ab8a5dd-8bc6-46c1-8ca9-a0c245a896ad type Dataset assertion.
46379747-2240-4167-8bab-2deab6decab5 type Folder assertion.
46379747-2240-4167-8bab-2deab6decab5 type Dataset assertion.
66c44a5e-0727-4667-b868-dafa772c0a33 type Folder assertion.
66c44a5e-0727-4667-b868-dafa772c0a33 type Dataset assertion.
78e37aaa-926d-4a03-b835-9761e5c250d5 type Folder assertion.
78e37aaa-926d-4a03-b835-9761e5c250d5 type Dataset assertion.
8a0897c2-8eff-4790-bac4-6b29479dc217 type Folder assertion.
8a0897c2-8eff-4790-bac4-6b29479dc217 type Dataset assertion.
939d8834-ab5e-4dae-858f-4dc29464dca6 type Folder assertion.
939d8834-ab5e-4dae-858f-4dc29464dca6 type Dataset assertion.
bd9c36a5-1910-4e9c-a74d-6a16c0a4bec3 type Folder assertion.
bd9c36a5-1910-4e9c-a74d-6a16c0a4bec3 type Dataset assertion.
cf012660-57f9-4ff1-aa21-c514a14892e4 type Folder assertion.
cf012660-57f9-4ff1-aa21-c514a14892e4 type Dataset assertion.
fd63033f-ee5b-42c7-9177-98c634fec03c type Folder assertion.
fd63033f-ee5b-42c7-9177-98c634fec03c type Dataset assertion.
062ee024-e0b7-43af-be26-77ec31e94bb9 type Resource assertion.
062ee024-e0b7-43af-be26-77ec31e94bb9 type MediaObject assertion.
08dfe3af-ce53-48ea-910b-31e06328aba7 type Resource assertion.
08dfe3af-ce53-48ea-910b-31e06328aba7 type MediaObject assertion.
1ec1efa3-054b-4cc6-b06b-a2d0326d7dfb type Resource assertion.
1ec1efa3-054b-4cc6-b06b-a2d0326d7dfb type CreativeWork assertion.
1ec1efa3-054b-4cc6-b06b-a2d0326d7dfb type MediaObject assertion.
1ece3eec-38e5-4140-a677-cb905a0b6cb5 type Resource assertion.
1ece3eec-38e5-4140-a677-cb905a0b6cb5 type MediaObject assertion.
2bc1a7dc-a3e0-4819-9bba-5c47b9ec537b type Resource assertion.
2bc1a7dc-a3e0-4819-9bba-5c47b9ec537b type MediaObject assertion.
38c4e5ac-ddf5-4ca7-9efb-c8610686327c type Resource assertion.
38c4e5ac-ddf5-4ca7-9efb-c8610686327c type MediaObject assertion.
3f0e3090-ca7e-4cfd-bb4b-2a0b0fd2ed7a type Resource assertion.
3f0e3090-ca7e-4cfd-bb4b-2a0b0fd2ed7a type MediaObject assertion.
41deb7c8-6b36-481e-9a3a-c47a70b56df0 type Resource assertion.
41deb7c8-6b36-481e-9a3a-c47a70b56df0 type MediaObject assertion.
4242e632-5e7f-4532-93bc-159b21e92b4a type Resource assertion.
4242e632-5e7f-4532-93bc-159b21e92b4a type MediaObject assertion.
794f6066-94f3-4eb1-943a-0e46e48d27fa type Resource assertion.
794f6066-94f3-4eb1-943a-0e46e48d27fa type MediaObject assertion.
7e9943ba-f08c-4176-9943-c4b7c739746a type Resource assertion.
7e9943ba-f08c-4176-9943-c4b7c739746a type MediaObject assertion.
8c925c69-f249-4477-964b-734bd0157131 type Resource assertion.
8c925c69-f249-4477-964b-734bd0157131 type MediaObject assertion.
8ca49483-617b-47f7-8f6a-f5061a0648c2 type Resource assertion.
8ca49483-617b-47f7-8f6a-f5061a0648c2 type MediaObject assertion.
98431cde-dbeb-4d23-a614-63e252a373bd type Resource assertion.
98431cde-dbeb-4d23-a614-63e252a373bd type MediaObject assertion.
99f209fd-1409-45fd-9003-c4be7fe0deb7 type Resource assertion.
99f209fd-1409-45fd-9003-c4be7fe0deb7 type MediaObject assertion.
a551d6e7-6d83-493e-b18b-76a085f1f96f type Resource assertion.
a551d6e7-6d83-493e-b18b-76a085f1f96f type MediaObject assertion.
a64bdbbc-05ea-4f60-8c51-9679fbce26a2 type Resource assertion.
a64bdbbc-05ea-4f60-8c51-9679fbce26a2 type MediaObject assertion.
cb26b8ff-a3a7-4b78-967d-3ef31184b642 type Resource assertion.
cb26b8ff-a3a7-4b78-967d-3ef31184b642 type MediaObject assertion.
d0fbc637-146c-4d81-97af-00cd95ec1692 type Resource assertion.
d0fbc637-146c-4d81-97af-00cd95ec1692 type MediaObject assertion.
d9f38986-7753-486d-aa09-bacf33643dbb type ComputationalWorkflow assertion.
d9f38986-7753-486d-aa09-bacf33643dbb type SoftwareSourceCode assertion.
d9f38986-7753-486d-aa09-bacf33643dbb type Resource assertion.
d9f38986-7753-486d-aa09-bacf33643dbb type MediaObject assertion.
dab03da9-6f4d-4a21-bbec-439a907d7b97 type Resource assertion.
dab03da9-6f4d-4a21-bbec-439a907d7b97 type MediaObject assertion.
e00cd2fc-e208-40bd-8128-33ac97eebd9e type Resource assertion.
e00cd2fc-e208-40bd-8128-33ac97eebd9e type MediaObject assertion.
e1404702-1a21-4bbd-81bf-c467650425d5 type Resource assertion.
e1404702-1a21-4bbd-81bf-c467650425d5 type MediaObject assertion.
eaac98ec-5a60-4019-aa2b-2e66c63cb493 type Resource assertion.
eaac98ec-5a60-4019-aa2b-2e66c63cb493 type MediaObject assertion.
ede95598-0c03-45db-b667-802fc33a1666 type Resource assertion.
ede95598-0c03-45db-b667-802fc33a1666 type MediaObject assertion.
fa4dfed0-adf2-4c22-8b0d-f95e0efbec0b type Resource assertion.
fa4dfed0-adf2-4c22-8b0d-f95e0efbec0b type MediaObject assertion.
ff01fad8-983f-4915-bbcd-bb23704689b0 type Resource assertion.
ff01fad8-983f-4915-bbcd-bb23704689b0 type MediaObject assertion.
ro-crate-metadata.json type CreativeWork assertion.
compss.bsc.es type ComputerLanguage assertion.
165 type Organization assertion.
165 type Project assertion.
7ab8a5dd-8bc6-46c1-8ca9-a0c245a896ad mainEntity "Workflow/PyCOMPSs/run.sh" assertion.
7ab8a5dd-8bc6-46c1-8ca9-a0c245a896ad importedBy 0000-0003-2388-0744 assertion.
d9f38986-7753-486d-aa09-bacf33643dbb sdPublisher "https://about.workflowhub.eu/" assertion.
d9f38986-7753-486d-aa09-bacf33643dbb producer "https://workflowhub.eu/projects/165" assertion.
7ab8a5dd-8bc6-46c1-8ca9-a0c245a896ad description "# Drug Synergies Screening Workflow ## Table of Contents - [Drug Synergies Screening Workflow](#drug-synergies-screening-workflow) - [Table of Contents](#table-of-contents) - [Description](#description) - [Contents](#contents) - [Building Blocks](#building-blocks) - [Workflows](#workflows) - [Resources](#resources) - [Tests](#tests) - [Instructions](#instructions) - [Local machine](#local-machine) - [Requirements](#requirements) - [Usage steps](#usage-steps) - [MareNostrum 4](#marenostrum-4) - [Requirements in MN4](#requirements-in-mn4) - [Usage steps in MN4](#usage-steps-in-mn4) - [License](#license) - [Contact](#contact) ## Description This pipeline simulates a drug screening on personalised cell line models. It automatically builds Boolean models of interest, then uses cell lines data (expression, mutations, copy number variations) to personalise them as MaBoSS models. Finally, this pipeline simulates multiple drug intervention on these MaBoSS models, and lists drug synergies of interest. The workflow uses the following building blocks, described in order of execution: 1. Build model from species 2. Personalise patient 3. MaBoSS 4. Print drug results For details on individual workflow steps, see the user documentation for each building block. [`GitHub repository`](https://github.com/PerMedCoE/drug-synergies-workflow>) ## Contents ### Building Blocks The ``BuildingBlocks`` folder contains the script to install the Building Blocks used in the Drug Synergies Workflow. ### Workflows The ``Workflow`` folder contains the workflows implementations. Currently contains the implementation using PyCOMPSs. ### Resources The ``Resources`` folder contains a small dataset for testing purposes. ### Tests The ``Tests`` folder contains the scripts that run each Building Block used in the workflow for a small dataset. They can be executed individually *without PyCOMPSs installed* for testing purposes. ## Instructions ### Local machine This section explains the requirements and usage for the Drug Synergies Workflow in a laptop or desktop computer. #### Requirements - [`permedcoe`](https://github.com/PerMedCoE/permedcoe) package - [PyCOMPSs](https://pycompss.readthedocs.io/en/stable/Sections/00_Quickstart.html) - [Singularity](https://sylabs.io/guides/3.0/user-guide/installation.html) #### Usage steps 1. Clone this repository: ```bash git clone https://github.com/PerMedCoE/drug-synergies-workflow.git ``` 2. Install the Building Blocks required for the COVID19 Workflow: ```bash drug-synergies-workflow/BuildingBlocks/./install_BBs.sh ``` 3. Get the required Building Block images from the project [B2DROP](https://b2drop.bsc.es/index.php/f/444350): - Required images: - PhysiCell-COVID19.singularity - printResults.singularity - MaBoSS_sensitivity.singularity - FromSpeciesToMaBoSSModel.singularity The path where these files are stored **MUST be exported in the `PERMEDCOE_IMAGES`** environment variable. > :warning: **TIP**: These containers can be built manually as follows (be patient since some of them may take some time): 1. Clone the `BuildingBlocks` repository ```bash git clone https://github.com/PerMedCoE/BuildingBlocks.git ``` 2. Build the required Building Block images ```bash cd BuildingBlocks/Resources/images sudo singularity build PhysiCell-COVID19.sif PhysiCell-COVID19.singularity sudo singularity build printResults.sif printResults.singularity sudo singularity build MaBoSS_sensitivity.sif MaBoSS_sensitivity.singularity sudo singularity build FromSpeciesToMaBoSSModel.sif FromSpeciesToMaBoSSModel.singularity cd ../../.. ``` **If using PyCOMPSs in local PC** (make sure that PyCOMPSs in installed): 4. Go to `Workflow/PyCOMPSs` folder ```bash cd Workflows/PyCOMPSs ``` 5. Execute `./run.sh` > **TIP**: If you want to run the workflow with a different dataset, please update the `run.sh` script setting the `dataset` variable to the new dataset folder and their file names. ### MareNostrum 4 This section explains the requirements and usage for the Drug Synergies Workflow in the MareNostrum 4 supercomputer. #### Requirements in MN4 - Access to MN4 All Building Blocks are already installed in MN4, and the Drug Synergies Workflow available. #### Usage steps in MN4 1. Load the `COMPSs`, `Singularity` and `permedcoe` modules ```bash export COMPSS_PYTHON_VERSION=3 module load COMPSs/3.1 module load singularity/3.5.2 module use /apps/modules/modulefiles/tools/COMPSs/libraries module load permedcoe ``` > **TIP**: Include the loading into your `${HOME}/.bashrc` file to load it automatically on the session start. This commands will load COMPSs and the permedcoe package which provides all necessary dependencies, as well as the path to the singularity container images (`PERMEDCOE_IMAGES` environment variable) and testing dataset (`DRUG_SYNERGIES_WORKFLOW_DATASET` environment variable). 2. Get a copy of the pilot workflow into your desired folder ```bash mkdir desired_folder cd desired_folder get_drug_synergies_workflow ``` 3. Go to `Workflow/PyCOMPSs` folder ```bash cd Workflow/PyCOMPSs ``` 4. Execute `./launch.sh` This command will launch a job into the job queuing system (SLURM) requesting 2 nodes (one node acting half master and half worker, and other full worker node) for 20 minutes, and is prepared to use the singularity images that are already deployed in MN4 (located into the `PERMEDCOE_IMAGES` environment variable). It uses the dataset located into `../../Resources/data` folder. > :warning: **TIP**: If you want to run the workflow with a different dataset, please edit the `launch.sh` script and define the appropriate dataset path. After the execution, a `results` folder will be available with with Drug Synergies Workflow results. ## License [Apache 2.0](https://www.apache.org/licenses/LICENSE-2.0) ## Contact This software has been developed for the [PerMedCoE project](https://permedcoe.eu/), funded by the European Commission (EU H2020 [951773](https://cordis.europa.eu/project/id/951773)). ![](https://permedcoe.eu/wp-content/uploads/2020/11/logo_1.png "PerMedCoE") " assertion.
7ab8a5dd-8bc6-46c1-8ca9-a0c245a896ad description "# Drug Synergies Screening Workflow ## Table of Contents - [Drug Synergies Screening Workflow](#drug-synergies-screening-workflow) - [Table of Contents](#table-of-contents) - [Description](#description) - [Contents](#contents) - [Building Blocks](#building-blocks) - [Workflows](#workflows) - [Resources](#resources) - [Tests](#tests) - [Instructions](#instructions) - [Local machine](#local-machine) - [Requirements](#requirements) - [Usage steps](#usage-steps) - [MareNostrum 4](#marenostrum-4) - [Requirements in MN4](#requirements-in-mn4) - [Usage steps in MN4](#usage-steps-in-mn4) - [License](#license) - [Contact](#contact) ## Description This pipeline simulates a drug screening on personalised cell line models. It automatically builds Boolean models of interest, then uses cell lines data (expression, mutations, copy number variations) to personalise them as MaBoSS models. Finally, this pipeline simulates multiple drug intervention on these MaBoSS models, and lists drug synergies of interest. The workflow uses the following building blocks, described in order of execution: 1. Build model from species 2. Personalise patient 3. MaBoSS 4. Print drug results For details on individual workflow steps, see the user documentation for each building block. [`GitHub repository`](https://github.com/PerMedCoE/drug-synergies-workflow>) ## Contents ### Building Blocks The ``BuildingBlocks`` folder contains the script to install the Building Blocks used in the Drug Synergies Workflow. ### Workflows The ``Workflow`` folder contains the workflows implementations. Currently contains the implementation using PyCOMPSs. ### Resources The ``Resources`` folder contains a small dataset for testing purposes. ### Tests The ``Tests`` folder contains the scripts that run each Building Block used in the workflow for a small dataset. They can be executed individually *without PyCOMPSs installed* for testing purposes. ## Instructions ### Local machine This section explains the requirements and usage for the Drug Synergies Workflow in a laptop or desktop computer. #### Requirements - [`permedcoe`](https://github.com/PerMedCoE/permedcoe) package - [PyCOMPSs](https://pycompss.readthedocs.io/en/stable/Sections/00_Quickstart.html) - [Singularity](https://sylabs.io/guides/3.0/user-guide/installation.html) #### Usage steps 1. Clone this repository: ```bash git clone https://github.com/PerMedCoE/drug-synergies-workflow.git ``` 2. Install the Building Blocks required for the COVID19 Workflow: ```bash drug-synergies-workflow/BuildingBlocks/./install_BBs.sh ``` 3. Get the required Building Block images from the project [B2DROP](https://b2drop.bsc.es/index.php/f/444350): - Required images: - PhysiCell-COVID19.singularity - printResults.singularity - MaBoSS_sensitivity.singularity - FromSpeciesToMaBoSSModel.singularity The path where these files are stored **MUST be exported in the `PERMEDCOE_IMAGES`** environment variable. > :warning: **TIP**: These containers can be built manually as follows (be patient since some of them may take some time): 1. Clone the `BuildingBlocks` repository ```bash git clone https://github.com/PerMedCoE/BuildingBlocks.git ``` 2. Build the required Building Block images ```bash cd BuildingBlocks/Resources/images sudo singularity build PhysiCell-COVID19.sif PhysiCell-COVID19.singularity sudo singularity build printResults.sif printResults.singularity sudo singularity build MaBoSS_sensitivity.sif MaBoSS_sensitivity.singularity sudo singularity build FromSpeciesToMaBoSSModel.sif FromSpeciesToMaBoSSModel.singularity cd ../../.. ``` **If using PyCOMPSs in local PC** (make sure that PyCOMPSs in installed): 4. Go to `Workflow/PyCOMPSs` folder ```bash cd Workflows/PyCOMPSs ``` 5. Execute `./run.sh` > **TIP**: If you want to run the workflow with a different dataset, please update the `run.sh` script setting the `dataset` variable to the new dataset folder and their file names. ### MareNostrum 4 This section explains the requirements and usage for the Drug Synergies Workflow in the MareNostrum 4 supercomputer. #### Requirements in MN4 - Access to MN4 All Building Blocks are already installed in MN4, and the Drug Synergies Workflow available. #### Usage steps in MN4 1. Load the `COMPSs`, `Singularity` and `permedcoe` modules ```bash export COMPSS_PYTHON_VERSION=3 module load COMPSs/3.1 module load singularity/3.5.2 module use /apps/modules/modulefiles/tools/COMPSs/libraries module load permedcoe ``` > **TIP**: Include the loading into your `${HOME}/.bashrc` file to load it automatically on the session start. This commands will load COMPSs and the permedcoe package which provides all necessary dependencies, as well as the path to the singularity container images (`PERMEDCOE_IMAGES` environment variable) and testing dataset (`DRUG_SYNERGIES_WORKFLOW_DATASET` environment variable). 2. Get a copy of the pilot workflow into your desired folder ```bash mkdir desired_folder cd desired_folder get_drug_synergies_workflow ``` 3. Go to `Workflow/PyCOMPSs` folder ```bash cd Workflow/PyCOMPSs ``` 4. Execute `./launch.sh` This command will launch a job into the job queuing system (SLURM) requesting 2 nodes (one node acting half master and half worker, and other full worker node) for 20 minutes, and is prepared to use the singularity images that are already deployed in MN4 (located into the `PERMEDCOE_IMAGES` environment variable). It uses the dataset located into `../../Resources/data` folder. > :warning: **TIP**: If you want to run the workflow with a different dataset, please edit the `launch.sh` script and define the appropriate dataset path. After the execution, a `results` folder will be available with with Drug Synergies Workflow results. ## License [Apache 2.0](https://www.apache.org/licenses/LICENSE-2.0) ## Contact This software has been developed for the [PerMedCoE project](https://permedcoe.eu/), funded by the European Commission (EU H2020 [951773](https://cordis.europa.eu/project/id/951773)). ![](https://permedcoe.eu/wp-content/uploads/2020/11/logo_1.png "PerMedCoE")" assertion.
d9f38986-7753-486d-aa09-bacf33643dbb description "# Drug Synergies Screening Workflow ## Table of Contents - [Drug Synergies Screening Workflow](#drug-synergies-screening-workflow) - [Table of Contents](#table-of-contents) - [Description](#description) - [Contents](#contents) - [Building Blocks](#building-blocks) - [Workflows](#workflows) - [Resources](#resources) - [Tests](#tests) - [Instructions](#instructions) - [Local machine](#local-machine) - [Requirements](#requirements) - [Usage steps](#usage-steps) - [MareNostrum 4](#marenostrum-4) - [Requirements in MN4](#requirements-in-mn4) - [Usage steps in MN4](#usage-steps-in-mn4) - [License](#license) - [Contact](#contact) ## Description This pipeline simulates a drug screening on personalised cell line models. It automatically builds Boolean models of interest, then uses cell lines data (expression, mutations, copy number variations) to personalise them as MaBoSS models. Finally, this pipeline simulates multiple drug intervention on these MaBoSS models, and lists drug synergies of interest. The workflow uses the following building blocks, described in order of execution: 1. Build model from species 2. Personalise patient 3. MaBoSS 4. Print drug results For details on individual workflow steps, see the user documentation for each building block. [`GitHub repository`](https://github.com/PerMedCoE/drug-synergies-workflow>) ## Contents ### Building Blocks The ``BuildingBlocks`` folder contains the script to install the Building Blocks used in the Drug Synergies Workflow. ### Workflows The ``Workflow`` folder contains the workflows implementations. Currently contains the implementation using PyCOMPSs. ### Resources The ``Resources`` folder contains a small dataset for testing purposes. ### Tests The ``Tests`` folder contains the scripts that run each Building Block used in the workflow for a small dataset. They can be executed individually *without PyCOMPSs installed* for testing purposes. ## Instructions ### Local machine This section explains the requirements and usage for the Drug Synergies Workflow in a laptop or desktop computer. #### Requirements - [`permedcoe`](https://github.com/PerMedCoE/permedcoe) package - [PyCOMPSs](https://pycompss.readthedocs.io/en/stable/Sections/00_Quickstart.html) - [Singularity](https://sylabs.io/guides/3.0/user-guide/installation.html) #### Usage steps 1. Clone this repository: ```bash git clone https://github.com/PerMedCoE/drug-synergies-workflow.git ``` 2. Install the Building Blocks required for the COVID19 Workflow: ```bash drug-synergies-workflow/BuildingBlocks/./install_BBs.sh ``` 3. Get the required Building Block images from the project [B2DROP](https://b2drop.bsc.es/index.php/f/444350): - Required images: - PhysiCell-COVID19.singularity - printResults.singularity - MaBoSS_sensitivity.singularity - FromSpeciesToMaBoSSModel.singularity The path where these files are stored **MUST be exported in the `PERMEDCOE_IMAGES`** environment variable. > :warning: **TIP**: These containers can be built manually as follows (be patient since some of them may take some time): 1. Clone the `BuildingBlocks` repository ```bash git clone https://github.com/PerMedCoE/BuildingBlocks.git ``` 2. Build the required Building Block images ```bash cd BuildingBlocks/Resources/images sudo singularity build PhysiCell-COVID19.sif PhysiCell-COVID19.singularity sudo singularity build printResults.sif printResults.singularity sudo singularity build MaBoSS_sensitivity.sif MaBoSS_sensitivity.singularity sudo singularity build FromSpeciesToMaBoSSModel.sif FromSpeciesToMaBoSSModel.singularity cd ../../.. ``` **If using PyCOMPSs in local PC** (make sure that PyCOMPSs in installed): 4. Go to `Workflow/PyCOMPSs` folder ```bash cd Workflows/PyCOMPSs ``` 5. Execute `./run.sh` > **TIP**: If you want to run the workflow with a different dataset, please update the `run.sh` script setting the `dataset` variable to the new dataset folder and their file names. ### MareNostrum 4 This section explains the requirements and usage for the Drug Synergies Workflow in the MareNostrum 4 supercomputer. #### Requirements in MN4 - Access to MN4 All Building Blocks are already installed in MN4, and the Drug Synergies Workflow available. #### Usage steps in MN4 1. Load the `COMPSs`, `Singularity` and `permedcoe` modules ```bash export COMPSS_PYTHON_VERSION=3 module load COMPSs/3.1 module load singularity/3.5.2 module use /apps/modules/modulefiles/tools/COMPSs/libraries module load permedcoe ``` > **TIP**: Include the loading into your `${HOME}/.bashrc` file to load it automatically on the session start. This commands will load COMPSs and the permedcoe package which provides all necessary dependencies, as well as the path to the singularity container images (`PERMEDCOE_IMAGES` environment variable) and testing dataset (`DRUG_SYNERGIES_WORKFLOW_DATASET` environment variable). 2. Get a copy of the pilot workflow into your desired folder ```bash mkdir desired_folder cd desired_folder get_drug_synergies_workflow ``` 3. Go to `Workflow/PyCOMPSs` folder ```bash cd Workflow/PyCOMPSs ``` 4. Execute `./launch.sh` This command will launch a job into the job queuing system (SLURM) requesting 2 nodes (one node acting half master and half worker, and other full worker node) for 20 minutes, and is prepared to use the singularity images that are already deployed in MN4 (located into the `PERMEDCOE_IMAGES` environment variable). It uses the dataset located into `../../Resources/data` folder. > :warning: **TIP**: If you want to run the workflow with a different dataset, please edit the `launch.sh` script and define the appropriate dataset path. After the execution, a `results` folder will be available with with Drug Synergies Workflow results. ## License [Apache 2.0](https://www.apache.org/licenses/LICENSE-2.0) ## Contact This software has been developed for the [PerMedCoE project](https://permedcoe.eu/), funded by the European Commission (EU H2020 [951773](https://cordis.europa.eu/project/id/951773)). ![](https://permedcoe.eu/wp-content/uploads/2020/11/logo_1.png "PerMedCoE")" assertion.
Workflow-RO-Crate version "0.2.0" assertion.
d9f38986-7753-486d-aa09-bacf33643dbb version "1" assertion.
7ab8a5dd-8bc6-46c1-8ca9-a0c245a896ad contentSize "41338757" assertion.
062ee024-e0b7-43af-be26-77ec31e94bb9 contentSize "41737701" assertion.
08dfe3af-ce53-48ea-910b-31e06328aba7 contentSize "1265" assertion.
1ec1efa3-054b-4cc6-b06b-a2d0326d7dfb contentSize "25003" assertion.
1ece3eec-38e5-4140-a677-cb905a0b6cb5 contentSize "2478" assertion.
2bc1a7dc-a3e0-4819-9bba-5c47b9ec537b contentSize "903" assertion.