Hi,
I wanted to post about something I found out today working with the MACS tool (under NGS: peak calling) for ChIP analysis. I found that the MACS tool will run with the 'use fixed background lambda as local lambda for every peak region' box invisibly checked when used as part of an automated workflow. You will see an error message in the MACS html output file that says !!!! DYNAMIC LAMBDA IS DISABLED !!!!. The results appear incorrect as well.
This is a bug, but you can get around it by checking this option box in the saved workflow - this has the effect of running as unchecked.
I can't find the bug report button, so I haven't reported it as a bug, but it would be good to fix probably. perhaps there are other invisibly checked options with this tool as well that I haven't noticed.
Cheers, chris
Can you be more specific about the "Workflow automated MACS tool" - what implementation are you working with? I'm aware of MACS as a standalone python program, but you mention radio buttons and html with no other identifying info. Suite name? URL?
I'm guessing that this is a galaxy workflow.
right, sorry for not mentioning it in the original post. i was using the online interface Galaxyproject.org
Guys is the question frames correctly. when I say yes to use local lamda it gives me a message saying dyanamic lambda is disabled. When I run the workflow clicking on No to use local lambda. I dont get the error.
Please can somebody point out what is lamda and why is it importantto use or not to use.