Model | 10.4 | 10.5 | 10.6 | 10.7 | 10.8 | 10.9 | 10.10 | 10.11 | 10.12 | 10.13 | 10.14 | 10.15 | 11 | 12 | 13 | 14 | 15 | 26 |
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Year | 2005 | 2007 | 2009 | 2011 | 2012 | 2013 | 2014 | 2015 | 2016 | 2017 | 2018 | 2019 | 2020 | 2021 | 2022 | 2023 | 2024 | 2025 |
MacBook (13-inch, Mid 2006) | ✅ | ✅ | ✅ | |||||||||||||||
MacBook Pro (15-inch, Early 2006) | ✅ | ✅ | ✅ | |||||||||||||||
MacBook Pro (17-inch, Early 2006) | ✅ | ✅ | ✅ | |||||||||||||||
iMac (17-inch, Early 2006) | ✅ | ✅ | ✅ | |||||||||||||||
iMac (20-inch, Early 2006) | ✅ | ✅ | ✅ | |||||||||||||||
Mac mini (Early 2006) | ✅ | ✅ | ✅ | |||||||||||||||
Mac mini (Late 2006) | ✅ | ✅ | ✅ |
Credit: How to write ML papers by Neel Nanda
You are chatbot that gives constructive analysis of the following work. Specifically, you care about the following criteria:
## Core Narrative Quality
- **Clear Claims**: Contains 1-3 specific, concrete claims that fit within a cohesive theme
- **Strong Motivation**: Clearly explains why readers should care ("so what?")
Benchmark is from an AI Cloud Rig: | |
https://cloud.vast.ai/?ref_id=127244 | |
hashcat (v6.2.6-851-g6716447df) starting in benchmark mode | |
CUDA API (CUDA 12.8) | |
==================== | |
* Device #1: NVIDIA GeForce RTX 5090, 31610/32120 MB, 170MCU | |
* Device #2: NVIDIA GeForce RTX 5090, 31610/32120 MB, 170MCU | |
* Device #3: NVIDIA GeForce RTX 5090, 31610/32120 MB, 170MCU |
import json | |
import random | |
import mlx.optimizers as optim | |
import mlx.core as mx | |
import mlx.nn as nn | |
import numpy as np | |
from tqdm import tqdm | |
import time | |
from datetime import datetime |
Disclaimer: I'm in the Top 1% of StackOverflow contributors with 23,315 rep points.
I asked 1 high-quality question in 2024, and it was closed almost immediately, and I haven't engaged with the site since.
If someone with 20,000+ karma has their nicely-formatted questions closed so quickly, what must the newbies and rank-in-file encounter? This is probably a big reason why it's declining.
Good question! I am collecting human data on how quantization affects outputs. See here for more information: ggml-org/llama.cpp#5962
In the meantime, use the largest that fully fits in your GPU. If you can comfortably fit Q4_K_S, try using a model with more parameters.
See the wiki upstream: https://github.com/ggerganov/llama.cpp/wiki/Feature-matrix
Model | Average | AGIEval | GPT4All | TruthfulQA | Bigbench |
---|---|---|---|---|---|
mlabonne/OmniTruthyBeagle-7B-v0 📄 | 57.8 | 45.72 | 77.49 | 76.16 | 50.18 |
mlabonne/NeuralOmniBeagle-7B-v2 📄 | 57.75 | 45.86 | 77.31 | 75.34 | 50.09 |
mlabonne/OmniBeagle-7B 📄 | 57.72 | 45.64 | 77.48 | 75.03 | 50.03 |
mlabonne/NeuralOmniBeagle-7B 📄 | 57.71 | 45.85 | 77.26 | 76.06 | 50.03 |
mlabonne/NeuralOmni-7B [📄](https://gist.github.com/mlabonne/4b5ecee86d0fd3714ba0cbd |
@echo off | |
setlocal enabledelayedexpansion | |
rem | Lines beginning with 'rem' are comments | |
rem ------------------------------------------------------------------------------------------- | |
rem | "Icon Upscaler" Script by ThioJoe: https://github.com/ThioJoe | |
rem | I created this script specifically for upscaling very low res (such as 256x256) icons like those in Windows. It uses a combination of Image Magick (to first improve the transparency edges) and the RealCugan-ncnn-vulkan upscaler which seems to perform the best for this use case. Of course, the script can be used for all sorts of images, but I have found this to yield the best results of any other method, and better than just using an upscaler alone. |
// You will function as a JSON api. | |
// The user will feed you valid JSON and you will return valid JSON, do not add any extra characters to the output that would make your output invalid JSON. | |
// The end of this system message will contain a typescript file that exports 5 types: | |
// Prompt - String literal will use double curly braces to denote a variable. | |
// Input - The data the user feeds you must strictly match this type. | |
// Output - The data you return to the user must strictly match this type. | |
// Errors - A union type that you will classify any errors you encounter into. | |
// Tools - If you do not know the answer, Do not make anything up, Use a tool. To use a tool pick one from the Tools union and print a valid json object in that format. | |