From a7e56af1e560809a764f52b96bf01853b7ffd84d Mon Sep 17 00:00:00 2001 From: Nick Dumas Date: Fri, 6 Sep 2024 11:08:50 -0400 Subject: [PATCH] typo fixes --- config/_default/params.toml | 6 +++--- content/posts/golang-quantize/index.md | 2 +- content/posts/prom-primer/index.md | 2 +- 3 files changed, 5 insertions(+), 5 deletions(-) diff --git a/config/_default/params.toml b/config/_default/params.toml index 503e124..1901c26 100644 --- a/config/_default/params.toml +++ b/config/_default/params.toml @@ -149,6 +149,6 @@ smartTOC = true # yandex = "" [AnalyticsURL] - "https://ndumas.com" = "blog.ndumas.com" - "https://drafts.ndumas.com" = "drafts.blog.ndumas.com" - "https://dev.ndumas.com" = "dev.blog.ndumas.com" + "https://ndumas.com" = "ndumas.com" + "https://drafts.ndumas.com" = "drafts.ndumas.com" + "https://dev.ndumas.com" = "dev.ndumas.com" diff --git a/content/posts/golang-quantize/index.md b/content/posts/golang-quantize/index.md index b3ee554..d93ab80 100644 --- a/content/posts/golang-quantize/index.md +++ b/content/posts/golang-quantize/index.md @@ -26,7 +26,7 @@ My use case is a little less straightforward. The OpenSimplex implementation I'm [1.9052595476929043e-65 0.23584641815494023 -0.15725758120580122 -0.16181229773462788 -0.2109552918614408 -0.24547524871149487 0.4641016420951697 0.08090614886731387 -0.3720484238283594 -0.5035758520116665 -0.14958647968356706 -0.22653721682847863 0.4359742698469777 -0.6589156578369094 -1.1984697154842467e-66 0.2524271844660192 -0.3132366454912306 -0.38147748611610527 5.131908781688952e-66 0.3814774861161053 0.07543249830197025 0.513284589875744 -1.4965506447200717e-65 0.031883015701786095 0.392504694554317] ``` -As you can see, there are some reasonably comprehensible values, like `-0.50357585`, `-0.222`, `0.075432`, but there's also values like `-1.1984697154842467e-66` and `1.9052595476929043e-65`. Mathematically, these values end up being continous and suitable for generating a noisemap but for a human being doing development work and examining raw data, it's almost impossible to have any intuitive grasp of the numbers I'm seeing. Furthermore, when I pass these values to a visualization tool or serialize them to a storage format, I want them to be meaningful and contextually "sane". The noisemap values describe the absolute height of terrain at a given (X,Y) coordinate pair. If we assume that terrain hight is measured in meters, a world whose total height ranges between -1 meter and 1 meter isn't very sensible. A good visualization tool can accomodate this data, but it's not good enough for my purposes. +As you can see, there are some reasonably comprehensible values, like `-0.50357585`, `-0.222`, `0.075432`, but there's also values like `-1.1984697154842467e-66` and `1.9052595476929043e-65`. Mathematically, these values end up being continuous and suitable for generating a noisemap but for a human being doing development work and examining raw data, it's almost impossible to have any intuitive grasp of the numbers I'm seeing. Furthermore, when I pass these values to a visualization tool or serialize them to a storage format, I want them to be meaningful and contextually "sane". The noisemap values describe the absolute height of terrain at a given (X,Y) coordinate pair. If we assume that terrain height is measured in meters, a world whose total height ranges between -1 meter and 1 meter isn't very sensible. A good visualization tool can accomadate this data, but it's not good enough for my purposes. To that end, I'm working on implementing a quantization function to scale the [-1,1] float values to arbitrary user defined output spaces. For example, a user might desire a world with very deep oceans, but relatively short mountain features. They should be able to request from the map generator a range of [-7500, 1000], and Quantize() should evenly distribute inputs between those desired outputs. diff --git a/content/posts/prom-primer/index.md b/content/posts/prom-primer/index.md index c32f971..3fa24e0 100644 --- a/content/posts/prom-primer/index.md +++ b/content/posts/prom-primer/index.md @@ -37,7 +37,7 @@ This query looks at the metric `http_request_duration_microseconds`, buckets it ## Labels -Prometheus lets you apply labels to your metrics. Some are specificed in the scrape configurations; these are usually things like the hostname of the machine, its datacenter or geographic region, etc. Instrumented applications can also specify labels when generating metrics; these are used to indicate things known at runtime like the specific HTTP route ( e.g. `/blog` or `/images/kittens` ) being measured. +Prometheus lets you apply labels to your metrics. Some are specified in the scrape configurations; these are usually things like the hostname of the machine, its datacenter or geographic region, etc. Instrumented applications can also specify labels when generating metrics; these are used to indicate things known at runtime like the specific HTTP route ( e.g. `/blog` or `/images/kittens` ) being measured. Prometheus queries allow you to specify labels to match against which will let you control how your data is grouped together; you can query against geographic regions, specific hostnames, etc. It also supports regular expressions so you can match against patterns instead of literal strict matches.