You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: CHANGELOG.md
+15Lines changed: 15 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -6,6 +6,21 @@ and this project adheres to [Semantic Versioning](http://semver.org/spec/v2.0.0.
6
6
7
7
## [Unpublished / Dev Branch]
8
8
9
+
## [2.0.5] - 2019-01-28
10
+
11
+
### `Added`
12
+
*[#127](https://github.com/nf-core/eager/pull/127) - Added a second testcase for testing the pipeline properly
13
+
*[#129](https://github.com/nf-core/eager/pull/129) - Support BAM files as [input format](https://github.com/nf-core/eager/issues/41)
14
+
*[#131](https://github.com/nf-core/eager/pull/131) - Support different [reference genome file extensions](https://github.com/nf-core/eager/issues/130)
Copy file name to clipboardExpand all lines: docs/troubleshooting.md
+18Lines changed: 18 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,5 +1,22 @@
1
1
# nf-core/eager: Troubleshooting
2
2
3
+
## My pipeline update doesn't seem to do anything!
4
+
5
+
To download a new version of a pipeline, you can use the following, replacing `<VERSION>` the the corresponding verison.
6
+
7
+
```bash
8
+
nextflow pull nf-core/eager -r <VERSION>
9
+
```
10
+
However, in very rare cases, minor fixes to a version will be pushed out without a version number bump. This can confuse nextflow slightly, as it thinks you already have the 'broken' version from your original pipeline download.
11
+
12
+
If when running the pipeline you don't see any changes in the fixed version when running it, you can try removing your nextflow EAGER cache typically stored in your home directory with
13
+
14
+
```bash
15
+
rm -r ~/.nextflow/assets/nf-core/eager
16
+
```
17
+
18
+
And re-pull the pipeline with the command above. This will install a fresh version of the version with the fixes.
19
+
3
20
## Input files not found
4
21
5
22
If no file, only one input file, or only read one and not read two is picked up then something is wrong with your input file declaration
@@ -26,3 +43,4 @@ If you still have an issue with running the pipeline then feel free to contact u
26
43
Have a look at the [pipeline website](https://github.com/nf-core/eager) to find out how.
27
44
28
45
If you have problems that are related to Nextflow and not our pipeline then check out the [Nextflow gitter channel](https://gitter.im/nextflow-io/nextflow) or the [google group](https://groups.google.com/forum/#!forum/nextflow).
0 commit comments