Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

vars_media_update_starttime.py does not update duration or end time #9

Open
SarahRDBingo opened this issue Oct 13, 2022 · 3 comments
Open

Comments

@SarahRDBingo
Copy link

using this script is helpful for manually setting the start time, but the duration does not change and therefore the end time of a media set will be wrong.

@hohonuuli
Copy link
Member

hohonuuli commented Oct 25, 2022

Duplicated at DARC-UHM/m3-quickstart#2

@SarahRDBingo
Copy link
Author

SarahRDBingo commented Oct 25, 2022

Examples:

  1. Deployment "Deep Discoverer 14040301" was registered with an image collection pertaining to the incorrect deployment "Deep Discoverer14040203". The image collection start time and duration were created based on this folder https://hurlimage.soest.hawaii.edu/SupplementalPhotos/D2photos/EX1404photos/EX1404L2_DIVE03_20140907/ . I used the annotation gui to move the problematic images into their respective image collection URI (urn:imagecollection:org.mbari:Deep_Discoverer_14040203). The correct set of images (https://hurlimage.soest.hawaii.edu/SupplementalPhotos/D2photos/EX1404photos/EX1404L3_DIVE01_20140919/) was then registered to the already existing URI urn:imagecollection:org.mbari:Deep_Discoverer_14040301. The start time was adjusted using the vars_media_update_starttime.sh script. The start time is now correct, but the duration and calculated end time is still based off the erroneous image set. The result is some images in the last hour of the deployment exist outside the time bounds of the urn:imagecollection:org.mbari:Deep_Discoverer_14040301 collection.
  2. Testing was conducted to adjust the start time for deployment "Pisces 4 218". The result was the new clips were given corrected start times. The duration given to the clips when they were first "registered" was 02:12:00.000, while actual clip durations should be around 10 minutes. The durations of the clips are documented in spreadsheets, but they aren't consistently the same across the deployment. We need a way to manually enter the durations of each clip to correctly calculate the end times. The testing phase of this script also generated name sequences on the registered clips themselves. We would like to be able to change these video names to reflect the proper start-time that is used in the vars_media_update_starttime.py It would be nice if the clips were ordered by time sequence.

I need a way to edit the metadata of registered medias and/or remove erroneous media registered in vampire squid without having to ask the developer for help.

@MeaganPutts
Copy link

@hohonuuli Just as a heads up, I was working on dive "Deep Discover 14040309" and found that oddly, the images collection for the dive had incorrect start time, end time and duration. The first images in the collection is dated 2014-09-29T18:18:32Z and last at 2014-09-29T22:19:26. However, the registration info has the images starting at 16:50 and ending at 21:50 with a duration of 04:59:55, which is wrong. Fortunately, we were able to edit the start time of the image collection to solve this issue for now. However, if we run into this problem again in future, we may not b so lucky to have a duration time that spans the length of time necessary for the dive. Therefore, I would like to not the importance of being able to edit end time as well to be sure duration is calculated correctly.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants