-
Notifications
You must be signed in to change notification settings - Fork 42
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Some fixes before the upcoming release #257
Conversation
…obs_name_col optional in report.rmd
Is it necessary to "unbump" the versions? |
|
…ybe it works online?
…nd messed them up
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Mostly OK, but sorry, I think the space thing is a hack, we need a better workaround.
nextflow_schema.json
Outdated
@@ -268,8 +268,9 @@ | |||
"properties": { | |||
"proteus_measurecol_prefix": { | |||
"type": "string", | |||
"default": "LFQ intensity ", | |||
"description": "Prefix of the column names of the MaxQuant proteingroups table in which the intensity values are saved; the prefix has to be followed by the sample names that are also found in the samplesheet. Default: 'LFQ intensity '; take care to also consider trailing whitespace between prefix and samplenames." | |||
"default": "LFQ intensity_s", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This seems weird and brittle- too hacky for me. People are going to misunderstand this and get it wrong. We need a different solution - why not just make the proteus module allow for an optional space after the prefix?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I generally prefer not having my code assume that a whitespace is necessary and instead just take directly what the user inputs...but I suppose here, the flexible whitespace addition is the best solution. I just updated the proteus module with those changes
Co-authored-by: Jonathan Manning <[email protected]>
Co-authored-by: Jonathan Manning <[email protected]>
Co-authored-by: Jonathan Manning <[email protected]>
…ntialabundance into prerelease_fixes
…o python); undid the changes to the docs/defaults for --proteus_measurecol_prefix regarding the final space
…into prerelease_fixes
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm a bit nervous of a complete re-write of a module being smuggled into a set of minor pre-release fixes. I'm concerned it could break something.
Can you clarify why that rewrite is necessary here, and demonstrate clearly that it's doing the same thing?
modules/local/filter_difftable.nf
Outdated
@@ -2,10 +2,10 @@ process FILTER_DIFFTABLE { | |||
|
|||
label 'process_single' | |||
|
|||
conda "conda-forge::gawk=5.1.0" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Re-writing this process in Python is a quite a major change to smuggle into a PR of small fixes ;-).
Can you say why the process was re-written, and demonstrate that the output is the same relative to previous?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If you prefer, I can also do the module change in a separate PR, that's not a problem!
Nope, can't demonstrate that, the output changed; it was incorrect before, that's why I had to change it :') AWK suddenly filtered out all the genes and just produced an empty table (was not the case when I originally added the module).
I tried a lot to change it in AWK but it simply did not work and I have to be honest, I found the AWK code quite painful to deal with as I'm simply not experienced enough with it.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Oh, but as a follow-up, I did check the output. The new module + this code makes it so that the results are the same as the DE genes according to the html report, see here:
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Actually, could you raise this as a separate PR? I think that would make more sense and you can post the reasoning and the evidence there.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes of course, see #264
…into prerelease_fixes
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
added maxquant profile to nextflow.config, clarified some docu, made obs_name_col optional in report.rmd,
fixed FILTER_DIFFTABLE module (changed to python as AWK stopped filtering correctly)(done in #264)PR checklist
nf-core lint
).nextflow run . -profile test,docker --outdir <OUTDIR>
).docs/usage.md
is updated.docs/output.md
is updated.CHANGELOG.md
is updated.README.md
is updated (including new tool citations and authors/contributors).