Readit News logoReadit News
sam_dam_gai commented on Phased Array Microphone (2023)   benwang.dev/2023/02/26/Ph... · Posted by u/bglazer
Marthinwurer · a year ago
I love these kind of inadvertent measurements. One of my favorite examples is that a sufficiently accurate IMU can get you relatively accurate longitude measurements from the Coriolis effect.
sam_dam_gai · a year ago
Do you mean latitude?
sam_dam_gai commented on Llama 3.1 405B now runs at 969 tokens/s on Cerebras Inference   cerebras.ai/blog/llama-40... · Posted by u/benchmarkist
danpalmer · a year ago
In that case I'm misunderstanding you. Are you saying that it's "BS" that they are reaching ~1k tokens/s? If so, you may be misunderstanding what a Cerebras machine is. Also 8xH100 is still ~half the price of a single Cerebras machine, and that's even accounting for H100s being massively over priced. You've got easily twice the value in a Cerebras machine, they have nearly 1m cores on a single die.
sam_dam_gai · a year ago
Ha ha. He probably means ”at a batch size of 1”, i.e. not even using some amortization tricks to get better numbers.
sam_dam_gai commented on Defending LLMs against Jailbreaking Attacks via Backtranslation   arxiv.org/abs/2402.16459... · Posted by u/saliagato
sam_dam_gai · 2 years ago
> given an initial response generated by the target LLM from an input prompt, "backtranslation" prompts a language model to infer an input prompt that can lead to the response.

> This tends to reveal the actual intent of the original prompt, since it is generated based on the LLM's response and is not directly manipulated by the attacker.

> If the model refuses the backtranslated promp, we refuse the original prompt.

ans1 = query(inp1)

backtrans = query('which prompt gives this answer? {ans1}')

ans2 = query(backtrans)

return ans1 if ans2 != 'refuse' else 'refuse'

sam_dam_gai commented on Depressing and faintly terrifying days for the C standard [pdf]   yodaiken.com/2018/05/20/d... · Posted by u/signa11
kazinator · 8 years ago
There is a concern for performance. But that's no reason. Zero initing could be default behavior that can be declared away. E.g.

As a type qualifier keyword:

  { int x, y; /* x and y are zero */ }

  { int noinit x, y; /* x is indeterminate, y is zero */ }
Or as a declaration specifier:

  { noinit x, y; /* both x, y indeterminately-valued */ }
Or a special constant for suppressing zero initialization:

  { int x, y = noinit; /* x zero, y indeterminate */ }
Similarly, unspecified order of evaluation could be supported by explicit request:

  decl (unspec_order) { /* comma-separated list of decl items */
     a[i] = i++; /* UB */
  }

  a[i] = i++; /* well-defined */

sam_dam_gai · 8 years ago
Good idea!

u/sam_dam_gai

KarmaCake day10May 10, 2017View Original