Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
  • 19:56
    bentsherman commented #3459
  • 17:26
    corneliusroemer commented #3458
  • 17:23
    corneliusroemer commented #3457
  • 17:08
    bentsherman commented #3457
  • 16:57
    bentsherman commented #3458
  • 16:43
    bentsherman labeled #3457
  • 16:43
    bentsherman labeled #3459
  • 16:43
    bentsherman labeled #3458
  • 11:34
    jordeu opened #3460
  • 09:43
    marcodelapierre edited #3012
  • 09:42
    marcodelapierre edited #3012
  • 08:35

    pditommaso on master

    Improve Wave config error repor… (compare)

  • 08:10

    pditommaso on master

    Fix typos in changelog.txt (#34… (compare)

  • 08:10
    pditommaso closed #3456
  • 08:02

    pditommaso on master

    Add tests Signed-off-by: Paolo… (compare)

  • 04:18
    daigok commented #3452
  • 03:59
    corneliusroemer edited #3459
  • 03:54
    corneliusroemer opened #3459
  • 03:48
    corneliusroemer opened #3458
  • 03:46
    corneliusroemer opened #3457
Paolo Di Tommaso
@pditommaso
then much simpler to test it using a test class
have a look at this example
and the invocation as operator
I would suggest also to open a draft pull request and keep a discuss thread there
Pierre Lindenbaum
@lindenb
@pditommaso :thumbsup:
Philip Jonsson
@kpjonsson
Question: In Nextflow version 19.07.0.5106, I get WARN: The channelcreatemethod is deprecated -- it will be removed in a future release when I use the Channel.create() method, but I find nowhere any mention of what's replacing it. Is the warning wrong or is there some undocumented feature I'm missing?
Ghost
@ghost~57581dbcc2f0db084a1ccd04
Don't worry, it won't happen overnight
AFAIK you can safely already remove the stuff like ch_input = Channel.create()
Philip Jonsson
@kpjonsson
@MaxUlysse Got it, thanks.
Ghost
@ghost~57581dbcc2f0db084a1ccd04

And I do believe that was the important part:

to me the only use for create that makes sense is when used with choice

Paolo Di Tommaso
@pditommaso
this is just great, isn't it ?
Hugues Fontenelle
@huguesfontenelle
hi!
How do I read the documentation for an older release? ie 19.04
well I guess I can simply read in github ..
Paolo Di Tommaso
@pditommaso
indeed
evanbiederstedt
@evanbiederstedt

@pditommaso
this is just great, isn't it ?
https://twitter.com/yokofakun/status/1159468857934929922

Confirmed, this is great

evanbiederstedt
@evanbiederstedt

https://gitter.im/nextflow-io/nextflow?at=5d4802a1475c0a0feb021c1b

Could you give us a few examples @pditommaso to illustrate this point? It still feels a bit abstract without a few concrete examples

Pierre Lindenbaum
@lindenb
@evanbiederstedt @pditommaso thanks ! I'm still not convinced it's the right way to implement the idea. 1) one can still use a bash script to extract the data 2) or it would be better using a 'static' method: something like:Channel.fromMap("my.bam").flatMap(Htsjdk::extractSamples)
Taylor Falk
@taylor.f_gitlab
Is there an easy way to pass two channel outputs and some associated strings to a process? I'm currently trying output = Channel.from(['filter1', channel1_out], ['filter2', channel2_out]) but this only returns the blank DataflowQueue(queue=[]) string inside the process.
Stijn van Dongen
@micans
@taylor.f_gitlab that would mean you'd have channels in a channel. What are you trying to achieve? What's in channel1_out and channel2_out?
Taylor Falk
@taylor.f_gitlab
@micans those channels contain singular files, so I am really just trying to run the next process on each output from channel1 and channel2, and passing along the correct filter string. How do I move those files into one channel, concat?
Stijn van Dongen
@micans

@taylor.f_gitlab do you have a source process? Normally you'd see something like

output: set val('filter'), file('*.txt') into channel1

then if there are multiple files in that output that you want to flatten you can use transpose().

Taylor Falk
@taylor.f_gitlab
Oh that's a good idea, let me try it that way.
Gabriel Abud
@G_Abud_twitter
I'm getting the error: fatal error: An error occurred (AccessDenied) when calling the ListObjectsV2 operation: Access Denied when trying to run a pipeline on AWS Batch. Pretty sure it's due to the s3 access of the workDir but I've double checked and I am the owner of that bucket. Any ideas?
Combiz
@combiz_k_twitter
Hi, this may be more of a singularity question than a nextflow one. I'm trying to run a test hello world nextflow script with -with-singularity image.sif on an HPC cluster. There seems to be an issue with mounting as the short script runs but produces an error `Command error: Fatal error: cannot create 'R_TempDir'. Any ideas? My guess is the singularity container can't write files to the HPC filesystem? Thanks for any pointers.
Combiz
@combiz_k_twitter
Ok so the script now runs with containerOptions '-B $PWD:/tmp' in the process
Johannes Alneberg
@alneberg

A question regarding input of memory specifications. Using the config

params {
  memParam = 7.GB
}

process {
  withName:sayHello {
    memory = {2 * params.memParam}
  }
}

works fine when memParam is not used, but when it is: nextflow run main.nf -c base.conf --memParam 8.GB, I get either

ERROR ~ Error executing process > 'sayHello (3)'

Caused by:
  No signature of method: java.lang.Integer.multiply() is applicable for argument types: (java.lang.String) values: [8.GB]
Possible solutions: multiply(java.lang.Character), multiply(java.lang.Number)

or

Error executing process > 'sayHello (1)'

Caused by:
  Not a valid 'memory' value in process definition: 8.GB8.GB

depending on the order of the multiplication. What am I missing? (I'm on Nextflow version 19.04.1 build 5072)

Paolo Di Tommaso
@pditommaso
umm, because when passing on the command line the string 8.GB does not get parse to Memory unit object
therefore for the interpreter it's a string
Johannes Alneberg
@alneberg
Is it possible to go around?
Paolo Di Tommaso
@pditommaso
you may try 2 * (params.memParam as nextflow.util.MemUnit)
quite ugly
Johannes Alneberg
@alneberg
Well, rather ugly than broken, I'll give it a try
it throws me unable to resolve class nextflow.util.MemUnit
Alaa Badredine
@AlaaBadredine_twitter
not Util ?
Johannes Alneberg
@alneberg
Same error using Util I'm afraid
Alaa Badredine
@AlaaBadredine_twitter
did you put the parenthesis ?
Johannes Alneberg
@alneberg
Yes:
process {
  withName:sayHello {
    memory = {2 * (params.memParam as nextflow.util.MemUnit)}
  }
}
Alaa Badredine
@AlaaBadredine_twitter
nextflow.util.MemUnit()
maybe he meant it like that ?
Johannes Alneberg
@alneberg
That gave me some syntax error: expecting ')', found '(' @ line 7, column 60.
I think I fixed it
Alaa Badredine
@AlaaBadredine_twitter
nice
Johannes Alneberg
@alneberg
nextflow.util.MemoryUnit did the trick
Alaa Badredine
@AlaaBadredine_twitter
oh neat
Johannes Alneberg
@alneberg
Thank you both!