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
overall, nested structure where the user chooses to go deeper. start with broad overview, drill down to more info
levels (at tf level)
global view provides an overview that says that "cc is better than others," or whatever
another view that shows integrated network of the TF
target list (tf locus tag, gene locus tag, strength)
find spot in site to also search for regulators of a given gene
per tf overview page
what datasets are available for that tf
which datasets are 'best' (for that tf)
next level down from this view is justification on why these datasets are recommended (for now, at least as placeholder, use rank recall)
all visualizations sizes (size of plots) should take into account scaling, so that for example if a 20 new expression datasets are added, we aren't displaying 20 very small rank response plots horizontally
Must set defaults on what displays (eg, for side by side rank response, only 2 of n would display by default, user selects more)
to the extent possible, make the layout something the user can manipulate
parameterize both the faceting, and also the grouping, so there is an option to show 12 lines on 2 plots or 6 lines on 4
GO
allow user to click into a "go" page to get more detail
exporting data
The text was updated successfully, but these errors were encountered:
all pages should export data
overall, nested structure where the user chooses to go deeper. start with broad overview, drill down to more info
levels (at tf level)
find spot in site to also search for regulators of a given gene
per tf overview page
all visualizations sizes (size of plots) should take into account scaling, so that for example if a 20 new expression datasets are added, we aren't displaying 20 very small rank response plots horizontally
GO
exporting data
The text was updated successfully, but these errors were encountered: