diff --git a/REANA.html b/REANA.html index e944049..2c39102 100644 --- a/REANA.html +++ b/REANA.html @@ -461,7 +461,8 @@
More about reana.yaml
files can be found here.
Let’s get familiar with the steps necessary to run our workflow in @@ -562,7 +563,7 @@
Unfortunately, not yet
But before throwing your laptop out the window, don’t worry, this @@ -661,7 +662,7 @@
Finally yes!
If the previous Snakemake command didn’t execute as expected, it’s likely due to the requirement for access to CERN tools like CVMFS, EOS, diff --git a/Snakemake.html b/Snakemake.html index 22c50ce..20ee9d4 100644 --- a/Snakemake.html +++ b/Snakemake.html @@ -734,7 +734,7 @@
A key feature of Snakemake is its ability to efficiently manage workflow execution based on file timestamps. When you run a Snakemake diff --git a/aio.html b/aio.html index 31e61df..a5fc573 100644 --- a/aio.html +++ b/aio.html @@ -423,7 +423,7 @@
Me, myself and my group. 😁
You can add a line with at least three colons and a
solution
tag.
A key feature of Snakemake is its ability to efficiently manage workflow execution based on file timestamps. When you run a Snakemake @@ -1404,7 +1404,7 @@
If the previous Snakemake command didn’t execute as expected, it’s likely due to the requirement for access to CERN tools like CVMFS, EOS, @@ -1590,6 +1590,7 @@
More about reana.yaml
files can be found here.
Unfortunately, not yet
But before throwing your laptop out the window, don’t worry, this @@ -1795,7 +1796,7 @@
Finally yes!
By default, REANA utilizes Kubernetes as its computing backend. This +allows you to easily scale your workflows and allocate resources as +needed. For instance, to increase the memory allocated to a specific +rule, you can specify it in the resources section:
+rule skimming:
+ ...
+ resources:
+ compute_backend="kubernetes",
+ kubernetes_memory_limit="8Gi",
+ ...
+Note that Kubernetes imposes a maximum memory limit of
+9.5Gi
per container.
For more demanding workloads or specific resource requirements, REANA +also supports integration with HTCondor +and Slurm. +These backends can provide access to larger computing resources and more +flexible scheduling options, but their usage is outside the scope of +this tutorial. Please refer to the official documentation for more +information.
+Each REANA user is allocated 300GB of storage space on the platform. +(This is visible in under your profile in the web interface). While this +is typically sufficient for most workflows, you can leverage REANA’s +integration with your personal EOS storage area for larger datasets. To +enable this integration, ensure that your Kerberos credentials are +configured correctly in your REANA profile.
+In this case, the workflow should work perfectly.
+The REANA team has a compilation of examples in their github +area. It is well recommended to visit them for more inspiration.
+In addition, users can seek for support and help in the following +channels:
+By default, REANA utilizes Kubernetes as its computing backend. This +allows you to easily scale your workflows and allocate resources as +needed. For instance, to increase the memory allocated to a specific +rule, you can specify it in the resources section:
+rule skimming:
+ ...
+ resources:
+ compute_backend="kubernetes",
+ kubernetes_memory_limit="8Gi",
+ ...
+Note that Kubernetes imposes a maximum memory limit of
+9.5Gi
per container.
For more demanding workloads or specific resource requirements, REANA +also supports integration with HTCondor +and Slurm. +These backends can provide access to larger computing resources and more +flexible scheduling options, but their usage is outside the scope of +this tutorial. Please refer to the official documentation for more +information.
+Each REANA user is allocated 300GB of storage space on the platform. +(This is visible in under your profile in the web interface). While this +is typically sufficient for most workflows, you can leverage REANA’s +integration with your personal EOS storage area for larger datasets. To +enable this integration, ensure that your Kerberos credentials are +configured correctly in your REANA profile.
+In this case, the workflow should work perfectly.
+The REANA team has a compilation of examples in their github +area. It is well recommended to visit them for more inspiration.
+In addition, users can seek for support and help in the following +channels:
+Let’s get familiar with the steps necessary to run our workflow in @@ -563,7 +564,7 @@
Unfortunately, not yet
But before throwing your laptop out the window, don’t worry, this @@ -638,7 +639,7 @@
It will be nice to have a list of REANA variables
Finally yes!
If the previous Snakemake command didn’t execute as expected, it’s likely due to the requirement for access to CERN tools like CVMFS, EOS, diff --git a/instructor/Snakemake.html b/instructor/Snakemake.html index ac911ba..bfa5489 100644 --- a/instructor/Snakemake.html +++ b/instructor/Snakemake.html @@ -735,7 +735,7 @@
A key feature of Snakemake is its ability to efficiently manage workflow execution based on file timestamps. When you run a Snakemake diff --git a/instructor/aio.html b/instructor/aio.html index 6e2dca1..f413ae1 100644 --- a/instructor/aio.html +++ b/instructor/aio.html @@ -424,7 +424,7 @@
Me, myself and my group. 😁
Inline instructor notes can help inform instructors of timing challenges associated with the lessons. They appear in the “Instructor @@ -486,7 +486,7 @@
You can add a line with at least three colons and a
solution
tag.
A key feature of Snakemake is its ability to efficiently manage workflow execution based on file timestamps. When you run a Snakemake @@ -1421,7 +1421,7 @@
If the previous Snakemake command didn’t execute as expected, it’s likely due to the requirement for access to CERN tools like CVMFS, EOS, @@ -1608,6 +1608,7 @@
More about reana.yaml
files can be found here.
Unfortunately, not yet
But before throwing your laptop out the window, don’t worry, this @@ -1789,7 +1790,7 @@
It will be nice to have a list of REANA variables
Finally yes!
By default, REANA utilizes Kubernetes as its computing backend. This +allows you to easily scale your workflows and allocate resources as +needed. For instance, to increase the memory allocated to a specific +rule, you can specify it in the resources section:
+rule skimming:
+ ...
+ resources:
+ compute_backend="kubernetes",
+ kubernetes_memory_limit="8Gi",
+ ...
+Note that Kubernetes imposes a maximum memory limit of
+9.5Gi
per container.
For more demanding workloads or specific resource requirements, REANA +also supports integration with HTCondor +and Slurm. +These backends can provide access to larger computing resources and more +flexible scheduling options, but their usage is outside the scope of +this tutorial. Please refer to the official documentation for more +information.
+Each REANA user is allocated 300GB of storage space on the platform. +(This is visible in under your profile in the web interface). While this +is typically sufficient for most workflows, you can leverage REANA’s +integration with your personal EOS storage area for larger datasets. To +enable this integration, ensure that your Kerberos credentials are +configured correctly in your REANA profile.
+In this case, the workflow should work perfectly.
+The REANA team has a compilation of examples in their github +area. It is well recommended to visit them for more inspiration.
+In addition, users can seek for support and help in the following +channels:
+By default, REANA utilizes Kubernetes as its computing backend. This +allows you to easily scale your workflows and allocate resources as +needed. For instance, to increase the memory allocated to a specific +rule, you can specify it in the resources section:
+rule skimming:
+ ...
+ resources:
+ compute_backend="kubernetes",
+ kubernetes_memory_limit="8Gi",
+ ...
+Note that Kubernetes imposes a maximum memory limit of
+9.5Gi
per container.
For more demanding workloads or specific resource requirements, REANA +also supports integration with HTCondor +and Slurm. +These backends can provide access to larger computing resources and more +flexible scheduling options, but their usage is outside the scope of +this tutorial. Please refer to the official documentation for more +information.
+Each REANA user is allocated 300GB of storage space on the platform. +(This is visible in under your profile in the web interface). While this +is typically sufficient for most workflows, you can leverage REANA’s +integration with your personal EOS storage area for larger datasets. To +enable this integration, ensure that your Kerberos credentials are +configured correctly in your REANA profile.
+In this case, the workflow should work perfectly.
+The REANA team has a compilation of examples in their github +area. It is well recommended to visit them for more inspiration.
+In addition, users can seek for support and help in the following +channels:
+