Newest at the top
| 2024-05-21 08:01:56 +0200 | tromp | (~textual@92-110-219-57.cable.dynamic.v4.ziggo.nl) |
| 2024-05-21 08:00:39 +0200 | <vladl> | Also because my particular use case ultimately does need to synchonize layer-by-layer for other reasons (memory allocation strategy) so I may as well |
| 2024-05-21 07:59:11 +0200 | <vladl> | That's true but I'm relaxing my focus to the layer scale in hopes of making it easier for me to reason about |
| 2024-05-21 07:58:13 +0200 | <probie> | I don't see what requires you to synchronize layer-by-layer. A subpixel merely requires its neighbours at the previous resolution to have been computed, not the entire previous layer |
| 2024-05-21 07:57:40 +0200 | <vladl> | Yes I think I see a comonad in there too, but its also split. Like, lets suppose a 1D array of pixels p with neighborhoods w, so something like [w p]. We have a (w p -> p), but in order to extend and get a (w p) out, we have to step all the way out of the [] in order to propagate neighbor values. So we can go [p] -> [w p], but that [] prevents me from making it a proper comonad. |
| 2024-05-21 07:57:35 +0200 | peterbecich | (~Thunderbi@syn-047-229-123-186.res.spectrum.com) (Ping timeout: 264 seconds) |
| 2024-05-21 07:54:55 +0200 | johnw | (~johnw@69.62.242.138) |
| 2024-05-21 07:53:39 +0200 | <vladl> | At a given resolution j, before interpolating the subpixels at resolution j+1, the neighboring (sub)pixels at resolution j have to have been computed. So we need to sync layer-by-layer. Synchronization like a fence or a barrier. |
| 2024-05-21 07:53:11 +0200 | geekosaur | is thinking this sounds more like a comonad |
| 2024-05-21 07:50:40 +0200 | <probie> | I don't quite understand what you mean by "synchronization" here |
| 2024-05-21 07:45:55 +0200 | demon-cat | (~demon-cat@dund-15-b2-v4wan-169642-cust1347.vm6.cable.virginm.net) (Ping timeout: 268 seconds) |
| 2024-05-21 07:41:35 +0200 | <vladl> | can't really find much on it, which could definitely be a skill issue. I read "Fantastic Morphisms and where to find them" but none of these really fit the bill. There's a problem on tree nexuses in Richard Bird's Pearls of Functional Algorithm design that I went through that, again, seemed very close to what I wanted but I couldn't make the pieces fit. |
| 2024-05-21 07:41:29 +0200 | <vladl> | What patterns are present in a recursion scheme that requires synchronization? For example, recursively interpolating subpixels in an image, where the interpolation step requires the parent pixel neighborhood? The subpixels get folded back into the original resolution, so this is almost a hylomorphism, except the coalgebra gets "split" over the synchronization step. This seems like a common pattern but I |
| 2024-05-21 07:40:59 +0200 | demon-cat | (~demon-cat@dund-15-b2-v4wan-169642-cust1347.vm6.cable.virginm.net) |
| 2024-05-21 07:38:50 +0200 | peterbecich | (~Thunderbi@syn-047-229-123-186.res.spectrum.com) |
| 2024-05-21 07:37:18 +0200 | johnw_ | (~johnw@69.62.242.138) (Quit: ZNC - http://znc.in) |
| 2024-05-21 07:30:42 +0200 | vladl | (~vladl@24.35.90.183) |
| 2024-05-21 07:30:07 +0200 | Sgeo | (~Sgeo@user/sgeo) (Read error: Connection reset by peer) |
| 2024-05-21 07:27:43 +0200 | y04nn | (~username@2a03:1b20:8:f011::e10d) |
| 2024-05-21 07:20:52 +0200 | peterbecich | (~Thunderbi@syn-047-229-123-186.res.spectrum.com) (Ping timeout: 260 seconds) |
| 2024-05-21 07:18:08 +0200 | zetef | (~quassel@5.2.182.99) |
| 2024-05-21 07:17:01 +0200 | takuan | (~takuan@178-116-218-225.access.telenet.be) |
| 2024-05-21 06:46:50 +0200 | peterbecich | (~Thunderbi@syn-047-229-123-186.res.spectrum.com) |
| 2024-05-21 06:37:54 +0200 | michalz | (~michalz@185.246.207.221) |
| 2024-05-21 06:35:05 +0200 | michalz | (~michalz@185.246.207.203) (Client Quit) |
| 2024-05-21 06:34:50 +0200 | michalz | (~michalz@185.246.207.203) |
| 2024-05-21 06:26:36 +0200 | agent314 | (~quassel@162.219.176.19) |
| 2024-05-21 06:26:23 +0200 | agent314 | (~quassel@104.129.57.116) (Ping timeout: 264 seconds) |
| 2024-05-21 06:00:35 +0200 | demon-cat | (~demon-cat@dund-15-b2-v4wan-169642-cust1347.vm6.cable.virginm.net) (Ping timeout: 264 seconds) |
| 2024-05-21 05:56:02 +0200 | demon-cat | (~demon-cat@dund-15-b2-v4wan-169642-cust1347.vm6.cable.virginm.net) |
| 2024-05-21 05:52:55 +0200 | justsomeguy | (~justsomeg@user/justsomeguy) (Quit: WeeChat 3.6) |
| 2024-05-21 05:49:24 +0200 | peterbecich | (~Thunderbi@syn-047-229-123-186.res.spectrum.com) (Ping timeout: 260 seconds) |
| 2024-05-21 05:42:48 +0200 | peterbecich | (~Thunderbi@syn-047-229-123-186.res.spectrum.com) |
| 2024-05-21 05:28:38 +0200 | aforemny | (~aforemny@2001:9e8:6cca:4800:37b5:fb76:9e3f:6a26) |
| 2024-05-21 05:28:11 +0200 | aforemny_ | (~aforemny@i59F516F9.versanet.de) (Ping timeout: 264 seconds) |
| 2024-05-21 05:17:17 +0200 | yin | (~yin@user/zero) (Ping timeout: 240 seconds) |
| 2024-05-21 05:11:23 +0200 | raehik | (~raehik@rdng-25-b2-v4wan-169990-cust1344.vm39.cable.virginm.net) (Ping timeout: 264 seconds) |
| 2024-05-21 05:06:52 +0200 | Midjak | (~MarciZ@82.66.147.146) (Quit: This computer has gone to sleep) |
| 2024-05-21 04:50:46 +0200 | joeyadams | (~joeyadams@2603:6010:5100:2ed:64b6:9e88:7ce7:a120) |
| 2024-05-21 04:44:59 +0200 | demon-cat | (~demon-cat@dund-15-b2-v4wan-169642-cust1347.vm6.cable.virginm.net) (Ping timeout: 252 seconds) |
| 2024-05-21 04:41:37 +0200 | justsomeguy | (~justsomeg@user/justsomeguy) |
| 2024-05-21 04:41:23 +0200 | justsomeguy | (~justsomeg@user/justsomeguy) (Quit: WeeChat 3.6) |
| 2024-05-21 04:40:45 +0200 | demon-cat | (~demon-cat@dund-15-b2-v4wan-169642-cust1347.vm6.cable.virginm.net) |
| 2024-05-21 04:15:35 +0200 | machinedgod | (~machinedg@d173-183-246-216.abhsia.telus.net) (Ping timeout: 264 seconds) |
| 2024-05-21 04:15:07 +0200 | agent314 | (~quassel@104.129.57.116) |
| 2024-05-21 04:14:11 +0200 | xff0x | (~xff0x@125x103x176x34.ap125.ftth.ucom.ne.jp) |
| 2024-05-21 04:14:05 +0200 | agent314 | (~quassel@184.75.215.3) (Ping timeout: 240 seconds) |
| 2024-05-21 04:07:44 +0200 | td_ | (~td@i5387090E.versanet.de) |
| 2024-05-21 04:05:59 +0200 | td_ | (~td@i53870921.versanet.de) (Ping timeout: 264 seconds) |
| 2024-05-21 04:02:56 +0200 | otto_s | (~user@p5de2f060.dip0.t-ipconnect.de) |