search

idia-astro / iDaVIE

immersive Data Visualisation Interactive Explorer (iDaVIE). The specific goal of iDaVIE is to enable the interrogation of 3D data using virtual reality technology.
https://idavie.readthedocs.io/
Other
5 stars 0 forks source link

have the ability to make "controlled" movie of cubes #240

Open lmarIT opened 2 years ago

lmarIT commented 2 years ago

Similar to what DS9 does. the file name can have the name encapsulating the RA/DEC centroid of the region selected. The user will see the movie in the desktop interface.

thjarrett commented 2 years ago

Purpose: to make a 'quicklook' video of your target object.
Basic idea: create a set of frame snaps where the camera (a 2nd virtual camera) orbits the target in a 360deg circle, always facing the object; the snaps could then be collated into a video

Details: The user selects the object as usual (crop selection). They would then adjust their orientation for the start of the video (e.g., a good standard orientation would be to face the spatial axis), including how far away the target is located from the viewer. The user would then execute a voice command (or via quick menu, etc) that fires off a 2nd camera that starts from the viewers location, facing the target, and circles 360 along the horizontal plane (perpendicular to the ground). The camera orbits the target, snapping a picture every set angular travel (e.g., every 2 degrees, thus 180 frames). The frame parameters could be set in the idavie config json. The output (snap frames) are sent to the usual Outputs folder , with a sub-folder (named by the date-time-stamp, e.g.). The frames would be there for the user to extract and make a video of their choice etc. But idavie could also simply make a video (by easily calling ffmpeg) and placing it in the same folder. The user may edit the video and/or frames at their leisure.

Tech parameters include: (1). numbers of frames per 360 degrees, (2). fov of view for the snap, keeping in mind the camera always faces the target as it orbits, (3) quality of the snap, we should make sure this is practical, so modest quality JPEGS to create frames that are not too big (say less than a MB each).

More technical: while the camera is orbiting, the user should NOT have the ability to change the target situation. Perhaps shut off the ability to interact, etc. The user waits for the completion of the snaps, and then the VR comes back to life. If the user can see and monitor the orbiting camera, they will at least know its progress and how much time is left in this limbo (like have a progress bar).

marcinglowacki commented 2 years ago

I endorse this idea; it is something that the WALLABY team would find useful e.g. for outreach, PR.