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

Raise the term number cap in the Matrix tool #621

Open
ValWood opened this issue Sep 21, 2021 · 3 comments
Open

Raise the term number cap in the Matrix tool #621

ValWood opened this issue Sep 21, 2021 · 3 comments

Comments

@ValWood
Copy link

ValWood commented Sep 21, 2021

@cmungall
@kltm
I know I asked this before, but is it possible to increase the number of terms we can add to the matrix tool?
@pgaudet @RLovering and I are trying to improve the generic GO slim. Putting the terms into the matrix tool is a great way to assess the modularity (reduced overlap between slim terms).
At present we have too many terms:

ask_seth_Screenshot 2021-09-17 at 18 48 51

@kltm kltm changed the title matrix, term number cap Raise the term number cap in the Matrix tool Sep 21, 2021
@kltm
Copy link
Member

kltm commented Sep 21, 2021

@ValWood Honestly, I'm not sure if I remember this specifically from before; poking around a little isn't turning up much.

About how many would you need? Unfortunately, without rewriting a whole bunch of the core here, there is not a lot of flexibility--the code is unfortunately tweaked with a lot of hard-coded values in a library I'm not particularly familiar with anymore. That said, I may be able to do something like increase the base canvas size or double the density without much additional work, depending on what your expected needs are.

@ValWood
Copy link
Author

ValWood commented Sep 22, 2021

We can let you know the final number once we have the slim set It is likely to be around 70-75 ball-park for process.
cheers,
Val

@ValWood
Copy link
Author

ValWood commented Sep 22, 2021

I went hunting for the old ticket but I couldn't find it anywhere...

@kltm kltm transferred this issue from geneontology/go-site Sep 22, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants