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
Copy file name to clipboardExpand all lines: docs/source/usage.ipynb
+7-7Lines changed: 7 additions & 7 deletions
Original file line number
Diff line number
Diff line change
@@ -40,7 +40,7 @@
40
40
"import numpy as np\n",
41
41
"import pandas as pd\n",
42
42
"\n",
43
-
"from sainsc import read_StereoSeq"
43
+
"from sainsc.io import read_StereoSeq"
44
44
]
45
45
},
46
46
{
@@ -992,9 +992,9 @@
992
992
"metadata": {},
993
993
"source": [
994
994
"To analyse other technologies beside Stereo-seq such as imaging-based (e.g. Xenium) we only need to generate a [`sainsc.GridCounts`](#sainsc.GridCounts) or [`sainsc.LazyKDE`](#sainsc.LazyKDE) instance from a dataframe and then proceed as previously described. \n",
995
-
"If the data is stored in GEM file format you can use the [`sainsc.io.read_gem_file`](#sainsc.io.read_gem_file) function to conveniently read the file and ensure the correct format.\n",
996
-
"Otherwise we can manually prepare the dataframe as shown below for the case of Xenium data (obtained from [10x website](https://www.10xgenomics.com/datasets/fresh-frozen-mouse-brain-replicates-1-standard)).\n",
995
+
"If the data is stored in GEM file format you can use the [`sainsc.io.read_gem_file`](#sainsc.io.read_gem_file) function to conveniently read the file and ensure the correct format. Other technologies, such as Xenium or Vizgen are already supported as well. Have a look at the [`sainsc.io`](#sainsc.io) module.\n",
997
996
"\n",
997
+
"In case the technology/file format is not supported, we can manually prepare the data as shown below for the case of Xenium (obtained from [10x website](https://www.10xgenomics.com/datasets/fresh-frozen-mouse-brain-replicates-1-standard)).\n",
998
998
"The dataframe needs to contain a 'gene', 'x', and 'y' column. If a 'count' column is present it will be used otherwise a count of 1 (single transcript) will be assumed for each row. If the 'x' and 'y' columns are integers they will be assumed as indices of a square grid. Otherwise we can additionally define a bin size to use when instantiating the objects."
999
999
]
1000
1000
},
@@ -1028,7 +1028,7 @@
1028
1028
"id": "48494ac5-9f69-4ece-9dd1-a10c94cf88aa",
1029
1029
"metadata": {},
1030
1030
"source": [
1031
-
"We can now generate a [`sainsc.GridCounts`](#sainsc.GridCounts) object from this dataframe. We will generate bins with a size of 500 nm."
1031
+
"We can now generate a [`sainsc.GridCounts`](#sainsc.GridCounts) object from this `polars.DataFrame`. We will generate bins with a size of 500 nm."
1032
1032
]
1033
1033
},
1034
1034
{
@@ -1062,7 +1062,7 @@
1062
1062
"id": "72bda2b1-b6ed-4204-a144-5390ba8ad35a",
1063
1063
"metadata": {},
1064
1064
"source": [
1065
-
"Alternatively we can directly generate a [`sainsc.LazyKDE`](#sainsc.LazyKDE) object. This has the additional benefit, that we can supply either a `polars.DataFrame` or a `pandas.DataFrame`. [`sainsc.GridCounts`](#sainsc.GridCounts) can only be generated from a `polars.DataFrame`."
1065
+
"Alternatively, we can directly generate a [`sainsc.LazyKDE`](#sainsc.LazyKDE) object. This has the additional benefit, that we can supply either a `polars.DataFrame` or a `pandas.DataFrame`. [`sainsc.GridCounts`](#sainsc.GridCounts) can only be generated from a `polars.DataFrame`."
0 commit comments