Location
Badges
Activity
Ratings Progression
Challenge Categories
Challenges Entered
Shopping Session Dataset
Latest submissions
Audio Source Separation using AI
Latest submissions
See Allfailed | 220446 | ||
failed | 220436 | ||
graded | 220403 |
Specialize and Bargain in Brave New Worlds
Latest submissions
Machine Learning for detection of early onset of Alzheimers
Latest submissions
Reinforcement Learning on Musculoskeletal Models
Latest submissions
Music source separation of an audio signal into separate tracks for vocals, bass, drums, and other
Latest submissions
See Allfailed | 220436 | ||
graded | 220403 | ||
failed | 220395 |
Source separation of a cinematic audio track into dialogue, sound-effects and misc.
Latest submissions
See Allfailed | 220446 | ||
graded | 220402 | ||
graded | 220397 |
Participant | Rating |
---|---|
the_acapellaguru | 0 |
tyler_weitzman | 0 |
Participant | Rating |
---|
Sound Demixing Challenge 2023
Submission Times
Over 1 year agoHi,
first, congrats to your great scores!
I didnβt get any extra submissions and, to be honest, had a hard time understanding how the submission quota actually works, myself. As I didnβt team up with individual accounts, the max submission count was likely different. I canβt say if aicrowd has some rounding issues when it comes to team submissions vs individual submission so maybe they can improve their docs on this part.
No submission remaining
Over 1 year agoHi wondering how the submission are counted. If itβs by local time zone, then my account should have 7 left, if by a rolling window counting backwards 24 hours ago, my account still should have 3. Any explain nations? thank you.
Submission Times
Over 1 year agoWe also investigated our submissions again, I have two more findings
we seemed to only have tested
debug=True
once on Mar 30th and left it todebug=False
since then. We didnβt notice it back then but we can confirm that we got 6 submissions through on that day. As I remember, the reasons for enabling it, was to check weather we get more accurate readings on the runtime duration (not the case ) Here is the blame log foraicrowd.json
.The listing that @JusperLee posted above, showing that we got 7 submissions on May 8th UTC. seems not related to the debug issue. In fact, there seem to be two other reasons for it:
220307
. In fact we accidentially created a new tag for the exact same git commit. Funnily, it seems the submission system created identical timestamps and logs for both, so it might be the same submission and we accidentially discovered that you can do unlimited submission (when they are all the same)β¦ I donβt think there is any way to benefit from this issue, right?update: @dipam already mentioned the second issue in his post above