Open Boehmin opened 1 year ago
@jmuhlich, @Yu-AnChen Should this be handled using the fileseries interface?
@ArtemSokolov are you referring to the Galaxy workflow? This I haven`t tried yet.
No, ASHLAR has an undocumented feature called fileseries, which lets you explicitly map parts of the filename to tile number and cycle number.
Some discussions about it can be found in:
MCMICRO doesn't wrap this feature, so you would need to run ASHLAR "by hand" (using instructions at https://github.com/labsyspharm/ashlar). However, once you have a registered image, you can place it into the registration/
subfolder of your project and add the following to your params.yml
to run the rest of the pipeline:
workflow:
start-at: segmentation
Thank you for the advice, I will try this! I do not acquire images in a conventional grid so I`m waiting for some support from the ASHLAR team.
I've been trying to run the stitching+registration on my data: .nd2 files, FOVs saved individually: In total 8 rounds a 47 FOVs a 5 channels each
Going through some of the issues on github I saw that some others had similar file structures (img_cycle_FOV.filename), however reading through the ashlar documentation I read that only one image file should be processed per cycle?
How do I go about supplying the right information in params.yml for the ashlar module in mcmicro to recognise that I have multiple FOVs? Is this possible? Attached are myparams.yml and markers.csv the way I ran them currently. markers.csv myparams.txt
That's the error I receive (full nextflow log attached nextflowlog.txt ):