Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

cNMF - user experience #257

Open
2 of 6 tasks
sjfleming opened this issue Oct 22, 2024 · 0 comments
Open
2 of 6 tasks

cNMF - user experience #257

sjfleming opened this issue Oct 22, 2024 · 0 comments

Comments

@sjfleming
Copy link
Contributor

sjfleming commented Oct 22, 2024

Notes from meeting with Jim Nemesh.

Improve the user experience for running cNMF.

Usability:

  • Streamline the config file
    • don’t require total genes to be input manually (anything that can be inferred from the data should be)
      • or get stuff from a saved checkpoint if applicable
    • require the absolute minimum necessary input in the YAML for functionality
  • Ensure HVG finding is streamlined (outside of nmf)
    • this may require writing a separate tool, not sure
    • somehow we need a command-line way for users to use CellariumML to come up with the HVG list for use in a Filter
  • Enable users to input a range of k values
    • Do all the runs
    • How do we want to do this? In series? In parallel? Could it be done in parallel...?
      • Maybe we could set things up so that the model itself sequentially fits a lot of k models (in each minibatch)
  • Compute and output metrics for all runs in a way that’s readable and plottable (maybe even make the plot)
    • Output “stability” and “error” (use the same terminology as cNMF paper)
    • Have a CSV output file that can be used to make the plot very simply
  • Have code to make the necessary stability and consensus clustermap/hist plots in jupyter notebook
    • Simple API for interactive analysis
    • The “consensus” part need not be a command line tool really… they want it to be interactive in a notebook

Note:

  • If you have multiple command line steps… then you better do input validation
  • Make sure that a user cannot change the input file between the initial fit and the final refit part, for example
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant