Opened 11 years ago
Closed 9 years ago
#20 closed defect (duplicate)
Sessions and Scenes Master Ticket
Reported by: | Scooter Morris | Owned by: | Greg Couch |
---|---|---|---|
Priority: | major | Milestone: | Core API Complete |
Component: | Sessions | Version: | |
Keywords: | Cc: | ||
Blocked By: | Blocking: | ||
Notify when closed: | Platform: | all | |
Project: | chimera |
Description
Change History (5)
comment:1 by , 11 years ago
comment:2 by , 11 years ago
Eric points out the session support will need to control order of restoring, for example, molecule data may need to be restored before a tool that uses that molecule data has its state restored.
comment:4 by , 10 years ago
Owner: | changed from | to
---|---|
Priority: | blocker → major |
Status: | new → assigned |
comment:5 by , 9 years ago
Resolution: | → duplicate |
---|---|
Status: | assigned → closed |
No longer using "master" tickets. Now use specific tickets for each issue.
Note:
See TracTickets
for help on using tickets.
From yesterday's Chimera meeting discussion, this Session and Scene and project does not include actually saving data for any models. For instance, the code to save and restore all molecule data is part of the molecule data project. This session and scene project only covers providing the basic mechanism for the saving and restoring of data. For instance it may use a Python dictionary with a key for each tool's data. It may provide methods to serialize numpy arrays and compress them. It may provide a way to reference model using a session specific id number.
Most of the session and scene code will be part of other projects such as molecule data and volume data.