Skip to content

Commit

Permalink
Merge pull request #455 from nextflow-io/minor_fixes
Browse files Browse the repository at this point in the history
Fix minor issues in the hello nextflow training
  • Loading branch information
mribeirodantas authored Nov 17, 2024
2 parents 5de49e5 + a019107 commit 4964be8
Show file tree
Hide file tree
Showing 2 changed files with 6 additions and 6 deletions.
10 changes: 5 additions & 5 deletions docs/hello_nextflow/02_hello_world.md
Original file line number Diff line number Diff line change
Expand Up @@ -503,7 +503,7 @@ This is where channels come in: Nextflow uses channels to feed inputs to process

There are multiple ways to do this, but for now, we're just going to use the simplest possible channel, containing a single value.

We're going to create the channel using the `Channel.of()` factory, which sets up a simple value channel, and give it a hardcoded string to use as greeting by declaring `greeting_ch = Channel.of('Hello world!')`.
We're going to create the channel using the `of()` channel factory, which sets up a simple value channel, and give it a hardcoded string to use as greeting by declaring `greeting_ch = Channel.of('Hello world!')`.

_Before:_

Expand Down Expand Up @@ -843,7 +843,7 @@ Learn how to make the workflow run on a batch of input values.

Workflows typically run on batches of inputs that are meant to be processed in bulk, so we want to upgrade the workflow to accept multiple input values.

Conveniently, the `Channel.of()` factory we've been using is quite happy to accept more than one value, so we don't need to modify that at all; we just have to load more values into the channel.
Conveniently, the `of()` channel factory we've been using is quite happy to accept more than one value, so we don't need to modify that at all; we just have to load more values into the channel.

### 8.1. Load multiple greetings into the input channel

Expand Down Expand Up @@ -1063,8 +1063,8 @@ params.input_file = "data/greetings.csv"

### 9.2. Update the channel declaration to handle the input file

At this point we introduce a new channel factory, `Channel.fromPath()`, which has some built-in functionality for handling file paths.
We're going to use that instead of the `Channel.of()` factory we used previously; the base syntax looks like this:
At this point we introduce a new channel factory, `fromPath()`, which has some built-in functionality for handling file paths.
We're going to use that instead of the `of()` channel factory we used previously; the base syntax looks like this:

```groovy title="channel construction syntax"
Channel.fromPath(params.input_file)
Expand Down Expand Up @@ -1126,7 +1126,7 @@ After flatten: Holà
[ee/280f93] Submitted process > convertToUpper (3)
```

As you can see, the flatten() operator has transformed the channel from containing arrays to containing individual elements. This can be useful when you want to process each item separately in your workflow.
As you can see, the `flatten()` operator has transformed the channel from containing arrays to containing individual elements. This can be useful when you want to process each item separately in your workflow.

Remove the `.view()` operations before you continue.

Expand Down
2 changes: 1 addition & 1 deletion docs/hello_nextflow/09_hello_nf-core.md
Original file line number Diff line number Diff line change
Expand Up @@ -139,7 +139,7 @@ nextflow run nf-core/demo -profile docker,test --outdir results

!!! hint "Changing Nextflow version"

Depending on the nextflow version you have installed, this command might fail due to a version mismatch.
Depending on the Nextflow version you have installed, this command might fail due to a version mismatch.
If that happens, you can temporarily run the pipeline with a different version than you have installed by adding `NXF_VER=version` to the start of your command as shown below:

```bash
Expand Down

0 comments on commit 4964be8

Please sign in to comment.