Difference between revisions of "WormBase-Caltech Weekly Calls"

From WormBaseWiki
Jump to navigationJump to search
(22 intermediate revisions by 5 users not shown)
Line 35: Line 35:
 
[[WormBase-Caltech_Weekly_Calls_May_2021|May]]
 
[[WormBase-Caltech_Weekly_Calls_May_2021|May]]
  
 +
[[WormBase-Caltech_Weekly_Calls_June_2021|June]]
  
== June 3, 2021 ==
 
  
=== Reserving meeting rooms ===
+
== July 1, 2021 ==
* 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) ===
+
=== Importing genes for tm alleles from GeneACE ===
* Anatomy function project with Raymond
+
* https://github.com/WormBase/website/issues/8262
* Many types of anatomy function data submitted via AFP
+
* Nightly dump currently excludes tm allele genes
 +
* Most tm (Mitani) alleles are not being manually connected to specific genes in GeneACE
 +
* Should pull the data from WS release (into Postgres) after the build has mapped the alleles to genes
 +
* ~100,000 alleles in Postgres; ~70,000 don't have a gene connection
 +
* Would Hinxton be willing to take WS-mapped allele-to-gene associations and populate GeneACE with associations not already in there?
  
== June 10, 2021 ==
+
=== Citace upload ===
 +
* Curators upload files to Spica for citace upload on Tuesday (July 6)
  
=== Variation-Gene Associations ===
+
=== Chen B1 kitchen Usage Considerations ===
*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
+
* Clean up after oneself.
*https://github.com/WormBase/author-first-pass/issues/204
+
* Mark food storage with name and date.
*https://github.com/WormBase/website/issues/8262
+
* Mark storage drawers
*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
+
* Consumables
  
===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 ?)
 
  
=== Confirm WS282 Upload Dates ===
+
== July 8, 2021 ==
*July 6th?
 
*Data freeze/upload date on the release schedule is July 12th
 
  
=== CenGen bar plots ===
+
=== Alliance work ===
*Initially discussed to have the bar plot images going in as image data
+
* Orange team presenting initial plans at Alliance PI meeting tomorrow
*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.
+
* What working groups are still meeting? What are their responsibilities?
*They can provide the underlying data and have the WB team generate interactive plots for each gene
+
** Expression
*Sibyl said that this is feasible and we could: 1. bring the data files in OR 2. call the CenGen API on the fly
+
** Variants
*The first approach may be more work but better in the long run as we store the data
+
** Disease & Phenotype
*Will ping Hinxton and see how they can integrate the data
+
** Technical working groups
 +
*** Technical call
 +
*** Data quartermasters
 +
*** DevOps
 +
* Expression working group working on LinkML model with Gil (FB)
 +
** Includes work on antibody class, image class, movie class
 +
** Are species-specific anatomy ontologies being utilized for expression annotations or still just Uberon?
 +
* Creating a curation interface/tool:
 +
** Will require loading auxiliary data types in addition to primary data types (e.g. if we are focused on disease annotation curation, we will need to load genes, alleles, strains, etc. in addition to the disease annotations themselves) to be available to make connections to
 +
** One requirement already expressed by curators is the need to generate new entities, like alleles, and have them quickly (immediately?) available for use in curation
 +
** Maybe this could be handled by an Alliance central name server that mints new IDs (Alliance IDs and maybe also MOD IDs?) for the objects to make them available (also with a mechanism for these new objects/IDs to make their way back to the MODs as well)
 +
** Micropublication curation forms have tackled a lot of issues of collecting lexica and entity names and IDs; should consider work already done with Micropubs
 +
 
 +
== July 15, 2021 ==
 +
 
 +
=== hlh-34 expression ===
 +
