-
Notifications
You must be signed in to change notification settings - Fork 8
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
Add PPI demo #1065
Comments
We’ll start with an export based on the database then move on to Dr. Dabir’s data when ready |
Demo #5 PPI Network (Yeastmine - SGD 2023-03-29; 18 proteins, 81 edges).xlsx I created this network from the database. It is all the proteins that interact with Aim32p, which is the protein that Dr. Dabir studies. I exported it from GRNsight and then modified the filename. It has only a "network" sheet. I changed the text in cell A1 to read "protein 1/protein 2". It loads back into GRNsight OK, but currently, it loads as a GRN, not PPI because there's nothing to tell GRNsight that it is a PPI network. In doing this, I think I uncovered a bug, but will report in a different issue. |
I'm open to shortening the filename to something like: Demo #5 PPI (18 proteins, 81 edges) "Network" is probably redundant. If we shorten it this way, we lose the provenance of the data, but that could be put into the documentation. This could be better due to readability in the dropdown menu. |
File is ready to go—we will use the content of cell A1 to determine the Network Mode to switch to, as noted in #1066. Label the demo as noted in the comment above Demos are encoded directly as JSON objects; the easiest way to convert is probably to temporarily add a As noted, we will use cell A1 of the Network sheet to determine the Network Mode. Further, we will need to adjust the warning to adapt to these changes |
Verified present in beta 7.0.8 |
For parity with GRNs, we need to add PPI demos to the app. @kdahlquist will generate the file and this can be added to the app in the same way that the existing demos are added.
The text was updated successfully, but these errors were encountered: