Advertisement
Guest User

Untitled

a guest
Mar 22nd, 2017
135
0
Never
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 22.66 KB | None | 0 0
  1. <Deedlit> hey Kthulhu koteitan
  2. <Kthulhu> Hey, Deedlit
  3. <Kthulhu> I wanted to ask you a few questions about FOFT
  4. <Kthulhu> is that alright?
  5. <Deedlit> sure!
  6. <Kthulhu> so from what I understood, 0-functionals are ordinals, right?
  7. <Deedlit> yes
  8. <Kthulhu> then how are 1-functionals comparable to oodinals? Are they the same, "bigger", "smaller"?
  9. <Deedlit> they are a different thing than oodinals
  10. <Kthulhu> I know
  11. <Kthulhu> wait
  12. <Kthulhu> one second
  13. * koteitan_mobile (~AndChat20@p896078-ipngn200610sizuokaden.shizuoka.ocn.ne.jp) has joined
  14. <Kthulhu> so do you mind explaining it to me?
  15. <Kthulhu> I'm afraid I don't really understand your blog post on the subject
  16. <Kthulhu> I tried to do so, but I lack the complete background
  17. <Deedlit> okay
  18. <Deedlit> so first, do you understand FOOT?
  19. <Kthulhu> yes
  20. <Kthulhu> more or less
  21. <Deedlit> so the idea there is that with FOOT we can describe these large ordinals
  22. <Deedlit> and these ordinals allow us to have more expressive power
  23. * koteitan_mobile2 has quit (Ping timeout: 252 seconds)
  24. <Deedlit> for example, the first big ordinal that FOOT talks about is what we call Ord
  25. <Deedlit> and it is the smallest ordinal such that V and V_Ord satisfy the same sentences of FOST
  26. <Deedlit> and since we can quantify over V_Ord, we can basically quantify over V in a sense
  27. <Deedlit> so for example we can define a truth predicate over V_Ord (which mirrors a truth predicate for V)
  28. <Deedlit> so now we have this stronger language FOST + Ord
  29. * koteitan (~koteitan@p896078-ipngn200610sizuokaden.shizuoka.ocn.ne.jp) has joined
  30. <Deedlit> and now we would like to quantify over this stronger language to obtain an even stronger language
  31. <Deedlit> and so we define Ord_2 to be the smallest ordinal such that V and V_{Ord_2} satisfy the same sentences in FOST + Ord
  32. <Kthulhu> one second
  33. <Deedlit> and so now in the language FOST + Ord_2 we can quantify over V_Ord_2, so we can define a truth predicate for FOST + Ord for example
  34. <Kthulhu> are you familiar with my norminals thing?
  35. <Deedlit> it's been a while
  36. <koteitan> (I am also listening your explanation)
  37. <Kthulhu> well, I think it may be better for the both of us if we simply compare FOFT to some norminal
  38. <Kthulhu> it's a much simpler system
  39. <Kthulhu> so as it stands
  40. <Kthulhu> FOST is equivalent to 1, when treated as a norminal
  41. <Kthulhu> SOST is equivalent to 2,
  42. <Kthulhu> aOST is equivalent to <1>
  43. <Kthulhu> FOOT is equivalent to <0,1>
  44. <Deedlit> looking at it now
  45. <Kthulhu> which is otherwise notated <0<0>1>
  46. <Kthulhu> this is where it's all present: https://sites.google.com/view/norminals/home
  47. <Deedlit> I disagree that it's a much simpler system
  48. <Kthulhu> really? hmm; maybe it's just a matter of familiarity
  49. <Deedlit> it's more vague, but if you interpret it so that it works out like FOOT then it's the same thing really
  50. <Kthulhu> it's really the same thing, but it goes onwards from there
  51. <Kthulhu> so we've agreed that FOOT is equivalent to <0<0>1>
  52. * koteitan has quit (Read error: Connection reset by peer)
  53. * koteitan_mobile has quit (Read error: Connection reset by peer)
  54. <Kthulhu> where do you think FOFT would land?
  55. * koteitan_mobile (~AndChat20@p896078-ipngn200610sizuokaden.shizuoka.ocn.ne.jp) has joined
  56. <Deedlit> to be as strong as FOFT, you would have to extend your notation very far
  57. * koteitan (~koteitan@p896078-ipngn200610sizuokaden.shizuoka.ocn.ne.jp) has joined
  58. <Deedlit> the strength of higher-order functionals is quite impressive
  59. <Kthulhu> still
  60. <Kthulhu> how do you think certain individual functionals compare?
  61. <Deedlit> Func^0_alpha is along the lines of your <alpha>
  62. <Kthulhu> I'd agree
  63. <Kthulhu> given that Func^1_0 is like FOOT
  64. <Kthulhu> from what I've read
  65. <Kthulhu> would Func^1_a be like <a<0>1>, then?
  66. <Deedlit> No, I think Func^1_a(b) would be like <b<0>a>
  67. <Deedlit> then things really get going at Func^2
  68. <Kthulhu> so Func^0_a(b) would be like <a>
  69. <Kthulhu> so Func^1_a(b) would be like <b<0>a>
  70. <Deedlit> I think so
  71. <Kthulhu> well, how does b come into play with the case of Func^0_a(b)?
  72. <Kthulhu> if it's equivalent to <a>
  73. <Deedlit> Func^0_a is just an ordinal
  74. <Deedlit> so there is no parameter
  75. <Kthulhu> oh, right
  76. <Deedlit> Func^1_a is a 1-functional, so it takes an ordinal to an ordinal
  77. <Kthulhu> so Func^2_a(b) would be like...
  78. <Kthulhu> <b<0>0<0>a>?
  79. <Deedlit> nah, it would be a lot more powerful than that
  80. <Kthulhu> then tell me
  81. <Deedlit> Func^2_a takes a 1-functional to a 1-functional
  82. <Deedlit> so for any function on ordinals, you get back a function on ordinals
  83. <Kthulhu> hmm
  84. <Kthulhu> (thinking)
  85. <Deedlit> I would have to really analyze how far FOFT^2 goes, but I don't think that you can easily match it with a simple array notation
  86. <Kthulhu> do consider what happens with the stronger norminals
  87. <Kthulhu> even within the first mural, I am quite certain it can be contained within the norminals present there
  88. <Kthulhu> I'll just give you a reminder
  89. <Kthulhu> or to be precise, an explanation
  90. <Kthulhu> SOST predicates over the truth of FOST, correct?
  91. <Deedlit> SOST is stronger than that
  92. <Kthulhu> hold on
  93. <Kthulhu> right
  94. <Kthulhu> my bad
  95. <Kthulhu> I was getting confused between FOST+T and SOST
  96. <Kthulhu> well
  97. <Kthulhu> would saying "SOST predicates over the truth of the variables over which FOST predicates" be more precise?
  98. <Deedlit> SOST quantifies over predicates of sets
  99. <Deedlit> FOST quantifies over sets
  100. <Kthulhu> yes
  101. <Kthulhu> that's (more or less) what I meant
  102. <Kthulhu> so N1 quantifies over sets
  103. <Kthulhu> N2 quantifies over predicates of sets
  104. <Kthulhu> N3 quantifies over predicates of those predicates
  105. <Kthulhu> similarly, N<1> quantifies over these hierarchies of predication, for any ordinal
  106. <Deedlit> I wonder, can you extend higher-order set theory to infinite ordinals?
  107. <Kthulhu> "infinite"?
  108. <Kthulhu> do you mean "transfinite"?
  109. <Deedlit> same thing
  110. <Kthulhu> no, it's not the same thing
  111. <Deedlit> ?
  112. <Kthulhu> infinite is "the greatest", it's ill-defined
  113. <Deedlit> no, infinite just means not finite
  114. <Kthulhu> that's transfinite
  115. <Kthulhu> whatever
  116. <Deedlit> no, we use infinite all the time
  117. <Kthulhu> semantics
  118. <Kthulhu> semantics
  119. <Kthulhu> semantics
  120. <Kthulhu> to answer your question, then
  121. <Kthulhu> you can
  122. <Kthulhu> and I did
  123. <Deedlit> I think I would like outside corroboration on this
  124. <Deedlit> I'll ask Wojowu when he comes around
  125. <Kthulhu> I mean
  126. <Kthulhu> he did too
  127. <Deedlit> no, he didn't
  128. <Kthulhu> higher order set theory with transfinite ordinals is Na, for some transfinite a
  129. <Kthulhu> isn't it?
  130. <Deedlit> but does it make sense?
  131. <Kthulhu> it does
  132. <Deedlit> what does it mean to have an infinite chain of "predicate of predicate of predicate of..."
  133. <Kthulhu> I'll explain
  134. <Kthulhu> let's start with omega
  135. <Kthulhu> in Nw, we can specify, within the language
  136. <Kthulhu> which finite ordinal we use to create the chain
  137. <Kthulhu> for example, we can have an expression in the language that says "predicate of predicate of predicate of..." twelve googol times
  138. <Kthulhu> similarly, we can do the same with larger ordinals
  139. <Kthulhu> did you understand?
  140. <Deedlit> oh, we can certainly do that
  141. <Deedlit> basically you are diagonalizing over N -> Nth order set theory
  142. <Kthulhu> yup!
  143. <Kthulhu> that's what <1> does, only to all norminals
  144. <Kthulhu> I'm starting to feel that FOFT^1 is lower on the scale than we both thought
  145. <Kthulhu> *all ordinals
  146. <Deedlit> FOFT intentionally avoids higher order set theory
  147. <Deedlit> to put it on better philosophical ground
  148. <Kthulhu> well, then I'm not sure why it's so strong
  149. <Kthulhu> shouldn't SOST be stronger than FOFT, if it builds off something weaker?
  150. <Kthulhu> as in, FOFT
  151. <Deedlit> SOST is stronger than FOFT
  152. <Kthulhu> oh, right
  153. <Kthulhu> well, then,---
  154. <Kthulhu> N2 would be stronger than anything FOFT related
  155. <Kthulhu> if it was better-defined
  156. <Kthulhu> as SOST is kind of- well -sick
  157. <Deedlit> sure, if you believe in the absolute truth of Nth-order set theory
  158. <Kthulhu> I don't take things for granted
  159. <Kthulhu> if nobody has yet properly defined it, it's ill-defined
  160. <Kthulhu> I'm not asking for a formal proof
  161. <Deedlit> then you can define Rayo_n(m) to be "the smallest number greater than all numbers definable in nth order set theory using at most m symbols"
  162. <Kthulhu> *definition
  163. <Kthulhu> yes, but is "nth order set theory" well defined?
  164. <Kthulhu> that's the crux
  165. <Kthulhu> here's a thought!
  166. <Kthulhu> if you sneeze N_<<1>>^10(10^100) times,
  167. <Kthulhu> this video will eventually be created: https://www.youtube.com/watch?v=cB_AnteqNJ0
  168. <Deedlit> ha
  169. <Kthulhu> but on another similar subject
  170. <Kthulhu> how do you think FOFT and little bigeddon compare?
  171. <Deedlit> Emlightened's language is equivalent to FOFT^1_1
  172. <Kthulhu> hmm
  173. <Kthulhu> it's not much greater than FOOT
  174. <Kthulhu> we've agreed that (if norminals were to use the FOST+T thing instead of SOST), Func^1_a would be equivalent to <0<0>a>
  175. <Kthulhu> and that Func^0_a would be to <a>
  176. <Kthulhu> right?
  177. <Deedlit> assuming <a<0>b> is defined how I am thinking, yes
  178. <Kthulhu> and how do you think it's defined?
  179. <Deedlit> well, I would use the language I used before with FOOT
  180. <Deedlit> that you didn't like all that much
  181. <Kthulhu> describe it in terms of other norminals
  182. <Kthulhu> that's how it's actually defined
  183. <Deedlit> <a+1<0>b> would be the smallest ordinal such that V and V_<a+1<0>b> satisfied the same sentences of V + <a<0>b>
  184. <Kthulhu> yes
  185. <Kthulhu> but I'm talking about <0<0>a>
  186. <Kthulhu> do you understand how <0<0>a+1> is defined?
  187. <Deedlit> and <0<0>a+1> would be the smallest ordinal such that V and V_<0<0>a+1> satisfied the same sentences of V + the function b -> <b<0>a>
  188. <Kthulhu> pretty sure that's right
  189. <Kthulhu> to put it in my words,
  190. <Kthulhu> <0<0>1> is the limit of all <a>
  191. <Kthulhu> <0<0>a> is the limit of all <c<0>b>, where b < a
  192. <Kthulhu> <b+1<0>a> is the limit of all <b<0>a>
  193. <Kthulhu> so yes
  194. <Deedlit> it's not clear to me what that means
  195. <Kthulhu> read in my site, under the section dedicated to explaining what "limit" means
  196. <Deedlit> I have to say, your definitions are quite vague
  197. <Kthulhu> yes, I know they might be slightly vague
  198. <Kthulhu> that's because my knowledge is rusty
  199. <Kthulhu> still
  200. <Kthulhu> one can understand what they mean
  201. <Deedlit> it's somewhat hard to pin down actually
  202. <Deedlit> for example, something like <0<0>1>_1 "which would be the limit of all well-ordered array norminals (similarly to how omega_1 functions)"
  203. <Kthulhu> what's the problem? I could explain
  204. <Deedlit> what exactly are the well-ordered array norminals?
  205. <Kthulhu> oh
  206. <Kthulhu> right, I got mixed up again
  207. <Kthulhu> *facepalm*
  208. <Kthulhu> I meant all reorderings, you know
  209. <Kthulhu> wait one second
  210. <Kthulhu> let me find it
  211. <Kthulhu> there
  212. <Kthulhu> tell me if the new definition is any good
  213. <Deedlit> I still don't see what you mean
  214. <Deedlit> what are "all array norminals"
  215. <Kthulhu> is it any better now?
  216. <Kthulhu> the limit of all norminals derived via surjection from <1>
  217. <Deedlit> as far as I can tell, norminals are not derived via surjection from <1>
  218. <Kthulhu> well
  219. <Kthulhu> reordering?
  220. <Kthulhu> something?
  221. <Kthulhu> I'm trying to find the right word
  222. <Kthulhu> you know the definition of omega_1, right?
  223. <Deedlit> yes
  224. <Kthulhu> well
  225. <Deedlit> but I'm not sure how that helps here
  226. <Deedlit> the next cardinal after <1> would not be all that much larger
  227. <Kthulhu> yes, certainly
  228. <Kthulhu> the limit of all norminals derived via some well-defined reordering of entries within the array, perhaps?
  229. <Deedlit> I don't think that works
  230. <Deedlit> if we take the set of arrays of the form <a1<A1>a2<A2>...<An>a(n+1)>, where the Ai are themselves arrays
  231. <Deedlit> reordering entries would stay within the set
  232. <Kthulhu> fine
  233. <Kthulhu> I'll just erase that part
  234. <Kthulhu> I mean, considering it isn't crucial for anything further than itself
  235. <Kthulhu> there
  236. <Kthulhu> done
  237. <Deedlit> it doesn't look like you have any definition of AO[n] though, other than anything in AO[2] is bigger than anything in AO[1]
  238. <Kthulhu> I do, that being:
  239. <Kthulhu> AO[n] is bigger than anything in AO[m], when n > m
  240. <Kthulhu> I do not know, they are the only cost way way of resurrection, I do not know, it is my name and I alea, but if we think your name is Weslie your child, older age I can say that I guess, and my growing tree of growth, I think to me as Lara Lala speaks Adult, my name is Maria, whatever I am 3 is simply buried I can not do planting the seeds, it is big in size, I will say what I want, mega oom where - white hair, but it shows tree
  241. <Kthulhu> oh, whoops
  242. <Kthulhu> wrong IRC
  243. <Deedlit> that's not a definition
  244. <Deedlit> AO[n] could be anything
  245. <Deedlit> like, AO[n] = {n}
  246. <Kthulhu> AO[n] isn't an individual norminal
  247. <Kthulhu> read
  248. <Kthulhu> the class-ordinary of AO[n] is, however
  249. <Kthulhu> and that is defined as the smallest norminal in AO[n] that is bigger than anything in AO[m], when n > m
  250. <Deedlit> but you haven't defined what AO[n] is
  251. <Deedlit> just being bigger than the last one isn't even close to a unique description
  252. <Kthulhu> it's a category of norminals
  253. <Kthulhu> I don't see what else I have to add
  254. <Deedlit> saying what it is would be a good start
  255. <Deedlit> let's say I tell you this
  256. <Deedlit> A_1 is a set of numbers
  257. <Deedlit> A_2 is a set of numbers, all of which are bigger than the numbers in A_1
  258. <Deedlit> okay, no I have defined A_1 and A_2
  259. <Deedlit> *now
  260. <Kthulhu> I already said what it is, on the site, I just don't remember to quote the whole thing in one go
  261. <Deedlit> I've read your site, it's not there
  262. <Kthulhu> "Introducing AO[2], a new type of norminal variable identical to AO[1], only that we specify two things: One, all AO[2] are larger than all AO[1]; and two, they are within a different category than AO[1]. This, inevitably, allows us to create languages so useful, hence functions so powerful, and hence numbers so large that the mind cannot even begin to conceive of them."
  263. <Kthulhu> oh whoops
  264. <Kthulhu> meant to quote less
  265. <Kthulhu> "Introducing AO[2], a new type of norminal variable identical to AO[1], only that we specify two things: One, all AO[2] are larger than all AO[1]; and two, they are within a different category than AO[1]."
  266. <Kthulhu> here I state what they are
  267. <Kthulhu> "Note that these aren't individual norminals, but rather categories of norminals."
  268. <Deedlit> that's just like the A_1 and A_2 I defined above
  269. <Kthulhu> right
  270. <Deedlit> can you tell me what numbers are in my A_1?
  271. <Kthulhu> which is already there, great
  272. <Kthulhu> hmm
  273. <Kthulhu> A_1 is AO[1], right?
  274. <Deedlit> nope
  275. <Kthulhu> then what is it?
  276. <Deedlit> I've told you
  277. <Kthulhu> right
  278. <Kthulhu> I see
  279. <Deedlit> each A_n consists of numbers bigger than the previous numbers
  280. * koteitan_mobile has quit (Read error: Connection reset by peer)
  281. * koteitan has quit (Read error: Connection reset by peer)
  282. <Kthulhu> you see, with AO[n], we start with the class-ordinary of the category, then begin to build new norminals off it using the system already explained
  283. <Kthulhu> a new class-ordinary is then defined, AO[n+1], as greater than anything in the previous category
  284. * koteitan (~koteitan@p896078-ipngn200610sizuokaden.shizuoka.ocn.ne.jp) has joined
  285. <Kthulhu> and the smallest one
  286. <Kthulhu> because n will always be unique,
  287. <Kthulhu> each class is unique
  288. * koteitan_mobile (~AndChat20@p896078-ipngn200610sizuokaden.shizuoka.ocn.ne.jp) has joined
  289. <Kthulhu> and every unique norminal has to be in one unique class
  290. <Kthulhu> that's pretty much it
  291. <Deedlit> how is AO[1] defined exactly?
  292. <Kthulhu> oh
  293. <Kthulhu> as I said
  294. <Kthulhu> it's the category assigned to 1
  295. <Deedlit> and how do you define categories
  296. <Kthulhu> ...a set?
  297. <Deedlit> ...that can be anything
  298. <Kthulhu> categories are classes of norminals, each defined by containing norminals smaller than each lower category
  299. <Deedlit> you can do anything with that
  300. <Deedlit> AO[n] could contain just the nth smallest norminal
  301. <Kthulhu> I honestly don't see what's the problem here, or why we're stalling so much on this detail
  302. <Kthulhu> let me try again
  303. <Kthulhu> categories are classes of norminals, each defined by containing norminals smaller than each lower category, starting with their corresponding class-ordinary
  304. <Kthulhu> *,
  305. <Kthulhu> is that enough?
  306. <Deedlit> nope
  307. <Deedlit> you can fit just about anything into that definition
  308. <Kthulhu> how so?
  309. <Deedlit> just make the next category larger than the previous
  310. <Deedlit> but each category can be whatever you want it to be
  311. <Kthulhu> ...how would you do it, then?
  312. * koteitan_mobile has quit (Read error: Connection reset by peer)
  313. <Deedlit> I'm not sure that you can do what you seem to be trying to do
  314. <Deedlit> it seems like you are trying to make AO[2] surpass all "array notations", or something like that
  315. <Kthulhu> not exactly, but it's close to that
  316. <Deedlit> but "array notation" is too vague and general to do that, I think
  317. <Kthulhu> yes, which is why we have the "limit of" thing
  318. <Deedlit> how does "limit of" solve things?
  319. <Kthulhu> if we take some array notation, then "limit of" it, we get the next diagonalisation, right?
  320. <Deedlit> well, for a specific array notation indexed by n, you can diagonalize over n, yes
  321. <Kthulhu> so we have "limit of" to diagonalise,
  322. <Kthulhu> and the simple successor to expand further
  323. <Kthulhu> given those two things,
  324. <Kthulhu> we can express "any array notation"
  325. * koteitan_mobile (~AndChat20@p896078-ipngn200610sizuokaden.shizuoka.ocn.ne.jp) has joined
  326. <Kthulhu> the next category simply diagonalises over all that
  327. <Deedlit> I think you are confusing things here
  328. <Deedlit> if we have an ordinal, taking limits and successors will take us up through the class of ordinals
  329. <Deedlit> for an array notation, you have to specify exactly what you are doing
  330. <Kthulhu> well
  331. <Kthulhu> I'm starting to get slightly tired of this now
  332. <Deedlit> yeah
  333. <Kthulhu> I'll think about it
  334. <Kthulhu> it's entirely possible that all along,
  335. <Kthulhu> actually, hold on
  336. <Kthulhu> if we specify some variable,
  337. <Kthulhu> that being the variable in AO[a]
  338. <Kthulhu> , what's the problem of just using it?
  339. <Deedlit> just using it for what?
  340. <Kthulhu> to diagonalise over anything with a lower value to that variable
  341. <Deedlit> I'm not sure what you mean
  342. <Deedlit> but you don't want to have arbitrary diagonalization
  343. <Kthulhu> I want to buy ONE yoga
  344. <Kthulhu> oh, shit
  345. <Deedlit> or arbitrary array notations
  346. <Deedlit> lol
  347. <Kthulhu> wrong IRC again
  348. <Kthulhu> lol
  349. <Kthulhu> what's the problem with arbitrary diagonalisation? I'd like to hear the specific reason
  350. <Deedlit> well, it should be easy to define array notations A_n such that "the largest number in A_n using a googol symbols" is at least n
  351. <Deedlit> in which case, if you can access all of those array notations, "the largest number definable in a googol symbols" becomes infinite
  352. <Kthulhu> to be completely honest,
  353. <Kthulhu> I was dodging this fact the whole time
  354. <Kthulhu> I am ashamed of myself
  355. <Deedlit> no need to be
  356. <Kthulhu> oh well, XD
  357. <Kthulhu> guess it's just a matter of definition higher and higher array notations...
  358. <Kthulhu> because it is
  359. <Deedlit> yeah, that seems like what one ultimately winds up doing in this quest for higher numbers
  360. <Kthulhu> which was my point yesterday
  361. <Kthulhu> it "kills" googology
  362. <Kthulhu> no longer whimsical and fun, just diagonals over diagonals
  363. <Deedlit> well, I actually find that interesting
  364. <Deedlit> since it matters a great deal HOW you do it
  365. <Kthulhu> not all too much,
  366. <Kthulhu> anyone can expand an already existing array notation
  367. <Deedlit> well yes
  368. <Deedlit> if you take the view of "I can just take your number and beat it"
  369. <Kthulhu> no, even without that
  370. <Deedlit> no, I disagree
  371. <Kthulhu> there aren't that many unique ways one can create an array notation
  372. <Kthulhu> there's like
  373. <Kthulhu> 1
  374. <Deedlit> I think you just aren't familar with the stronger notations out there
  375. <Deedlit> take ordinal collapsing functions for instance
  376. <Kthulhu> I am, and I've seen one thing
  377. <Deedlit> there isn't like 1
  378. <Kthulhu> when you have something like that
  379. <Kthulhu> it's really just the concise way of saying something similar
  380. <Kthulhu> take TAN, for example
  381. <Kthulhu> take BEAF
  382. <Kthulhu> they're all, in the end, the same
  383. <Deedlit> I disagree
  384. <Kthulhu> different tastes of the same treat
  385. <Kthulhu> well, I guess it's a matter of how you see things
  386. <Deedlit> I guess so
  387. <Deedlit> I don't see how you could say TAN is like BEAF
  388. <Kthulhu> if you can find points of comparison, where the diagonalisation meets,
  389. <Kthulhu> you found the similarity
  390. <Deedlit> every number is representable as 1+1+1+...+1
  391. <Deedlit> so every number is similar there
  392. <Deedlit> but finding a powerful way to describe a lot of those +1's is a different sort of thing
  393. <Deedlit> same with diagonalization
  394. <Deedlit> TAN is way more powerful than BEAF, for instance
  395. <Kthulhu> ...is it?
  396. <Kthulhu> it might be, for all I know
  397. <Kthulhu> I don't remember where I left off
  398. <Deedlit> it is
  399. <Kthulhu> at which point does it become more powerful?
  400. <Deedlit> even at the first level of TAN, which only goes up to the Bachmann-Howard ordinal, goes beyond where BEAF is well-defined
  401. <Kthulhu> hold up
  402. <Kthulhu> are we talking about the same TAN?
  403. <Deedlit> maybe not
  404. <Deedlit> I was talking about Taranovsky's notation, but you were probably talking about something else
  405. <Kthulhu> http://googology.wikia.com/wiki/User_blog:KthulhuHimself/Terminal_array_notation.
  406. <Kthulhu> lel
  407. <Kthulhu> that's what I was thinking about
  408. <Deedlit> oh okay, lol
  409. <Deedlit> but my point, is it's not just diagonals over diagonals
  410. * koteitan has quit (Ping timeout: 260 seconds)
  411. <Deedlit> if your method is to diagonalize in some repetitive way, then you can be easily beaten by someone who loops over what you are doing
  412. <Kthulhu> that's just the thing
  413. <Kthulhu> for every method you create
  414. <Kthulhu> there can be devised a method to beat it
  415. <Kthulhu> using it
  416. <Deedlit> but that's the point
  417. <Deedlit> numbers are endless
  418. <Kthulhu> that's the whole concept behind norminals
  419. <Kthulhu> here, look
  420. <Kthulhu> you have Func^a_b, right?
  421. <Deedlit> okay
  422. <Kthulhu> we can put that in an array
  423. <Kthulhu> <a,b>
  424. <Kthulhu> right?
  425. <Kthulhu> actually, let's notate it (a,b)
  426. <Kthulhu> just for clarity
  427. <Deedlit> I know where you are going
  428. <Kthulhu> we can then define (0,0,1) as the limit of all (a,b), by letting it access a and b
  429. <Kthulhu> of course
  430. <Kthulhu> it's obvious
  431. <Kthulhu> I should just repair the part about categories and all that
  432. <Deedlit> it sort of seems like a naive extension though
  433. <Deedlit> because with Func^a_b we used more powerful methods then what you would get with a normal array
  434. <Kthulhu> I know
  435. <Kthulhu> come to think of it, everything I've done until now was futile
  436. <Kthulhu> it all kind of is
  437. <Deedlit> if you are looking for an endpoint, then yes, it is futile
  438. <Kthulhu> no
  439. <Kthulhu> that's not it
  440. <Kthulhu> whatever
  441. <Kthulhu> I'll come back sometime later with an answer
  442. <Deedlit> okay
Advertisement
Add Comment
Please, Sign In to add comment
Advertisement