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
The DESeq frontend sprint recently agreed on using a notebook-style interface for the wdk search. I propose we develop this as a new eda "app", similar to the workspace and mapveu apps.
Since we want to use a fixed set of cells for DESeq, part of the API for this webapp should be to declare a fixed set of cells, in addition to indicating if custom cells can be added, and possibly which apps and vizs can be included.
screenshot of proposed interface
Related, since genomics sites are going to have a variety of data types in eda (rnaseq, wgcna, etc), we will likely need a way to declare which data types an app can be used for. This is general eda thing, which I will raise for discussion in the appropriate venue.
The text was updated successfully, but these errors were encountered:
The DESeq frontend sprint recently agreed on using a notebook-style interface for the wdk search. I propose we develop this as a new eda "app", similar to the
workspace
andmapveu
apps.Since we want to use a fixed set of cells for DESeq, part of the API for this webapp should be to declare a fixed set of cells, in addition to indicating if custom cells can be added, and possibly which apps and vizs can be included.
screenshot of proposed interface
Related, since genomics sites are going to have a variety of data types in eda (rnaseq, wgcna, etc), we will likely need a way to declare which data types an app can be used for. This is general eda thing, which I will raise for discussion in the appropriate venue.
The text was updated successfully, but these errors were encountered: