Add to openlifu the concept of a photoscan and the ability to serialize them to and from json. Photoscans are added to a particular session, similar to how volumes are added to a subject. Similar to how volumes metadata include the filepath to the mri file, photoscan metadata will include the filepath to the model file, mtl file, and texture file. It will also include an approval flag with indicates whether the scan is good enough for use in transducer tracking. This issue will add a method to the Database class to write/load a photoscan for a particular session. The Database should also be able to retrieve photoscans by ID.
Would there be multiple photoscans associated with a session? Should only be one approved photoscan, but there may be multiple "unapproved" scans?
This assumes that the photoscan <> mri transform is saved to sessions file and that a single photoscan won't be used across different sessions.
Add to openlifu the concept of a photoscan and the ability to serialize them to and from json. Photoscans are added to a particular session, similar to how volumes are added to a subject. Similar to how volumes metadata include the filepath to the mri file, photoscan metadata will include the filepath to the model file, mtl file, and texture file. It will also include an approval flag with indicates whether the scan is good enough for use in transducer tracking. This issue will add a method to the Database class to write/load a photoscan for a particular session. The Database should also be able to retrieve photoscans by ID. Would there be multiple photoscans associated with a session? Should only be one approved photoscan, but there may be multiple "unapproved" scans? This assumes that the photoscan <> mri transform is saved to sessions file and that a single photoscan won't be used across different sessions.