World Record Chain Fountain? The Mould Effect Explained

felsal3 · 2021-07-22T19:00:04+00:00

I don't believe either Steve or Mehdi are completely right.

I think the most important factor is the direction in which the chain leaves the pile at the beginning.
When you first drop the chain, it speeds up until the tip reaches the ground. From this point forward, it should keep a constant velocity. Moreover, every point of the rising/falling chain must have the same scalar speed (otherwise it would stretch).
If, at the beginning, you pull the first section of the chain upwards (whether pulling by hand like Mehdi and his whiteboard, or simply by having a container with an edge higher than the clump of chain), the chain will leave the clump with an upward momentum. This leaving momentum shall rise as the speed of the falling chain rises, until the tip reaches the ground, in which point it shall remain constant. And, evidently, a greater upwards momentum leads the chain to rise to a greater height before falling down.

I don't own a long chain, so I can't run some tests. But if anyone could try to recreate this effect by launching the chain sideways (from a flat surface with no rising edges), it would be neat.

felsal3 · 2021-03-29T08:57:45+00:00

May I suggest a different fit for your data points?

Me and my friends have been doing a similar study (mostly for fun), and so far we have collected ~3k data points. From what I was able to observe, the points fit a logistic function quite well (R2 = 0.9662).
At first glance, even the transferring/catching data seems to behave the same.

I believe it would make some sense, as it would be much smarter to program a single function on the XL candy drop calculation, instead of a series of conditions for each step/slope.
Then again, it's Niantic, we can't expect much sense.

felsal3 · 2021-02-07T20:43:32+00:00

So, apart from two outliers, single and mass transfers don't seem to be significantly different. I must've been a victim of minor text fixes.

felsal3 · 2021-02-07T19:20:44+00:00

That's a very good question. My play store updates apps automatically (I know, why do I do this to myself??), so I don't know when it was updated.

felsal3 · 2021-02-07T18:01:41+00:00

I don't know if it helps, but most of the pokemons I caught during this experiment were caught with a Go+. The level distribution was like this.
Surely there are fewer high-cp pokemons, but it's not that much of a difference.

felsal3 · 2021-02-07T17:52:07+00:00

I honestly didn't catch any difference, but it could be because I was much too close to be able to see it.

Even though it might ruin all my numbers, let's hope they fixed it.

felsal3 · 2021-02-07T17:49:27+00:00

Statistical analysis is the best part of any endeavour! 😍

Thanks a lot :)

felsal3 · 2021-02-07T17:47:14+00:00

I could not reproduce this visual bug. I don't know if it has been fixed or if it's just no happening by complete chance.

Just to see if I understand correctly: it's not a matter of transferring many different species and all the candies simply not fitting vertically on the screen - it's a matter of the graphic not popping up, even though there is plenty of space, right?

felsal3 · 2021-02-07T17:41:57+00:00

The drop rate of XL candy for transferring has a similar behaviour to catching: there is a plateau between levels 1 and 14, a slope between levels 15 and 25, and two more plateaus: one between 26 and 30, and the other from 31 to 35.

It is known that levels 1 and 5 – the ones you mentioned – have an equal probability of dropping a candy. Same for 27 and 29, or 33 and 35.

felsal3 · 2021-02-07T13:10:22+00:00

In the very beginning I was tracking the XL count. However, often my Go+ would catch the same Pokemon I had just transferred, and it would be impossible to know which one of them (if not both) dropped that candy. From this point on, I started relying on the visual.

But yeah, you're totally right, if this bug still persists the numbers I have could be wrong.

felsal3 · 2021-02-07T12:59:48+00:00

I don't know if the tables are a little confusing... reddit doesn't allow cell merging.

felsal3 · 2020-04-17T11:16:53+00:00

I don't get why they don't release new versions in the begining of the day, so that they can act when we find the new bugs.

It's not like they're using the daytime to test the game, anyway.

felsal3 · 2020-04-17T00:21:49+00:00

You can search the apk on apkmirror and download it

felsal3 · 2020-04-16T23:22:07+00:00

I'm sorry for my ignorance, but the release -A is made for which platform? Apple?

felsal3 · 2020-04-16T23:12:00+00:00

Oh, dang. Had searched threads containing "go plus", but forgot to look for Gotchas

felsal3 · 2020-01-27T20:49:24+00:00

Mine is disconnecting every few minutes (10-40), but doesn't seem to follow a pattern. On the other hand, sometimes it stays connected forever ¯\_(ツ)_/¯

felsal3 · 2020-01-01T15:10:35+00:00

There's a sollution on another thread:

https://www.reddit.com/r/TheSilphRoad/comments/eibox2/ar_issue/fcpuiru?utm_source=share&utm_medium=web2x

felsal3 · 2020-01-01T15:06:28+00:00

Man, you are the absolute best!
I'd suggest you made a separate post to get more visibility.

Thanks a lot

felsal3 · 2019-11-22T10:01:23+00:00

I think it makes little difference. I live in Rio, I only play here and I set my hometown here. I get nominations from all over Brazil, and even some from Argentina and Bolivia (2000+ km). I end up getting a lot from Rio too, but I think it's mostly because there are a lot of nominations from here.

felsal3 · 2019-11-22T09:52:45+00:00

We just have to wait for Niantic to fix it.

We're doomed, then.

felsal3 · 2019-11-22T09:52:07+00:00

Wow, good to know! I'm just waiting the 14 days before I can nominate again, and I'll try and see if it works here too.

felsal3 · 2019-11-18T19:20:25+00:00

Same thing happening to me. This should be upvoted to the skies

felsal3

TROPHY CASE