Difference between revisions of "WormBase-Caltech Weekly Calls"

From WormBaseWiki
Jump to navigationJump to search
 
(413 intermediate revisions by 9 users not shown)
Line 21: Line 21:
 
[[WormBase-Caltech_Weekly_Calls_2019|2019 Meetings]]
 
[[WormBase-Caltech_Weekly_Calls_2019|2019 Meetings]]
  
 +
[[WormBase-Caltech_Weekly_Calls_2020|2020 Meetings]]
  
 +
= 2021 Meetings =
  
 +
[[WormBase-Caltech_Weekly_Calls_January_2021|January]]
  
= 2020 Meetings =
+
[[WormBase-Caltech_Weekly_Calls_February_2021|February]]
  
[[WormBase-Caltech_Weekly_Calls_January_2020|January]]
+
[[WormBase-Caltech_Weekly_Calls_March_2021|March]]
  
[[WormBase-Caltech_Weekly_Calls_February_2020|February]]
+
[[WormBase-Caltech_Weekly_Calls_April_2021|April]]
  
[[WormBase-Caltech_Weekly_Calls_March_2020|March]]
+
[[WormBase-Caltech_Weekly_Calls_May_2021|May]]
  
[[WormBase-Caltech_Weekly_Calls_April_2020|April]]
 
  
[[WormBase-Caltech_Weekly_Calls_May_2020|May]]
+
== June 3, 2021 ==
  
[[WormBase-Caltech_Weekly_Calls_June_2020|June]]
+
=== Reserving meeting rooms ===
 +
* Raymond encountering challenges with setting up regular meeting room reservations in Chen building
 +
* We've been asked to make reservations one week in advance
 +
* Need to use a room if we reserve it
  
[[WormBase-Caltech_Weekly_Calls_July_2020|July]]
+
=== Summer student(s) ===
 +
* Anatomy function project with Raymond
 +
* Many types of anatomy function data submitted via AFP
  
 +
== June 10, 2021 ==
  
==July 9th, 2020==
+
=== Variation-Gene Associations ===
===Gene names issue in SimpleMine and other mining tools===
+
*Some QC on AFP-extracted data led to the realization that at least some of the 'tm' variations aren't associated with genes on tazendra
*Wen: Last week, Jonathan Ewbank raised the issue of gene names that may refer to multiple objects.
+
*https://github.com/WormBase/author-first-pass/issues/204
*this can be an issue for multiple data mining tools including WormMine, BioMart, and Gene Set Enrichment.
+
*https://github.com/WormBase/website/issues/8262
*Perhaps have a standalone approach to check if any gene name among a list may refer to multiple objects (users check their name lists before submitting them to any data mining tool).
+
*It looks like non-manually asserted variation-gene associations will be generated via the VEP pipeline during the build, so Caltech would need to get this information from each WB release
*Jae: The public name issue has heterogeneous natures. That means there may be no single solution to solve all those problems.  
 
*Gene list curation from high-throughput studies, confusing usage of public names probably less than 2% (still cannot be ignored). See examples below--
 
**single public name is assigned to multiple WBgene ID, Wen has a list of these genes
 
**overlapped or dicistronic genes, ex. mrpl-44 and F02A9.10
 
**overlapped or dicistronic, but has a single sequence name, examples:
 
    exos-4.1 and tin-9.2 (B0564.1)
 
    eat-18 and lev-10 (Y105E8A.7)
 
    cha-1 and unc-17 (ZC416.8)
 
  
**simple confusion from authors, ex. mdh-1 and mdh-2
+
===Variation in name service but not in OA===
*One of the most significant problems is a propagation to other DB and papers of  these gene name issues.
+
*Ranjana: I could not find gk315316 in the OA though it exists in the name server. I agree that we probably don’t want to let all the million mutations into the OA since that would slow the drop-downs, but when we need one for curation, what needs to be done?
*We can make a special note for each gene page, but the people using batch analysis could not catch that easily.
+
*Juancarlos: That might be right.  It seems to try to create the variation in the name service, and if it gets a 409 Conflict error, it adds it to the temp variation file, and the obo_ tables in postgres. Since it fails to create in the name service, that's probably okay with Hinxton, and since it gets added to postgres, you should be able to use it in the OA, and since it gets added to the temp variation file, on future updates of the ontology it gets added again. Probably best if someone confirms that's the process (and maybe points us to a wiki ?)
*Conclusion: Jae and Wen will work on a tool that lets Users "sanitize" their gene lists before submission to data mining tools.  They will also write a microPub explaining this issue to the community.
 
  
===Wormicloud===
+
*Solution from Karen and Chris: If the Hinxton name server already has the variation but it isn't in the OA (as expected for Million Mutation Project variants like gk315316), we just need to add it through the old temp variations CGI:
*Please test and leave any feedback on the word cloud tool (Wormicloud), https://wormicloud.textpressolab.com/
 
*Valerio and Jae have worked on a tool that uses data in Textpresso; given a keyword, eg. "transposon", the tool generates a word cloud and word trend.
 
*Any keyword can generate a graph that plots trends of occurence across the years in publication abstracts.
 
  
===Noctua 2.0 form ready to use===
+
http://tazendra.caltech.edu/~azurebrd/cgi-bin/forms/generic.cgi?action=TempVariationObo
*Caltech summer student will try using Noctua initially for dauer (neuronal signaling) pathways
 
  
===Nightly names service updates to postgres===
+
making sure to enter the variation with name-space-WBVarID like:
*Nightly using Matt's wb-names-export.jar to get full output of genes from datomic/names service, and updating postgres based on that.
 
  
 +
