[HN Gopher] RETRO is fast
___________________________________________________________________
RETRO is fast
Author : bilsbie
Score : 79 points
Date : 2022-07-03 13:19 UTC (9 hours ago)
(HTM) web link (mitchgordon.me)
(TXT) w3m dump (mitchgordon.me)
| PKop wrote:
| I find the font contrast far too low, and therefore the text is
| hard to read.
| rightbyte wrote:
| I barely can read it. I got that thing where circles are oval-
| shaped at the eye exam.
| MollyRealized wrote:
| Unless I have something specific to my computer going on, or
| something was altered in the last 30 minutes, I'm seeing black
| on white.
| Palomides wrote:
| I get #3c484e text with weight of 200
| dang wrote:
| " _Please don 't complain about tangential annoyances--things
| like article or website formats, name collisions, or back-
| button breakage. They're too common to be interesting._"
|
| https://news.ycombinator.com/newsguidelines.html
| PKop wrote:
| OK I didn't know this was against the rules, I see it on here
| often. Small quibble: difficulty to actually read the
| submission doesn't seem completely tangential.
| bitforger wrote:
| Hey! Author here. I've noticed on certain mobile devices the
| contrast can be weird, not sure why.
|
| I updated the default theme's text color to be 10% darker, lmk
| if that looks better to you.
| slater wrote:
| Chiming in here w/ same complaint ;)
|
| On macOS (display: 15.4-inch, 2880 x 1800), it's really
| difficult to read. I set the font to ''400 1.2rem/1.5 "Fira
| Sans",sans-serif'' and color to #111 in dev tools, way better
| readability.
|
| (sidenote: is Fira Sans a default installed font on Linux
| systems? I'm on macOS and don't have that, and don't see a
| font embed anywhere in your source code. So that might be the
| issue - 'sans-serif' at 200 weight is way too faint)
| PKop wrote:
| Pretty sure it's the font-weight that needs increased, when
| you do the current color is fine.
| [deleted]
| hwers wrote:
| I guess an interesting way to translate this technique to text-
| to-image would be to get an image from a database that matches
| the text query (via CLIP) and feed that + noise into a diffusion
| model that only does a few denoising iterations (and no clip
| guidance maybe). Would be a lot faster than from-scratch
| diffusion.
|
| (Another way could be to redo the architecture to include a
| "inspired by this image" input, which is queried from an image
| server at inference time.) Anyone have other ideas?
| ShamelessC wrote:
| This was one of the motivations for `clip-retrieval`, a faiss
| index over the CLIP embeddings (CLIP ViT-L/14 to be precise)
| for all the captions/images in the LAION5B-Aesthetic dataset.
|
| https://rom1504.github.io/clip-retrieval
|
| Try the reverse image search - it can be shockingly effective.
|
| You can pretty easily rehost the index or build a lookup over
| your own data if you check the GitHub repo.
|
| If you don't have any data of your own, enter a query and hit
| that download icon to get a CSV of `URL,Caption,CLIP score`.
| mbforbes wrote:
| Did anyone else read the generations? They're... really poor
| quality, right? Im not sure whether I'm misunderstanding though.
| ShamelessC wrote:
| I don't think they are generations, but rather samples from The
| Pile that are semantically close to the input.
|
| Actually, as far as I can tell - the RETRO arch itself isn't
| trained in this article. It focuses more on how to build the
| retrieval system with a fast KNN index over all of the Pile.
| visarga wrote:
| This is great for speed, maybe we can also increase the window
| size if the model is so small, but how about the quality of the
| generated text? With a 20x smaller model does quality drop?
|
| How many chunks do you retrieve? The paper shows best results at
| k=1 and then at k>50.
___________________________________________________________________
(page generated 2022-07-03 23:00 UTC)