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

Better UX for CoclusteringReport #88

Open
popescu-v opened this issue Jul 5, 2023 · 0 comments
Open

Better UX for CoclusteringReport #88

popescu-v opened this issue Jul 5, 2023 · 0 comments
Labels
Priority/2-Low To do after P1 Status/Draft The issue is still not well defined Type/Feature A new feature request or an improvement of a feature

Comments

@popescu-v
Copy link
Collaborator

Some queries in the CoclusteringReport class are difficult to program. For example:

  • Obtain the parts of a cell for a specific dimension by name
  • Given a cluster in a dimension, obtain all cells in another one that have that cluster as a marginal

The idea is to extend the classes for the coclustering results, possibly by creating indexes to ease these kind of queries. However, this must be done carefully as the memory consumption can explose.

Implementation Ideas

  • A "lever" method index that would create the indexes on request
@popescu-v popescu-v added Status/Draft The issue is still not well defined Type/Feature A new feature request or an improvement of a feature labels Jul 5, 2023
@folmos-at-orange folmos-at-orange added the Priority/2-Low To do after P1 label Mar 12, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Priority/2-Low To do after P1 Status/Draft The issue is still not well defined Type/Feature A new feature request or an improvement of a feature
Projects
None yet
Development

No branches or pull requests

2 participants