>You know how to look up a number c from column 0 or 1
Do you mean a c we're looking for as an actual c value, or are you referring to the thing you were talking about a while ago where a[t] in (2c,1) is equal to c?
Great, he went to bed I guess. I've been doing some testing and it seems like he has to be referring to something new and completely different to the (2c,1,1) thing or c being the actual c value (despite him saying "you know how" to do it). With the example of c559, if you take a[2] from (0,1) and (1,1) (2 because it's the first valid element in (0,1)), which is 2 and 5 respectively, and add (c-a[2])/2 = 278 and 277 respectively to the e values, you get (278,1) for both. c shows up as a d value in (278,1,15). If you start from (0,1,3) and (1,1,3), you get (275,1) and (274,1). c-1 shows up as an a value in (275,1,15), and c-2 shows up as a d value in (274,1,15). For (0,1,4) and (1,1,4), which give (270,1) and (268,1), c-4 shows up as d in (270,1,15) and c-5 shows up as d in (268,1,15). For (0,1,5) and (1,1,5), which give (263,1) and (260,1), c-7 shows up as a in (263,1,15) and c-9 turns up as d in (260,1,15).
There's definitely a pattern, but it seems like something weird happens with the values that are taken away from c. Obviously the important part here seems to be that it's always at t=15 for this example. Maybe that's the t value the trivial method returns.
Happy birthday. I guess since you're Chris' shitposting account, that means you can fill us in on the trivial method like he was meant to on his birthday.
I'll do some work on this today.
It doesn't seem to work straight away for every example. Here's another two examples.
c203=7*29
If we started from a[2] in (0,1) and (1,1), which gives us (100,1), the closest thing we get to 203 in an a or d value is 212 as an a value. It isn't until we get to (1,1,5) that we find 203 as an a value in (82,1,10).
c2537=43*59
If we started from a[2] in (0,1) and (1,1), which gives us (1267,1), the closest thing we get to 2537 in an a or d value is 2555 as a d value. As a matter of fact with this example, it passes right by 2537. c does not appear in any of the calculated cells without anything added or taken away. 2537 turns up as a d value in (1231,1,31) and as an a value in (1230,1,32), but the e value we get around here using this are 1243, 1238, 1232, 1226, 1219, 1212, etc. 1231 and 1230 don't turn up. Only values close to c turn up as a or d values in these (e,1) cells, but not exactly c. Instead of everything being in the same t value, with these values that are close, they turn up at t=31 when they turn up as d values, but they turn up at t=32 when they turn up as a values.
This is weird, and it warrants way more study.
Here's code for viewing all the n' values we can directly calculate given we know the primes that make up q. Since there's been confusion surrounding whether to use all primes or just primes that end in 01, I put an option in there when you're putting in a and b.
https://files.catbox.moe/8vegrw.zip
e % d is equal to c % d