gk315316 WBVar01148785
  
==July 16th, 2020==
+
and then, after refresh, it should be available to the OA. Hinxton never has to get involved in this scenario.
===Citing ontologies and their versions===
 
*Came up in the context of the Alliance: It would be best practice to provide users with the list of ontologies used and their versions/date.
 
*If WB ontology developers could make sure their ontology file headers (WB anatomy ontology, WB life stage, etc.) conformed to obo file header specifications, then it would be easy to pull in version and date information into the Alliance.
 
*Some useful links
 
**http://www.obofoundry.org/principles/fp-004-versioning.html
 
**http://obo-dashboard-test.ontodev.com/ (you can see that wbbt, wbls version metadata attribute is generating a warning).
 
**Note: OBO-foundry may not have been updated, but good practice to check your headers, anyway.
 
* Chris worked with Nico yesterday to update the ODK version for WBbt and WBls; versioning should be fine now (once the OBO dashboard runs again (hasn't run since February))
 
* Important point: the GitHub release version date tag (e.g. "v2020-06-30") needs to match the ODK release date (as stored in the OBO and OWL file headers)
 
** There are some existing mismatches, Chris is cataloging them now
 
  
=== Gene Name Sanitizer ===
+
=== Confirm WS282 Upload Dates ===
* Would be good to always (when possible) make users aware of name ambiguities
+
*July 6th?
* Wen will keep the "Multiple Output" section at the bottom of SimpleMine output
+
*Data freeze/upload date on the release schedule is July 12th
* The gene name sanitizer will be built as a stand alone tool
 
* Important to include history of gene names
 
  
=== Tools linking to SimpleMine ===
+
=== CenGen bar plots ===
* Vennter and other tools link to SimpleMine with hard coded field/column names; we should have more dynamic/robust linking without relying on hard coded field names
+
*Initially discussed to have the bar plot images going in as image data
 +
*CenGen group wants interactive bar plots similar to the modENCODE bar plots currently displayed in the FPKM expression data section on the expression widget. That way users could hover over a bar plot and see the cell type, the expression value (TPM, in our case) and the proportion of cells of each neuron type expressing the gene.
 +
*They can provide the underlying data and have the WB team generate interactive plots for each gene
 +
*Sibyl said that this is feasible and we could: 1. bring the data files in OR 2. call the CenGen API on the fly
 +
*The first approach may be more work but better in the long run as we store the data
 +
*Will ping Hinxton and see how they can integrate the data
 +
 
 +
* Bring in data  both as pictures and interactive bar plots
 +
* Ping Hinxon on GitHub to move this forward

Latest revision as of 18:59, 10 June 2021

Previous Years

2009 Meetings

2011 Meetings

2012 Meetings

2013 Meetings

2014 Meetings

2015 Meetings

2016 Meetings

2017 Meetings

2018 Meetings

2019 Meetings

2020 Meetings

2021 Meetings

January

February

March

April

May


June 3, 2021

Reserving meeting rooms

  • Raymond encountering challenges with setting up regular meeting room reservations in Chen building
  • We've been asked to make reservations one week in advance
  • Need to use a room if we reserve it

Summer student(s)

  • Anatomy function project with Raymond
  • Many types of anatomy function data submitted via AFP

June 10, 2021

Variation-Gene Associations

Variation in name service but not in OA

  • Ranjana: I could not find gk315316 in the OA though it exists in the name server. I agree that we probably don’t want to let all the million mutations into the OA since that would slow the drop-downs, but when we need one for curation, what needs to be done?
  • Juancarlos: That might be right. It seems to try to create the variation in the name service, and if it gets a 409 Conflict error, it adds it to the temp variation file, and the obo_ tables in postgres. Since it fails to create in the name service, that's probably okay with Hinxton, and since it gets added to postgres, you should be able to use it in the OA, and since it gets added to the temp variation file, on future updates of the ontology it gets added again. Probably best if someone confirms that's the process (and maybe points us to a wiki ?)
  • Solution from Karen and Chris: If the Hinxton name server already has the variation but it isn't in the OA (as expected for Million Mutation Project variants like gk315316), we just need to add it through the old temp variations CGI:

http://tazendra.caltech.edu/~azurebrd/cgi-bin/forms/generic.cgi?action=TempVariationObo

making sure to enter the variation with name-space-WBVarID like:

gk315316 WBVar01148785

and then, after refresh, it should be available to the OA. Hinxton never has to get involved in this scenario.

Confirm WS282 Upload Dates

  • July 6th?
  • Data freeze/upload date on the release schedule is July 12th

CenGen bar plots

  • Initially discussed to have the bar plot images going in as image data
  • CenGen group wants interactive bar plots similar to the modENCODE bar plots currently displayed in the FPKM expression data section on the expression widget. That way users could hover over a bar plot and see the cell type, the expression value (TPM, in our case) and the proportion of cells of each neuron type expressing the gene.
  • They can provide the underlying data and have the WB team generate interactive plots for each gene
  • Sibyl said that this is feasible and we could: 1. bring the data files in OR 2. call the CenGen API on the fly
  • The first approach may be more work but better in the long run as we store the data
  • Will ping Hinxton and see how they can integrate the data
  • Bring in data both as pictures and interactive bar plots
  • Ping Hinxon on GitHub to move this forward