List view
## Use Case It would be nice if users could set geometry files, either OBJ mesh files or PDB files/ids, and have them used for rendering agents. ## Acceptance Criteria Users can specify mesh or PDBs in their .simularium files, somehow provide those files to the viewer, and see their agents rendering with the correct mesh or PDB by their type. ## Details Currently this works for streaming files (using an additional metadata file, vis_data.json) but not for files loaded by drag/drop or from a URL. .simularium file format v3 includes "geometry" for each agent type in `data["trajectoryInfo"]["typeMapping"]` (https://docs.google.com/document/d/1hxRQ1quZecX3Lo7WEDLN-MPU1Ebiiv6f9WKMt8i_8ZE) For local import (drag/drop): - use relative paths and either drag a folder or a group of files onto the browser or choose multiple files or a folder in the import dialog, or - use web URLs and the viewer will request them For load by URL: - use web URLs and the viewer will request them For streaming: - use web URLs and the viewer will request them - this replaces how the viewer requests vis_data.json (since this wasn't available to users in v1, files that don't have "geometry" can fallback to spheres just like for agent types in v3 .simularium data that don't have geometry specified) Use the "displayType" field of "geometry" to render the downloaded file. If a requested file fails to download, or if a URL is not provided for "displayType" of "PDB" or "OBJ", display a warning like "Failed to load geometry for [agent type] because [error reason]" Relative paths are relative to the directory containing the .simularium file. Only load the first 100,000 geometry files. Some agents may have the same geometry file, so count the number of unique requests rather than the number of agent types with geometry. If there are more urls than this in the file, warn the user that only the first 100,000 were used.
No due date•6/6 issues closed