Changes between Version 6 and Version 7 of NTTData

Timestamp:

May 6, 2021, 1:48:04 PM (4 years ago)

Author:

Elaine Meng

Comment:

--

NTTData

@@ -137 +137 @@
 Phil, Philip, Meghan, Darrell; Scooter, Elaine, Eric, Greg
 
-Use of PDB or other database metadata in pipelines: they want to include/use metadata in output files; it can be done in pipelines, but what is handled by ChimeraX already? For example, Eric's script uses the suggested contour level from an EMDB file. Greg: metadata in scene export formats is which graphical object corresponds to which atom(s), but other metadata is best obtained from original data file, e.g. mmCIF/PDF. Meghan: another example is to look in the header to distinguish a virion from other viral proteins (Phil: this is in a record in the header) and direct them to different pipeline branches. 
+Use of PDB or other databases' metadata in pipelines
 
-Scooter: the previous discussion is using existing metadata to influence processing... what about writing metadata into the GLTF?  Meghan: we can do that in our pipeline code.  Phil: maybe something like the structural hierarchy, overall complex -> different proteins -> chain descriptions, and which graphical objects correspond to each, similar to what Greg was describing. Greg: we would need to know what tags are required for the intended application (Enduvo, Phil says it's like powerpoint for VR, used in Uganda for training content, includes 2D assets like slides and 3D assets, movies, sound, evaluation questions).
+For example, Eric's script uses the suggested contour level from an EMDB file.  Meghan: another example is to look in the header to distinguish a virion from other viral proteins (Phil: this is in a record in the header) and direct them to different pipeline branches. Greg: metadata in scene export formats is which graphical object corresponds to which atom(s), but other metadata is best obtained from original data file, e.g. mmCIF/PDF. 
+
+Scooter: so you want to use existing metadata to influence pipeline processing... what about writing metadata into the GLTF?  Phil: yes, maybe something like the structural hierarchy, overall complex -> different proteins -> chain descriptions, and which graphical objects correspond to each, similar to what Greg was describing. Greg: we would need to know what tags are required for the intended application (Enduvo, Phil says it's like powerpoint for VR, used in Uganda for training content, includes 2D assets like slides and 3D assets, movies, sound, evaluation questions).
+
+Kristin is developing the Enduvo content with NIAID. We would like to talk directly to Kristin and Enduvo, primarily Greg to discuss what tags would be needed. Meghan and Phil: we will discuss with them and try to organize a collective meeting. Darrell: not sure which of these tasks are worth ChimeraX development. Need to strive for only what we think is highest value to both NIAID and ChimeraX user community. ChimeraX team can weigh in on what seems to be within our reasonable scope of effort. Scooter: seems worthwhile for export from ChimeraX to be showable in 3D web viewers. Meghan's idea: maybe have ChimeraX button to put the scene on NIH 3D, which would allow people to view it via the web there. Could have some limited interactivity using hierarchy metadata, e.g. turning chains on and off. Scooter: sounds like a great idea!  Meghan: conversely, going the other direction, could also have links from entries in NIH 3D to download the corresponding ChimeraX session files.