Closed Nick-Eagles closed 1 month ago
Can you show the first 10-20 lines of the ....pixel.sorted.tsv.gz file?
Actually, you need to use --mu-scale 1 (or do not use the parameter) because the data is already scaled to micrometer. Can you rerun it?
Thanks! I'll try that. In case it's still helpful, this is the first 10 lines of the *pixel.sorted.tsv.gz
file:
##K=12;TOPK=3
##BLOCK_SIZE=2000;BLOCK_AXIS=X;INDEX_AXIS=Y
##OFFSET_X=1905.437;OFFSET_Y=6844.177;SIZE_X=6735;SIZE_Y=6735;SCALE=100
#BLOCK X Y K1 K2 K3 P1 P2 P3
0 0 0 0 10 1 1.00e+00 1.00e-05 4.02e-10
0 0 0 0 10 1 1.00e+00 1.00e-08 7.37e-11
0 0 0 0 10 1 1.00e+00 1.00e-09 1.97e-13
0 0 0 0 10 1 1.00e+00 1.00e-12 5.41e-27
0 0 0 0 10 1 1.00e+00 1.00e-13 4.54e-17
0 0 0 0 10 1 1.00e+00 1.01e-04 3.75e-11
It looks that X/Y coordinates in your output seems not recognized. It is possible that --mu-scale parameter in run_together is not working properly. Please let me know if --mu-scale 1 solved the problem.
Thank you! --mu-scale 1
indeed solved the problem.
Hello,
I'm working with Visium HD data and used a combination of
spatula convert-sge
(for input preparation) andficture run_together
to run FICTURE. The coarse output images (such asanalysis/nF12.d_12/figure/nF12.d_12.coarse.png
) look reasonable for the two samples I ran the pipeline for, but in both cases the pixel-level image (analysis/nF12.d_12/figure/nF12.d_12.decode.prj_12.r_4_5.pixel.png
) show up as a purely black image.The input preparation piece looks like this (and follows your spatula guide):
The FICTURE command then looks like this:
Please let me know if I can provide more information.
Best, -Nick