You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi there,
When I am running Baysor on CosMx data, it seems to work great for many of my fields of view (FOVs). However, with a select few, I get the following error:
Update: I have identified the problem. I read the transcripts (tx) files into R for a few of the select FOVs that did not work. After grouping by z position and counting, I get a table like this for all of the FOVs:
In each FOV, one of the z positions has very few tx associated with it. In this example, after removing the two tx that had a z position of -1, Baysor worked. So, in the general case, if I simply exclude all tx that occur in a certain z plane that contains less than say 5 tx, then I am in business.
Is there an option or flag that I am missing that would resolve this problem?
Thank you for debugging it, @ccnawrocki ! That's the first time I see negative z. That might be the problem. I will test it more for the next release. Currently there are no flags to deal with it, unless you want to convert it all to 2D (--config.data.force-2d=true)
Hi there,
When I am running Baysor on CosMx data, it seems to work great for many of my fields of view (FOVs). However, with a select few, I get the following error:
Everything seems to run fine, but there is a problem with saving.
I am using Baysor version 0.7.1 on MacOS 15.1.1
Julia version 1.10.7
I have an M3 MacBook Pro
Any help would be much appreciated.
The text was updated successfully, but these errors were encountered: