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

node coloring glitch when loading network from database #1080

Open
kdahlquist opened this issue Jan 23, 2024 · 13 comments
Open

node coloring glitch when loading network from database #1080

kdahlquist opened this issue Jan 23, 2024 · 13 comments

Comments

@kdahlquist
Copy link
Collaborator

kdahlquist commented Jan 23, 2024

Do this in beta 7.0.8:

  • load a GRN from the database
  • uncheck node coloring
  • recheck nod coloring--the checkbox gets checked and the node coloring comes back in the display, but the options don't show on the side panel

This bug is also seen in production 6.0.7

@ceciliazaragoza
Copy link
Collaborator

I tried this on beta 7.0.13 and this behavior no longer seems to be occurring. However, I do see that this is an issue when checking and unchecking node coloring for PPIs. @kdahlquist Should I disable the ability to check or uncheck node coloring for PPIs?

@kdahlquist
Copy link
Collaborator Author

I think we should keep the ability to check/uncheck node coloring for PPIs. People might have protein-expression data that they want to visualize or they might want to overlay the mRNA expression data on the PPI network.

@ceciliazaragoza
Copy link
Collaborator

I mentioned that the workbook was the issue during the meeting, but after looking over the code again, that was not the issue. There was a check for grnState.mode === NETWORK_PPI_MODE where grnState.nodeColoring.nodeColoringEnabled was set to false. I was able to get the Node Coloring Menu to show with PPIs, but should the options below "Enable Node Coloring" still display when viewing a PPI?
image

@kdahlquist
Copy link
Collaborator Author

Yes, those options should show because they enable the user to customize how the nodes are colored.

ceciliazaragoza added a commit that referenced this issue Apr 23, 2024
…ring is clicked and viewing a PPI. Want to change so that Warnings List is already collapsed and can view warning message immediately. Also found issue where Can enable node coloring from left panel with PPI but not with navbar menu
@dondi
Copy link
Owner

dondi commented Apr 23, 2024

We clarified at the 4/23 meeting that we can go ahead and have the warning appear each time. A “don’t show this again” option might be something for the future

@ceciliazaragoza
Copy link
Collaborator

ceciliazaragoza commented Oct 9, 2024

I am able to display a warning each time a PPI is displayed and node coloring is enabled, and I am trying to decide what text to display. Should the warning display in warningList or just in the top header? I have both options displayed in this image.
image
Also, in grnState I am thinking of making the default behavior to display the node coloring menus, so is there any case where node coloring should be disabled and we wouldn't want to disable node coloring menus by default?

@kdahlquist
Copy link
Collaborator Author

Here are the use cases:

  • User uploads their own PPI network with their own expression data in the workbook; node-coloring should be enabled.
  • User uploads their own PPI network with no expression data in the workbook; node-coloring should default to disabled
  • User loads a PPI network from the back-end database; node-coloring should default to disabled. If they then enable node coloring to use our expression database, that is when the warning should pop up.

For the warning message, will you please replace the word "accurate" with "appropriate". I don't think we need to have the sentence about checking the format of their workbook. Presumably if they made their workbook with expression data, they meant to do that.

While I am thinking about it, the use cases for a GRN should be:

  • User uploads their own GRN network with their own expression data in the workbook; node-coloring should be enabled.
  • User uploads their own GRN network with no expression data in the workbook; node-coloring should default to disabled
  • User loads a GRN network from the back-end database; node-coloring should default to disabled.

I.e., if a user is not uploading their own data through a file upload, then they should be forced to enable node coloring.

@ceciliazaragoza
Copy link
Collaborator

Got it. There are cases that should default to disabled or enabled, but are there any cases where we completely disable the option to enable node coloring? Previously, the node coloring menu was grayed out when using PPIs, so is there another case where we would do the same?

@kdahlquist
Copy link
Collaborator Author

I don't think there is a case where it would be grayed out completely.

ceciliazaragoza added a commit that referenced this issue Oct 16, 2024
…Is, but need to make sure node coloring sidebar not disabled when first load PPI and that don't get long list of console warnings when load PPI the first time
ceciliazaragoza added a commit that referenced this issue Oct 16, 2024
dondi added a commit that referenced this issue Oct 16, 2024
#1080: Display warning when node coloring enabled for PPIs
@dondi
Copy link
Owner

dondi commented Oct 16, 2024

After reviewing the deployment on beta, it was noted that:

  • The node coloring options only appear in the menu bar and not the sidebar after activation
  • Node coloring data doesn’t appear when an expression dataset is selected (the warnings do show up as expected)

@dondi
Copy link
Owner

dondi commented Oct 16, 2024

@ceciliazaragoza will also move the warning message outside of the network-opening routine so that it will only open at the point that node coloring is enabled. This will result in a distinct dialog from the one used in the PR, which is meant to catch data integrity issues with an uploaded workbook or network

@ntran18
Copy link
Collaborator

ntran18 commented Oct 17, 2024

"The node coloring options only appear in the menu bar and not the sidebar after activation" issue. Is it the same issue I reported #1055?

@ceciliazaragoza
Copy link
Collaborator

I was able to make the sidebar and navbar display all node coloring options when node coloring enabled by adding a boolean var to grnState. I still have to investigate how to make node coloring display on PPI nodes.

ceciliazaragoza added a commit that referenced this issue Oct 24, 2024
…out attribute not having .length. will probably have to go back to #1080 and reserve issue there
ceciliazaragoza added a commit that referenced this issue Oct 25, 2024
ceciliazaragoza added a commit that referenced this issue Oct 27, 2024
…correctly for node coloring. investigating why when load a database, it says it's NETWORK_PPI_MODE and even though node coloring enabled, node coloring doesn't display on node until change dataset and len of timepoints array is 0, so not querying expression database correctly
ceciliazaragoza added a commit that referenced this issue Oct 27, 2024
ceciliazaragoza added a commit that referenced this issue Oct 27, 2024
…MODE, and removed that code so that now databases load in correct mode
ceciliazaragoza added a commit that referenced this issue Oct 30, 2024
…r and side menu display the same status of node coloring and when node coloring disabled, the navbar and sidebar options for node coloring are hidden
dondi added a commit that referenced this issue Nov 4, 2024
#1068 Allow node coloring for PPI by matching the gene name (MERGE #1080 first)
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

4 participants