* Rebecca Mcwhirter (Miller lab) contacted WB saying that the annotations to AVJ for hlh-34 are incorrect. 4 evidences list AVJ -> the authors of the first paper that describes hlh-34 expression (Cunningham et al, 2012 : http://dx.doi.org/10.1016/j.cmet.2012.05.014) had to pick one neuron per reviewer's request. The neuron should instead be AVH.
 +
* Oliver is putting together a micropub to clarify the issue
 +
* How to deal with existing  annotations? Add a comment in the remarks that points to the microPub? remove AVJ from the anatomy association list?
 +
* Should we also add public comments to the relevant papers?
 +
 
 +
== July 22, 2021 ==
 +
 
 +
=== Copying data from textpresso-dev to tazendra ===
 +
* Michael has been asking curators to retrieve any data they might still want on textpresso-dev before the machine dies
 +
* Can we copy files to tazendra?
 +
* If so, do we need to have a more general approach/strategy other than creating new folders in the individual curator directories?
 +
* Are there any size considerations for what we copy over?  There are 1.1T free in /home2 which is not backed up

Revision as of 18:00, 22 July 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


July 1, 2021

Importing genes for tm alleles from GeneACE

  • https://github.com/WormBase/website/issues/8262
  • Nightly dump currently excludes tm allele genes
  • Most tm (Mitani) alleles are not being manually connected to specific genes in GeneACE
  • Should pull the data from WS release (into Postgres) after the build has mapped the alleles to genes
  • ~100,000 alleles in Postgres; ~70,000 don't have a gene connection
  • Would Hinxton be willing to take WS-mapped allele-to-gene associations and populate GeneACE with associations not already in there?

Citace upload

  • Curators upload files to Spica for citace upload on Tuesday (July 6)

Chen B1 kitchen Usage Considerations

  • Clean up after oneself.
  • Mark food storage with name and date.
  • Mark storage drawers
  • Consumables


July 8, 2021

Alliance work

  • Orange team presenting initial plans at Alliance PI meeting tomorrow
  • What working groups are still meeting? What are their responsibilities?
    • Expression
    • Variants
    • Disease & Phenotype
    • Technical working groups
      • Technical call
      • Data quartermasters
      • DevOps
  • Expression working group working on LinkML model with Gil (FB)
    • Includes work on antibody class, image class, movie class
    • Are species-specific anatomy ontologies being utilized for expression annotations or still just Uberon?
  • Creating a curation interface/tool:
    • Will require loading auxiliary data types in addition to primary data types (e.g. if we are focused on disease annotation curation, we will need to load genes, alleles, strains, etc. in addition to the disease annotations themselves) to be available to make connections to
    • One requirement already expressed by curators is the need to generate new entities, like alleles, and have them quickly (immediately?) available for use in curation
    • Maybe this could be handled by an Alliance central name server that mints new IDs (Alliance IDs and maybe also MOD IDs?) for the objects to make them available (also with a mechanism for these new objects/IDs to make their way back to the MODs as well)
    • Micropublication curation forms have tackled a lot of issues of collecting lexica and entity names and IDs; should consider work already done with Micropubs

July 15, 2021

hlh-34 expression

  • Rebecca Mcwhirter (Miller lab) contacted WB saying that the annotations to AVJ for hlh-34 are incorrect. 4 evidences list AVJ -> the authors of the first paper that describes hlh-34 expression (Cunningham et al, 2012 : http://dx.doi.org/10.1016/j.cmet.2012.05.014) had to pick one neuron per reviewer's request. The neuron should instead be AVH.
  • Oliver is putting together a micropub to clarify the issue
  • How to deal with existing annotations? Add a comment in the remarks that points to the microPub? remove AVJ from the anatomy association list?
  • Should we also add public comments to the relevant papers?

July 22, 2021

Copying data from textpresso-dev to tazendra

  • Michael has been asking curators to retrieve any data they might still want on textpresso-dev before the machine dies
  • Can we copy files to tazendra?
  • If so, do we need to have a more general approach/strategy other than creating new folders in the individual curator directories?
  • Are there any size considerations for what we copy over? There are 1.1T free in /home2 which is not backed up