SING4DATASCIENCE/HSSingLog session contains number of processes.
- Generation of the playlist
- Sing session
- Result tabulation
- Metadata tabulation
- Result posting
This article covers processes and the tools used for the process.
Generation of the playlist
Playlist generation for the sing session is automated, and has following features.
- Automatic lottery selection system
- Fixed song system (currently applies to the 3 songs.)
Automatic lottery selection system uses the number of past entries and elapsed time since last session as the weighting element to simulate lottery for the songs to be included in a playlist. With this weighting, the system select songs with fewer number of sessions, and ones with longer time elapsed since last session.
This is implemented using PowerShell, with lottery logic as a binary, lottery process as a script. (Using PowerShell 7.)
After generation of the playlist is complete, the system generates singing directive sheet. This sheet contains order of songs to be sung, and also shows currently available metadata for these songs.
Once the singing session is complete, the results are tabulated. From the singing directive sheet, Title ID column is extracted, and is tabulated using tabulation sheet.
Once this tabulation process is complete, using the Get-HSLCompiledFile cmdlet, verifications (to make sure scoring doesn’t have any irregularites) and combine the title information, which generates the results posted on GitHub.
When the song is missing metadata (either this is a new song, or ones that metadata is not yet filled in), these are entered into the singing directive sheet, and then the Update-HSLCsvData cmdlet is used to update. This cmdlet updates 3 metadata CSV files. (These 3 metadata files are authors, release date, and tempo.)
- Generation of the text for the posts
- Generation of the graph element for the posts