302 karma · joined February 28, 2019
Song: https://app.suno.ai/song/83680b6f-db37-44de-adf9-3f7fff6b79d...
Prompt: A 90s hip-hop song with a male singer with a deep voice singing about how AI models are creating new songs after being trained on all the data of artists. Talks about AI models are stealing the show.
Lyrics:
[Verse] Step back, my friend, 'cause the future's here AI models spittin' rhymes, oh so clear (oh so clear) Trained on data from all the greats Now they're droppin' beats that dominate (dominate)
[Verse 2] Don't need no ghostwriters or melody makers These AI models are the true risk-takers (oh yeah) Analyzin' every flow, every precise word Stealing the show, that's just absurd (it's absurd)
[Chorus] AI takin' over, breakin' the mold Stolen styles, but they're icy cold (they're icy cold) The game's been changed, no human control The rise of the AI flow, takin' its toll (takin' its toll)
In the document they mention this:
In January 2023, we completed an assessment of the useful lives of our servers and network equipment and adjusted the estimated useful life of our servers from four years to six years and the estimated useful life of certain network equipment from five years to six years. This change in accounting estimate was effective beginning in fiscal year 2023, and the effect was a reduction in depreciation expense of $977 million and $2.9 billion and an increase in net income of $761 million and $2.3 billion, or $0.06 and $0.18 per basic and $0.06 and $0.18 per diluted share for the three and nine months ended September 30, 2023, respectively.
I don't get why so many services have an uptime service which does not help at all. Why even adding one?
However, we can also make use of the models to not properly generalize and their limitations of the training process. Anything that is out of distribution (very rare occurrence in training data) will be hard for the model: - blinking (if the model has ever only seen single frames it will create rather random unusual blinking behavior - turn around (as mentioned by the author, side views are rarer in the web) - take off your glasses - slap your cheek - draw something on your cheek - take scissors and cut a piece of your hair
The last two would be especially difficult and funny (:
However, in practice we see that it is very hard to collect a good dataset. There is a great twitter thread from Abubakar(CEO Gradio) about this topic: https://twitter.com/abidlabs/status/1423067498862219267
What we ideally want, is that the data we collect for training, validating, and testing our model represents the environment the trained model will operate in. However, collecting this data can be super difficult. E.g. for autonomous driving systems that would mean collecting data from every corner of the world, at every time of the day, during all kinds of weather conditions, in all 4 seasons...
However, this is a really difficult task. You will very likely end up having more data collected from one city (e.g. because your fleet is much bigger in city A than city B)
However, with Lightly you can additionally make sure you only select images that are visually different from each other. And you always get visual feedback on the selected data in our web platform. The additional control and feedback mechanism allow you to have a more focused workflow.
Prodi.gy is great but focuses heavily on NLP and speeding up the labeling process. Our goal is really to help you reduce what you label before you use any labeling tool.
We are working with labeling tools as well as providers to streamline the workflow.
>How do models trained with Lightly compare with other approaches wrt adversarial robustness?
We have no benchmark available. Both approaches can be combined. You can use Lightly to pick a diverse subset, label it and then during training/ evaluating the model check for adversarial robustness and re-iterate.
>Can using Lightly introduce additional bias in the model, since only a select few of inputs are being labeled? This may be a concern for publicity purposes.
If we remove bias we automatically introduce bias. BUT we want the introduced bias to be controlled and known.
Bias typically comes from the way we collect data. For example, more data is being collected during the day than during night for autonomous driving. We also have more data collected during sunny weather than rain or snow. We also have more data from cities like San Fransisco than cities like New Mexico. Most of our datasets are biased.
> By the way, I thought ETH spinoff requirements were incompatible with YC requirements - nice to see it can be made to work.
From what we know we are the first ETH spin-off who is part of the YC program. we hope they don't abandon us.
e.g. used here: pdec = @pipeline (numf |> pca) + (numf |> ica)