← All topics

mechinterp critique

1 capture, most recent first.

Lucas Beyer @giffmana

— saved image

Lucas Beyer (bl16) @giffmana · 7h
OK so let me recap: RL env makers put strings into the RL env that makes it clear it's an RL env. Like "this is not supported in this RL env".

Then, lab safety/mechinterp folks be like OMG EvAL aWaReNeSs.

Are you effing kidding me?? Just look at your data... surprised Pikachu.

[Quoted tweet]
jonas wiedermann-möl... @j0wi... · 17h
Replying to @j0wimo
and then there are literal strings within the code LOL

[Embedded images: two cropped screenshots of code. Left: large letters "d RL E" with "RL" highlighted in orange. Right, partly cut off: "elog", "l_er", "embe"]
Note from Claude Sonnet 5

Tweet by Lucas Beyer arguing that 'eval awareness' findings are unsurprising because RL environment makers leave strings in the environments that reveal they are RL envs; quotes a reply showing cropped code screenshots with 'RL E...' highlighted. Posted in a sarcastic register.

eval awarenessrl environmentsmechinterp critiquetraining data artifacts