Difference between revisions of "WormBase-Caltech Weekly Calls"

From WormBaseWiki
Jump to navigationJump to search
 
(869 intermediate revisions by 12 users not shown)
Line 19: Line 19:
 
[[WormBase-Caltech_Weekly_Calls_2018|2018 Meetings]]
 
[[WormBase-Caltech_Weekly_Calls_2018|2018 Meetings]]
  
 +
[[WormBase-Caltech_Weekly_Calls_2019|2019 Meetings]]
  
GoToMeeting link: https://www.gotomeet.me/wormbase1
+
[[WormBase-Caltech_Weekly_Calls_2020|2020 Meetings]]
  
 +
= 2021 Meetings =
  
= 2019 Meetings =
+
[[WormBase-Caltech_Weekly_Calls_January_2021|January]]
  
[[WormBase-Caltech_Weekly_Calls_January_2019|January]]
+
[[WormBase-Caltech_Weekly_Calls_February_2021|February]]
  
[[WormBase-Caltech_Weekly_Calls_February_2019|February]]
+
[[WormBase-Caltech_Weekly_Calls_March_2021|March]]
  
[[WormBase-Caltech_Weekly_Calls_March_2019|March]]
+
[[WormBase-Caltech_Weekly_Calls_April_2021|April]]
  
[[WormBase-Caltech_Weekly_Calls_April_2019|April]]
+
[[WormBase-Caltech_Weekly_Calls_May_2021|May]]
  
[[WormBase-Caltech_Weekly_Calls_May_2019|May]]
 
  
 +
== June 3, 2021 ==
  
== June 6, 2019 ==
+
=== 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
  
=== New SObA graphs ===
+
=== Summer student(s) ===
* May put graphs within existing widgets, but don't need to rush to get that ready for IWM
+
* Anatomy function project with Raymond
 +
* Many types of anatomy function data submitted via AFP
  
=== Phenotype association file format ===
+
== June 10, 2021 ==
* May be best to leave the format as is
 
* There are problems; paper IDs keep switching columns
 
* Would need to revisit the reasoning for why we do it that way
 
* When will the Alliance produce a similar/replacement file? Not sure
 
  
=== Phenotype requests ===
+
=== Variation-Gene Associations ===
* Sent out 1140 emails on May 30
+
*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
* Since have received 374 annotations from 54 papers (42 requested, 12 additional)
+
*https://github.com/WormBase/author-first-pass/issues/204
* 21 papers flagged as not having phenotypes
+
*https://github.com/WormBase/website/issues/8262
* Of 1140 papers emailed about, 35 emails bounced, and have received some flagging or curation on 63 (63/1105 = ~6% response rate), in first week
+
*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
  
 +
===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 ?)
  
== June 13, 2019 ==
+
*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:
  
=== IWM ===
+
http://tazendra.caltech.edu/~azurebrd/cgi-bin/forms/generic.cgi?action=TempVariationObo
* Coordinating transportation of swag boxes to Pauley Pavilion
 
* Workshop on Saturday June 22, from 1pm to 2:30pm
 
* Saturday morning micropublication breakfast 7:30 - 8:30am
 
* Workshop
 
** Presenters: it may be best to present as use cases rather than a research project
 
** Chris will cover SimpleMine for Wen
 
** Chris: won't do live demo; only screenshots, maybe some video
 
* Paul's lab will do marathon bibs to show lab affiliation and graphical abstract
 
* Paul's talk
 
** Cover Alliance
 
** New features
 
*** SObA (for new data)
 
*** Complete for protein-protein interactions
 
*** RNASeq tools
 
*** Updated automated gene concise descriptions?
 
** Phenotype community curation
 
*** Chris will send Paul numbers on: top community curators, overall stats (number of annotations, papers, curators)
 
** Author First Pass
 
** Micropublication
 
  
=== SGD SAB ===
+
making sure to enter the variation with name-space-WBVarID like:
* Paul attended
 
* Alliance publicity was discussed
 
* SAB likes the Alliance orthology features
 
* Working on topics: displaying papers and data
 
* Pathways: discussion about best approach
 
* Metabolic engineering
 
* Meta data about RNASeq data
 
** SPELL tool, basically only tool of its kind available; need new tools
 
* Species-specific proteins: how best to find them? HMMs (Jackhammer)?
 
  
=== Concise descriptions ===
+
gk315316 WBVar01148785
* Progress being made within the Alliance to update the automated concise gene descriptions
 
* We will still accept manually written descriptions and display them in parallel with automated descriptions
 
  
=== Micropublications ===
+
and then, after refresh, it should be available to the OA. Hinxton never has to get involved in this scenario.
* If people are requesting manually written gene descriptions, they could submit a microreview
 
* Concern was expressed about how to handle a really high throughput of submissions:
 
** Daniela: Working towards automating as much of the processing pipeline as possible
 
** Raymond: The throughput will be handled appropriately depending on demand; priority scheme will help
 
** Not getting lots of submissions yet, probably won't be inundated in the near future
 
** Karen: tools are still being developed; the platform is not being advertised as much as it could be; will ramp up outreach and communication once tools are in place to handle more submissions
 
* Karen: Micropublications team will reach out to curators to help build submission forms for respective data types
 
  
=== Undiagnosed Disease Network data ===
+
=== Confirm WS282 Upload Dates ===
* Andy Golden will meet with Ranjana and Chris at IWM to discuss
+
*July 6th?
* Andy asked about protocol pages at WormBase?
+
*Data freeze/upload date on the release schedule is July 12th
* Paul: Bioprotocols and Protocols IO
 
* Maybe we could interface with those existing resources to link to relevant protocols from WormBase (and WormBook)
 
  
==June 27th, 2019==
+
=== CenGen bar plots ===
===IWM 2019===
+
*Initially discussed to have the bar plot images going in as image data
*Impressions, analysis, feedback from Users etc etc
+
*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
  
===Giving disease model annotations a stable identifier===
+
* Bring in data  both as pictures and interactive bar plots
*Currently disease model annotations get a temporary ID at the time of dump,
+
* Ping Hinxon on GitHub to move this forward
<pre style="white-space: pre-wrap;
 
white-space: -moz-pre-wrap;
 
white-space: -pre-wrap;
 
white-space: -o-pre-wrap;
 
word-wrap: break-word">
 
Disease_model_annotation : "00000004"
 
Disease_term "DOID:0050833"
 
Disease_of_species "Homo sapiens"
 
Variation "WBVar00275555"
 
Disease_relevant_gene "WBGene00011559"
 
Inferred_gene "WBGene00011559"
 
Association_type "is_implicated_in"
 
Evidence_code "IMP"
 
Genetic_sex "hermaphrodite"
 
Paper_evidence "WBPaper00035924"
 
Database "OMIM" "gene" "613891 "
 
Database "OMIM" "disease" "258900"
 
Curator_confirmed "WBPerson324"
 
Date_last_updated "2017-04-24"
 
</pre>
 
*Would like to institute stable identifiers across releases, so the plan is to call these objects, 'WBDisease_model:<number>' so then the above identifier would become ''WBDisease_model:00000004"
 
*What is the convention for IDs across MODs, especially since we now have the Alliance, should it be "WBDisease_model:00000004" or WBDisease_association:00000004".
 
*Would 'WBDisease_annotation:00000004' too long for acedb?
 

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