Closed Nick-Eagles closed 1 month ago
Hi @Nick-Eagles , converting Visium HD data can be a bit tricky because it involves joining multiple files. We've written another tool to make this process more seamless. I will be giving the details in the next few days.
I still want to make sure whether our current bash-based instruction has any errors, I would suggest to see if your transcript file was correctly generated. It should be sorted by Y-axis by default. If it is sorted by X-axis, you may need to provide --major-axis option in ficture run_together
. Could you confirm if your transcripts.tsv.gz
is sorted properly?
Awesome, a tool for preparing Visium HD would definitely be useful. I just verified that transcripts.tsv.gz
is sorted by Y-axis (well, at least the first 10,000 rows), though during that check I noticed at least one row with NA
Count
, which sounds like the complaint in the original error message. As the data is large and private, I'm not sure the best way to help you diagnose things further. I'm happy to wait for the new tool unless you have other checks in mind.
Hi @Nick-Eagles -- We have published a separate tool in spatula package to handle this request. In case the current documentation in FICTURE does not work, please follow the instruction in the spatual documentation at the following URL:
If you encounter any bugs or have any further questions, please let us know.
Thanks, the spatula
tool seems to be working so far. I'll close this issue and open a different one if I encounter issues.
Hello,
First, thanks for developing this powerful software. I'm working with Visium HD data, so I first followed your tutorial for preparing the
transcripts.tsv.gz
. The first suspicious message I got was when running the following commands from the tutorial:The warnings were:
I don't use
join
much, but read that it's problematic if inputs aren't sorted a particular way. Other than those warnings, I ultimately produced thetranscripts.tsv.gz
file.Next, I attempted to run the entire FICTURE pipeline:
The error appears to occur in the
make_dge
step:Do you have a sense of what I can check to investigate this error? Do you think the
join
warnings are problematic and/or related? Please let me know if I can provide additional information. Thanks in advance!Best, -Nick