Newest at the top
| 2025-03-26 12:03:13 +0100 | <tomsmeding> | shelf? |
| 2025-03-26 12:03:11 +0100 | <tomsmeding> | there is probably a way to write this up properly so that it's publishable, but among us, we've spent enough hours on trying to write it down that we're likely to just shelve it. |
| 2025-03-26 12:02:51 +0100 | <Athas> | Mikolaj is doing almost ten commits per day, so I can't imagine it will be long before it works! |
| 2025-03-26 12:02:25 +0100 | <tomsmeding> | if it worked out just a little bit more, it would work just fine, but as it is, it's complex _and_ has annoying limitations |
| 2025-03-26 12:02:04 +0100 | fp | (~Thunderbi@2001:708:20:1406::1370) fp |
| 2025-03-26 12:01:51 +0100 | <tomsmeding> | horde-ad tries to do quite a bit more than ad-dual, though, and there the tricky bit is that there are lots of parts where the algorithm has unfortunate limitations |
| 2025-03-26 12:01:19 +0100 | alfiee | (~alfiee@user/alfiee) alfiee |
| 2025-03-26 12:01:11 +0100 | <tomsmeding> | I'm not sure that's a paper. |
| 2025-03-26 12:01:04 +0100 | <tomsmeding> | number goes down as in what my ad-dual hack does is compelling as in: it's much faster than something that's very crap compared to the state of the art |
| 2025-03-26 12:00:41 +0100 | xff0x | (~xff0x@2405:6580:b080:900:6185:acb4:363b:5fd3) |
| 2025-03-26 12:00:32 +0100 | <Athas> | "Number goes down" is not compelling? Or is it the actual explanation that is difficult to get right? |
| 2025-03-26 12:00:30 +0100 | <tomsmeding> | the possibility exists that it will just be a library and a "here's some text" on arXiv |
| 2025-03-26 12:00:01 +0100 | <tomsmeding> | we're tried to write it up, and we have some kind of write-up, in fact, but we've been struggling to find a presentation that is compelling enough for a successful publication |
| 2025-03-26 11:58:57 +0100 | <tomsmeding> | the point of horde-ad is that it's an extension to that |
| 2025-03-26 11:58:51 +0100 | <tomsmeding> | yes, indeed |
| 2025-03-26 11:58:49 +0100 | <tomsmeding> | oh, it is, at some point -- but that paper essentially just describes 'ad' |
| 2025-03-26 11:58:45 +0100 | <Athas> | But then that paper says that it's really just a different exposition of how 'ad' works, so who knows. |
| 2025-03-26 11:58:33 +0100 | <Athas> | The horde-ad README says it's based on "Provably Correct, Asymptotically Efficient, Higher-Order Reverse-Mode Automatic Differentiation"! |
| 2025-03-26 11:58:08 +0100 | <tomsmeding> | horde-ad is based on unpublished stuff :P |
| 2025-03-26 11:57:55 +0100 | <tomsmeding> | Athas: what paper? |
| 2025-03-26 11:57:42 +0100 | merijn | (~merijn@77.242.116.146) merijn |
| 2025-03-26 11:57:14 +0100 | <Athas> | tomsmeding: so when will horde-ad be ready? I have (re?)-read the paper and now I am excited. |
| 2025-03-26 11:57:03 +0100 | merijn | (~merijn@77.242.116.146) (Ping timeout: 246 seconds) |
| 2025-03-26 11:56:21 +0100 | dhil | (~dhil@2a0c:b381:52e:3600:79cd:9b5b:3ea2:beda) dhil |
| 2025-03-26 11:49:53 +0100 | hattckory | (~hattckory@bras-base-toroon4524w-grc-30-70-27-118-207.dsl.bell.ca) (Ping timeout: 248 seconds) |
| 2025-03-26 11:48:49 +0100 | coldtom8 | (~coldtom@coldrick.cc) () |
| 2025-03-26 11:48:15 +0100 | coldtom8 | (~coldtom@coldrick.cc) coldtom |
| 2025-03-26 11:46:20 +0100 | ash3en | (~Thunderbi@149.222.157.169) (Remote host closed the connection) |
| 2025-03-26 11:45:40 +0100 | hattckory | (~hattckory@bras-base-toroon4524w-grc-30-70-27-118-207.dsl.bell.ca) |
| 2025-03-26 11:42:22 +0100 | ash3en | (~Thunderbi@149.222.157.169) ash3en |
| 2025-03-26 11:39:44 +0100 | ash3en | (~Thunderbi@149.222.157.169) (Quit: ash3en) |
| 2025-03-26 11:37:04 +0100 | merijn | (~merijn@77.242.116.146) merijn |
| 2025-03-26 11:33:45 +0100 | bitdex | (~bitdex@gateway/tor-sasl/bitdex) bitdex |
| 2025-03-26 11:33:33 +0100 | hattckory | (~hattckory@bras-base-toroon4524w-grc-30-70-27-118-207.dsl.bell.ca) (Ping timeout: 276 seconds) |
| 2025-03-26 11:33:24 +0100 | bitdex_ | (~bitdex@gateway/tor-sasl/bitdex) (Remote host closed the connection) |
| 2025-03-26 11:30:23 +0100 | merijn | (~merijn@77.242.116.146) (Ping timeout: 268 seconds) |
| 2025-03-26 11:23:30 +0100 | hattckory | (~hattckory@bras-base-toroon4524w-grc-30-70-27-118-207.dsl.bell.ca) |
| 2025-03-26 11:20:44 +0100 | alfiee | (~alfiee@user/alfiee) (Ping timeout: 272 seconds) |
| 2025-03-26 11:16:15 +0100 | alfiee | (~alfiee@user/alfiee) alfiee |
| 2025-03-26 11:06:48 +0100 | orslon^ | (dehsou@c-71-199-187-173.hsd1.ga.comcast.net) (Ping timeout: 272 seconds) |
| 2025-03-26 11:05:53 +0100 | merijn | (~merijn@77.242.116.146) merijn |
| 2025-03-26 11:05:37 +0100 | dsrt^ | (dsrt@c-71-199-187-173.hsd1.ga.comcast.net) (Ping timeout: 252 seconds) |
| 2025-03-26 11:04:09 +0100 | merijn | (~merijn@77.242.116.146) (Ping timeout: 252 seconds) |
| 2025-03-26 10:53:48 +0100 | lortabac | (~lortabac@2a01:e0a:541:b8f0:55ab:e185:7f81:54a4) (Quit: WeeChat 4.5.2) |
| 2025-03-26 10:51:49 +0100 | hattckory | (~hattckory@70.27.118.207) (Ping timeout: 260 seconds) |
| 2025-03-26 10:46:54 +0100 | hattckory | (~hattckory@70.27.118.207) |
| 2025-03-26 10:40:14 +0100 | pavonia | (~user@user/siracusa) (Quit: Bye!) |
| 2025-03-26 10:39:30 +0100 | sprotte24 | (~sprotte24@p200300d16f097d0088a61901ba3f264c.dip0.t-ipconnect.de) |
| 2025-03-26 10:39:14 +0100 | sprotte24 | (~sprotte24@p200300d16f097d0088a61901ba3f264c.dip0.t-ipconnect.de) (Read error: Connection reset by peer) |
| 2025-03-26 10:36:35 +0100 | __monty__ | (~toonn@user/toonn) toonn |