After folder setup update, reference database updated with --update_db
Output result after standard crop/sort operation:
Kpop SNSD - Taeyeon and Kpop SNSD 1 Taeyeon interpreted as two different faces: output sorted files are split across the two folders.
Inferences:
Changes made to a previously processed folder are interpreted as a brand new folder created as the mapping in Windows is based on filepath name.
Original reference folder and updated reference folder are mapped as different faces.
Potential solution ideas?
To enable folder setup to be updated before database update:
Add possibility to request to list db.pt recorded references/faces associated paths
Parameter could generate and output a file referenceslist.txt (would then not require #9 prior to implementation)
Add possibility to edit db.pt to change linked face/folderpath name?
'Simplest' idea would be by user manually replacing referenceslist.txt with updated values and running a parameter to merge that with currently existing db.
Other idea would be to set a parameter allowing user to modify an existent reference foldername to another via command line.
Record existing list of reference folders and add step to --update_db to check if the structure has been changed and notify user of potential problems (e.g. renamed folders)
If another solution is implemented that allows user to update the references' filepath name prior to update, step could instead reject db update completely, or require manual confirmation input from user. (a la 'Are u sure? Enter Y if yes, N to cancel')
Assign unique IDs per reference folder/face pathname and store them
Could make above suggestions more straight-forward.
Original example reference folder setup:
After folder setup, references processed and reference database created.
Renamed reference folder setup:
After folder setup update, reference database updated with
--update_dbOutput result after standard crop/sort operation:
Kpop SNSD - TaeyeonandKpop SNSD 1 Taeyeoninterpreted as two different faces: output sorted files are split across the two folders.Inferences:
Potential solution ideas?
To enable folder setup to be updated before database update:
db.ptrecorded references/faces associated pathsParameter could generate and output a file
referenceslist.txt(would then not require #9 prior to implementation)db.ptto change linked face/folderpath name?'Simplest' idea would be by user manually replacing
referenceslist.txtwith updated values and running a parameter to merge that with currently existing db. Other idea would be to set a parameter allowing user to modify an existent reference foldername to another via command line.--update_dbto check if the structure has been changed and notify user of potential problems (e.g. renamed folders)If another solution is implemented that allows user to update the references' filepath name prior to update, step could instead reject db update completely, or require manual confirmation input from user. (a la 'Are u sure? Enter Y if yes, N to cancel')