-
Notifications
You must be signed in to change notification settings - Fork 4
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
Suggested additional Panache features #36
Comments
Hi @brettChapman ,
... sorted with the most present gene on top. |
Hi @brettChapman , I took some time to add an export function button that you can find in the latest versions of Panache, added with commits 7644990 (for the bananaGenomeHub branch) and commit d81a3d7 (for the main branch). It enables users to export a file looking like the following:
In Panache, when you click on the download button, it creates this 'coverage' matrix, where for each annotation ID it computes a 'coverage' score. This score per genome is based on the proportion of the annotation that is covered by at least one present panBlock. A mean score is calculated and all annotations are sorted, with the most covered/present on top. The downloaded file extracts only the annotation that are visible on screen when pressing the button, but the data for the whole chromosome are created anyway so we could download these if you prefer. I have just noticed that the header is not writing properly, I will be working on it right away. |
Done! I corrected the matrix so that it displays this header now: |
Thanks @SingingMeerkat Sorry for the delay, I've been preoccupied with other projects. I'll test out the new updated and provide feedback when I can. Where should the GFF and PAV files be located? At the moment I just have the corresponding JSON files uploaded to Panache |
I tried with the new commit '76449907eb5600a578748bd4a097632ab5f3d7cc` on the bananaGenomeHub branch. git cloned the branch and then did a git checkout 7644990 I noticed while ediitng the LocalFilter.vue file that new entries are available: Should these point to the PAV file and GFF file used to generate the JSON files, and should they be in the Public folder? and should they have the exact same naming convention as the JSON files? I did all that, and found that the page doesn't load up. |
Hi @brettChapman , sorry for the delay, I started a PostDoc a month ago and did not have much time to check that yet. About
|
I managed to get it working somehow. I have found the excel spreadsheet doesn't match up to the coverage reported though for the genes. I'm looking at gene HORVU.MOREX.r3.2HG0208140. The excel spreadhsheet says either 100% or 0%. While the hover over feature for the search criteria within Panache shows some genomes only have like 80% coverage. |
I've had a few users working with Barley Panache now. A request I have is an ability to highlight selected genes of interest, perhaps a tick box to show only genes being sorted by PAV so that it becomes easier to use a panel of genes in a single view for publication figures. Also an export/reporting feature of the selected gene regions to show PAV of that region, and the genes present with their percentage PAV. These would improve the functionality of Panache a lot. Thanks.
The text was updated successfully, but these errors were encountered: