| 139 | | 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. |
| | 139 | 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. |
| | 140 | |
| | 141 | 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). |
![[ChimeraX Issue Tracking System]](/trac/ChimeraX/chrome/site/ChimeraX-icon.svg){kind=icon}
