Skip to content

MEMO OF THINGS TO DO #27

@dalessioluca

Description

@dalessioluca
  1. produce one large segmentation of smFISH_OLEH and VISIUM
  2. check batch_norm in UNET (currently is not there)
  3. reflection padding in UNET (currently is not there) or nothing and then prediction on a smaller region?
  4. the graph is not a K_NN graph. is that ok? Optimize the radius. It seems that larger is better (i.e. 5 is better than 2). To evaluate this systematically you need to make plots of N_OBJECTS vs RESOLUTION parameters. Hopefully for large radius we will see a plateau
  5. is greedy modularity optimization the thing we are interested in? TIM suggests: If you aren’t committed to greedy modularity maximization, one of the fastest libraries that will get you community detection (using Stochastic Block Models) is graph tool (https://graph-tool.skewed.de/). It’s c++ underneath (using Boost I believe), so it is very fast. The tradeoff is that it can be a huge pain in the ass to install, though I have heard it has recently been simplified.
  6. the graph is partitioned in disconnected components. Is there an advantage in treating each connected component separately. Is community detection faster? Can I use the same resolution parameters for all the different disconnected components
  7. loss function optimization. It seems that the best loss function was the one in
    folder: /home/jupyter/REPOS/spacetx-research/NEW_ARCHIVE/merfish_june22_v2
    commit 39d6bf2
    Change master implementation back to that one. Try to understand the differences.
  8. can i reduce operation for the creation of the graph to 1/4 by using roller2d on just one quadrant?

Metadata

Metadata

Assignees

Labels

prioritysomething that need to be fixed urgently

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions